Services

From the first assessment to support after launch

Every engagement starts with an assessment of your products. After that you choose how much of the work we do. Your team can write and maintain the technical file with our templates, or we can do it with them.

Book a call Try the CRA checker first

Where to start

Start with a CRA assessment

Every engagement starts here. At the end you'll have a gap assessment, and a roadmap for compliance, and what to do next.

From your side, a few hours with the people who know the product and the documents you already have. We go through the findings with you on a call.

Book a call

What you get

  • Scope and class, in writingWhether the CRA applies to each product, which class it falls in and how its conformity is assessed, with our reasoning for any borderline call.
  • Gap assessmentWe go through each of the CRA's essential cybersecurity requirements and note what the product already does, what's partly there and what's missing.
  • Next-steps planThe work to do, in order, and who could do each piece: your team, us or a test lab.

After the assessment

Writing the technical file, and post market obligations

With the assessment's plan in hand, you can decide how much more support you want from Xyan

01Writing the file

Templates and guidance

Your team writes the file from our templates, with a set budget for questions and review.

or

Full service

We write the file with your engineers and set up vulnerability handling. You sign the EU declaration of conformity at the end.

02After launch

Self-serve

Your team keeps the file current and handles vulnerabilities, with our templates and a set budget for questions.

or

Post-market support

We review each release and design change with your team, and help you assess and report vulnerabilities.

The work in detail

What the CRA asks, before and after launch

The work for one product, from the first question to the end of its support period. The assessment covers the fundamentals and the plan. Your team can do the rest from our templates, or we can do it with them. If you only need one piece, ask.

A full set of templates. We have templates for the documents in each part of the work, before and after launch, ready to start from. Each is mapped to the standards that apply, so an auditor, a notified body or your own team can find the evidence for any clause.

Pre-market

Before the product goes on the EU market.

  • Fundamentals: scope and classIn the assessment
    • Whether the CRA applies
    • Default, important or critical, and the conformity route
    • Your role, and the support period
  • Gap assessment and planningIn the assessment
    • Each essential requirement checked against the product
    • The work to do, in order, and who does it
  • Cybersecurity risk assessment
    • Threats, and the controls that treat them
    • A method you can rerun for each release
  • Processes and traceability through development
    • Secure development and vulnerability handling, in your lifecycle
    • Each requirement traced to its control and its test
    • An SBOM from your build
  • Technical file and declaration
    • The technical documentation
    • Conformity assessment, with a notified body where the class needs one
    • The EU declaration of conformity and user information

Post-market

For the support period, once the product is on the market.

  • Keeping the file current
    • An assessment of each release
    • The risk assessment updated when something changes
  • Vulnerability handling
    • Components watched for known vulnerabilities
    • Security updates through the support period
    • Vulnerabilities in a component reported to its maintainer
  • Reporting to the authorities
    • Actively exploited vulnerabilities and severe incidents
    • Early warning in 24 hours, then 72 hours, then a final report
    • Telling your users what to do
  • Requests from authorities
    • The file and declaration kept for at least ten years
    • Evidence ready when an authority asks for it

The standards we work to

We use the published standards your product and market need, and map the file to the CRA's own harmonised standards as they're finished. None of those is cited in the Official Journal yet.

  • IEC 62443-4-1The secure development lifecyclePublished
  • IEC 62443-4-2Security requirements for componentsPublished
  • EN 18031-1, -2 and -3Radio equipment, under the Radio Equipment DirectivePublished
  • ETSI EN 303 645Consumer connected productsPublished
  • ISO/IEC 29147 and ISO/IEC 30111Vulnerability disclosure and handlingPublished
  • BSI TR-03183German guidance on SBOMs and vulnerability reportsGuidance
  • EN 40000-1 seriesThe CRA's horizontal standardsDraft
  • Product-specific CRA standardsImportant and critical productsDraft

Working with your teams

Your engineers keep releasing, and the file keeps up

Most of the CRA's duties land on how the product is built and released, so most of the day-to-day work falls to engineering. The file, the declaration and any questions from an authority sit with whoever owns compliance. We work with both teams and agree with them who does what.

By the end, your engineers know what each release needs, and your compliance team can see that it was done.

  • Engineers work in their own tools

    Requirements are written as things they can build and test, and kept where the team already works, such as a shared repository or Google Docs. When the product changes, its evidence changes with it.

  • A file your compliance team can stand behind

    It follows Annex VII, traces each requirement to its evidence and fits into the ISO/IEC 27001 or ISO 9001 system you already run. Whoever signs off a release has its evidence in front of them.

  • One release process both teams agree to

    What engineering checks, what compliance signs and which changes call for a fresh look at the risk assessment, kept short enough that people follow it.

  • Your team carries it on

    We take the people who'll run the process through it on your own products, and checks in CI flag missing evidence before a release goes out.

AI

AI for the mechanical work, people for the judgement

AI is good at the repetitive parts of compliance work. It can go through a long standard one requirement at a time, compare two versions of a document or find every mention of a component. We use it for that, and for systematic review, where it checks a whole file the same way every time.

  • Drafts that show their sources

    Many teams already use AI to draft documentation. We help you set it up to draft from your own sources and the regulation's text, with each statement pointing to where it came from.

  • Checks before anything goes in the file

    Your review should catch a reference that doesn't exist, or doesn't say what the draft claims, before an authority does. We build those checks into how you review the file.

  • Confidential material stays where it belongs

    We agree with you which AI tools may see your source code, test reports and unfixed vulnerabilities, and which may not.

  • AI in your product is a separate question

    If the product itself uses AI, the AI Act may apply alongside the CRA, and we plan the two together.

Talk to us

Book a 30-minute call

Tell us what the product does and where you sell it. We'll talk through what the CRA is likely to ask of it, and whether an assessment is worth doing.

Book a call or email [email protected]

Useful to have to hand

  • What the product is and how it connects
  • Where you sell it, and who places it on the EU market
  • How often you release software or firmware
  • Any date you're working towards

Questions

Common questions

Are you a notified body?

No. We prepare you and your file. Where your product needs third-party assessment, we prepare the file for the notified body you choose and support you through it.

Is this legal advice?

No. Our work is technical: classification rationale, risk assessment, technical documentation and the processes behind them. Where a question needs a lawyer, we say so and work alongside your counsel.

Who owns the file?

You do. It lives in your own systems, such as a shared repository or Google Docs, and it stands on its own if you stop working with us.

What does it cost?

It depends on the products, their class and how much evidence you already have. We agree the assessment once we know which products it covers, and price writing the file and support after launch from its plan. Book a call and we'll talk it through.

We have several products. Do we need an assessment for each?

No. One assessment can cover a family of products that share hardware, software and a release process. Where products differ, we say which ones need their own and why.