Start hereClassify the product and operators
~129 days leftOpen step
Guide library
Regulation Europe

EU Cyber Resilience Act

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.

Who it applies to

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.

What you’ll produce

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.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the 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.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Is the product with digital elements placed on the EU market, and which economic operator role do you have?
  • Can you detect an actively exploited vulnerability and file an early warning before the complete investigation is ready?

Worked scenario

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.

What to read next

  • EUCC product certification

    Check whether cybersecurity certification may be relevant to the product’s conformity route.

  • OWASP ASVS

    Turn application security requirements into testable release checks.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 129 days across 4 steps
  1. 01Classify the product and operatorsProduct counsel + security architect · ~21 days
  2. 02Build security into design and supportProduct security + engineering · ~45 days
  3. 03Exercise the actual reporting sequenceProduct security response + regulatory affairs · ~21 days
  4. 04Assemble the technical and conformity fileRegulatory lead + engineering · ~42 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify the product and operatorsProduct counsel + security architectBefore choosing the conformity routeSet a start dateClassification memo; System boundary; Role mapOpen
Build security into design and supportProduct security + engineeringBefore release and throughout the support periodSet a start dateRisk register; Software bill of materials; Vulnerability handling procedureOpen
Exercise the actual reporting sequenceProduct security response + regulatory affairsOn a qualifying event and in drillsSet a start dateIncident classification; Reporting templates; Exercise recordOpen
Assemble the technical and conformity fileRegulatory lead + engineeringBefore placing a covered product on the marketSet a start dateTechnical documentation; Declaration; Patch advisoryOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Classify the product and operators

    Who Product counsel + security architect When Before choosing the conformity route

    Map software, hardware, essential remote components, intended use and operator roles. Check exclusions, product classes and the applicable assessment route.

    What to produce

    Classification memoSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    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.

    System boundaryMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    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.

    Role mapMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    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.

  2. 02

    Build security into design and support

    Who Product security + engineering When Before release and throughout the support period

    Assess foreseeable use and risks, trace mitigations to tests, maintain component and version evidence, and specify how vulnerabilities and updates will be handled.

    What to produce

    Risk registerSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    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.

    Software bill of materialsSpreadsheet

    Gather first

    • Build artifacts, lockfiles and dependency metadata
    • Product versions and configurations
    • SBOM format requirements

    How to prepare it

    1. Generate the inventory from the actual build. Identify direct and transitive components with names, versions and stable identifiers.
    2. Check scope, completeness, relationships and provenance. Keep one record per release and distinguish unknown metadata from verified values.
    3. Export the machine-readable format your workflow or authority requires. Link it to the release and use it to test a vulnerability lookup by component and version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Product and build
    Router firmware 3.2.3, release job 412
    Component and version
    Enter the dependency and resolved version from the build.
    Identifier and relationship
    Record a package URL or equivalent identifier and the parent component.
    Verification
    Compare generated results with build and lockfile evidence.
    Storage and access
    Link immutable SBOM to the exact build and store per access policy.

    Check before handing it over

    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.

    Vulnerability handling procedureMemo

    Gather first

    • Product inventory and support dates
    • Disclosure contact and criteria
    • Incident, patch and regulator workflows

    How to prepare it

    1. Define intake, the acknowledgement owner and how to reproduce the report safely. Record product version, technical impact and evidence of exploitation.
    2. Set severity, escalation and reporting decision rules. Assign ownership of mitigation, customer updates and any separate legal clocks.
    3. Run a mock report through disclosure and patch release. Verify deadlines, authority contact and customer instructions before adopting the procedure.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Intake
    Product security mailbox and monitored vulnerability disclosure form
    Triage
    Identify affected releases and preserve reproduction details in the restricted case.
    Escalation
    Page product security for signs of active exploitation. Regulatory affairs checks reporting triggers.
    Release and validation
    Engineer builds a fix, QA runs exploit regression and service tests.
    Disclosure and closure
    Publish an approved advisory, record receipts and update the affected-version register.

    Check before handing it over

    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.

  3. 03

    Exercise the actual reporting sequence

    Who Product security response + regulatory affairs When On a qualifying event and in drills

    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.

    What to produce

    Incident classificationSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    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.

    Reporting templatesMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    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.

    Exercise recordMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    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.

  4. 04

    Assemble the technical and conformity file

    Who Regulatory lead + engineering When Before placing a covered product on the market

    Reconcile versions, secure development evidence, documentation, support dates and assessment outputs. Complete the applicable declaration, marking and distribution checks.

    What to produce

    Technical documentationMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    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.

    DeclarationMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    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.

    Patch advisoryMemo

    Gather first

    • Confirmed affected versions
    • Vulnerability analysis and released fix
    • Customer support channels and disclosure rules

    How to prepare it

    1. State which product and versions are affected and what a user could experience. Record workarounds and security impact using confirmed details.
    2. Give the fixed version, update steps, prerequisites and a way to verify successful installation. State whether users need to act immediately.
    3. Have engineering and product security verify technical claims. Coordinate publication with required reporting and keep the original release and revisions.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Affected versions
    Example router firmware 3.2.0 through 3.2.2
    Impact
    An authenticated operator can reach a restricted diagnostic action.
    Remediation
    Install approved firmware 3.2.3 and check the version in the admin console.
    Temporary measure
    Restrict management access to trusted networks while the update is scheduled.
    Published and reviewed
    Record approval, time and applicable case reference before publishing.

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes