Insider threat investigation files

Name: Insider threat investigation files
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies insider threat investigation files 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. Added context gating and exclusion rules improve precision and reduce incidental matches.
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(?:insider\s+threat|employee\s+investigation|unauthorized\s+access|data\s+exfiltration|behavioral\s+analysis|user\s+activity\s+monitoring|privilege\s+abuse|HR\s+investigation|disciplinary\s+action|termination\s+review|security\s+clearance)\b

Corroborative evidence keywords

insider threat investigation files, insider, threat, investigation, files, security, operations, data

Proximity: 300 characters

Should match

insider threat — Primary topic phrase match
employee investigation — Case-insensitive topic phrase match
unauthorized access — Alternative topic phrase match
data exfiltration — 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
insider threat case — 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.

References

https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism
https://www.legislation.gov.au/C2018A00029/latest/text
https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/preventing-preparing-for-and-responding-to-data-breaches/data-breach-preparation-and-response
https://handbook.apra.gov.au/standard/cps-234