--- title: "Segmentation and zero trust | Nexus Observatory" description: "Segmentation and zero trust, inside Security and trust: zero trust architecture, workload identity, port-based access and link encryption…" url: https://observatory.global/security-trust/segmentation-and-zero-trust/ publisher: Nexus Observatory Inc. updated: 2026-11-07 --- Segmentation and zero trust: zones fenced inside one site, every crossing checked. The loop, step by step: 1. Three fenced zones and one narrow gate. 2. The chain from source to console stands ready. 3. A device in the outer zone probes the gate. 4. The gate asks for identity and purpose. 5. Each reading is stamped with time and place. 6. Signatures are checked before any model runs. 7. Policy allows one service and nothing else. 8. The edge releases confirmed results only. 9. Permitted traffic crosses the gate. 10. The relay forwards sealed packets untouched. 11. Other traffic stops at the fence. 12. Sensors check that the response worked. 13. Every decision is logged for audit. 14. The alert arrives with its evidence attached. 15. Record, proof and action are archived together. 16. Everything settles back to idle. 01 / 16 Three fenced zones and one narrow gate [Nexus Observatory](https://observatory.global/) / [Security and trust](https://observatory.global/security-trust/) / **Segmentation and zero trust** # Least privilege between nodes, tenants and sites. Segmentation and zero trust, inside Security and trust: zero trust architecture, workload identity, port-based access and link encryption, transport security and more. Every item is traced to its specification, from NIST SP 800-207 to CISA Zero Trust Maturity Model 2.0, and runs on the open Observatory Protocol. [Plan with us](https://observatory.global/contact/) Architecture [The protocol](https://observatory.global/protocol/specification/) **Technologies**: 7 **At the frontier**: 0 **Protocol functions**: 4 of 12 **Industries served**: 5 At a glance ## Zero trust architecture No implicit trust from network location; each request authenticated, authorised and logged. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds zero trust architecture, drawn against NIST SP 800-207 and CISA Zero Trust Maturity Model 2.0 and used beside zones, conduits and segmentation on the same sites. The problem ### Least privilege between nodes, tenants and 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 **Specification**: NIST SP 800-207 · CISA Zero Trust Maturity Model 2.0 **Specification**: IETF RFC 4301 (IPsec) · IETF RFC 7296 (IKEv2) **Specification**: IEEE 802.1X-2020 · IEEE 802.1AE (MACsec) **Specification**: IETF RFC 8446 (TLS 1.3) · IETF RFC 9147 (DTLS 1.3) **Specification**: SPIFFE specification Components - Pole-mounted edge gateway node - Fixed gas detectors on a drift wall - Particulate monitoring station and sensor node - Overhead line sensor on a distribution span - Private LTE mast on a solar skid - "AI tower in a box" - Hardware security module, 1U, in an edge rack - Data hall row pair with cold-aisle containment Interfaces **Instruments**: SDI-12 · RS-485 / Modbus RTU · 4–20 mA **Radio**: Ethernet · LTE-M / NB-IoT · LoRaWAN **Time and position**: GNSS 1PPS **Security**: TPM 2.0 **Publishing**: MQTT Where it works - IPsec and site tunnels - Transport security In the story below 1. The system, part by part 2. Assembly 3. Installation 4. Deployment 5. Connections 6. Operation 7. Failure and recovery 8. Scale and federation 9. What you get Scenes · 13 Next steps [Plan a deployment](https://observatory.global/security-trust/contact/deployment/) [Open the Field Deployment Studio](https://observatory.global/studio/) [See Security and trust](https://observatory.global/security-trust/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) 1. Security and trust · Segmentation and zero trust Least privilege between nodes, tenants and 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. 2. What it does Zero trust architecture No implicit trust from network location; each request authenticated, authorised and logged. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds zero trust architecture, drawn against NIST SP 800-207 and CISA Zero Trust Maturity Model 2.0 and used beside zones, conduits and segmentation on the same sites. SpecificationNIST SP 800-207 · CISA Zero Trust Maturity Model 2.0 3. Zero trust and network security IPsec and site tunnels Encrypted tunnels between sites, gateways and the NOC. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds IPsec and site tunnels, drawn against IETF RFC 4301 and IETF RFC 7296. We build it into every site for segmentation and zero trust against that standard, and keep its version and its test results on the site’s record. SpecificationIETF RFC 4301 (IPsec) · IETF RFC 7296 (IKEv2) 4. Zero trust and network security Port-based access and link encryption Authenticating devices on wired ports and encrypting Ethernet links. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds port-based access and link encryption, drawn against IEEE 802.1X-2020 and IEEE 802.1AE. We build it into every site for segmentation and zero trust against that standard, and keep its version and its test results on the site’s record. SpecificationIEEE 802.1X-2020 · IEEE 802.1AE (MACsec) 5. Zero trust and network security Transport security Modern encrypted transport for APIs, telemetry and constrained links. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds transport security, drawn against IETF RFC 8446 and IETF RFC 9147. We build it into every site for segmentation and zero trust against that standard, and keep its version and its test results on the site’s record. SpecificationIETF RFC 8446 (TLS 1.3) · IETF RFC 9147 (DTLS 1.3) 6. Time and place When and where, on every record Every record made for segmentation and zero trust 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 segmentation and zero trust says so, and every user downstream sees the same warning. 7. Zero trust and network security Workload identity Short-lived, attested identities for services and agents rather than static secrets. In segmentation and zero trust, part of Security and trust, the zero trust and network security layer holds workload identity, drawn against SPIFFE specification and used beside GNSS interference and spoofing resilience on the same sites. SpecificationSPIFFE specification 8. Trust Proved before it is trusted A node joins a network for segmentation and zero trust 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 segmentation and zero trust carries a signature, so anyone downstream can check where a value came from. 9. Evidence Traced to its specifications We trace each part of segmentation and zero trust to its specification: NIST SP 800-207, CISA Zero Trust Maturity Model 2.0 and SPIFFE specification. We keep the versions, configurations and test results of segmentation and zero trust as signed records, so a buyer or an auditor can check what was delivered against what was specified. StandardsNIST SP 800-207 · CISA Zero Trust Maturity Model 2.0 · SPIFFE specification · IEEE 802.1X-2020 10. Failure and recovery When a node fails, the fleet knows first When a node for segmentation and zero trust goes silent or a sensor drifts, the node buffers its data and fails over to a second link where the site has one. The alert carries the evidence a responder needs, and the record for segmentation and zero trust loses nothing and counts nothing twice. 11. How it scales One base unit, repeated A network for segmentation and zero trust 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 segmentation and zero trust grows by adding units, never by replacing what works. 12. What you get Operational-technology assurance for observing sites Identity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits. Stated as services, never as a security guarantee. For segmentation and zero trust, it goes to operators of critical sites and agencies as a managed service or professional services, sized to the sites they run. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 13. Next step Segmentation and zero trust, planned with you Tell us the sites, the systems segmentation and zero trust 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 segmentation and zero trust, and the plan grows from one site to the network you need. [Plan a deployment](https://observatory.global/security-trust/contact/deployment/) [Open the Field Deployment Studio](https://observatory.global/studio/) [See Security and trust](https://observatory.global/security-trust/) More presentations ## See it from every side. 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 presentations](https://observatory.global/presentations/) ### In depth [Use case **Utility grid-edge private LTE and wildfire weather**](https://observatory.global/use-cases/utility-grid-edge/) [ISIC section · ISIC B **Mining and quarrying**](https://observatory.global/industries/b-mining-and-quarrying/) [ISIC section · ISIC F **Construction**](https://observatory.global/industries/f-construction/) [Sector **Industrial**](https://observatory.global/sectors/industrial/) ### Explainers [Explainer · Industrial **Industrial** Blast vibration at the pit, fire weather at the grid edge, methane at the fenceline and tailings movement from GNSS.](https://observatory.global/industries/infrastructure/explainer/) [Platform **Security and trust** Every unattended node is an entry point](https://observatory.global/security-trust/) [Platform **Sensors & instruments** A number without its story](https://observatory.global/sensors/) ### Stories [Story · Private 5G and AI-RAN **Private 5G with the inference in the radio** A private cellular network gives a site its own coverage, its own security and its own priorities. AI-RAN adds a second idea: the accelerators that run the…](https://observatory.global/stories/private-5g-ai-ran/) [Story · Post-quantum cryptography **Cryptography that outlasts the quantum computer** Data signed today may need to be trusted in 2040. Post-quantum standards were first published in August 2024, and governments have set dates for leaving…](https://observatory.global/stories/pqc-migration/) [Story · Timing and PNT **Time as infrastructure** A 5G cell must hold its phase within 3 µs of its neighbours, ±1.5 µs of a common reference; a synchrophasor’s one per cent vector error leaves room for only…](https://observatory.global/stories/timing-pnt/) ### Places and networks [Guided tour · Guided 3D tour **Open-pit mine** GNSS slope monitors on the benches, a blast seismograph at the boundary and a private cell for the fleet, around a benched pit cut into the ground.](https://observatory.global/environments/open-pit-mine/) [Guided tour · Guided 3D tour **Transmission corridor** Lattice towers carry a line across open country; conductor sensors report temperature and sag, and the substation edge brings them into the grid operator’s systems.](https://observatory.global/environments/transmission-corridor/) [Network scene · Private 5G · Mining **Private 5G in an open-pit mine** A private network for haul trucks, drills and slope radar: a mast on the rim, a cell in the pit, the core at the plant, and coverage computed over the benches themselves.](https://observatory.global/environments/networks/private5g-mine/) ### Heritage observatories [Heritage observatory · Kīlauea) · 1912 **Hawaiian Volcano Observatory** A volcanologist set up a hut on the rim of Kīlauea's crater in 1912 and stayed to measure what the volcano does.](https://observatory.global/observatories/hawaiian-volcano-observatory/) [Heritage observatory · Italy (historic building on the slopes of Vesuvius) · 1841 **Vesuvius Observatory** Founded in 1841 on the slope of Vesuvius, this is the oldest volcano observatory in the world.](https://observatory.global/observatories/vesuvius-observatory/) ### Interactive tools [Interactive tool · Configure a station **Station Builder** Configure a station part by part in 3D, check the rules as you go and request a quote for the assembly.](https://observatory.global/studio/builder/) **01** What it is ## Zero trust and network security. 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 ### Zero trust architecture No implicit trust from network location; each request authenticated, authorised and logged. We design, integrate and operate. NIST SP 800-207 · CISA Zero Trust Maturity Model 2.0 Security, identity and trust ### Workload identity Short-lived, attested identities for services and agents rather than static secrets. We design and integrate. SPIFFE specification Security, identity and trust ### Port-based access and link encryption Authenticating devices on wired ports and encrypting Ethernet links. We design, integrate and deploy. IEEE 802.1X-2020 · IEEE 802.1AE (MACsec) Security, identity and trust ### Transport security Modern encrypted transport for APIs, telemetry and constrained links. We design and integrate. IETF RFC 8446 (TLS 1.3) · IETF RFC 9147 (DTLS 1.3) Security, identity and trust ### IPsec and site tunnels Encrypted tunnels between sites, gateways and the NOC. We design, integrate and operate. IETF RFC 4301 (IPsec) · IETF RFC 7296 (IKEv2) Security, identity and trust ### Zones, conduits and segmentation Grouping assets by risk and controlling every flow between groups. We design, integrate and operate. IEC 62443-3-2 (risk assessment, zones and conduits) Security, identity and trust ### GNSS interference and spoofing resilience Detecting jamming and spoofing and holding time and position during outages. We design, integrate and operate. US DHS Resilient PNT Conformance Framework · Galileo Open Service Navigation Message Authentication **02** Architecture ## Where it sits, and what it speaks. Segmentation and zero trust 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 Privacy and data protection 7 Keys, cryptography and post-quantum migration 9 Monitoring, incident response and governance 8 01**Join** Identity, attestation quote, signed policy. 02**Admit** Admitted for a stated scope, nothing wider. 03**Describe** What, where, how and by whom, with calibration. 04**Time** One clock across the grid, with its error bound. 05**Observe** Every value with quality and provenance. 06**Qualify** Tested against the specification, state on record. 07**Federate** Signed exchange across grids and trust domains. 08**Orchestrate** Software and configuration by signed plan. 09**Correct** A correction marks what depends on it and publishes a new version. 10**Exchange** Products reach people and applications through versioned interfaces. 11**Prove** Signed proof receipts that an independent verifier can check. 12**Exit and decommission** An open exit path, and a record that closes. **03** On the grid ## Every site joins one observing 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. ## The observing grid 1. Open instruments on the observing grid. **04** In the field ## Where this runs, sector by sector. Deployment scenarios from the sector research that rely on segmentation and zero trust. [Defence-adjacent (civil dual-use) Critical-infrastructure resilience sensing Utility and pipeline monitoring under grid-security rules.](https://observatory.global/sectors/defence-adjacent/) [Government and public safety National GBON surface and upper-air network WMO-grade stations reporting through WIS 2.0, funded through the systematic-observations financing pathway.](https://observatory.global/sectors/public-safety/) [Government and public safety Wildfire camera network and fire-weather stations Camera towers with edge inference and co-located fire-weather stations, utility- or agency-funded.](https://observatory.global/sectors/public-safety/) [Government and public safety Urban street-flood sensor network Open-hardware depth sensors with open data and alerts to emergency management.](https://observatory.global/sectors/public-safety/) [Government and public safety Alerting integration with the Common Alerting Protocol and cell broadcast Software-heavy: sensor triggers feed an alert origination tool; the alert authority keeps every decision.](https://observatory.global/sectors/public-safety/) [Government and public safety Deployable communications and sensing for incident command A cell on wheels with satellite backhaul, mesh telemetry and environment nodes at the incident base.](https://observatory.global/sectors/public-safety/) **05** Open and enterprise ## Open by default. Enterprise by contract. 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 - Threat model for observing sites - Attestation profile in the protocol Enterprise, on this site - Operational-technology assurance - Security monitoring for observing sites - Key and PKI operations **06** The rest of the line ## Security and trust, area by area. [Security and trust Identity and attestation Hardware roots of trust, quotes checked at every join.](https://observatory.global/security-trust/identity-and-attestation/) [Security and trust Keys and PKI Issuance, rotation and post-quantum migration.](https://observatory.global/security-trust/keys-and-pki/) [Security and trust OT and wireless security Field networks, 5G and the software supply chain.](https://observatory.global/security-trust/ot-and-wireless-security/) [Security and trust Monitoring and response Detect, contain, recover, with the evidence kept.](https://observatory.global/security-trust/monitoring-and-response/) ## Bring us the site. Survey, design, deployment and operation for segmentation and zero trust. The form names who receives your details. [Talk to us](https://observatory.global/contact/) [Ask for a quote](https://observatory.global/contact/sales-enquiry/) [Nexus Observatory](https://observatory.global/) **Security and trust** . Every node proves what it is. [Talk to us](https://observatory.global/contact/) Security and trust - [Overview](https://observatory.global/security-trust/) - [Areas](https://observatory.global/security-trust/areas/) - [Technologies](https://observatory.global/security-trust/technologies/) - [Architecture](https://observatory.global/security-trust/architecture/) - [Industries](https://observatory.global/security-trust/industries/) - [Resources](https://observatory.global/security-trust/resources/) - [Contact](https://observatory.global/security-trust/contact/) Platforms - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Positioning, navigation and timing](https://observatory.global/pnt/) - [Security and trust](https://observatory.global/security-trust/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Design and integration](https://observatory.global/integration/) - [Test and qualification](https://observatory.global/qualification/) - [Operations centre](https://observatory.global/operations/) - [Training and enablement](https://observatory.global/training/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Presentations](https://observatory.global/presentations/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Observatory Protocol](https://observatory.global/protocol/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Careers](https://observatory.global/contact/careers/) - [Press](https://observatory.global/contact/press/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/) [Status](https://status.observatory.global/) [Help translate](https://observatory.global/translate/)