Competitive intelligence reports

Identifies documents containing references to competitive intelligence reports 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), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth)

Frameworks

ISO 27001, ISO 27701

Data categories

pii

Scope

wide

Risk rating

7

Platform compatibility

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

Pattern

(?i)\b(?:competitor\s+(?:analysis|comparison)|competitive\s+(?:analysis|positioning|landscape))\b

Corroborative evidence keywords

competitive intelligence reports, competitive, intelligence, reports, mergers, acquisitions, strategy

Proximity: 300 characters

Should match

• Competitive intelligence reports — Exact phrase marker match
• competitive intelligence reports — Case-insensitive phrase match
• Competitive intelligence reports — Normalized whitespace phrase
• structured artifact containing anchor terms and contextual fields — Structural anchor sample

Should not match

• unrelated generic text — No relevant phrase context
• placeholder value 12345 — Random text should not match phrase marker
• generic prose without structural artifact anchors — Should not match plain mentions

Known false positives

• Common words and phrases related to competitive intelligence reports 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.accc.gov.au/business/competition-and-exemptions
• https://www.accc.gov.au/business/competition-and-exemptions/cartels