Threats classified againstICAO Annex 17.
Security events share the same operational picture as safety. Acts of unlawful interference are classified against ICAO Annex 17 on intake. A security event that also creates a safety hazard is one record, visible to both teams under their own access scope, sensitive fields stay inside the security perimeter.
Security and safety in one operational picture.
A threat that creates a safety hazard is one record, visible to both teams under their own access scope. Security-sensitive fields stay inside the security perimeter even when the underlying event is shared.
The capabilities, on one record.
Every security event is classified against the ICAO Annex 17 taxonomy on intake, a closed list, audit-ready.
Severity is set by the security officer with an AI-assisted threat-vulnerability-impact view, proposed, never auto-applied.
A security event that also creates a safety hazard is one linked record, sensitive fields scoped to the security perimeter.
Protective and corrective actions close through the same effectiveness gate as the rest of the operation.
Real records, one reference each.
Every record carries a stable reference and a source on every field. Nothing is silently overwritten, and the trail is the record.
Classification aligned to ICAO Annex 17
Severity is officer-set and AI-assisted, never auto-applied
Security and safety share one operational picture
Sensitive fields stay behind the security perimeter
It links to the rest of the graph.
Security rides the same spine.
Security events carry sensitivity tiers and restricted access, and still link to the barriers and actions of the one operation. Confidential never means disconnected.
The operation is guarded. The next chapter is the paper that proves all of it: documents under control.