PRODUCT PROFILEGOVERNED REFERENCE

Device & Thing Trust

Select L0–L3 assurance by risk/capability and keep certificate lifecycle separate from runtime appraisal.

RELEASE2026.09

STATUSREFERENCE ARCHITECTURE

AUDIENCEDevice Operations · IoT Operations · Security · Integrators

SOURCE OF TRUTHProduct profile + architecture/evidence registers

PRODUCT FACTS

Select L0–L3 assurance by risk/capability and keep certificate lifecycle separate from runtime appraisal.

A printed carrier, signed data, hardware identity and runtime posture provide different assurance and must not be represented as the same trust level.

Family: Device & Thing Trust
Maturity: REFERENCE ARCHITECTURE
Primary personas: Device Operations · IoT Operations · Security · Integrators
Business objects: Device Identity · Certificate · Attestation · Appraisal · Enforcement Decision
Architecture: P05/P06
Standards: IEEE 802.1AR · RFC 8995/9334/9711 where selected · IEC 62443 / ETSI EN 303 645 context
Last reviewed: 2026-09-02

OPERATING WORKFLOW

From input to evidence-backed state.

Onboard → Bind identity → Issue/rotate certificate → Collect attestation → Appraise → Enforce → Audit

01Onboard

02Bind identity

03Issue/rotate certificate

04Collect attestation

05Appraise

06Enforce

07Audit

Inputs: Carrier/data signature · device certificate · hardware-bound key · attestation evidence · risk context
Outputs: Certificate status · assurance context · appraisal decision · enforcement action evidence
API: Device Attestation API · Connector API
Events: device.attested · device.appraised · device.quarantined
Connectors: Device PKI · attestation verifier · telemetry/operations

Authority: Device CA is authoritative for certificate lifecycle; runtime trust is a separate policy/appraisal decision.
Policy: Risk profile · assurance level · appraisal rules · enforcement policy
Mandate: Administrative action requires device-operations authority.
Evidence: Certificate lifecycle · attestation evidence · appraisal inputs/decision · enforcement audit
External dependencies: Device hardware capability · PKI/attestation stack

ACTUAL PRODUCT UI

Approved reference screen from the UI/UX package.

No website-made screenshot replacement.

Dashboard OverviewTTID--M01-L01-001 · 09_DEVICE_THING_OPERATIONS_CONSOLE.zip

BOUNDARY & EVIDENCE

Decision boundaries stay explicit before deployment.

Failure & recovery

Failure modes: Expired/revoked certificate · failed attestation · unsupported capability · stale evidence
Retry / recovery: Rotate/reissue certificate; re-attest; quarantine or restore after policy-qualified evidence.
Limitations: Device Certificate Status ≠ Runtime Device Trust; Ownership/Custody ≠ Device Certificate ≠ Runtime Trust.

Implementation links

Related portals: Device / Thing Operations · Operations Admin
Related scenarios: RS-07
Architecture: P05/P06
Standards: IEEE 802.1AR · RFC 8995/9334/9711 where selected · IEC 62443 / ETSI EN 303 645 context

READINESS PASSPORT

Readiness is scoped—not a certification claim.

PROFILE IDTTID-DEVICE_THING_TRUST-2026.09

MATURITYREFERENCE ARCHITECTURE

ARCHITECTUREP05/P06

ACTUAL UIEMBEDDED

API CONTRACTREFERENCE

CONFORMANCEREFERENCE / PROJECT GATE

SECURITYDEPLOYMENT-SPECIFIC

EXTERNAL DEPENDENCYDevice hardware capability · PKI/attestation stack

LAST REVIEWED2026-09-02

EVALUATE / PILOT

Pilot L0–L3 on representative devices and review negative attestation/enforcement paths.

Review Product Readiness Explore API Center Reference Architecture