Business continuity plans

Identifies business continuity plans 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

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

Risk rating

8

Platform compatibility

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

Pattern

(?i)\b(?:business\s+continuity\s+(?:plan|management|program)|bcp\s+(?:document|plan|procedures?)|continuity\s+of\s+(?:operations?|business)\s+plan)\b

Corroborative evidence keywords

business continuity plans, business, continuity, plans, operations, resilience, student, transcript, grade, GPA, enrollment, FERPA, FAFSA, financial aid, tuition, degree

Proximity: 300 characters

Should match

• Business continuity plans — Exact phrase marker match
• business continuity plans — Case-insensitive phrase match
• Business continuity plans — 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.homeaffairs.gov.au/about-us/our-portfolios/emergency-management
• https://www.disasterassist.gov.au/
• https://www.oaic.gov.au/privacy/australian-privacy-principles-guidelines/chapter-11-app-11-security-of-personal-information