AI-incidentrapportage
Een AI-systeem begint hele regio’s af te wijzen. De klok loopt.
Wat is AI-incidentrapportage?
Article 73 of the EU AI Act requires providers of high-risk AI systems to report serious incidents to market surveillance authorities within strict deadlines, and deployers must inform the provider and the authority. In this exercise, you investigate an AI-powered customer onboarding system that has been rejecting applicants from specific regions, determine whether the anomaly meets the Article 73 threshold for a serious incident, contain the damage, file the report, and resist vendor pressure to delay.
Wat je leert in AI-incidentrapportage
- Identify what constitutes a 'serious incident' under the EU AI Act and when Article 73 requires reporting
- Pas de juiste volgorde van reageren toe: inperken, onderzoeken/rapporteren, herstellen
- Begrijp de rapportagetijdlijnen voor aanbieders en gebruiksverantwoordelijken van AI-systemen met een hoog risico
- Herken en weersta de druk om de verplichte melding van incidenten uit te stellen
- Documenteer AI-incidenten nauwkeurig voor indiening bij markttoezichtautoriteiten
AI-incidentrapportage — Trainingsstappen
-
Artikel 73: Rapportage van ernstige incidenten
Under Article 73 of the EU AI Act, providers of high-risk AI systems must report 'serious incidents' to the relevant market surveillance authority, and deployers must inform the provider and the authority (Article 26(5)). Article 3(49) defines a serious incident as an incident or malfunctioning that directly or indirectly leads to death or serious harm to health, a serious and irreversible disruption of critical infrastructure, an infringement of obligations under Union law protecting fundamental rights, or serious harm to property or the environment. Reporting timelines are strict, and providers and deployers have distinct obligations. Today, one of your company's AI systems has triggered exactly this scenario.
-
Een dringende ondersteuningsescalatie
Alice ontvangt een dringende e-mail van het klantenserviceteam. Ze hebben een verontrustend patroon ontdekt in het OnboardAI-systeem, de AI-aangedreven onboardingtool van het bedrijf.
-
Het AI-dashboard controleren
Alice opent het AI-monitoringdashboard om de afwijking met harde gegevens te bevestigen. Het dashboard houdt alle AI-systeemstatistieken bij, inclusief goedkeuringspercentages, waarschuwingen en operationele kosten.
-
Bevestiging van de anomalie
Het dashboard bevestigt wat de klantenondersteuning heeft gerapporteerd. De kritische waarschuwing toont een duidelijk, systematisch patroon van regionale discriminatie door het OnboardAI-systeem.
-
Is dit een te melden incident?
-
Onmiddellijke insluiting
The data is clear. Now Alice must determine: does this meet the threshold for a 'serious incident' under Article 3(49)? The answer is yes. Systematic discrimination affecting 230 applicants constitutes a potential breach of the right to non-discrimination - a fundamental right protected under EU law. Key factors that make this reportable: Systematic pattern: Not a random error, but a consistent 0% approval (100% rejection) rate sustained over 7 days Fundamental rights impact: The right to non-discrimination is a protected fundamental right Significant scale: 230 people denied access to services based on their region Ongoing harm: The system is still actively rejecting applicants right now Under Article 3(49), a serious incident includes an incident or malfunctioning that directly or indirectly leads to an infringement of obligations under Union law intended to protect fundamental rights. Regional discrimination in access to services qualifies clearly. Before investigating the root cause or filing a formal report, the first priority is containment. The OnboardAI system is still actively rejecting applicants from the affected regions right now. From the AI dashboard, Alice halts the OnboardAI system and routes all applications from the three affected regions to manual processing. No more automated decisions until the system is investigated and cleared. The correct order of response is: contain first , then investigate and report. Never wait for root cause analysis before stopping ongoing harm.
-
Inloggen op het Incidentportaal
Nu het systeem onder controle is, opent Alice het interne portaal voor het melden van incidenten. De toegang is beperkt tot geautoriseerd operationeel personeel. Zij logt in met haar bedrijfsreferenties voordat ze het rapport indient.
-
Het indienen van het incidentrapport
Alice vult het incidentrapport in met de feiten die het ondersteuningsteam heeft bevestigd en de inperkingsmaatregelen die het operationele team al heeft ondernomen. Dit rapport wordt doorgestuurd naar het complianceteam, dat het doorstuurt naar de markttoezichtautoriteit.
-
Waarom elke sectie ertoe doet
Het rapport maakt nu deel uit van het proces-verbaal. Elke sectie dient een specifiek doel voor het complianceteam en de markttoezichtautoriteit.
-
Tijdlijnen voor rapportage
The report has been submitted internally. Now, the legal timeline begins. Under Article 73, providers of high-risk AI systems must report serious incidents to the market surveillance authority: Immediately after the provider has established a causal link, or the reasonable likelihood of one, between the AI system and the incident No later than 15 days after the provider or, where applicable, the deployer becomes aware of the serious incident Sooner in the gravest cases: no later than 2 days for a widespread infringement or a serious and irreversible disruption of critical infrastructure, and no later than 10 days if a person has died Deployers must inform the provider immediately, and then the market surveillance authority (Article 26(5)). Both providers and deployers must cooperate fully with any subsequent investigation by the authorities. SynapseAI deploys OnboardAI but did not build it - the provider is OnboardAI's vendor. SynapseAI must notify them immediately so they can fulfill their own reporting obligations.
Dekking van beveiligingsframeworks
CIS Controls
- CIS 17 Incident Response Management
- CIS 14.6 Train Workforce Members on Recognizing and Reporting Security Incidents
NIST CSF
- PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
- RS.MA Incident Management
NICE Framework
- OG-WRL-008 Privacy Compliance
- OG-WRL-002 Cybersecurity Policy and Planning
EU AI Act
- Art. 73 Reporting of serious incidents