From 11 September 2026, the EU Cyber Resilience Act’s Article 14 reporting obligations apply: an actively exploited vulnerability or a severe incident must reach ENISA and your coordinating CSIRT within 24 hours. The clock starts when a developer notices, not when a lawyer does. If the path from that developer to ENISA has never been tested, 11 September is a poor day to find out where it breaks.
Who this is for
- Manufacturers placing products with digital elements on the EU market — connected hardware, embedded software, standalone software.
- PSIRT and security teams who own vulnerability disclosure and incident triage.
- Engineering leads whose developers are usually the first people to see an actively exploited flaw.
- Compliance owners who need a working 24-hour reporting chain, not a policy PDF.
What’s happening
Article 14 of the Cyber Resilience Act is the reporting duty, and it switches on ahead of the main obligations everyone is watching. From 11 September 2026, a manufacturer must notify both ENISA and the CSIRT designated as coordinator in its main place of establishment about any actively exploited vulnerability in its product, and any severe incident affecting the product’s security. The reporting runs in three stages: an early warning within 24 hours, a full notification within 72 hours, and a final report once the matter is resolved. Submissions go through the single reporting platform ENISA operates as the common front door. I set out how that platform and your PSIRT connect in this piece on the single reporting platform.
Why it bites
Twenty-four hours is not much time, and the duty is triggered by awareness — the moment someone in your organisation becomes aware of active exploitation. That moment almost always happens at an engineer’s desk, not in a compliance meeting. The failure is organisational, not technical: the person who sees it first often has no idea a legal clock has started, and the person who knows the obligation is two escalations and an out-of-hours handover away. Add a weekend, a contractor who owns the platform login, or a coordinating CSIRT nobody has registered with, and the early warning that was meant to take an hour takes three days.
Free · 4 minutes
Do you know where AI is already being used in your business — and what it can see?
Fourteen questions on shadow AI, data exposure, oversight, and governance debt — the gap between how fast AI is arriving and how much control you have over it. Banded finding on screen, full sheet by email.
The one thing to do before 11 September
Run one timed dry-run of the whole chain. Pick a plausible actively-exploited-vulnerability scenario, start the clock at the moment a developer would first notice it, and see whether an early-warning notification could actually reach ENISA and your coordinating CSIRT within 24 hours. Confirm you are registered on the reporting platform, confirm who holds the credentials, and confirm the out-of-hours route works when the usual person is unreachable. Then time it. If it does not clear 24 hours on a calm Tuesday, it will not clear them during a real incident.
If you want a second pair of eyes on that chain before the date, that is the kind of review I do: walking the path from developer to ENISA, timing each hop, and finding where the 24 hours leaks. A technology control review covers exactly this and leaves you with evidence you can show a regulator.
If the gap is capacity rather than judgement — someone to build the intake, wire up on-call routing and integrate with the reporting platform — my sister-brand delivery team can stand that up for you.
Reviews are fixed-scope and priced up front, so you know the cost before you commit.
Test the path while it costs you an afternoon. On 11 September 2026 it costs you the 24 hours you no longer have.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Free interactive tool
Interactive deadline calculator
Check which regulations apply to you and when
Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.
Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.
Full Governance by Sixteen Pillars
Govern your business. Prove your compliance.
A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.
See what's coming