Refinery process control setpoints

Identifies substantive refinery process-control setpoint and operating-envelope records. Topic phrases are retained for discovery; enforcement requires an actual process value, and high confidence also requires a control-loop tag or named refinery process asset.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium confidence requires a populated process value rather than general control-engineering prose. High confidence adds a refinery asset or loop tag, reducing matches on standards and textbooks.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: GDPR
Data categories: security
Scope: wide
Risk rating: 10
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:refinery\s+process\s+control|refinery\s+control\s+loop|crude\s+(?:distillation\s+)?unit|distillation\s+unit|reactor\s+temperature|refinery\s+operating\s+parameter|refinery\s+safety\s+limit)\b

Corroborative evidence keywords

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

Proximity: 300 characters

Should match

refinery process control setpoints — Low-tier probe - topic without a populated process value
Crude distillation unit operating parameter: reactor temperature SP=365 C and pressure 18.5 bar — Medium-tier probe - populated refinery process values without a control tag
Refinery control loop TIC-204 on the crude unit: SP=365 C, high alarm 380 C, valve output 64% — High-tier probe - process values with a loop tag and named process asset

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
The chemical-engineering textbook introduces PID process control. — Generic educational control theory, not refinery setpoint data
Worked example: refinery control loop TIC-204 SP=365 C and pressure 18.5 bar — Explicit worked example must not enforce

Known false positives

Process-control standards, textbooks, and vendor manuals discuss loops, PID control, temperatures, and safety limits without exposing refinery operating data. Mitigation: Require a refinery/crude/distillation/reactor topic and a populated process value before enforcement.
Worked examples can contain realistic loop tags and engineering values. Mitigation: Reject explicit template, demo, tutorial, sample-data, and worked-example framing from enforcing tiers.

References

https://www.legislation.gov.au/C2018A00029/latest/text
https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism