Penetration testing reports

Identifies penetration testing reports 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

Not detected

Jurisdictions

au

Regulations

Criminal Code Act 1995 (Cth), SOCI Act 2018 (Cth)

Frameworks

CIS Controls, ISO 27001

Data categories

credentials, security

Scope

wide

Risk rating

10

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:penetration\s+test(?:ing)?\s+(?:report|findings?|assessment)|pen\s*test\s+(?:report|results)|offensive\s+security\s+(?:assessment|report)|external\s+(?:penetration|security)\s+test)\b

Corroborative evidence keywords

penetration testing reports, penetration, testing, reports, software, engineering, architecture

Proximity: 300 characters

Should match

• Penetration testing reports — Exact phrase marker match
• penetration testing reports — Case-insensitive phrase match
• Penetration testing reports — Normalized whitespace phrase
• structured artifact containing anchor terms and contextual fields — Structural anchor sample

Should not match

• unrelated generic text — No relevant phrase context
• placeholder value 12345 — Random text should not match phrase marker
• generic prose without structural artifact anchors — Should not match plain mentions

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.

References

• https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism
• https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/essential-eight
• https://www.oaic.gov.au/privacy/australian-privacy-principles-guidelines/chapter-11-app-11-security-of-personal-information