Start a project

Service

EU Cyber Resilience Act readiness

Reporting duties have applied since 11 September 2026 and the main obligations follow on 11 December 2027. We turn the regulation into an engineering plan — and help you deliver it.

A good fit if…

  • You sell software or connected products to customers in the EU — including from the UK.
  • You aren’t sure whether you could report an actively exploited vulnerability within 24 hours.
  • You need SBOMs, a support policy and technical documentation, but don’t know where to start.

What we do

Scope & classification

Which products are in scope, and whether any fall into the “important” or “critical” categories.

Gap analysis

Your products and processes measured against the CRA’s essential requirements, with a prioritised plan.

Reporting readiness

Vulnerability intake, 24-hour triage, and a rehearsed path to ENISA early warnings and notifications.

SBOM pipeline

Machine-readable SBOMs generated in your builds and kept up to date with each release.

Secure development evidence

Threat models, secure defaults, vulnerability scanning and update processes — recorded as you go.

Technical documentation

The documentation set for conformity assessment, built from real engineering artefacts.

What you get

  • Scope and classification of your products
  • CRA gap analysis and plan to December 2027
  • Working vulnerability-handling and reporting process
  • SBOM pipeline and documentation set

How an engagement runs

  1. Diagnose (1–2 weeks). We read the code and the data, and agree the baseline and the number we expect to move.
  2. Prove (3–5 weeks). A thin, real slice in production, measured against that baseline.
  3. Scale and hand over. Widen the change with your engineers, then leave docs, runbooks and a team that owns it.