GitHub Audit: High-Risk Security Controls Disabled

Alerts when GitHub audit logs show advanced security, OAuth restrictions, or 2FA requirements disabled for orgs or repos.

FreeReviewedSigma · High · v5
Product
github
Service
audit
Author
Muhammad Faisal (@faisalusuf) (SigmaHQ), DRL 1.1
Published
2023-01-29
Updated
2026-07-31

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 flags GitHub audit events where an admin disables high-risk security features at the organization or repository level. Disabling controls like advanced security settings or OAuth/2FA restrictions can reduce account and credential protections and increase attacker persistence opportunities. It relies on GitHub audit log telemetry that records specific security-disabling actions in the matched event fields.

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
Windows Security Event 5136: msDS-KeyCredentialLink Shadow Credential Added to AD Object
GitHub Audit: High-Risk Security Controls Disabled
Pivot detection · T1556 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.