Key recovery material
Identifies key recovery material 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
- structural regex with domain-specific anchors and constrained context replaces phrase-only marker. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Mixed
- 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(?:key\s+recovery|recovery\s+key|escrow\s+key|break-glass)\b
Corroborative evidence keywords
key recovery, recovery key, escrow key, break-glass, hsm, kms
Proximity: 240 characters
Should match
Break-glass recovery key escrow procedure for HSM cluster— Recovery material phrase with security contextKey recovery request approved for KMS tenant— Key recovery anchor phrase
Should not match
General key performance indicators for project recovery timeline— Unrelated use of key/recovery wordsGeneric policy prose without key escrow context— No structural security anchorstemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
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.
References
- https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism
- https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/essential-eight
- https://www.oaic.gov.au/privacy/australian-privacy-principles-guidelines/chapter-11-app-11-security-of-personal-information