Who is a manufacturer
The Act applies to "products with digital elements": software or hardware products, and their remote data processing solutions, that are made available on the EU market. The manufacturer is whoever develops or manufactures such a product, or has it developed, and markets it under their own name or trademark. Charging for it is not required. A two-person company selling a desktop application, a firmware vendor, and a company shipping a mobile app together with the backend it depends on can all be manufacturers.
Some things fall outside. Products already covered by certain sector rules, such as medical devices and motor vehicles, are excluded. Free and open-source software that is not supplied in the course of a commercial activity is out of scope, and open-source software stewards have a lighter regime of their own. Software offered purely as a service is generally dealt with under NIS2 instead, unless it is the remote data processing that a product needs in order to work. Scope is the part of the Act where guessing is most expensive, so check Articles 2 and 3 and the recitals against your own product before you conclude that you are in or out.
One detail catches people out. The reporting duty also covers products that were placed on the market before 11 December 2027. You do not get to wait for the main obligations before you start reporting.
What must be reported, and how fast
Article 14 creates two reporting tracks. Both go through the single reporting platform that ENISA operates, to the CSIRT designated as coordinator in the member state of your main establishment and to ENISA at the same time.
Actively exploited vulnerabilities. A vulnerability counts as actively exploited when there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Once you become aware of one in your product, the timeline is as follows.
1. An early warning within 24 hours.
2. A vulnerability notification within 72 hours, with general information about the product, the nature of the exploit and the vulnerability, and any corrective or mitigating measures taken or available to users.
3. A final report no later than 14 days after a corrective or mitigating measure is available, describing the vulnerability, its severity and impact, and the fix.
Severe incidents that affect the security of the product. The first two steps are the same: an early warning within 24 hours and an incident notification within 72 hours. The final report is due within one month of the incident notification.
In both cases you also have to inform the affected users of the product, and where appropriate all users, about the vulnerability or incident and about what they can do to reduce the risk.
Every deadline runs from when you become aware. That makes the internal question of who is allowed to say "we are now aware" a real one. Decide it in advance. Article 64 contains a limited relief from fines for micro and small enterprises that miss the 24-hour early warning. Read it before you rely on it.
Why an SBOM is the groundwork
A vulnerability in your product is often a vulnerability in something you ship. When a library you depend on is reported as exploited in the wild, you have 24 hours from awareness to send an early warning. You cannot do that if finding out whether you ship the library takes a week of asking around.
A software bill of materials answers that question quickly: which components, at which versions, are in which release. The vulnerability handling requirements in Annex I of the Act ask manufacturers to identify and document the components in their products, including by drawing up an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies. That requirement belongs to the main obligations that apply from December 2027, but the reporting duty makes it useful now. CycloneDX and SPDX are the two formats in common use.
Generate the SBOM for each release and keep the old ones. The report you may have to file concerns the versions your customers are running, which are rarely only the latest.
Why a vulnerability handling process is the other half
An SBOM tells you what you ship. A process tells you what to do when something in it breaks. The minimum that makes the Article 14 deadlines achievable is short.
1. An intake route. A security contact address and a published disclosure policy, so that a researcher or customer who finds a problem can reach someone who will act. Annex I asks for a coordinated vulnerability disclosure policy in any case.
2. Monitoring. Something that watches your components against new advisories and against lists of exploited vulnerabilities such as the CISA Known Exploited Vulnerabilities catalogue.
3. Triage with a named owner, so that each report gets a decision and a record.
4. A reporting runbook: who registers on the reporting platform, who drafts the early warning, who approves it, and what happens outside office hours.
5. A way to ship a fix and tell users, since the final report depends on a corrective measure being available.
Run the runbook once as an exercise with a made-up vulnerability. The gaps tend to be ordinary ones: nobody has the login, or the person who can approve is on leave.
How Spoorder fits
Spoorder generates SBOMs in CycloneDX 1.7 and SPDX 2.3 from dependency and container scan results, flags findings whose CVE is on the CISA KEV list, and keeps a history of each finding from detection to verified fix. On the Scale plan it maps findings and evidence to the EU CRA framework. It does not file reports with ENISA or a CSIRT for you, and it does not decide whether your product is in scope.
Ready to scan your application?
Free health check: HTTPS, TLS and security headers for one URL, in about a minute. Free account, no credit card.
Scan your app free →