NIS2 Directive
Directive (EU) 2022/2555 on measures for a high common level of cybersecurity across the Union. For essential and important entities, NIS2 requires an early warning within 24 hours and an incident notification within 72 hours of becoming aware of a significant incident. Where a NIS2-covered entity operates an Annex III point 2 AI system, Article 73(9) of the AI Act narrows the Article 73 obligation to fundamental-rights incidents.
Defined in 2 GAGE programs, which carry 2 distinct definitions of it. The wording above is taught in EU AI Act Implementation Expert.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
Directive (EU) 2022/2555 on measures for a high common level of cybersecurity across the Union. For essential and important entities, NIS2 requires an early warning within 24 hours and an incident notification within 72 hours of becoming aware of a significant incident. Where a NIS2-covered entity operates an Annex III point 2 AI system, Article 73(9) of the AI Act narrows the Article 73 obligation to fundamental-rights incidents.
The European Union's Network and Information Security Directive (2022/2555), whose incident reporting obligations for essential and important entities include a 24 hour early warning, a 72 hour detailed notification, and a final report within one month, forming a comparison point for multinational organizations also operating in China.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Cybersecurity Incident Reporting · Enforcement and Incident Response, Certified China AI Regulatory Professional (CCARP)
- The First 72 Hours: AI Incident Response · Post-Market Monitoring and Enforcement, EU AI Act Implementation Expert
Where it shows up at work
A definition is where NIS2 Directive starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Classifies AI incidents by severity, runs containment, preserves evidence, manages notification, and closes the loop with lessons learned.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Chief Information Security Officer, AI security focusneeds it at depth
- AI Incident Response Leadneeds it at depth · 1 open posting this week
- Chief Privacy Officer, AI privacy editionneeds working knowledge
- Chief Risk Officer, AI risk editionneeds working knowledge
- AI Security Architectneeds working knowledge · 8 open postings this week
- Physical AI Safety Engineer, autonomous systems editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: EU AI Act Article 73; ISO/IEC 42001 Annex A incident controls; NIST AI RMF MANAGE 4.
One interview question about it
An AI system has just caused harm to a customer. Walk me through the first 48 hours.
Asked of candidates for ai incident response and recovery. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Cybersecurity and IT carries it as work you can show: Incident playbooks and post-incident reviews are your artifacts.
- A cybersecurity or information assurance degree carries it as a claim to back up: Incident response is a course; AI incidents add model failure to the playbook.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.