Sensitive network topology diagrams

Identifies sensitive network topology diagrams patterns in security and access control contexts. Detects potential exposure of sensitive security information in international 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: global
Regulations: GDPR
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(?:network\s+topology|network\s+diagram|network\s+architecture|ip\s+addressing|routing\s+table|network\s+segment|infrastructure\s+diagram|network\s+map|data\s+center\s+layout)\b

Corroborative evidence keywords

sensitive network topology diagrams, sensitive, network, topology, diagrams, security, operations, threat, data, address, age, birthday, citizenship, city, date of birth, DOB, email, ethnicity, fax, first name (+47 more)

Proximity: 300 characters

Should match

network topology — Primary topic phrase match
network diagram — Case-insensitive topic phrase match
network architecture — Alternative topic phrase match
ip addressing — 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
network diagram dmz — 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.