For manufacturers of connected products
We help you get (and stay) compliant with the EU Cyber Resilience Act
Many hardware devices and downloaded software sold in the EU will need to be compliant with the CRA from December 2027. That means creating a technical file, support through audit, and to meet ongoing obligations. Xyan Labs works with your team to advise on and develop compliant processes and docs.
Book a call Check if the CRA applies
or email [email protected]
Who we work with
Manufacturers selling connected products in the EU
Device makers, machine builders, and companies with an app or a cloud service behind their hardware. The CRA covers nearly all of them. Where you start depends on how much you know already.
Which of these sounds like you?
-
“We're not sure whether the CRA covers our products.”
The CRA checker gives you a first answer in a few minutes. The assessment then puts it in writing. Start the CRA checker
-
“We know the CRA covers our products, but not what it asks of us.”
The CRA assessment works that out for each product and ends with a plan. The CRA assessment
-
“We need our CRA technical file written, and kept up to date after launch.”
We can write it with your engineers and review each release after launch, or give your team the templates and guidance to write it and keep it current. Writing the file and keeping it current
-
“We already sell connected products in the EU and need a way to report vulnerabilities.”
We set up vulnerability handling with your team: your components watched for known vulnerabilities, and a reporting process built around the deadlines. With post-market support, we assess and report them with you. After launch
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.
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.
How we work
Proportionate compliance
We work with your team to add the processes the CRA needs, shaped around how you already plan, build and release. Your tools and CI do the routine checking, so the file keeps up with the product without anyone chasing it.
We're pragmatic about it. The CRA asks for security that fits each product's risks, so a smart plug and a firewall don't get the same file. We write down what you already do, close the gaps that matter, and stop there.
-
Processes that fit your team
We start from how you plan, review and release, and add the steps the CRA needs to that. A small team gets a short process.
-
Your tools and CI keep it on track
Our command-line tools trace each risk to its mitigations and to the tests that verify them. The trace is kept in your own systems, and CI flags a gap before a release goes out.
-
The risk assessment sets the depth
For each essential requirement, the file says how far the product goes and why. Most products are in the default class and can be self-assessed; we suggest a notified body only where the class requires one.
Who you'll work with
Ben Howes
Founder
Before Xyan, Ben was Director of Technology at a leading healthtech regulatory consultancy working with clients on regulated software medical devices for UK, EU, and US markets. Ben has also been CTO at Neuronostics and ran Zoetrope labs, an IoT consultancy. Over these experiences, Ben has designed, coded, and documented regulated devices, as well as working on hardware and CE marking embedded devices. Ben's clients have ranged from two-person startups through to multinational organisations.
Blog
Recent articles
-
Our product only has a USB port. Is it in scope of the CRA?
Almost certainly. A USB port that carries data is a physical data connection, and the CRA covers those whether or not the product ever reaches a network. A port that only charges is a different case.
-
Article 14 reporting is live: what the 24-hour clock asks of you
Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours, for products already on the market too.
-
Is your product in scope of the CRA? Five questions that decide it
Scope under the Cyber Resilience Act turns on five questions. Most products answer them quickly; the ones that do not need a written rationale.
Talk to us
Book a 30-minute call with Ben
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