Cyber Resilience Act

Cyber Resilience Act compliance software

The CRA asks you to handle every vulnerability. Prove each fix in one place.

Acuna GRC follows each vulnerability from your scanner to a verified fix, keeps the technical documentation of your products and records what happened when one is exploited. The work you already do for NIS2 counts again.

Sample company · Brenvara AGWatch the video
  • 35+ years of experience
  • 50+ frameworks
  • ISO 27001 certified

What the CRA asks

What does the Cyber Resilience Act ask of manufacturers? Secure products, for their whole support period.

The Cyber Resilience Act sets cybersecurity rules for products with digital elements sold in the EU, from design to the end of their support period.

  1. Security by design

    Meet the essential cybersecurity requirements of Annex I, backed by a cyber risk assessment and the technical documentation of each product.

  2. Vulnerability handling

    Know the components of each product, fix vulnerabilities without delay, run a coordinated disclosure policy and ship security updates.

  3. Reporting

    Since 11 September 2026, report actively exploited vulnerabilities and severe incidents in stages. The other obligations apply from 11 December 2027.

Does this sound like you?

Why does the CRA feel hard to prove? The work is real. The trail is not.

Most product teams already scan and patch. The time goes into showing which fixes happened, when, and for which product, and into rebuilding the story when a vulnerability is exploited.

Our scanner finds hundreds of vulnerabilities. Nobody can say which ones are fixed.

Fix: Each vulnerability becomes one issue with an owner and a due date set by its severity. Reminders run until the scanner reports it fixed and the owner verifies it.

See vulnerability handling
We already run NIS2. Is the CRA a fourth silo?

Fix: No. Adopt the CRA in Comply next to NIS2. One measure counts for every framework that asks for it, so you see what is already covered.

See what is reused
When a vulnerability is exploited, the facts are spread across chats.

Fix: Log it as an Incident issue. Its timeline keeps dated steps, backdated if needed, with the files of each step.

See the incident timeline

How Acuna GRC covers it

What does Cyber Resilience Act compliance software need to do? Handle vulnerabilities, and keep the proof.

Acuna GRC runs the CRA with Vulnerability management at the center: Comply sets the program, Operate holds the risks and the technical documentation, Assure keeps incidents and records, and TPRM checks the suppliers of your components.

01 · Vulnerability management

How do we track each vulnerability to a fix?

Tenable, Qualys and Rapid7 connectors bring results in about every 4 hours, and any other scanner can send a CSV or use the API. Each vulnerability becomes one issue with an owner and a due date set by its severity. The scanner marks it fixed, the owner verifies it, and an accepted risk goes through an exception.

  • Scanner connectors
  • One issue per vulnerability
  • Due dates by severity
  • Exceptions
See Vulnerability management →
02 · Comply

We already run NIS2. How much is reused?

Adopt the Cyber Resilience Act from the Frameworks library next to NIS2 or ISO 27001. Common Measures are mapped across frameworks, Mapping lists the CRA requirements with no measure yet, and a Product Line scope keeps each product family apart.

  • Frameworks
  • Common Measures
  • Mapping
  • Scopes & Tags
See Comply →
03 · Operate

Where do the risk assessment and the technical documentation live?

Operate keeps the cyber risks of each product with their assets, threats and treatment plans. Technical documentation and your coordinated disclosure policy are Documents with an owner, approvers, numbered revisions and a yearly review.

  • Risks
  • Threats
  • Documents
  • Version history
See Operate →
04 · Assure

How do we record an exploited vulnerability?

Log it as an Incident issue in Assure. Its timeline keeps dated steps with phase labels and the files of each step, and corrective actions carry the root cause until they are verified. Records keep the proof, such as test reports or the SBOM your own tools produce.

  • Incident timeline
  • Corrective actions
  • Records
  • Reports
See Assure →
05 · TPRM

How do we check the suppliers of our components?

TPRM keeps one supplier register. Send questionnaires one at a time or as a campaign, rate each assessment from one to three shields, and follow a daily A to F grade of each supplier’s public security posture.

  • Supplier register
  • Campaigns
  • Rating
  • OSINT grade
See TPRM →

Aiko at your pace

Can AI map our NIS2 measures to the CRA? Aiko proposes. You confirm.

In Mapping, Run AI ranks the best measures from your own library for each CRA requirement with no measure, each with a confidence score and a reason. Nothing is linked until you apply it.

  1. Aiko proposes

  2. You confirm

  3. You set the pace

  • Risks that know their vulnerabilities

    Ask Aiko whether a risk is still rated right, and it includes the open vulnerable items on the risk’s assets, with their source and date.

  • Some things always ask first

    Admins set the highest mode for each action.

  • Every step on record

    Every Aiko action goes into the Activity log.

One Aikoacross Acuna GRC. Add a module and it helps there too. How Aiko works

Swiss experts

Can experts assess where we stand on the CRA? Yes, with a gap assessment.

Our experts run a Cyber Resilience Act gap assessment with your team in Acuna GRC, then help you plan the measures that are missing.

  • Jean-Emmanuel Rodriguez

    Cybersecurity governance expert

    Jean-Emmanuel Rodriguez

    Gap analysis and framework implementation
  • Laura Menetrey

    Legal and compliance expert

    Laura Menetrey

    GDPR, NIS2, DORA, FADP
  • Bénédicte Sévin

    GRC Consulting team leader

    Bénédicte Sévin

    GRC project leadership
  1. Do it yourself

    You run the program in Acuna GRC, with Aiko.

  2. Done with youGap assessments

    Guidance, reviews and audit preparation with your team.

  3. Done for you

    Our experts run it. You review.

Gap assessment, done with you
  • Check where you stand against the CRA
  • Find what your NIS2 or ISO 27001 work already covers
  • Plan the missing measures with owners

Integrations

Can Acuna GRC pull in our scanner results? Yes, with 100+ connectors.

Connectors bring in vulnerability results from Tenable, Qualys and Rapid7, dependency alerts from GitHub Dependabot and security data from your code and cloud tools, on a schedule.

Animation: a robot arm takes data from Microsoft Entra ID, Microsoft Defender, Azure, AWS, GitHub and Jira and puts it on a belt into your workspace in Acuna, where your evidence, KPIs and security alerts stay current.

  • Tenable
  • Qualys
  • Rapid7
  • Dependabot
  • GitHub
  • GitLab
  • Defender
  • AWS
  • Azure
  • Jira
  • ServiceNow
  • 100+ connectors in all
  • Your tools feed Acuna GRC

    Connectors pull security data on a schedule, and API keys let your own systems push data in. Every call is logged.

  • Missing a connector? We build it.

    We design the integration around your setup. Every native connector we have exists because a client needed it.

  • Fixes land where your team works

    Tasks sync both ways with Jira and ServiceNow. See Integrations and API

FAQ

What else do buyers ask about CRA software?

Are our products in scope of the CRA?

It depends on what you place on the EU market and your role as manufacturer, importer or distributor. Our answer page walks through who the CRA applies to. Who does the CRA apply to?

Does Acuna GRC report vulnerabilities to ENISA for us?

No. You submit the report yourself. Acuna GRC keeps the incident record and its timeline, so the facts are ready when you report. CRA reporting deadlines

Does Acuna GRC give us the CE marking?

No. Conformity assessment and the CE marking stay with you and, where required, a notified body. Acuna GRC runs your measures and keeps the evidence. CRA conformity assessment and CE marking

Does Acuna GRC scan our products or generate an SBOM?

No. Acuna GRC is not a scanner and does not generate SBOMs. It brings in your scanner’s results, and you keep the SBOM from your own tools as a record.

We also need NIS2. Can both run together?

Yes. Measures are shared across frameworks, so the CRA and NIS2 link to the same measures and the same proof. NIS2 compliance software

Where is our data hosted?

In Switzerland, the EU or the US, as you choose.

Preparing for the CRA? Start with one step.

Tell us about your products and the frameworks you already run. We show you the CRA in Acuna GRC, and how our experts can assess where you stand.

Hosted in Switzerland, the EU or the US