Cyber Physical Systems: What They Are and Who Owns Them
Cyber physical systems tie software decisions to the equipment that controls rooms, production lines and doors. Here is how to find them and who should approve changes and vendor access.
Cyber-physical systems connect software to devices that sense or control physical conditions. A building controller reads a temperature, decides whether cooling is needed and changes the airflow. Securing that loop requires one named owner who approves changes and vendor access.
The vendor wants remote access, and IT and facilities each say it is the other's call
A technician asks to log in to fix a building controller. Facilities points to IT because IT runs the network. IT points back because facilities bought and maintains the equipment. Neither department approves the work, but the technician still needs an answer.
The gap sits between two budgets and two reporting lines. Facilities understands the equipment. IT understands its network connection. Without an accountable system owner, remote access opened for one service call can remain open after the work ends.
What makes a building system a cyber-physical system?
A cyber-physical system, usually shortened to CPS, combines software with a physical process. The Carnegie Mellon Software Engineering Institute described these systems in July 2026 as those in which “software components closely interact with physical processes.” A temperature sensor supplies data. Software decides what to do. A controller changes the equipment’s operation.
The defining feature is that feedback loop. A controller reads room temperature, starts an air handler and measures the result. A bad command can affect the room rather than just a file. Network access adds another exposure: someone outside the equipment itself can potentially influence that decision.
Which systems in your facility already qualify?
Network-connected building controls and production equipment belong in the inventory. The consequences depend on the system’s design and safeguards; a network connection does not mean every safety function is remotely controllable.
| System | What it controls | What a wrong command could do |
|---|---|---|
| Building automation | Lighting, schedules, airflow, setpoints | Disrupt ventilation or run equipment after hours |
| HVAC controls | Heating, cooling, dampers, pumps | Change temperatures outside operating limits or stress equipment |
| Access control panels | Door locks, readers, schedules | Open a secured door or deny authorized entry |
| Elevator controls | Car movement, recall, door operation | Disrupt elevator service or strand passengers |
| Fire and life-safety panels | Alarms, notification, configured suppression functions | Disrupt notification or trigger an unintended function where controls permit it |
| Production equipment with embedded controllers | Presses, conveyors, process lines | Interrupt production or command unsafe movement if safeguards fail |
Apply the bad-command test: what would happen if someone changed this setting without approval? If the answer includes an unlocked door or stopped production, record that consequence alongside the device. An equipment name alone does not tell an approver what is at stake.
Why being on the network changes the risk
A networked controller creates a possible route into other systems if network separation and access controls are weak. That does not make a thermostat equivalent to your finance server. It means the route between them needs to be understood and restricted.
Many controllers operate for years between updates. Patching can require vendor approval and a planned shutdown, so laptop update policies do not transfer directly.
Separate these systems from unrelated networks. Limit who can log in, and monitor access while updates await an approved maintenance window.
Physical access also matters. An unlocked controller cabinet or accessible network port can bypass controls intended to restrict remote access. CISA’s November 2, 2026 announcement of Critical Infrastructure Security and Resilience Month provides a dated reason to review those dependencies and recovery arrangements.
For the physical side of this, see our guide on what tailgating means in cyber security and how to stop it.
Who approves the change, and who approves the vendor's access?
Name one accountable owner for each connected system. Department placement matters less than authority: the owner must be able to approve the work and answer for its operational consequences. IT checks the network path. Facilities or the qualified equipment specialist checks the proposed controller change. The owner makes the decision with both inputs.
Vendor access should be temporary and traceable to approved work. Set these rules before the next service call:
- Keep vendor remote access off by default. Close it between service sessions.
- Authorize each session for a named technician and a specific work order.
- Require a written change description and rollback plan before work starts.
- Test on a non-production copy where one exists. Otherwise, agree on a vendor-supported validation plan before changing the live system.
- Have the system owner approve the change window. Do not leave credential control solely with the vendor.
- Log the work and verify that access is closed when the session ends.
For the broader supply chain view, read our piece on how to tier vendors by data access, and our guide on how to give facilities and IT one accountable owner.
What should a virtual CSO put in place first?
A virtual Chief Security Officer runs the security program across physical and digital risk. That role does not replace the technician who understands the controller or the IT team that runs its network. It establishes decision authority and checks whether access rules are followed.
Start with ownership and an inventory before buying another security tool.
Start with the inventory. List every connected physical system. Record who installed it and whether its factory password has been changed. Name the owner and document what happens physically if the system fails. Use that consequence to prioritize review: a controller supporting safe operations deserves different treatment from an after-hours lighting schedule.
Put requirements in the purchase terms. For Q4 and 2027 upgrades, specify how vendor access will be controlled before signing. Require a supported update process and usable access logs. Name the owner before installation, rather than leaving that decision to the handover meeting.
Name an emergency approver before the holidays. Put the backup approver in writing before the primary owner leaves. Safety-related equipment and production controls require qualified technical review, even when a change is urgent. Bring in the qualified vendor technician and check applicable insurer requirements before approving work that affects safe operation.
Our Virtual CSO program covers executive leadership across all 13 Enterprise Security Risk Management domains, including physical security and board reporting.
Where to start before the holiday schedule locks in
In Texas, holiday absences make backup approval a practical November priority. Review systems whose failure would interrupt operations first. Check who can authorize emergency work when the usual owner is unavailable.
We are Texas DPS-licensed, with Certified Protection Professional (CPP), Certified Information Systems Security Professional (CISSP) and Certified Information Security Manager (CISM) credentials. We have operated since 2013. Our programs cover all 13 risk domains and report directly to the board.
Bring your connected-system inventory and unresolved ownership questions to a 30-minute Risk Discussion, or call 817-677-0515.
Frequently asked questions
What is CPS security?
CPS security protects systems in which software interacts with physical processes, such as building controls or production equipment. It starts with controlling who can change the system and how vendors get in. Recovery planning must address the physical consequences of failure, not just restoring software.
Is a building management system a cyber-physical system?
Yes. A building management system that reads sensors and adjusts equipment connects software decisions to physical conditions. A system that measures temperature and changes airflow is a straightforward example. Its security review should identify what an unauthorized command could change.
Who should approve a vendor's remote access to a facility system?
The named system owner should approve each session against a specific work order. IT should verify the access path, while a qualified equipment specialist reviews changes affecting the controller. Approval should include a change window and rollback plan, with access closed and verified afterward.
What is physical security in cyber security?
Physical security restricts access to equipment and spaces that provide a route into digital systems. Locked network closets and controlled access to controller cabinets are examples. Tailgating controls also matter because an unauthorized person inside a facility can gain access to exposed equipment.
Does a small facility need a virtual CSO for this?
Not necessarily. A small facility can begin by listing its connected systems and naming an owner for each. Virtual CSO leadership becomes useful when physical and digital risks cross departments and need one executive program owner with board accountability.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article