NIS2
Identify your national implementation and prepare governance, security controls and incident reporting.
Cyber Resilience Act, Regulation (EU) 2024/2847
Plan security work for digital products sold in the EU, from vulnerability reporting to a release evidence file.
Covered products with digital elements made available on the EU market and their manufacturers, importers and distributors. Check sector exclusions and separate rules for open-source software stewards.
A product cybersecurity assessment, technical evidence, an operating vulnerability process and the applicable conformity and reporting records.
Track the reporting start date separately from the general conformity date. A major release can also change the scope or assessment route.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
EU Cyber Resilience Act kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Classify the product and operators · Product counsel + security architect [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A router maker learns that attackers are exploiting one shipped firmware component. Its product security team checks affected versions against its component inventory, records awareness, and prepares the regulatory filing while the engineering team works on a fix.
Check whether cybersecurity certification may be relevant to the product’s conformity route.
Turn application security requirements into testable release checks.
Applicable reports go through the single reporting platform.
Official reference (opens in a new tab)Use the rules for awareness and triggers. Final reports have different clocks for vulnerabilities and severe incidents.
Official reference (opens in a new tab)Check product scope, conformity route and any separate obligations for open-source software stewards.
Official reference (opens in a new tab)Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Classify the product and operators | Product counsel + security architect | Before choosing the conformity route | Set a start date | Classification memo; System boundary; Role map | Open |
| Build security into design and support | Product security + engineering | Before release and throughout the support period | Set a start date | Risk register; Software bill of materials; Vulnerability handling procedure | Open |
| Exercise the actual reporting sequence | Product security response + regulatory affairs | On a qualifying event and in drills | Set a start date | Incident classification; Reporting templates; Exercise record | Open |
| Assemble the technical and conformity file | Regulatory lead + engineering | Before placing a covered product on the market | Set a start date | Technical documentation; Declaration; Patch advisory | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map software, hardware, essential remote components, intended use and operator roles. Check exclusions, product classes and the applicable assessment route.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Assess foreseeable use and risks, trace mitigations to tests, maintain component and version evidence, and specify how vulnerabilities and updates will be handled.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The component inventory corresponds to a built product release and supports a reproducible affected-version search.
Use the worksheet as a review checklist. Supply the prescribed machine-readable SBOM where required.
Fictional details. Use the same fields with evidence from your work.
The workflow routes a report to a named decision maker even while facts are incomplete.
Provide the procedure to support, engineering, security and regulatory owners before the product enters service.
Record awareness and determine if active exploitation or a severe incident meets the trigger. Use the single reporting platform and track early, full and final reports.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.
Reconcile versions, secure development evidence, documentation, support dates and assessment outputs. Complete the applicable declaration, marking and distribution checks.
Fictional details. Use the same fields with evidence from your work.
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.
Fictional details. Use the same fields with evidence from your work.
The signer can explain the basis for each statement and the record reflects the required scope and period.
Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.
Fictional details. Use the same fields with evidence from your work.
A customer can identify affected devices and confirm the fix. Claims match reproducible engineering evidence.
Publish through the approved support channel and link the advisory to investigation and release records.