Target package intelligence

Identifies documents containing references to target package intelligence 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

category-aware structural regex with anchor and context constraints replaces phrase-only detection.

Detection quality

Mixed

Jurisdictions

global

Regulations

AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth)

Frameworks

ISO 27001

Data categories

government-id, pii

Scope

wide

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:target\s+package\s+intelligence|target\s+acquisition|intelligence\s+package|target\s+analysis|targeting\s+data|intelligence\s+assessment|threat\s+intelligence|target\s+identification|target\s+dossier|defence\s+intelligence|signals\s+intelligence|intelligence\s+product)\b

Corroborative evidence keywords

target package intelligence, target, package, intelligence, defense, government, agency, department, ministry, public sector, civil service, welfare, social services, public administration, statutory authority, regulatory body, public servant, government program, public benefit, constituency

Proximity: 300 characters

Should match

• target package intelligence — Primary topic phrase match
• target acquisition — Case-insensitive topic phrase match
• intelligence package — Alternative topic phrase match
• target analysis — Additional topic phrase match

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
• classified contingency — Generic word pair from old broad template should not match

Known false positives

• Common words and phrases related to target package intelligence 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.

References

• https://www.legislation.gov.au/C2004A00280/latest/text
• https://www.protectivesecurity.gov.au/