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.
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.
| Duration | 3 weeks |
|---|---|
| Scope | one product or firmware |
| Price | Fixed price, agreed before the sprint starts |
| You provide | firmware source or builds, hardware, how you ship updates and handle vulnerabilities today |
| You get | product class, gap list ranked by urgency, written plan with fixed-price follow-on work |
Scope
Fit
Use it when you
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
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
FAQ
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.
Yes. The gap list and the plan are yours, and your own team or any other can work from them.
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.
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.
Related
What your firmware, updates and vulnerability handling still need, in a few minutes.
ToolDates, product classes, the firmware and process checklist and a 12-month plan.
GuideRED cybersecurity for wireless devices, and how it leads into the CRA.
GuideSignals, embedded, cryptography and blockchain, when it is not yet clear what can be built.
DirectionNext step
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
