Skip to content
FRSign inBook a walkthrough
SeMSSecurity EventsSecurity Management

Aviation security event management, from report to closure.

In 50 words

Security event management records every breach, threat and suspicious act, then assesses, investigates and fixes it. In eAviora a security event is triaged before it is assessed, its risk level derives from impact and likelihood, and it closes only once the residual risk is assessed and every authority deadline is filed or waived.

Case file | SEMS-EVT-2026-0017Stage 4 of 10, Assessment
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
A security event, in assessment
01Reported, done02Triage, done03Classification, done04Assessment, current05Investigation, not reached06Remediation, not reached07Governance review, not reached08Action execution, not reached09Residual risk, not reached10Closure, not reached
Next step, waiting onImpact
Linked toCAP | GOV | Evidence Hub
Sample data | Northwind Air, a fictional airline
At a glance

The module, on one sheet.

Module sheet | SeMS
SuiteSecurity Management | Security Operations
ICAO Annex 17Event types aligned to Annex 17, from unauthorised access to suspected sabotage
RecordsSEMS-EVT security events
Stages
01Reported02Triage03Classification04Assessment05Investigation06Remediation07Governance review08Action execution09Residual risk10Closure
On the phoneReport a security event in the eAviora app
ReportUnder Security
What it does

Four things, done on the record.

Unescorted person airside at stand 7, CYUL
Threat credibilityCredibleDepthFull investigationTriageset before assessment
Exposure: current, the gate stayed unlocked until 06:10Z | recorded 11 Nov by J. Bergeron | Sample data | Northwind Air, a fictional airline
Derived security risk
Serious by Likely | Tolerable, action required | nobody types it
01Triage firstThreat credibility, current exposure and investigation depth are set before the event is assessed.
02A derived risk levelImpact and likelihood set the security risk level, from acceptable to intolerable.
03Authority deadlinesEach category your security manager lists starts a reporting deadline, filed or waived before closure.
04Residual risk before closureResidual impact and likelihood are scored before closure, and a residual above tolerance needs an authorised acceptance.
In the product

A security event, in assessment.

Case file | SEMS-EVT-2026-0017Stage 4 of 10, Assessment
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
The next stepThe next step and what it waits on.
  • Impact and likelihood are set, not yet
  • The risk assessment is written, not yet
Stage 4 of 10 | Assessment
On the recordInitial and residual security risk, with the owner and the approver.
InitialSerious by LikelyResidualBefore closure
Owner J. Bergeron | approver C. Wright
On the recordThe corrective actions and records linked to it.
ACT-2026-0244Fit a self-closing lock on the stand 7 gateremediated by | assigned
EVD-2026-0310Access control log, 11 Novevidence | submitted
AuthorityUnauthorised access, report to the authoritydue 14 Nov 14:00Z | 72 hours | open
Sample data | Northwind Air, a fictional airline
The rule it holds

Nobody types the security risk level.

  • It derives from impact and likelihood, and the event cannot move on while the stored level disagrees with them.Security EventsHolds
ImpactSeriousLikelihoodLikelyDerivedTolerable, action required
Illustrative | sample data
Questions buyers ask

Short answers.

Yes. A security event can be reported in the eAviora app, under Security, as well as on the web.

Reading | SMS fundamentalsThe Closure Gate, Not the Checkbox: Defensible-by-Construction SafetyReading | SMS fundamentalsAviation Risk Matrix Explained: Severity, Probability, TolerabilityReading | SMS fundamentalsThe Four Components of an Aviation SMS
All of SMS fundamentals

See Security Events on your own records.

A walkthrough with the people who build eAviora.