Suspicious X509Enrollment usage in Windows PowerShell scripts

Alerts on PowerShell script blocks containing X509Enrollment.CBinaryConverter and a specific enrollment GUID.

FreeReviewedSigma · Medium · v2
Product
windows
Category
ps_script
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-12-23
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags PowerShell script content that references X509Enrollment components, including the CBinaryConverter class and a specific X509Enrollment identifier. Attackers may use these .NET objects to interact with certificate enrollment or manipulate certificate-related data as part of broader abuse. Detection relies on Script Block Logging telemetry capturing the referenced class name and GUID within the executed PowerShell script text.

Related detections9 linkedT1553.004 — drag to rearrange
Suspicious Certutil Download and Certificate Installation via Living-off-the-Land
Suspicious Firefox Enterprise Root Certificate Trust Enabled
Malicious Root Certificate Installed via certutil addstore for AiTM Interception
Malicious Root Certificate Installation via certutil
Suspicious Root Certificate Installation via certutil (via process_creation)
Windows AD CS Denied Certificate Enrollment Requests (Event ID 53)
Windows: Root Certificate Added Using certutil.exe -addstore
Windows: Root Certificate Installation via CertMgr.EXE (/add root)
Linux Package Installation via apt/yum/rpm/dpkg with Networking Tools Keywords
Suspicious X509Enrollment usage in Windows PowerShell scripts
Pivot detection · T1553.004 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.