EN 18286 vs ISG
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 0 of 0 topics. Each verdict names what it rests on; read the wording before relying on it.
- EN 18286 Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- ISG Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | EN 18286 | ISG | Verdict |
|---|
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- EN 18286 EN 18286:2026; Commission Implementing Decision (EU) 2026/2274 of 12 October 2026
Status
Reviewed against the official texts.
Included
- ISG Informationssicherheitsgesetz (ISG) of 18 December 2020, SR 128, as amended on 29 September 2023 (reporting obligation); Information Security Ordinance and Cyber Security Ordinance
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
EN 18286: Not in the acts covered
ISG: Federal Office for Cyber Security (BACS)
Incident notification
EN 18286: Not in the acts covered
ISG: Within 24 hours of discovering the cyberattack
Intermediate report
EN 18286: Not in the acts covered
ISG: Missing information within the 14 days the Federal Office for Cyber Security grants
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.