Card verification values

Detects references to card verification values in financial and compliance documents. Commonly found in Australian regulatory filings, transaction records, and audit documentation.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: identifier/document-structure anchored regex with constrained context replaces phrase-only detection.
Detection quality: Mixed
Jurisdictions: au
Regulations: AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), SOCI Act 2018 (Cth)
Frameworks: ISO 27001, ISO 27701, PCI-DSS, SOC 2
Data categories: financial
Scope: wide
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:card\s+verification\s+value|card\s+security\s+code|verification\s+code|card\s+validation|PCI\s+DSS|cardholder\s+data|payment\s+card|three[\s-]+digit\s+code)\b

Corroborative evidence keywords

card verification values, card, verification, values, financial, accounts, payments, fiscal, monetary, accounting, treasury, audit, revenue, expenditure, budget, ledger, accounts payable, accounts receivable, balance sheet, profit and loss (+1 more)

Proximity: 300 characters

Should match

card verification value — Primary topic phrase match
card security code — Case-insensitive topic phrase match
verification code — Alternative topic phrase match
card validation — 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
payroll reimbursement — Generic word pair from old broad template should not match

Known false positives

Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
In Australian English, standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.

References

https://www.pcisecuritystandards.org/faq/articles/Frequently_Asked_Question/Can-card-verification-codes-values-be-stored-for-card-on-file-or-recurring-transactions
https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0_1.pdf