A manufacturer should train every employee who talks to customers, partners or the public to recognise two CRA Article 14 signals and to forward them to one internal security address within minutes. The 24-hour early warning runs from the moment the manufacturer becomes aware, and Article 13(17) allows users "to choose their preferred means of communication".
The CRA sets no general duty to train staff. That duty sits in the NIS2 Directive. The CRA reporting clock still makes training a practical need, because a report that waits in a support queue for a day uses up the whole early warning window.
Key takeaways
- Article 14 of Regulation (EU) 2024/2847 runs the 24-hour early warning from the moment the manufacturer becomes aware of an actively exploited vulnerability or a severe incident.
- Article 13(17) requires a single point of contact that allows users "to choose their preferred means of communication", so reports also reach support, sales and field service.
- Staff outside security need to recognise two signals and follow one rule. They forward the original message to one address, record the time, and decide nothing.
- A 15-minute briefing at onboarding and twice a year covers the knowledge. A seeded test message and a tabletop exercise prove that the route works.
- The CRA manufacturer course in the CVD Portal Academy suits the people who make the Article 14 decision. The briefing suits everyone else.
Why do support and sales staff start the Article 14 clock?
Article 14(1) and 14(3) apply to every actively exploited vulnerability and severe incident that the manufacturer "becomes aware of". The regulation does not define the moment of awareness, so the cautious reading is the moment a credible report reaches anyone in the company.
Article 13(17) makes this moment hard to control. It states that "The single point of contact shall allow users to choose their preferred means of communication and shall not limit such means to automated tools." A customer who sees strange behaviour will phone the account manager they know, open a support ticket, or post on social media. The report then sits with a person who has no security training.
The Article 14 readiness drill found the same gap from the other side. Most teams know the deadlines. The delay comes from the hours before the security team hears about the event.
Which employees need the briefing?
Every role that receives messages from outside the company needs the briefing. The table lists the usual entry points and a typical first signal for each. The examples do not form a complete list.
| Role | Where the signal arrives | Typical first signal |
|---|---|---|
| Customer support and helpdesk | Tickets, phone, chat | "All our units rebooted at 03:00 and now send traffic to an address we do not know." |
| Sales and account managers | Direct email, phone, meetings | "Our IT team traced last week's breach to your gateway." |
| Field service and installers | Site visits, returned units | A returned device with firmware that the factory did not ship. |
| Social media and marketing | Public posts, direct messages | A post that links to a working exploit for a named product. |
| General inbox and reception | info@ address, switchboard | A national CSIRT or authority asks for a security contact. |
| Legal and contracts | Customer claims, letters | A customer letter that holds the manufacturer liable for an intrusion. |
Engineering staff need the briefing too. One internal event crosses into Article 14. A compromise of the build server or the update server can put malicious code into the product, and point (b) of Article 14(5) covers that case.
Which two signals must staff recognise?
Staff need the two definitions as the regulation states them. The text below is copied from Regulation (EU) 2024/2847.
An actively exploited vulnerability, Article 3(42):
‘actively exploited vulnerability’ means a vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without permission of the system owner;
A severe incident, Article 14(5):
For the purposes of paragraph 3, an incident having an impact on the security of the product with digital elements shall be considered to be severe where:
(a) it negatively affects or is capable of negatively affecting the ability of a product with digital elements to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions; or
(b) it has led or is capable of leading to the introduction or execution of malicious code in a product with digital elements or in the network and information systems of a user of the product with digital elements.
Two parts of these definitions matter most in a briefing. Article 14(5) uses "is capable of", so an incident can be severe before any damage occurs. Point (a) names availability, so an attack that only stops a product from working can be severe. The examples in the table above are a sample of the cases these definitions cover.
The security team decides whether a report meets either definition. Staff escalate on suspicion. A false alarm costs a responder a few minutes. A missed report can cost the 24-hour deadline. The decision process that follows is in our guide to internal detection and escalation.
What should the escalation rule say?
The rule should fit on one card and contain one address, one time limit and one phone number. Here is an example that a team can copy and change.
If a customer, partner, researcher or authority says that someone attacked, misused, disabled or took control of one of our products, or could do so, forward the original message to security@ within 15 minutes. Write down when you received it. Outside office hours, also phone the on-call number. Do not reply with a promise, a denial or a cause.
Each part of the rule has a reason.
- Forward the original. The security team needs the sender's exact words, the headers and any attachments. A summary loses facts.
- Record the time of receipt. The time is evidence of when awareness may have started. The security team uses it to calculate the early warning deadline.
- Phone outside office hours. An email to a shared address on Friday evening can wait until Monday, while the 24-hour clock keeps running.
- Do not reply with a promise, a denial or a cause. A sales reply that says "our product is not affected" can be wrong, and the customer may forward it to a regulator.
The 15-minute limit is a recommendation from Porta Regulus. The CRA sets no internal time limit. A short limit leaves the security team most of the 24 hours for the assessment and the filing.
A 15-minute briefing script
The briefing fits into a team meeting. It needs no slides and works best with real example messages from the team's own channels.
- Minutes 0 to 3. Explain the 24-hour clock and Article 13(17). Users can contact us through any channel, so any of us can receive the first report.
- Minutes 3 to 8. Read five short example messages aloud. Three are signals and two are ordinary faults. Ask the team which ones to escalate and why.
- Minutes 8 to 12. Hand out the escalation card. Show the address, the on-call number and the place to record the time of receipt.
- Minutes 12 to 15. Each person sends a test message to the address. The security team confirms receipt before the meeting ends.
Porta Regulus recommends the briefing at onboarding and twice a year after that. Each repeat should use new example messages, because a team that hears the same five examples only learns those five.
How do you test that the briefing worked?
A seeded test message measures the real route. A colleague outside the security team sends a realistic report to the support desk or to an account manager, without notice. The security team records the time until the report reaches them. Repeat the test once a year and keep the result as evidence that the procedure works.
A tabletop exercise tests the decisions that follow. The free CRA tabletop exercise in the CVD Portal Academy takes 90 minutes, needs no account, and runs eight timed injects from first awareness to the Article 14 final report. The first inject is a report through the disclosure policy. Invite the support lead and one account manager, and ask them how the same report would reach them through a ticket or a phone call.
The AI tabletop exercise on the Enterprise plan builds the scenario from the manufacturer's own products. An AI controller plays the CSIRT, the researcher, a customer and a journalist, so support and communications staff can practise their part of the event. The background to both exercises is in how to rehearse Article 14 reporting.
Where does the CVD Portal Academy fit?
The CRA manufacturer course is for the people who decide whether a report is an Article 14 event. That group is usually the PSIRT, the product security lead and the compliance lead. The course is free, has eight modules with quizzes, ends with a timed exam and gives a verifiable certificate. It covers both Article 14 timelines, the recipients of a report and the boundary with Annex I Part II.
The 15-minute briefing is for everyone else. A support agent needs the two signals and the escalation card. The decision makers need the full course, and a team that has a PSIRT can find how to build one in our PSIRT guide.
How does CRA escalation training relate to NIS2 training?
The two laws have different triggers and different subjects. A manufacturer that is also an essential or important entity under NIS2 can add the Article 14 briefing to its NIS2 training plan, but the briefing must keep the two triggers apart.
| Question | CRA (Regulation (EU) 2024/2847) | NIS2 (Directive (EU) 2022/2555) |
|---|---|---|
| Who is bound | Manufacturers of products with digital elements | Essential and important entities |
| Training duty | None in the text | Article 20(2) for management bodies, Article 21(2)(g) for cyber hygiene and training |
| What is reported | Actively exploited vulnerabilities and severe incidents that affect the product | Significant incidents that affect the entity's own services |
| First deadline | Early warning within 24 hours of awareness, Article 14(2)(a) and 14(4)(a) | Early warning within 24 hours of awareness, Article 23(4)(a) |
A phishing click on a company laptop is a NIS2 matter for an entity in scope. A compromised device at a customer site is a CRA matter. A compromised update server can be both, so it goes to the security team in every case.
Sources
- Regulation (EU) 2024/2847, the Cyber Resilience Act, Article 3, Article 13 and Article 14. CELEX 32024R2847.
- Directive (EU) 2022/2555, the NIS2 Directive, Article 20, Article 21 and Article 23. CELEX 32022L2555.
Frequently asked questions
Does the Cyber Resilience Act require employee security training?
The Cyber Resilience Act sets no general duty to train employees. The training duties are in the NIS2 Directive, Article 20(2) for management bodies and Article 21(2)(g) for cyber hygiene and cybersecurity training. A CRA manufacturer still needs staff who recognise an Article 14 signal, because the 24-hour early warning runs from the moment the manufacturer becomes aware.
Which employees can start the CRA Article 14 clock?
Any employee who receives a credible report that a product is being exploited or has had a severe incident can start the CRA Article 14 clock. Article 13(17) requires a single point of contact that allows users "to choose their preferred means of communication", so customer support, sales, field service, social media staff and the general inbox all receive such reports.
What should an employee do with a report of an attacked product?
The employee should forward the original message unchanged to the internal security address, note the time of receipt, and phone the on-call number outside office hours. The employee should not confirm, deny or promise anything to the sender. The security team decides whether the report is an Article 14 event.
How often should staff receive the CRA escalation briefing?
Porta Regulus recommends the 15-minute escalation briefing at onboarding and twice a year after that, with one unannounced test message per year to measure how long a seeded report takes to reach the security team. The CRA sets no frequency. NIS2 Article 21(2)(g) asks essential and important entities for regular cybersecurity training.
