Refinery process control setpoints

Identifies documents containing references to refinery process control setpoints 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(?:process\s+control|control\s+loop|PID\s+controller|crude\s+unit|reactor\s+temperature|process\s+variable|control\s+valve|operating\s+parameter|safety\s+limit)\b

Corroborative evidence keywords

refinery process control setpoints, refinery, process, control, setpoints, critical, infrastructure, systems

Proximity: 300 characters

Should match

process control — Primary topic phrase match
control loop — Case-insensitive topic phrase match
PID controller — Alternative topic phrase match
crude unit — 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
refinery setpoint — Generic word pair from old broad template should not match

Known false positives

Common words and phrases related to refinery process control setpoints 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