Join our Newsletter — 33% off our NHI Course
Home› Guides› Matter Device Attestation and Security Guide: Certificates and…
Guide OT & IoT Security

Matter Device Attestation and Security Guide: Certificates and Commissioning

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Matter gives every certified smart home device a manufacturer-issued X.509 identity, and the security of the whole ecosystem depends on how well device makers protect those keys and how strictly commissioners check them. Device attestation is the step in commissioning where a controller proves a device is genuine and certified before it joins a fabric. It rests on a three-tier PKI (PAA, PAI, DAC), a signed Certification Declaration, and the Connectivity Standards Alliance's Distributed Compliance Ledger (DCL), which publishes trusted roots, certification status, revocation points and software update metadata. This guide explains how those parts fit together, what a commissioner actually verifies, how revocation works, and what manufacturers, platform owners and enterprise buyers should control. It is written for IoT product security engineers, PKI teams and security architects responsible for connected devices.

Key takeaways

  • Attestation is a device identity check, not a user check. The CSA states that a Matter device cannot join a fabric unless proven genuine, using an attestation key pair and an X.509 certificate chained to a trusted authority.
  • The chain is PAA to PAI to DAC, plus a Certification Declaration. The commissioner validates the chain to a trusted PAA, checks vendor and product IDs match across the chain, verifies the attestation signature over a fresh nonce, and validates the signed Certification Declaration.
  • The DCL is the public trust anchor store. Anyone can read it; writes require accounts with roles (Trustee, Vendor, VendorAdmin, CertificationCenter, NodeAdmin), and root certificates need multiple Trustee approvals.
  • Revocation is now part of the model. Vendors publish CRL distribution points for PAAs and PAIs on the DCL, and the reference SDK fails commissioning with explicit codes when a DAC or PAI is revoked.
  • The DAC private key is the crown jewel. Whoever holds it can make a counterfeit look certified, so factory provisioning, secure storage and PAI issuance controls matter more than anything on the device's network interface.

The Matter device attestation PKI

Matter separates two identities. The attestation identity is installed at manufacture and proves what the device is. The operational identity (a Node Operational Certificate, NOC, issued under a fabric's root, RCAC) is issued during commissioning and proves membership of a particular fabric. This guide is about the first; the second is an ecosystem PKI run by each controller or platform.

ElementWhat it isWho controls itKey security property
PAA (Product Attestation Authority)Root certificate for device attestation, published on the DCLA vendor (VID-scoped PAA) or a third-party PKI provider (non-VID-scoped PAA)Must be approved on the DCL; non-VID-scoped PAAs, per the CSA, passed an audit against the Alliance PKI Certificate Policy
PAI (Product Attestation Intermediate)Intermediate CA that issues DACsThe vendor or its PKI providerCarries the Vendor ID; may also be scoped to a Product ID
DAC (Device Attestation Certificate)Leaf certificate with the device's attestation public keyIssued per device at manufactureCarries Vendor ID and Product ID; private key never leaves the device
Certification Declaration (CD)CMS-signed statement that a product (Vendor ID, Product IDs, device type) is certifiedSigned by a CSA CD signing keyCertification type field distinguishes development and test, provisional and official
DCLPermissioned ledger of PAAs, models, model versions, compliance status and revocation pointsCSA members run nodes; CSA trustees approve accounts and rootsPublic read, signed and role-authorised writes, consensus

The Certification Declaration format in the reference SDK includes vendor ID, product IDs, device type ID, security level and information, version number, certification type, an optional DAC origin vendor and product ID (used where a product is built on another vendor's certified module), and an optional authorised PAA list. The DCL itself uses one certificate entity for PAA, PAI and the operational roots, with NOC root certificates distinguished by an isNOC field.

What the commissioner verifies

The open source Matter SDK (project-chip/connectedhomeip) is the reference implementation most commissioners build on. Its default verifier performs the checks below, and each failure maps to a defined result code that is useful in logs and support cases.

Check (in order of the reference verifier)Failure code examples
Attestation response present and within size limits; PAI suppliedkInvalidArgument (701), kPaiMissing (207)
PAI and DAC certificate formats validkPaiFormatInvalid (203), kDacFormatInvalid (303)
DAC Vendor ID equals PAI Vendor ID; DAC has a Product ID; if the PAI has a Product ID it matches the DACkDacVendorIdMismatch (305), kDacProductIdMismatch (306)
Attestation signature, made with the DAC private key over the attestation elements and challenge, verifieskAttestationSignatureInvalid (500)
PAA found in the trust store by the PAI's authority key identifier; PAA Vendor ID (if present) matches the PAIkPaaNotFound (101), kPaiVendorIdMismatch (205)
DAC valid at current time; chain PAA to PAI to DAC validateskDacExpired (300), kPaiExpired (200), signature errors
Attestation nonce matches the one the commissioner sentkAttestationNonceMismatch (502)
Certification Declaration signature verifies with a known CD signing key, and its Vendor ID, Product ID and authorised PAA list are consistent with the chainkCertificationDeclarationInvalidSignature (602), kCertificationDeclarationInvalidVendorId (604), kCertificationDeclarationInvalidPAA (606)
Revocation status of DAC and PAI against a revocation setkDacRevoked (302), kPaiRevoked (202), kPaiAndDacRevoked (208)

The nonce check is what stops a captured attestation response being replayed by a clone. The chain and CD checks are what stop a device signed by an unapproved CA, or an uncertified product, from looking legitimate. A commissioner that skips any of them, or that reports failures to the user but lets them continue anyway, weakens the whole scheme. The reference SDK's chip-tool uses a built-in test PAA unless pointed at a real trust store with --paa-trust-store-path; the development PAA and the test CD signing key in the repository are explicitly marked for development only and must never be trusted in production.

The Distributed Compliance Ledger as a trust service

The DCL is a public permissioned ledger based on CometBFT and Cosmos SDK. Anyone can read it; to write, an account must exist on the ledger with a role, and every transaction is signed with the account's private key. The CSA describes it as permissionless for reads and requiring authorised accounts for writes, with keys pre-approved by DCL trustees.

DCL roleWhat it can do (per the DCL project documentation)Control to apply
TrusteeCreate and approve accounts, approve root certificates (a root becomes approved after N or K% of Trustee approvals, with proof of private key possession)Multi-party approval; hardware-protected keys
VendorPublish vendor info, models and model versions, add PAIs chained to an approved PAA, revoke its own certificates, publish revocation distribution pointsTreat the vendor account key as a high-value machine credential: HSM or hardware wallet, named custodians, separation from build systems
VendorAdminAdd and update vendor info for any vendor; manage any model and model versionReserved for CSA operations
CertificationCenterCertify and revoke models (provisional, certified, revoked states)Reserved for certification bodies
NodeAdminAdd validator nodesProof of authority onboarding of node operators

Model version records on the DCL carry software update metadata including otaUrl, otaFileSize, otaChecksum and checksum type, and the minimum and maximum applicable software versions. That makes the DCL part of the firmware supply chain: an OTA provider can check that an image matches the checksum the vendor published. Clients that do not run their own node can use a Light Client Proxy, which verifies state proofs for single-value queries against untrusted full nodes.

Revocation of DACs and PAIs

The DCL's device attestation PKI revocation design lets a vendor publish, update or delete the location of a CRL distribution point for a PAA (to revoke PAIs) or for a PAI (to revoke DACs). Each distribution point record carries Vendor ID, optional Product ID, whether it relates to a PAA, a label, the CRL signer certificate, the issuer subject key ID, a data URL, optional file size and digest, and a revocation type (type 1 is an RFC 5280 CRL). Validation rules require a PAA CRL signer to already be on the ledger and a PAI CRL signer to chain to an approved PAA. Publishing a distribution point does not automatically remove revoked PAIs or DACs from the ledger: commissioners must fetch and apply the CRLs. The reference SDK accepts a pre-built revocation set and its test vectors show commissioning failing with kPaiRevoked, kDacRevoked or kPaiAndDacRevoked.

  • Manufacturer duty: run a CRL for every PAI and PAA you operate, publish its distribution point on the DCL, and have a tested procedure to revoke a batch of DACs if a factory or key store is compromised.
  • Commissioner duty: refresh revocation data on a defined schedule and fail closed on revoked DACs and PAIs.
  • Buyer duty: ask suppliers whether their PAIs have published revocation points and how quickly they can revoke.

For CRL mechanics and the trade-offs against OCSP, see the Certificate Revocation Guide.

Manufacturing and key protection

The attestation key is created or injected in the factory, and that is where most real risk sits. The CSA's Matter security white paper recommends secure manufacturing, with device identity and firmware provisioned in trusted facilities, and hardware platforms with secured cryptographic key storage proportionate to the product's threat analysis. Silicon vendors document concrete patterns in the SDK tree, for example a pre-provisioned secure certificate partition holding the DAC and PAI with the Certification Declaration in a factory data partition, or keys held in a secure element.

  1. Decide where keys are generated. Prefer on-device key generation in a secure element or protected key store, with only the certificate signing request leaving the device. If keys are injected, the injection station is in scope for the PKI audit.
  2. Separate PAI issuance from the production line. The PAI private key belongs in an HSM with quotas, logging and dual control. A line that can request unlimited DACs is a counterfeiting line.
  3. Use a distinct Product ID scoped PAI where practical. Narrow scope narrows the blast radius if a PAI must be revoked.
  4. Disable debug access before shipment. JTAG or serial debug on a production unit can expose the DAC key, which defeats attestation for that device and, if keys are shared, for many.
  5. Reconcile counts. Compare DACs issued, devices shipped and devices commissioned. Gaps are the early sign of key leakage or grey-market units.
  6. Pilot and roll back. Validate the full attestation chain against a production-like commissioner before mass production; if a batch fails, quarantine it and revoke the affected DACs rather than shipping with a relaxed check.

Matter is one example of hardware-rooted device identity; for the general model see the IoT Device Identity with TPM and DICE Guide and the Machine Identity, PKI and Certificate Lifecycle Guide.

Beyond attestation: commissioning and operational controls

  • Setup passcode: the SDK enforces the specification's range (1 to 99,999,998) and rejects trivial values such as 11111111, 12345678 and 87654321. Use a random per-device passcode, never a model-wide one, because the passcode protects the PASE session used before attestation completes.
  • PAKE parameters: the SDK bounds the PBKDF iteration count for the SPAKE2+ verifier between 1,000 and 100,000 with a minimum 16-byte salt. Use per-device salts and store a verifier, not the passcode, on the device where the platform supports it.
  • Access control: Matter access control lists grant privileges View, ProxyView, Operate, Manage and Administer per fabric. Limit Administer to the platform controller and review which fabrics hold it, especially after multi-admin sharing.
  • Software updates: the white paper recommends secure OTA updates for firmware and credentials, and firmware integrity attestation. Publish OTA metadata and checksums to the DCL and sign images.
  • Network segmentation: attestation proves provenance, not good behaviour. Matter devices in enterprises still belong on an IoT segment with egress control. See the Zigbee and Thread Security Guide.

Where identity fits

Matter is a clean case study in non-human identity at scale: millions of devices, each with a certificate-bound identity issued by an accountable authority, a public registry of trusted issuers, and a revocation path. The weak points are the same as in any NHI programme: long-lived signing keys held by too many systems, vendor ledger accounts used by build pipelines, and nobody owning revocation. Treat the PAI keys, the DCL vendor account key and the CD-related submission credentials as privileged machine identities with inventory, custodians and rotation plans. See the Non-Human Identity (NHI) Guide.

Detection and measurement

  • Attestation failure rate by code: track commissioning failures by result code. A spike in kPaaNotFound or CD failures for one Product ID can indicate counterfeits or a provisioning error.
  • Revocation freshness: age of the revocation set in each commissioner or platform; target refresh within your defined window, for example daily.
  • DAC issuance reconciliation: DACs issued versus units shipped per batch; target zero unexplained surplus.
  • Key custody events: HSM audit events for PAI signing outside production windows; target zero.
  • DCL record accuracy: percentage of shipped software versions with a DCL model version and valid OTA checksum.

Framework mapping

Matter controlNIST SP 800-53 Rev. 5NIST CSF 2.0
Device attestation during commissioningIA-3 Device Identification and Authentication; SR-11 Component AuthenticityPR.AA-03 users, services and hardware are authenticated
PAA/PAI/DAC PKI and key protectionSC-12 Cryptographic Key Establishment and Management; SC-17 Public Key Infrastructure CertificatesPR.AA-01 identities and credentials are managed
Signed OTA images and DCL checksumsSI-7 Software, Firmware, and Information Integrity; CM-14 Signed ComponentsPR.PS (platform security)
Device inventory and DAC reconciliationIA-3; supply chain controls in SR familyID.AM-01 hardware inventories are maintained

Common failure patterns

  • Development credentials in production: shipping with the SDK test PAA chain or test CD signing key, or a commissioner that still trusts them.
  • Soft failure on attestation: a controller that warns but allows a user to continue with an unattested device, which turns a strong check into a dialog box.
  • No revocation path: PAIs with no published CRL distribution point, so a known compromised batch cannot be blocked. On the commissioner side, the reference verifier logs a warning and skips revocation checks entirely when no revocation delegate is configured, so confirm one is.
  • Shared or extractable DAC keys: keys copied across units or readable through debug ports, so cloning one device clones many.
  • Static setup passcodes: one passcode for a product line, printed in manuals or reused in firmware.
  • Vendor DCL key on a build server: the ledger signing key stored as a plain CI secret, where any pipeline compromise could publish models or revoke certificates.

Practitioner checklist

  • Confirm your PAA is approved on the DCL and your PAIs chain to it; remove any trust in development PAAs from production commissioners.
  • Generate DAC keys in a secure element or protected key store and disable debug interfaces before shipment.
  • Hold PAI keys in an HSM with dual control, issuance quotas and audit logging.
  • Publish CRL distribution points for every PAA and PAI on the DCL and rehearse a batch revocation.
  • Ensure commissioners check nonce, chain, Vendor and Product IDs, Certification Declaration and revocation, and fail closed.
  • Use random per-device setup passcodes and per-device SPAKE2+ salts.
  • Publish every shipped software version on the DCL with OTA URL and checksum, and sign images.
  • Protect the DCL vendor account key as a privileged machine credential with named custodians.
  • Monitor attestation failure codes and reconcile DAC issuance against shipments.

Standards and references

Related NHI Mgmt Group resources: Smart Home Security Guide · IoT Device Onboarding Guide · IoT Secure Firmware Update Guide · PKI Basics Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.