Safety-Aware Zero Trust Enforcement for IoT and Cyber-Physical Systems
Researchers propose Safety-Aware Zero Trust that weighs physical harm from restricting IoT and cyber-physical components.
The paper proposes Safety-Aware Zero Trust for IoT and cyber-physical systems, where restricting a component can cause physical harm by removing needed telemetry or control. It maps NIST Zero Trust tenets to nine IoT and CPS strains and adds a Safety Engine and Telemetry Broker that weigh residual cyber risk against enforcement consequences. Command-side enforcement separates raw visibility, automated influence, and state-changing authority. An IEEE 30-bus false-data-injection case study makes containment, telemetry influence, physical impact, and authorization timing explicit.
- SA-ZT treats physical harm caused by a restriction as a policy input.
- A Safety Engine and Telemetry Broker extend the NIST Zero Trust Architecture.
- Enforcement separates visibility, automated influence, and state-changing authority.
- An IEEE 30-bus false-data-injection study illustrates the resulting trade-offs.
- Organizations
- NIST
From the original article
1 min read at arxiv.orgZero Trust (ZT) replaces the implicit trust of perimeter-based security with explicit, continuous, context-aware authorization. This shift is particularly relevant to IoT and cyber-physical systems, whose heterogeneous, long-lived, and remotely connected components make persistent trust untenable.
By Alessandro Lotto · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.