Guide · 7 min read
Device identity from manufacture to retirement
A practical architecture for provisioning, attestation, signed updates, recovery, and evidence across the life of a connected product.
Read the guideIdentify, update, isolate, and recover the systems you operate.
A device identity is useful when it survives the realities of manufacturing, deployment, maintenance, and incident response. These guides connect provisioning and attestation with the decisions to authorize, update, revoke, and retire a system.
Start with a question
Guide · 7 min read
A practical architecture for provisioning, attestation, signed updates, recovery, and evidence across the life of a connected product.
Read the guideField note · 5 min read
A proposed approval pattern that preserves a binding decision and the full review record for trust lists, signing releases, and other consequential changes.
Read the field noteGuide · 7 min read
Build certificate operations that can handle shorter lifetimes, changing trust policies, and the next algorithm transition.
Read the guidePractical guide · 6 min read
A practical operating model for secure releases, vulnerability response, and EU Cyber Resilience Act readiness.
Read the practical guidePractical guide · 5 min read
Build a decision around operating costs, required capabilities, and testable risk reduction. Make every assumption visible.
Read the practical guideFrance’s refrigeration attack hit about 700 supermarkets. What manufacturers need to learn about remote access, local control and OT security.
CRA reporting duties are live. Can your team identify affected product versions and file an early warning within 24 hours of awareness?
Forescout’s segmentation findings challenge the assumption that OT is isolated. NIST’s new draft shows how stronger architecture, device identity, trusted updates, and tested recovery can narrow the gap.