Suspicious Weakening of Certificate Binding Enforcement via Registry (via registry_set)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-16
Updated
2026-10-16

ATT&CK techniques

Persistence → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects changes to the StrongCertificateBindingEnforcement or SCHANNEL CertificateMappingMethods registry values that govern how certificates map to Active Directory accounts. Downgrading these controls re-enables weak certificate mapping abused in ADCS impersonation attacks. Relaxed binding lets a forged or requested certificate authenticate as a privileged account.

Related detections9 linkedT1556 — drag to rearrange
Suspicious XZ Utils Backdoor Kill-Switch Environment String via process_creation
Suspicious AWS SAML Identity Provider Creation
Suspicious Okta Sign-On Policy Lifecycle Modification
Possible Shadow Credentials Abuse via msDS-KeyCredentialLink Modification
Windows Registry Tampering: DsrmAdminLogonBehavior Value Changes (DSRM)
Azure AD Audit: Trusted Root CA Added for Passwordless Certificate Authentication
Azure AD Audit Logs: Certificate-based authentication enabled via AuthenticationMethodsPolicy update
AWS CloudTrail: AWS Identity Center Identity Provider Configuration Changes
GitHub Audit: High-Risk Security Controls Disabled
Suspicious Weakening of Certificate Binding Enforcement via Registry (via registry_set)
Pivot detection · T1556 · 9 related

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