Vendor master records
Identifies documents containing references to vendor master records in Australian contexts. This information type is classified as personally identifiable information under applicable data protection regulations.
- 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
- 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), GDPR
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- business
- Scope
- wide
- Risk rating
- 5
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:vendor\s+master|vendor\s+record|supplier\s+master|vendor\s+management|vendor\s+code|vendor\s+registration|accounts\s+payable|payment\s+terms|vendor\s+bank\s+details|approved\s+vendor\s+list)\b
Corroborative evidence keywords
vendor master records, vendor, master, records, procurement, supplier, management
Proximity: 300 characters
Should match
vendor master— Primary topic phrase matchvendor record— Case-insensitive topic phrase matchsupplier master— Alternative topic phrase matchvendor management— Additional topic phrase matchVendor master Payee: Riverbend Supplies Pty Ltd BSB: 064-000 Account number: 12345678 Payment reference: INV-20431— Populated payee/account 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 matchVendor master: Payee: Account name: Account number:— Empty form: the heading and field labels without values must not corroborate themselves (discovery only)Policy guidance: this procedure explains how records about vendor master 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 vendor master records 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.