OAuth client secrets
Identifies oauth client secrets patterns in security and access control contexts. Detects potential exposure of sensitive security information in international systems.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Not detected
- Jurisdictions
- global
- Regulations
- GDPR
- Data categories
- credentials, security
- Scope
- wide
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:client\s+secret|client\s+id|authorization\s+code|access\s+token|refresh\s+token|bearer\s+token|openid\s+connect|grant\s+type|redirect\s+uri|token\s+endpoint)\bCorroborative evidence keywords
oauth client secrets, oauth, client, secrets, credentials, keys, OFFICIAL, OFFICIAL:Sensitive, PROTECTED, SECRET, TOP SECRET, CABINET-IN-CONFIDENCE, NOFORN, REL TO, ORCON, National Cabinet, AUSTEO, AGAO, Sensitive: Legal, Sensitive: Personal Privacy (+58 more)
Proximity: 300 characters
Should match
client secret— Primary topic phrase matchclient id— Case-insensitive topic phrase matchauthorization code— Alternative topic phrase matchaccess token— Additional topic phrase match
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexsecret mfa— Generic word pair from old broad template should not match
Known false positives
- Authentication-related terminology in software documentation, security training materials, or system architecture descriptions without actual credentials. Mitigation: Require proximity to credential-specific patterns (API keys, connection strings, tokens) rather than general security terminology.
- Code snippets and configuration examples containing credential-related keywords or placeholder values in developer documentation. Mitigation: Check for common placeholder patterns (example.com, localhost, 0000) and documentation file types to reduce false positives from technical writing.