Procurement fraud investigation files
Identifies documents containing references to procurement fraud investigation files in international contexts. These are investigative and procurement-sensitive records that may contain personal allegations; the category is not blanket personally identifiable information.
- 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 false positive
- Jurisdictions
- global
- Regulations
- GDPR, Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), Telecommunications (Interception and Access) Act 1979 (Cth)
- Frameworks
- ISO 27001
- Data categories
- business, audit
- Scope
- wide
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:procurement\s+fraud\s+investigation\s+files|procurement\s+fraud|fraud\s+investigation|supplier\s+fraud|tender\s+irregularity|bid\s+rigging|forensic\s+audit|conflict\s+of\s+interest|due\s+diligence)\b
Corroborative evidence keywords
procurement fraud investigation files, procurement, fraud, investigation, files, supplier, management
Proximity: 300 characters
Should match
procurement fraud investigation files— Primary topic phrase matchprocurement fraud— Case-insensitive topic phrase matchfraud investigation— Alternative topic phrase matchsupplier fraud— Additional topic phrase matchprocurement fraud investigation files Name: Avery Teston Date of birth: 04/02/1991 Reference number: RX22914471 Notes: procurement fraud investigation files recorded against the subject; handling restricted.— Populated justice record 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 regexprocurement inventory— Generic word pair from old broad template should not matchPolicy guidance: this procedure explains how records about procurement fraud investigation files 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 procurement fraud investigation files 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.