OfferCRA readiness sprint

    Know what the Cyber Resilience Act asks of your device, and what to fix first

    For makers of connected devices and firmware selling into the EU. In three weeks we check one product against the CRA, rank the gaps and write a plan with fixed-price follow-on work.
    Short answer

    Since 11 September 2026 you must report actively exploited vulnerabilities and severe incidents within 24 hours. From 11 December 2027 every connected product you place on the EU market must meet the CRA's security requirements, ship with an SBOM and technical documentation, and get security updates for its support period. The sprint tells you where one product stands on all of it.

    Run the CRA check first
    SprintFixed scope
    Duration3 weeks
    Scopeone product or firmware
    PriceFixed price, agreed before the sprint starts
    You providefirmware source or builds, hardware, how you ship updates and handle vulnerabilities today
    You getproduct class, gap list ranked by urgency, written plan with fixed-price follow-on work
    Three weeks to a written planProduct → plan
    1. 01Product and classin scope? · conformity route
    2. 02Firmwareboot, updates · keys, attack surface
    3. 03ProcessSBOM, reporting · support period
    4. 04Plangaps by urgency · fixed-price follow-on

    Scope

    What the sprint covers

    • Scope and class. Whether the product is in scope, which class it falls in, and whether you can self-assess or need a notified body.
    • Firmware. Secure by default, secure boot, signed updates with rollback protection, automatic security updates, protected keys and data, minimal attack surface, resilience and logging.
    • Process. SBOM, vulnerability handling, coordinated disclosure, the 24-hour reporting duty, the support period you declare, and the risk assessment and technical documentation.
    • EN 18031. For wireless products, what you already meet under the Radio Equipment Directive and what the CRA adds on top.
    • Plan. Each gap with its urgency, the fix and who owns it, and a fixed-price quote for the follow-on work if you want us to do it.

    Fit

    When the sprint fits

    Use it when you

    • sell a connected device or firmware in the EU and have not mapped it against the CRA yet
    • need to know your product class before you plan the work or talk to a notified body
    • have no SBOM, vulnerability handling or 24-hour reporting process in place
    • need a plan and a fixed price to put in front of your board before 11 December 2027

    Skip it when

    You already have a gap assessment and a plan, and need engineers to carry it out. See engineers in your team.

    After the sprint

    If you want us to fix the gaps

    We are firmware and systems engineers. We implement secure boot, signed over-the-air updates, key storage and SBOM generation, and write Rust firmware that removes memory bugs from new code. The follow-on work is quoted at a fixed price in the plan; you decide after the sprint.

    Proof

    Device work we delivered

    All work
    Case · Devices · Europe

    Devices that prove where they are

    Problem
    Signed proof of physical presence that nobody can fake.
    Built
    Rust firmware on ESP32-C6, radio lab research, signed proofs.
    RustESP32-C6Embedded firmwareWi-Fi FTM
    Firmware to chain, signed off sprint by sprint.
    Case · AgTech · Europe

    Fertiliser sprayer, from hardware to field app

    Problem
    Operators had to run a sprayer from a tablet, offline.
    Built
    We assembled the sprayer and built its Android control app.
    Hardware assemblySprayerAndroidIonic
    A working sprayer, run from a tablet next to the machine.
    Case · Location proof · Global

    Proof of location, built on sensor fusion

    Problem
    Prove where a device is without trusting the device.
    Built
    Signal-harvesting mobile apps, token contracts, Java back end.
    Proof of locationSensor fusionEthereumEOS
    MVP and token contracts that reward confirming nodes.

    FAQ

    Common questions

    Q01Does the CRA apply to products we already sell?

    The product requirements apply to products placed on the EU market from 11 December 2027; each unit you sell after that date must comply, even if the model launched earlier. The reporting duty for actively exploited vulnerabilities and severe incidents has applied since 11 September 2026.

    Q02Is the sprint useful if we fix the gaps ourselves?

    Yes. The gap list and the plan are yours, and your own team or any other can work from them.

    Q03We already meet EN 18031. Do we still need this?

    EN 18031 covers part of the CRA's product requirements for wireless devices. The CRA adds the vulnerability handling process, the SBOM, the support period, reporting and the technical documentation, and the sprint checks those too. See the EN 18031 guide.

    Q04Is this legal advice?

    No. It is an engineering view of your product against the public text of the regulation. Your notified body or legal adviser has the final word on conformity.

    Next step

    Tell us about the device

    A 30 minute call with Mykhailo about your product, its class and what has to be ready by December 2027. After it you get the sprint scope in writing.

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger