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.
- Overview
- Workflow
- Linked
- Discussion
- History
A security event, in assessment
01, done02, done03, done04, current05, not reached06, not reached07, not reached08, not reached09, not reached10, not reached
Next step, waiting onImpact
Linked toCAP | GOV | Evidence Hub
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
Works with
What it does
Four things, done on the record.
Unescorted person airside at stand 7, CYUL
Threat credibilityCredibleDepthFull investigationTriage
Derived security risk
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.
- 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
On the recordInitial and residual security risk, with the owner and the approver.
InitialSerious by LikelyResidualBefore closure
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
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
On the graph
What it links to.
CAP | Linked recordAction PlansRemediation through linked corrective actions.
- From
- CAP
- To
- SeMS
- From
- GOV
- To
- SeMS
- From
- Evidence Hub
- To
- SeMS
Questions buyers ask
Short answers.
Yes. A security event can be reported in the eAviora app, under Security, as well as on the web.
Your security manager sets the list, the window and the authority. By default, acts of unlawful interference start a deadline.
Only with an authorised risk acceptance on the record. A residual at or below tolerance needs none.
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 fundamentalsSee Security Events on your own records.
A walkthrough with the people who build eAviora.