Compliance
Evidence, not attestations about attestations
Compliance as a by-product of how the system works.
Regulation has caught up with connected devices. Praecise Furcate produces the evidence as it runs: which device, which firmware, which vulnerability, which update, who approved what, and what was refused.
01
What applies now
Dates already in force.
The obligations are live; most fleets have no tools for them.
Praecise Furcate maps each obligation to something the system already records, rather than to a separate process people have to remember.
| Regime | Status | What Praecise Furcate provides |
|---|---|---|
| EU Cyber Resilience Act | Vulnerability and incident reporting since 11 September 2026; full obligations from December 2027 | Drafts for the 24-hour, 72-hour and 14-day reports, SBOM per device and adapter, signed update evidence |
| Radio Equipment Directive, EN 18031 | Applies to radio products since 1 August 2025 | Credential state per device as evidence; Furcate hardware designed to it |
| IEC 62443 | Industrial security practice | Zones and conduits as device segments; signed orders; audit in the ledger |
| GDPR and the EU AI Act | Video of people is personal data; biometric identification restricted | Redaction before egress, sealed originals, approvals recorded |
| ONVIF Media Signing | Final specification due end of 2026 | Verification and chaining of signed video from cameras |
02
Evidence the system keeps anyway
Recorded because the system needs it, usable because it is signed.
The ledger is the audit.
Every order, approval, refusal, update and posture change is chained in the ledger. An auditor reads the same record the operator acts on.
- 01
Who did what
Orders, approvals and refusals, with the passkey assertion attached.
- 02
What ran
Adapter and firmware hashes on every reading; measured boot on every node that supports it.
- 03
What changed
Updates as signed images, with the evidence they were applied and the previous image kept.