Zero Trust at the Door: A Physical Security Responsibility
Key Highlights
- Zero Trust in physical security involves continuous authentication and verification of all devices and systems at the edge, not just traditional network components.
- Legacy devices can be integrated into a Zero Trust framework through retrofit modules that authenticate and verify each operation without replacing existing infrastructure.
- Scene verification markers in video feeds help detect manipulated or false footage, ensuring real-time integrity of visual data.
- Secure field controllers support multi-protocol authentication, unifying access control, intrusion detection, and OT device management while verifying connected devices.
- Implementing Zero Trust at the physical layer reduces attack surfaces, prevents unauthorized device access, and enhances overall security posture.
It is 2:17 in the morning. Your operations center gets an alert that the north loading dock door opened for three seconds, then closed. The video feed shows the same static frame you have seen a hundred times before. The logs show that a valid badge was presented. The guard on duty marks it as a possible misread.
By 9:00 a.m., IT calls. They have detected unusual network traffic coming from a controller tied to your access control system. The traffic began at the same time as the door event. The badge had been cloned, the video feed looped, and the controller was compromised to gain a foothold inside the network.
This was not an IT-only breach. The attack began at a physical entry point. The systems you manage gave the attackers their first access. This is the kind of event that Zero Trust is designed to prevent.
Zero Trust is not limited to network firewalls and user accounts. It applies to every device and system that interacts with your environment. If you operate badge readers, intrusion sensors, cameras, or control panels, you are already in the middle of the Zero Trust problem.
What Zero Trust Means in Practice
Zero Trust is often referred to as a strategy, but to implement it you have to use solutions that support the core rule of never trust, always verify. Nothing is allowed to operate without proving its identity and authorization, not just once but continuously.
In physical security, you already use elements of this principle. Two-factor authentication for a secure room, a guard matching a photo to the person holding the badge, or dual authorization for certain actions are all examples. The difference now is that this level of scrutiny must extend to the devices themselves, the connections between them, and the data they send.
Every device in your environment is an edge device. A badge reader, a motion sensor, a camera, or a controller all sit at the point where the physical world meets the digital network. If an attacker can compromise one, they can use it to reach deeper into your systems.
Legacy devices are often the weakest point. Many were designed for an era when physical systems were separate from IT. They were not built to authenticate themselves or their data. Many still rely on outdated verification methods like end-of-line resistors, which can be bypassed in seconds.
Continuous Verification at the Physical Edge
In Zero Trust, users, devices, and data must both authenticate and verify. Authentication confirms identity. Verification confirms that the user, device, or data is still authorized and has not been altered. For example, a motion sensor should not just send an open or closed signal. It should also prove it is the genuine device you installed and that it has not been altered.
Addressing the vulnerabilities of cyber-physical systems through zero trust necessitates an approach that avoids costly and time-consuming rip/replace procurement strategies by supporting both new and legacy devices and infrastructure. Software and hardware that enable a device to authenticate and verify itself to the controller each time it sends a signal. In practice, that means an old door contact or sensor can be brought into a Zero Trust framework without replacement- the equivalent of adding a high-security lock to a door, but the lock checks itself every time it is used.
Authentication alone is insufficient if the system cannot detect data manipulation. Video is a clear example. In multiple incidents, attackers have looped recorded footage or inserted false images to hide movement. Operators believed they were seeing live video because the feed appeared normal.
While numerous solutions attempt to address this issue with encryption at the imager, this approach misses a key element: the scene itself. Mitigating risks associated with spoofed and manipulated video necessitates solutions that extend the aforementioned authentication and verification protections and embed them in the scene itself by adding a secure visual reference within the camera’s view. Systems are available that continuously check that these references are present and functioning. If missing or altered, the operator is alerted immediately. This verification prevents an attacker from inserting false or frozen video without detection.
Field panels and controllers are another point of vulnerability. Many existing solutions assume every connected device is trustworthy and have no way to confirm that assumption, leaving those systems vulnerable to spoofed signals or rogue devices.
A multi-protocol secure field controller authenticates and verifies every device it connects to, supports both analog and digital inputs, and can replace or retrofit legacy analog panels and controllers using an expansion module. In one government installation, replacing multiple legacy controllers with secure field controllers allowed the site to unify access control, intrusion detection, and OT device management while ensuring all connected devices were verified.
Mitigating risks associated with spoofed and manipulated video necessitates solutions that extend the aforementioned authentication and verification protections and embed them in the scene itself by adding a secure visual reference within the camera’s view.
Examples from Operations
In integrated deployments at high-security government sites, modernized end-of-line control interface encryption and embedded video scene-level protection work in unison. A cloned badge can be presented at a reader, but the secure device authentication module rejects the attempt because the reader itself was not recognized as genuine. Simultaneously, an attacker attempted to loop a camera feed to hide activity near the same entry point. The scene verification marker verification flagged the false feed within seconds, alerting operators in real time. At the same moment, the secure field controller refused to pass any data from an unverified intrusion sensor in the area, preventing a false clear signal from reaching the security system. This layered defense stopped the intrusion at three different points before it could gain any foothold in the network.
Consider a restricted lab area that uses card readers for entry. Without continuous verification, a cloned card can be used until it is detected, which may take hours or days. With the secure device authentication module’s authentication at the reader, the controller checks the device itself as well as the card. A cloned card will not work if the reader is not recognized as genuine.
Cameras monitoring a perimeter fence can be targeted. Attackers could insert a short loop of video showing an empty fence line. Without verification, the operators have no way to know the feed was false. A scene verification marker in each camera’s field would provide constant confirmation that the image was live. The looped feed would be detected almost immediately.
In a water treatment plant, legacy controllers for pumps and gates are often connected directly to the OT network. Unverified sensors can send false data about a gate position, which triggers an unnecessary response. The problem is traced to a device swap that had gone unnoticed. Replacing the controllers with secure field controllers ensured every connected device was authenticated and verified, preventing unauthorized replacements from communicating.
Why This Is Urgent for Physical Security Leaders
IT teams can segment networks, control user accounts, and monitor traffic. But if a compromised field panel or sensor remains connected, it can bypass those protections. Physical security owns the entry points and the devices at the edge. Without Zero Trust at this layer, the rest of the model is incomplete. The risk is not theoretical. Attackers already use physical devices to gain access to networks. In some cases, they target physical systems first because they are easier to compromise than hardened IT infrastructure. Every unverified device is a potential entry point.
Your position allows you to close these gaps. By implementing device authentication, video verification, and secure controllers, you ensure that only trusted devices operate in your environment. This also ensures the data used by analytics, AI models, and digital twins is accurate. A digital twin built on unverified inputs will make incorrect decisions, which in critical infrastructure can cause real-world damage.
The pace of attacks on OT and physical systems is increasing. Threat actors are testing the boundaries between physical and digital security. Many of these attacks are quiet, designed to blend in with normal operations. Without Zero Trust, they can remain invisible for weeks. By the time they are found, they have already been used for reconnaissance, staging, or direct disruption.
Beyond operational impact, you must also weigh the compliance and reputational risks. As we have seen too many times, a single physical-to-cyber breach can trigger regulatory investigations, contractual penalties, and public disclosure requirements that damage brand trust. Securing your physical edge with Zero Trust means that you are protecting not only your facilities but also your organization’s ability to operate without disruption or reputational loss.
Building Zero Trust in Physical Systems
Moving to Zero Trust cannot and does not mean replacing every device. It means adding the ability to authenticate and verify continuously. This can be done in stages. Secure device authentication modules retrofit existing devices. Scene verification markers integrate with the current camera infrastructure. Secure field controllers can replace legacy controllers as part of regular upgrade cycles.
The key change is cultural as much as technical. Physical security teams must stop assuming devices are trustworthy because they are inside the perimeter or have worked for years. Verification must be constant. The cost of assuming trust is far higher than the cost of confirming it.
The Zero Trust Implementation Guide we will discuss later is the primary resource for putting these concepts into action. It provides step-by-step instructions, sequencing, and integration details for applying Zero Trust at the physical edge.
This principle also applies to digital twins. A digital twin is only as accurate as the data it receives. Meaning, if the sensors feeding it are unverified, the model can be manipulated. In a physical security context, that means an operator could be looking at a model that shows all systems nominal while an attack is in progress. Zero Trust prevents this by ensuring only authenticated and verified data is used.
Zero Trust at Scale with the Right Partner
This all might sound like a major overhaul, but it is not difficult to accomplish if you work with a partner who truly understands both the physical and digital sides of security. The challenge is not in the concept; it is in applying it to every device and connection without disrupting daily operations. This is where choosing the right partner matters.
Very few companies provide a full-spectrum, turnkey approach to Zero Trust. Those solutions cover authentication for legacy and new devices, verification for video systems, and secure, unified field control. Secure device authentication modules bring continuous authentication to any device, scene verification markers maintain the integrity of video feeds, and the secure field controller connects and verifies all devices in one platform.
Because these tools are designed to work together, they allow organizations to move from assessment to implementation without having to source and integrate separate products. The result is a complete Zero Trust framework for the physical edge that can be deployed in phases or at scale, depending on operational priorities.
Working with a trusted partner means you are not left trying to connect separate solutions or interpret multiple technical standards. Instead, you get a unified system that is built to extend Zero Trust into the physical layer, with the flexibility to fit to, and scale with, your environment.
Your Role in Enterprise Zero Trust
Zero Trust is an enterprise model, but it only works if every layer participates. Physical security is the first layer in many environments. Your systems are often the first touched by an attacker, whether they come through a door, a fence, or a field device on the network.
To put this workflow in perspective, secure device authentication modules secure devices, scene verification markers protect video integrity, and secure field controllers control and verify at the panel level. Each fit into existing operations and extends the Zero Trust framework to the edge. Implementing these measures positions physical security as a full partner in the enterprise security model. It also shifts your role from reacting to incidents to preventing them. The responsibility is significant, but so is the opportunity to lead.
This is not about turning physical security into IT; It is about recognizing that your devices and systems are already part of the IT environment. The line between physical and digital no longer exists in practice. An access control panel is as much a network device as a switch or router. It deserves the same level of verification and protection.
So, What are the Next Steps?
The scenario at the start illustrates how quickly a physical event can become a network breach. The systems you manage can either be a barrier or a bridge. Zero Trust makes them a barrier by removing default trust and requiring constant proof.
The Zero Trust for Electronic Security Systems Concept of Operations (ZTA for ESS CONOPS) describes a high-level conceptual approach for applying Zero Trust principles in operationally relevant environments. It defines the objectives, scope, and relationships between physical and digital security but does not prescribe detailed steps.
The Zero Trust Implementation Guide is the primary resource for putting those concepts into action. It provides step-by-step instructions, sequencing, and integration details for securing every part of your environment, from the front gate to the control room, using continuous authentication and verification. At its core, it is about building a common language between physical security, IT, and OT to clarify where Zero Trust begins and ends. It begins everywhere.
The first step is assessment. Walk through your site with the mindset that every device must prove it belongs there. Look at your cameras, readers, sensors, and controllers as you would a contractor on site: if you cannot verify them, you cannot trust them. This process gives you a clear picture of what is in place today, where gaps exist, and what can be addressed through retrofits like secure device authentication modules or scene verification markers.
The second step is integration. The Implementation Guide outlines how authentication and verification should work between devices, networks, and people. This does not require replacing all working systems. It means adding verification layers so a compromised device cannot operate undetected. A secure field controller is one way to do this at scale, connecting legacy and modern systems while enforcing Zero Trust rules.
The third step is alignment. Physical security cannot operate in a silo. The Implementation Guide is designed to get your team in sync with IT and OT, so all sides know what “secure” means in practice. This shared understanding prevents weak links where one team assumes another has already addressed a risk.
The final step is validation. This is the ongoing process of testing and confirming that every part of the system still meets Zero Trust standards. Devices are checked, signals are confirmed, and data is verified. It is a cycle, not a one-time project, and it keeps your defenses active as technology and threats change.
Reviewing the Zero Trust Implementation Guide and referencing the CONOPS will give you both the detailed actions and the strategic context needed to start discussions with IT, OT, and executive leadership. This combination will help you explain to executives why physical security is essential to Zero Trust and how taking these steps now prevents the kind of breach that begins with a door, a badge, or a camera.
Click here to download the Zero Trust Architecture Implementation Guide and CONOPs.
About the Author

Seth Riser
Vice President of Operations at ESI Convergent
Seth Riser is the Vice President of Operations at ESI Convergent, where he oversees internal operations and provides strategic consulting to manufacturers and commercial end users. His current focus includes backend R&D strategy, AI integration, and aligning product development across physical security, IT, OT, and cybersecurity systems.
He advises leading manufacturers on platform strategy, protocol selection, and architecture validation, and works with critical infrastructure and enterprise clients to evaluate technologies and guide secure, scalable deployments. Seth serves on multiple advisory boards and speaks at industry events, offering insight on product direction and emerging technology development.

Steven Brown
Vice President for Strategy & Business Development at Prometheus Security Group Global (PSG).
Steven Brown is Vice President for Strategy & Business Development at Prometheus Security Group Global (PSG). He is a critical infrastructure security expert and USAF veteran with 23+ years of operations, strategy, policy, design, and implementation experience securing critical infrastructure and strategic assets worldwide.
PSG provides unified security solutions specializing in software and hardware for video surveillance, access control, intrusion detection, and cyber security. PSG’s open architecture, zero trust, scalable, reliable security solutions are entrusted to protect the United States’ most sensitive strategic assets along with critical missions, facilities, and people around the world.

Thomas Segars
Founder and President of Foursquare Security Solutions, LLC,
Thomas Segars is a retired United States Air Force Colonel with over 32 years in physical security, nuclear security, law enforcement, and anti-terrorism. After completing his final active-duty post in June 2024 as the Director of intelligence, Strategic Plans, and Requirements for the Air Force Installation and Mission Support Center in San Antonio, Texas, Thomas launched a consulting company, Foursquare Security Solutions, LLC, and provided independent security consulting services. Thomas has a bachelor’s degree in criminal justice from the University of Georgia, a master’s degree in human resources development from Webster University, and a Master of Strategic Studies from the United States Army War College. He is also a Federal Bureau of Investigation National Academy Session 263 graduate with a Department of Defense Counter Insider Threat Professional certification.