Security, identity and trust
Trusted Platform Module
A hardware root of trust that holds keys, measures boot and signs attestation evidence.
We design and integrate.
TCG TPM 2.0 Library Specification · ISO/IEC 11889
Global Privacy Control detected. We have honored it as your request to opt out of the sale and sharing of your personal information and of targeted advertising.Signal Global Privacy Control détecté. Nous l'avons respecté comme une demande d'opposition à la vente et à la communication de vos renseignements personnels ainsi qu'à la publicité ciblée.
Cookie policyPolitique relative aux témoins Privacy policyPolitique de confidentialité Do Not Sell or Share My Personal InformationNe pas vendre ni communiquer mes renseignements personnels
Your browser sent a Global Privacy Control signal. We treat it as a refusal for the purposes marked below, and those switches stay off.Votre navigateur a envoyé un signal Global Privacy Control. Nous le traitons comme un refus pour les finalités indiquées ci-dessous, et ces interrupteurs restent désactivés.
Needed for the site to work, to keep you signed in, to protect it from attacks and to remember your privacy choices and the settings you pick. Always on.Nécessaires au fonctionnement du site, pour vous garder connecté, le protéger contre les attaques et retenir vos choix de confidentialité et les réglages que vous choisissez. Toujours actifs.
Remember optional settings beyond the ones you pick yourself. Off until you allow it.Retenir des réglages facultatifs autres que ceux que vous choisissez vous-même. Désactivés tant que vous ne les autorisez pas.
Count visits and see how pages are used, so we can improve the site. Off until you allow it.Compter les visites et voir comment les pages sont utilisées, afin d'améliorer le site. Désactivés tant que vous ne les autorisez pas.
Show videos, maps and live data layers from other providers. They receive your IP address and may set their own cookies. Off until you allow it, or load a single item once.Afficher des vidéos, des cartes et des couches de données en direct d'autres fournisseurs. Ceux-ci reçoivent votre adresse IP et peuvent déposer leurs propres témoins. Désactivés tant que vous ne les autorisez pas, ou chargez un seul élément une fois.
Measure campaigns and personalise advertising. We use none today. Off until you allow it, and refused when your browser sends Global Privacy Control.Mesurer les campagnes et personnaliser la publicité. Nous n'en utilisons aucun actuellement. Désactivés tant que vous ne les autorisez pas, et refusés lorsque votre navigateur transmet le signal Global Privacy Control.
Nexus Observatory Inc. keeps a record of each choice as proof: a random consent ID, the time, your region and the rules applied, the choices, the notice shown, the page, a shortened IP address, a one-way code of your browser type and, if you are signed in, your account. Records are kept while your choice applies and for 3 years after, then deleted.Nexus Observatory Inc. conserve un registre de chaque choix à titre de preuve : un identifiant de consentement aléatoire, l'heure, votre région et les règles appliquées, les choix, l'avis affiché, la page, une adresse IP abrégée, un code à sens unique du type de navigateur et, si vous êtes connecté, votre compte. Les registres sont conservés tant que votre choix s'applique et pendant 3 ans par la suite, puis supprimés.
Untick to choose for this site only. You can change either at any time in Privacy choices.Décochez pour choisir pour ce site seulement. Vous pouvez modifier l’un ou l’autre à tout moment dans Vos choix de confidentialité.
Identity and attestation: a node’s trust module answering a challenge from the verifier. The loop, step by step: 1. A node, its security module and a verifier. 2. Sensor, link, edge and console stand ready. 3. The node boots and measures its own software. 4. Time and place are fixed to every sample. 5. The module signs the measurements. 6. The quote travels to the verifier. 7. The relay forwards sealed packets untouched. 8. Signatures are checked before any model runs. 9. The verifier compares it with the known-good set. 10. The edge releases confirmed results only. 11. A short-lived credential is issued. 12. The console shows the evidence with the alert. 13. The node joins with its credential. 14. Sensors check that the response worked. 15. Record, proof and action are archived together. 16. Everything settles back to idle.
01 / 16
A node, its security module and a verifier
Nexus Observatory/
Security and trust/
Identity and attestationIdentity and attestation, inside Security and trust: Trusted Platform Module, DICE layered identity, secure device identifiers, remote attestation architecture and more. Every item is traced to its specification, from TCG TPM 2.0 Library Specification to ISO/IEC 11889, and runs on the open Observatory Protocol.
Plan with usArchitectureThe protocolAt a glance
A hardware root of trust that holds keys, measures boot and signs attestation evidence. In identity and attestation, part of Security and trust, the device identity and attestation layer holds Trusted Platform Module, drawn against TCG TPM 2.0 Library Specification and ISO/IEC 11889 and used beside secure elements on the same sites.
问题所在
Field devices sit in public places, run for years and join networks that also carry control traffic. A single unverified node or unsigned update can reach far beyond the sensor it came with. Security has to be built into how every node joins, updates and reports, because nobody can guard unattended sites in person.
Key facts
Components
Interfaces
Where it works
In the story below
Scenes · 13
Next steps
Plan a deploymentOpen the Field Deployment StudioSee Security and trustTalk to salesSecurity and trust · Identity and attestation
Field devices sit in public places, run for years and join networks that also carry control traffic. A single unverified node or unsigned update can reach far beyond the sensor it came with. Security has to be built into how every node joins, updates and reports, because nobody can guard unattended sites in person.
功能
A hardware root of trust that holds keys, measures boot and signs attestation evidence. In identity and attestation, part of Security and trust, the device identity and attestation layer holds Trusted Platform Module, drawn against TCG TPM 2.0 Library Specification and ISO/IEC 11889 and used beside secure elements on the same sites.
Device identity and attestation
Signed claims about a device’s state carried as CWT or JWT. In identity and attestation, part of Security and trust, the device identity and attestation layer holds Entity Attestation Tokens, drawn against IETF RFC 9711. We build it into every site for identity and attestation against that standard, and keep its version and its test results on the site’s record.
Device identity and attestation
Factory-installed and locally significant device identities bound to hardware. In identity and attestation, part of Security and trust, the device identity and attestation layer holds secure device identifiers, drawn against IEEE 802.1AR-2018 and used beside zero-touch secure onboarding on the same sites.
Device identity and attestation
Roles of attester, verifier and relying party, so trust in a node is evidence-based. In identity and attestation, part of Security and trust, the device identity and attestation layer holds remote attestation architecture, drawn against IETF RFC 9334. We build it into every site for identity and attestation against that standard, and keep its version and its test results on the site’s record.
Time and place
Every record made for identity and attestation carries its time, from a clock disciplined by satellite time or a PTP grandmaster, with the position and siting record of the station that made it. When time or position degrades, the record for identity and attestation says so, and every user downstream sees the same warning.
Device identity and attestation
Device identity derived from each firmware layer for microcontrollers without a TPM. In identity and attestation, part of Security and trust, the device identity and attestation layer holds DICE layered identity, drawn against TCG DICE Layering Architecture and used beside physically unclonable functions on the same sites.
信任
A node joins a network for identity and attestation only after its hardware root of trust answers an attestation challenge. Its keys stay in secure hardware, its software arrives signed and every record it makes for identity and attestation carries a signature, so anyone downstream can check where a value came from.
证据
We trace each part of identity and attestation to its specification: TCG TPM 2.0 Library Specification, ISO/IEC 11889 and TCG DICE Layering Architecture. We keep the versions, configurations and test results of identity and attestation as signed records, so a buyer or an auditor can check what was delivered against what was specified.
动态
Software and configuration reach a fleet for identity and attestation in rings: one canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave, and each node for identity and attestation returns to its last good release without a site visit.
How it scales
A network for identity and attestation starts with one base node and the instruments it reads. A station adds power and radio, a site adds a relay and a fleet repeats the proven site, so capacity for identity and attestation grows by adding units, never by replacing what works.
What you get
Identity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits. Stated as services, never as a security guarantee. For identity and attestation, it goes to operators of critical sites and agencies as a managed service or professional services, sized to the sites they run.
Talk to salesNext step
Tell us the sites, the systems identity and attestation must work with and the outcome you need, with a map or a list of addresses if you have one. An engineer replies with a survey proposal, a design and a scope for identity and attestation, and the plan grows from one site to the network you need.
Plan a deploymentOpen the Field Deployment StudioSee Security and trustMore presentations
Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.
All presentations01概述
How every node proves what it is and what it runs, how links and keys are protected, how software is traced to its source, how personal data is minimised, and how incidents are found and handled. Each technology below carries what it is, what we do with it, and the standard it is drawn against.
Security, identity and trust
A hardware root of trust that holds keys, measures boot and signs attestation evidence.
We design and integrate.
TCG TPM 2.0 Library Specification · ISO/IEC 11889
Security, identity and trust
Device identity derived from each firmware layer for microcontrollers without a TPM.
We design and integrate.
TCG DICE Layering Architecture
Security, identity and trust
Factory-installed and locally significant device identities bound to hardware.
We design and integrate.
IEEE 802.1AR-2018 (IDevID, LDevID)
Security, identity and trust
Roles of attester, verifier and relying party, so trust in a node is evidence-based.
We design, integrate and operate.
IETF RFC 9334 (RATS architecture)
Security, identity and trust
Signed claims about a device’s state carried as CWT or JWT.
We design and integrate.
IETF RFC 9711 (EAT)
Security, identity and trust
Tamper-resistant chips that store credentials on constrained devices.
We design and integrate.
GlobalPlatform specifications
Frontier · Security, identity and trust
Keys derived from silicon variation rather than stored, resisting extraction.
We integrate.
ISO/IEC 20897-1 (PUF security requirements)
Security, identity and trust
Devices proving their identity to the owner’s network without shared secrets in the field.
We design, integrate and operate.
FIDO Device Onboard 1.1 · IETF RFC 8995 (BRSKI)
02Architecture
Identity and attestation draws on the spectrum below; the highlighted layers carry this area, and the protocol functions it speaks are marked.
Device identity and attestation
8
PKI, secure boot and updates
7
Zero trust and network security
7
5G and wireless security
6
OT security and software supply chain
9
隐私与数据保护
7
Keys, cryptography and post-quantum migration
9
Monitoring, incident response and governance
8
01加入 Identity, attestation quote, signed policy.
02Admit Admitted for a stated scope, nothing wider.
03描述 What, where, how and by whom, with calibration.
04Time One clock across the grid, with its error bound.
05Observe Every value with quality and provenance.
06Qualify Tested against the specification, state on record.
07Federate Signed exchange across grids and trust domains.
08Orchestrate Software and configuration by signed plan.
09Correct A correction marks what depends on it and publishes a new version.
10Exchange Products reach people and applications through versioned interfaces.
11Prove Signed proof receipts that an independent verifier can check.
12Exit and decommission An open exit path, and a record that closes.
03On the grid
The open networks on the grid today, over real relief and the geodesic cells we count them into. A site built here enrols into the same grid.
04In the field
Deployment scenarios from the sector research that rely on identity and attestation.
Defence-adjacent (civil dual-use)05Open and enterprise
The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.
Open, on the main site
Enterprise, on this site
06The rest of the line
Survey, design, deployment and operation for identity and attestation. The form names who receives your details.
Talk to usAsk for a quoteIdentity and attestation, inside Security and trust: Trusted Platform Module, DICE layered identity, secure device identifiers, remote attestation architecture and more. Every item is traced to its specification, from TCG TPM 2.0 Library Specification to ISO/IEC 11889, and runs on the open Observatory Protocol.
The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.