Privileged account inventories

Name: Privileged account inventories
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies privileged account inventories 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: category-aware structural regex with anchor and context constraints replaces phrase-only detection.
Detection quality: Mixed
Jurisdictions: au
Regulations: Criminal Code Act 1995 (Cth)
Frameworks: CIS Controls, ISO 27001
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(?:privileged\s+account|service\s+account|admin\s+account|root\s+access|domain\s+admin|elevated\s+privileges|privileged\s+access\s+management|break\s+glass\s+account|emergency\s+access|credential\s+vault|account\s+inventory)\b

Corroborative evidence keywords

privileged account inventories, privileged, account, inventories, operations, resilience

Proximity: 300 characters

Should match

privileged account — Primary topic phrase match
service account — Case-insensitive topic phrase match
admin account — Alternative topic phrase match
root access — 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
backup outage — 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.