Skip to content
Skip to content
THE GATE OPENS 11 SEPTEMBER

Cyber Resilience Act Requirements: What Actually Opens on 11 September

Four days before Article 14 becomes law, ENISA has confirmed exactly what its new reporting platform will and will not do on day one. Cyber resilience act requirements now has a sharper edge: for every security vendor briefing clients this week, the gap between the two is the whole story.

Summarise with
Set as preferred source on Google
15 min read
Quick answerCyber resilience act requirements changes on 11 September: mandatory Article 14 vulnerability and incident reporting opens on ENISA's new platform, but voluntary Article 15 reporting does not, a gap every security vendor should explain to clients this week.
SECTION 01

The Gate That Opens Halfway

Cyber resilience act requirements has, until this week, meant one date circled in red: 11 September 2026, the morning Article 14 of Regulation (EU) 2024/2847 stops being theory and starts being law. That date got its first folkfox treatment on 17 August, in a piece that declined to call the reporting platform behind it ‘late’. That verdict still holds. What has changed is the detail: ENISA has since spelled out, plainly, what its Single Reporting Platform will actually do on the morning it opens, and what it will not. Getting cyber resilience act requirements right in the next four days means understanding that difference, not just the date. That is what cra vulnerability reporting actually means on day one: a mandatory duty with no voluntary companion yet.

Start with the plain answer, given in ENISA’s own FAQ rather than inferred from a press release: ENISA, 2026 states that the platform ‘is scheduled to be operational from 11 September 2026’, the same date the Article 14 reporting duty becomes applicable, and that ‘at launch, the platform will support only mandatory reporting of actively exploited vulnerabilities and severe incidents under Art. 14’. The same page is unambiguous about what is missing: ‘voluntary reporting under Art. 15 will not be available at launch and will be introduced in a future phase of the platform.’ That is a specific, checkable claim, not a hedge.

Here is where a careful reader earns their keep. ENISA’s own general overview page, covering the same platform, reads more loosely: it says that ‘as of 11 September 2026 onwards, the SRP will be used by CSIRTs and manufacturers for mandatory reporting and could be used by any natural/legal persons for voluntary reporting’, a sentence that, taken alone, sounds like Article 15 opens on day one after all. Our own reading is that the FAQ page is the authoritative source on this narrow point, because it answers a direct question about launch-day scope, while the overview page is a broader summary that never quite pins voluntary reporting to a date. ENISA, 2026’s general page describes voluntary-reporting functionality without specifying that it is held back at launch; its own FAQ, answering the launch-day question head on, says plainly that it is. Two ENISA pages, two shades of confidence. ENISA is not offering a veiled version of the truth here, but it is offering two versions with different amounts of detail, and cyber resilience act requirements work for the next four days should be built on the more cautious of the two.

cyber resilience act requirements and the unfinished gate: an ink-drawn fox before a half built gate under a ticking clock
The gate opens on the hour whether or not the hinge is finished.

There is a second, smaller gate worth noting for anyone running an authorised representative (AR) structure in Europe. Non-validated ARs, per the same FAQ, ‘may submit up to 20 notifications for one manufacturer before validation becomes mandatory’, meaning the platform tolerates a working relationship that has not finished its paperwork, up to a point. It is a sensible piece of plumbing, and it says something honest about where ENISA’s priorities sit this week: get the mandatory duty running, let the softer edges catch up.

20

notifications a non-validated authorised representative may file for one manufacturer before validation is mandatory

ENISA, 2026

SECTION 02

The Timeline Behind Cyber Resilience Act Requirements

@DGProgress
A 24-hour cybersecurity incident-reporting duty starts on 11 September. Product rules it belongs to start in December 2027. The Cyber Resilience Act has been in force since December 2024 and its main obligations apply from 11 December 2027. But one duty arrives a great deal sooner. From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents having an impact on the security of their product with digital elements. The obligation is an early warning clock: within 24 hours of becoming aware, a full notification within 72 hours.
4 September 2026View on X

@DGProgress is not wrong to call this an early warning clock. Article 14 sets three deadlines, not one, and they apply whether or not a company has read the regulation closely. Per the text itself (a reliable mirror, since the official EUR-Lex page tends to render as an empty JavaScript shell on a simple fetch), an Cyber Resilience Act (EU text mirror), 2026 early warning notification is due ‘without undue delay and in any event within 24 hours’ of a manufacturer becoming aware of an actively exploited vulnerability or a severe incident. A fuller notification follows ‘within 72 hours’. Then a final report: ‘no later than 14 days after a corrective or mitigating measure is available’ for a vulnerability, or ‘within one month after the submission of the incident notification’ for an incident.

Jones Day, 2026 frames the stakes plainly: non-compliance can attract fines of up to fifteen million euro or 2.5% of worldwide turnover, whichever bites harder, and the duty applies to products already on the market, not only new ones queued for the December 2027 conformity deadline. A cyber resilience act requirements failure, in that light, starts as a missed 24-hour window and ends as a balance-sheet problem. Crowell & Moring, 2026 put it more bluntly back in June: ‘companies that are potentially in scope of the CRA and have not yet considered it should start now.’ Four days out, ‘now’ has become ‘this afternoon’.

None of this rhythm is unfamiliar to anyone who has already lived through NIS2. Timelex, 2026 documents the same 24-hour, 72-hour, one-month cadence for significant incidents under that directive, though the trigger differs: NIS2 watches for operational disruption, the Cyber Resilience Act watches for an actively exploited flaw in a product. A vendor who has already built an NIS2 runbook is halfway to meeting the cyber resilience act requirements that start applying on 11 September, and the muscle memory transfers even where the paperwork does not, which is exactly why folkfox tracks these regulatory shifts on its own news desk as they land, precisely because clients ask about the overlap more than they ask about either regulation alone.

SECTION 03

Cyber Resilience Act Requirements, Measured Against Itself

Readiness vs the 11 September target
Both of ENISA's own readiness numbers stall well short of the halfway mark, days before the reporting duty goes live.CRA awareness: 66 of 100CRA awareness66%IR maturity: 52 of 100IR maturity52%
Both of ENISA's own readiness numbers stall well short of the halfway mark, days before the reporting duty goes live.

The regulator that built the platform also measured the field it is aimed at, and the results are worth sitting with before anyone drafts a client email. ENISA, 2026 surveyed 194 organisations across 31 countries, including 25 EU member states, between February and March 2026. Sixty six per cent had heard of the Cyber Resilience Act before the survey even asked, which sounds respectable until it is converted the other way: a third of respondents, people close enough to the topic to answer a regulator's questionnaire, had not heard of the law that starts reporting them in days.

The deeper number sits in the ENISA, 2026 survey report itself: incident response and product lifecycle management, the exact muscle Article 14 exercises, came back as the weakest area measured, averaging 2.6 out of 5 across respondents. Cyber resilience act requirements, in other words, asks companies to sprint a process that the regulator's own research says is barely walking.

Chart142 of 194 organisations asked ENISA for money, not more paperwork.73% of surveyed SMEs wanted financialsupport to prepare
142 of 194 organisations asked ENISA for money, not more paperwork.

That figure, 142 of 194 organisations underlining a need for financial support, is the silent story of the whole survey. It is not a company asking for a longer deadline. It is a company saying the compliance burden and the balance sheet do not currently agree, four days before the clock the regulator itself set starts running.

SECTION 04

What Your Clients Are About to Ask You

This is where cyber resilience act requirements stops being a legal question and starts being a marketing one, and it is a thicket security vendors already know how to move through. Anyone selling cybersecurity marketing agency has spent years learning the discipline of saying exactly what a report covers and what it does not, because a client who thinks SOC 2 means ‘we cannot be breached’ is a client who will be furious later. The Cyber Resilience Act's split rollout, mandatory reporting live, voluntary reporting waiting, is the same trap in a new coat. A vendor, MSSP or compliance-services company that explains the gap honestly this week builds exactly the kind of trust a cybersecurity marketing agency pitch depends on; one that lets a client assume the platform does more than it does is setting up next quarter's awkward call, and folkfox helps compliance-adjacent vendors close that gap through brand strategy as often as through legal copy.

DLA Piper, 2026 calls the Cyber Resilience Act ‘not merely a technical regulation’ but ‘a strategic compliance challenge that will require close coordination between legal, engineering, and business teams’, which is a polite way of saying most manufacturers will need outside help translating the reporting duty into a runbook. That is the opening. A vendor who can point a prospective client at the exact clause, the exact hour, the exact platform gap, and say so before the client has to ask, has already outfoxed the version of this pitch built on vague urgency, the kind a prospect can scent a sales pitch inside from the far side of a hedgerow.

Skadden, 2026's own September checklist notes that notifications route through ‘a form on ENISA's newly created Single Reporting Platform’, requiring product type, category and an incident overview at each stage, and that the immediate priority is simply to ‘identify and inventory your PDEs’ (products with digital elements). None of that is glamorous. All of it is the kind of unglamorous groundwork a compliance-services company can sell without inflating what the regulation, or the platform, currently does.

SECTION 05

Cyber Resilience Act Requirements Starts With an Honest Briefing

Four days is not long enough to build new infrastructure. It is long enough to write one clear paragraph and send it to every client who touches a product with digital elements. That paragraph should say, in order: what is mandatory from 11 September, what is not yet, and where the two are easy to confuse. European Commission, 2026 keeps its own summary of the reporting duty short for exactly this reason: ‘manufacturers report only once through the CRA Single Reporting Platform’, addressed to the CSIRT of main establishment and mirrored automatically to ENISA.

There is a version of this moment that turns into scaremongering, a vendor waving the deadline like a torch through the undergrowth and hoping the noise alone drives clients toward the den. Here, as in the piece published in August, folkfox's advice is the quieter trail: name the date, name the gap, name what to do about both, and let the accuracy do the persuading. That is a briefing built on cold clarity rather than manufactured panic. A prospect can scent a sales pitch dressed as a public service announcement from the far side of a hedgerow; they trust the guide who has already read the fine print, and cyber resilience act requirements is, this week, mostly a question of who reads the fine print first.

None of this replaces legal advice, and nothing here should be read as a substitute for a manufacturer's own counsel confirming scope. What folkfox does well is the layer above that: turning a regulatory date into content, positioning and a briefing your own clients will actually read. If cyber resilience act requirements sits inside your cybersecurity marketing remit, or you are weighing how a compliance-services offer fits your content marketing and SEO and GEO plans for the rest of 2026, that is a conversation worth having this week, not after the platform's first outage headline. A quick pricing conversation now costs less than a scramble later, and folkfox's own AI consultancy practice is already fielding questions about how to draft this kind of regulatory content at speed.

Questions

Frequently asked questions

What are the requirements of the cyber resilience act?

The Cyber Resilience Act (Regulation (EU) 2024/2847) requires manufacturers of products with digital elements to meet essential cybersecurity requirements before sale, provide security updates through a defined support period, and report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform. Full conformity obligations apply from 11 December 2027; the Article 14 reporting duty, the part in the news this week, applies from 11 September 2026. Cyber resilience act requirements therefore arrives in stages, not as a single switch.

When will the cyber resilience act be implemented

In stages. The Article 14 reporting obligation, covering actively exploited vulnerabilities and severe incidents, becomes applicable on 11 September 2026, through ENISA's Single Reporting Platform. Open-source software steward obligations under Article 24(3) follow on 11 December 2027, the same date the Act's main conformity requirements apply to products with digital elements generally. There is not one implementation date; there are at least three.

Does ENISA's reporting platform support voluntary reporting from day one?

Not according to ENISA's own FAQ, which states that voluntary reporting under Article 15 ‘will not be available at launch and will be introduced in a future phase’. ENISA's general overview page describes voluntary-reporting functionality without pinning it to a launch date, which has caused some confusion; the FAQ, answering the launch-day question directly, is the more authoritative source on this specific point, and cyber resilience act requirements planning should follow it.

What is the difference between Article 14 and Article 15 of the Cyber Resilience Act?

Article 14 is mandatory: manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours, 72 hours and a final report. Article 15 is voluntary, open to any person, not only manufacturers, reporting other vulnerabilities, incidents or near misses, with no fixed deadlines. Only Article 14 reporting is live on ENISA's Single Reporting Platform from 11 September 2026.

How is cyber resilience act requirements different from NIS2 incident reporting?

The two share a rhythm, a 24-hour early warning, a 72-hour follow-up and a one-month final report for incidents, but different triggers. NIS2 covers operational incidents affecting essential and important entities under a transposed national directive; the Cyber Resilience Act covers actively exploited vulnerabilities and severe incidents in products with digital elements, as a directly applicable EU regulation. A company already compliant with NIS2 reporting has useful muscle memory, not automatic cyber resilience act requirements.

Can an authorised representative report before it is validated on the platform?

Yes, within limits. ENISA's FAQ confirms that validation runs in parallel with reporting and does not block submissions while it is pending: a non-validated authorised representative may submit up to 20 notifications for one manufacturer before validation becomes mandatory.

Keep reading

Read more on this topic

Cyber resilience act requirements: ready to brief clients before the clock starts?

This is the kind of deadline folkfox turns into content, positioning and campaigns clients actually read, without ever overstating what a platform can do.

Want folkfox in your Google results and AI answers? Set folkfox as a preferred source.

The den

Where to?

Pricing

Choose a section. Enter opens it, Escape continues reading.

Cookie preferences

folkfox uses data the way we use strategy: only when it earns its place.