Hacking Building Automation

🏭 Hacking the Building: How BAS, HVAC, and Lighting Systems Become Attack Vectors

By James K. Bishop, vCISO | Founder, Stage Four Security

🏢 Smart Buildings, Dumb Security

Today’s buildings are more intelligent and connected than ever. HVAC systems, lighting controls, elevators, and energy management platforms are all part of the modern Building Automation System (BAS). But these systems, often installed and managed outside IT oversight, are frequently vulnerable, unpatched, and network-accessible.

Attackers see BAS as an open door—one that can be exploited for lateral movement, disruption, or even direct sabotage.

🧠 Why Building Systems Are Targeted

  • Legacy protocols: BAS technologies like BACnet, Modbus, and KNX lack authentication and encryption by default.
  • Flat networks: Many BAS devices sit on the same network as corporate systems, offering a pivot path.
  • Third-party access: Vendors often have persistent VPN access into the system for “maintenance.”
  • Weak visibility: Most SOCs don’t monitor building systems as part of their threat model.

From temperature sensors to lighting controllers, attackers can use these endpoints as quiet entry points—or disrupt them to distract and destabilize operations.

🛠️ Real-World Case Study

A North American hospital experienced a network outage traced back to its HVAC control panel. A contractor had exposed the unit to the internet for remote access, and attackers exploited a default credential vulnerability. Once inside, they used the device to scan the internal network and eventually launched a ransomware attack—bringing down not just systems, but patient care operations.

The HVAC controller was the breach origin. It wasn’t even listed in the asset inventory.

🔐 How to Secure Building Systems

  • Isolate and segment: Place BAS systems on dedicated OT or facilities networks with strict firewall policies.
  • Access control: Eliminate shared vendor accounts and require MFA for remote access.
  • Monitor and alert: Integrate building systems into SIEM or NDR platforms. Watch for lateral movement or command injection.
  • Asset inventory: Maintain an up-to-date list of all building-connected devices and their firmware/software versions.
  • Vendor vetting: Require vendors to follow secure deployment practices—no open remote desktop, exposed ports, or weak credentials.

⚠️ Common Pitfalls to Avoid

  • Leaving contractor VPN access always-on with no audit trail
  • Assuming your building management vendor handles cybersecurity
  • Failing to monitor internal east-west traffic from BAS to core systems
  • Deploying “smart” sensors without secure provisioning

🧱 Applying Zero Trust to BAS

Zero Trust means no implicit access—even for thermostats. Enforce least privilege at the device level. Authenticate access to every building control system. Continuously monitor behavior and isolate abnormal activity fast.

Your building is part of your attack surface. Don’t treat it as an afterthought.

📣 Final Thought

When the lights go out or the HVAC shuts down, it’s not just uncomfortable—it can be catastrophic. BAS is no longer just operational—it’s critical infrastructure.

Need help securing your building systems before attackers find the gaps? Let’s talk.

Scroll to Top