Air traffic operational procedures

Identifies substantive air-traffic operational procedures. Topic phrases are retained for discovery; enforcement requires local runway, sector, waypoint, handoff, clearance, or airspace-procedure detail, and high confidence also requires an operational value such as a runway, flight level, distance, or radio frequency.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium confidence requires local procedure content rather than a generic aviation-control mention. High confidence adds an operational value, reducing matches on public standards and introductory training.
Detection quality: Not detected
Jurisdictions: global
Regulations: GDPR
Data categories: security
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:air\s+traffic\s+operational\s+procedure|air\s+traffic\s+control\s+procedure|separation\s+minima|flight\s+clearance|approach\s+procedure|radar\s+vectoring|flight\s+information\s+region|terminal\s+control\s+procedure)\b

Corroborative evidence keywords

air traffic operational procedures, air, traffic, operational, procedures, critical, infrastructure, systems

Proximity: 300 characters

Should match

air traffic operational procedure — Low-tier probe - topic without local procedure detail
Air traffic operational procedure for the Brisbane terminal sector and waypoint GOMOL handoff — Medium-tier probe - local sector and waypoint detail without an operational value
Separation minima for Brisbane terminal sector: 5 NM near runway 19L; controller frequency 118.700 MHz — High-tier probe - local procedure detail with distance, runway, and frequency values

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
air traffic procedure — Generic word pair from old broad template should not match
The ICAO overview explains the purpose of air traffic control. — Public overview without a protected operational procedure
Training example: separation minima for sector Delta is 5 NM near runway 19L — Explicit training content must not enforce

Known false positives

Public aviation standards, airport information, and training material discuss separation, approaches, runways, and clearances without exposing a local operating procedure. Mitigation: Keep topic-only matches discovery-only and require sector, waypoint, handoff, runway, or comparable local procedure detail for enforcement.
Controller training scenarios can include realistic sectors, runways, distances, flight levels, and frequencies. Mitigation: Reject explicit template, demo, tutorial, sample-data, and training-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