Weapons system vulnerability data
Identifies documents containing references to weapons system vulnerability data in Australian contexts. This information type is classified as personally identifiable information under the Privacy Act 1988.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- structural regex with domain-specific anchors and constrained context replaces phrase-only marker.
- Jurisdictions
- global
- Regulations
- Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth)
- Frameworks
- ISO 27001
- Data categories
- government-id, pii
- Scope
- wide
- Risk rating
- 10
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:weapons\s+system\s+vulnerability|vulnerability\s+assessment|exploit\s+analysis|armament\s+weakness|defense\s+vulnerability|weapons\s+system|threat\s+assessment|classified\s+vulnerability|penetration\s+testing|defense\s+intelligence|national\s+security|system\s+weakness)\b
Corroborative evidence keywords
weapons system vulnerability data, weapons, system, vulnerability, data, defense, intelligence, government, agency, department, ministry, public sector, civil service, welfare, social services, public administration, statutory authority, regulatory body, public servant, government program (+2 more)
Proximity: 300 characters
Should match
weapons system vulnerability— Primary topic phrase matchvulnerability assessment— Case-insensitive topic phrase matchexploit analysis— Alternative topic phrase matcharmament weakness— Additional topic phrase matchWeapons system vulnerability Hostname: app-prd-01.corp.local username: svc_deploy Source 10.20.30.40 tcp/443— Populated technical artefact reaching the 75/85 structure gate
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexarmament exploit— Generic word pair from old broad template should not matchWeapons system vulnerability: Hostname: username:— Empty form: the heading and field labels without values must not corroborate themselves (discovery only)Policy guidance: this procedure explains how records about weapons system vulnerability are handled, who may access them and how long they are kept. It contains no records about any person or system.— Policy guidance naming the topic without any record (discovery only)
Known false positives
- Common words and phrases related to weapons system vulnerability data 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 Australian English, 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.