Secrets vault exports

Identifies references to secrets-vault exports and backups. Product or operation phrases are discovery-only; structured export-record fields support medium confidence and a populated secret entry plus export-manifest metadata supports high.

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: Topic verified
Jurisdictions: global
Regulations: GDPR, AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth)
Data categories: pii
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:secrets\s+vault|vault\s+export|hashicorp\s+vault|azure\s+key\s+vault|aws\s+secrets\s+manager|secret\s+engine|vault\s+token|sealed\s+secrets|secret\s+rotation|vault\s+backup|credential\s+store)\b

Corroborative evidence keywords

secrets vault exports, OFFICIAL, OFFICIAL:Sensitive, PROTECTED, SECRET, TOP SECRET, CABINET-IN-CONFIDENCE, NOFORN, REL TO, ORCON, National Cabinet, AUSTEO, [object Object], Sensitive: Legal, Sensitive: Personal Privacy, Sensitive: Legislative Secrecy, X-Protective-Marking, data record, database record, record set (+21 more)

Proximity: 240 characters

Should match

Azure Key Vault — Low-tier probe - vault product phrase without export record structure
vault export {"path":"secret/prod/payments","version":4,"created_time":"2026-07-19T01:00:00Z"} — Medium-tier probe - export phrase with structured record fields but no secret value
HashiCorp Vault export manifest backup_id=vlt-20260719 exported_at=2026-07-19T01:00:00Z {"path":"secret/prod/payments","client_secret":"x7K2mN9pQ4sT8vW3yZ6aB1cD"} — High-tier probe - manifest metadata and populated secret entry
AWS Secrets Manager backup {"secret_name":"payments/api","version":"AWSCURRENT"} — Medium-tier probe - provider-specific backup record structure

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
secret mfa — Generic word pair from old broad template should not match
vault export {"path":} — Malformed export record with no field value
Vault export manifest backup_id=demo {"path":"secret/prod","client_secret":"PLACEHOLDER"} — Placeholder secret entry must not enforce
Documentation example: HashiCorp Vault export manifest backup_id=vlt-1 exported_at=2026-07-19 {"path":"secret/prod","token":"x7K2mN9pQ4sT8vW3yZ6"} — Documentation quoting a populated export must not enforce
Azure Key Vault certificate inventory lists public certificate names only — Sibling public-certificate inventory is not a secrets export record

Known false positives

Common words and phrases related to secrets vault exports appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
In English (as the primary international business language), similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.