Substation protection relay settings
Identifies documents containing references to substation protection relay settings in international contexts. This information type is classified as personally identifiable information under applicable data protection regulations.
- 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
- pii
- Scope
- wide
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:protection\s+relay|distance\s+relay|pickup\s+setting|trip\s+setting|fault\s+current|relay\s+coordination|impedance\s+zone|circuit\s+breaker|differential\s+protection|IED\s+settings)\b
Corroborative evidence keywords
substation protection relay settings, substation, protection, relay, settings, critical, infrastructure, systems
Proximity: 300 characters
Should match
protection relay— Primary topic phrase matchdistance relay— Case-insensitive topic phrase matchpickup setting— Alternative topic phrase matchtrip setting— Additional topic phrase match
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexprotection relay substation— Generic word pair from old broad template should not match
Known false positives
- Common words and phrases related to substation protection relay settings appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
- In English (as the primary international business language), similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
- High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.
References
- https://www.legislation.gov.au/C2018A00029/latest/text
- https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism