Patch exception records

Name: Patch exception records
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies patch exception records patterns in security and access control contexts. Detects potential exposure of sensitive security information in Australian systems.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: structural regex with domain-specific anchors and constrained context replaces phrase-only marker.
Detection quality: Mixed
Jurisdictions: au
Regulations: NDB Scheme (Cth), SOCI Act 2018 (Cth), TIA Act 1979 (Cth)
Frameworks: CIS Controls, DISP, ISO 27001, NIST CSF, PCI-DSS, SOC 2
Data categories: credentials, security
Scope: wide
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:patch\s+exception\s+records|patch\s+exception|risk\s+acceptance|patch\s+deferral|compensating\s+control|vulnerability\s+exception|risk\s+register|exception\s+approval|change\s+management|patch\s+compliance)\b

Corroborative evidence keywords

patch exception records, patch, exception, records, security, operations, threat, data

Proximity: 300 characters

Should match

patch exception records — Primary topic phrase match
patch exception — Case-insensitive topic phrase match
risk acceptance — Alternative topic phrase match
patch deferral — 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
patch exception cve — Generic word pair from old broad template should not match

Known false positives

Authentication-related terminology in software documentation, security training materials, or system architecture descriptions without actual credentials. Mitigation: Require proximity to credential-specific patterns (API keys, connection strings, tokens) rather than general security terminology.
Code snippets and configuration examples containing credential-related keywords or placeholder values in developer documentation. Mitigation: Check for common placeholder patterns (example.com, localhost, 0000) and documentation file types to reduce false positives from technical writing.