GitHub Repo

Certify Abuse

Date: 2023-06-30 ID: a6e1c749-e7b0-401e-9ce7-de9f38e7113f Author: Steven Dick Environment: attack_range Directory: certify_abuse

Description

Detection of common behaviors when certify/certipy tools are used to exploit AD CS for the ESC1 vulnerablity. Manual testing using standard compiled versions of both tools

MITRE ATT&CK Techniques

ID Technique Tactic
T1649 Steal or Forge Authentication Certificates Credential Access

Environment Details

Field Value
Environment attack_range
Directory certify_abuse
Test Date 2023-06-30

Datasets

The following datasets were collected during this attack simulation:

Certify_esc1_abuse_sysmon

  • Path: /datasets/attack_techniques/T1649/certify_abuse/certify_esc1_abuse_sysmon.log
  • Sourcetype: XmlWinEventLog
  • Source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational

The following detections in our security content repository use this attack data for testing:

Detection Name Type Source MITRE ATT&CK Analytic Story
Windows Steal Authentication Certificates - ESC1 Authentication TTP Endpoint T1649, T1550 Windows Certificate Services, Compromised Windows Host
Windows Steal Authentication Certificates - ESC1 Abuse TTP Endpoint T1649 Windows Certificate Services
Detect Certify With PowerShell Script Block Logging TTP Endpoint T1059.001, T1649 Windows Certificate Services, Malicious PowerShell
Detect Certify Command Line Arguments TTP Endpoint T1649, T1105 Compromised Windows Host, Windows Certificate Services, Ingress Tool Transfer
Windows Suspect Process With Authentication Traffic Anomaly Endpoint T1087.002, T1204.002 Active Directory Discovery
Detect Certipy File Modifications TTP Endpoint T1649, T1560 Windows Certificate Services, Data Exfiltration, Ingress Tool Transfer

Usage Instructions

Replay with Splunk Attack Data

Replay attack data with replay.py from Splunk Attack Data.

1python replay.py --dataset /datasets/attack_techniques/T1649/certify_abuse/certify_esc1_abuse_sysmon.log --index attack_data

Manual Import

  1. Download the dataset files from the paths listed above
  2. Configure your Splunk instance with the appropriate sourcetypes
  3. Import the logs using the Splunk Add Data wizard

Related Content

Find more detections and analytics for this attack technique in our security content repository.

Source: GitHub | Version: 1.0