November 10, 2026

BACnet Security: Why BACnet Was Never Built for It

BACnet Security: Why BACnet Was Never Built for It

Securing the Smart Building Stack Part 1: Why BACnet Was Never Built for Security

A BACnet controller will accept a new setpoint from any device that can reach it and speaks the protocol. It does not ask who you are. That is not a bug in one vendor's product. It is how most BACnet networks in service today were designed to work.

If you own or operate a commercial building, a hospital, a campus or an airport terminal, BACnet probably runs your heating, cooling, ventilation and lighting. Understanding what it trusts, and what it does not check, decides where your security effort should go.

A protocol designed for a closed room

ASHRAE formed the committee that wrote BACnet in 1987 and published it as Standard 135 in 1995. It became an international standard, ISO 16484-5, in 2003. The goal was interoperability: a chiller from one manufacturer, air handlers from another and a front-end from a third, all exchanging data without proprietary gateways. It succeeded.

The assumption behind the design was a physically isolated network inside the building, reachable only by people with keys to the mechanical room. Researchers at the Technical University of Munich, who measured BACnet devices on the internet in 2016 and 2017, put it plainly: security was not a priority when the protocol was designed.

When BACnet/IP was added in 1999, the same trust model moved onto IP networks. BACnet/IP runs over UDP, by default on port 47808, with no handshake. As most installed devices implement it, BACnet/IP has no authentication at all.

What that means on your network

Three features make a BACnet network easy to integrate. Each one also helps whoever else gets onto that network.

  • Discovery by broadcast. A device sends Who-Is and every BACnet device in range answers with I-Am. Anyone on the segment can map your building in seconds.
  • Self-description. Devices answer ReadProperty requests with their vendor, model, firmware, and object names. Object names are often written for technicians, such as "AHU-3 Supply Air Temp Setpoint, Level 4 Data Room". The TUM researchers found that about 15% of the devices that answered them disclosed a serial number.
  • Writes without identity. WriteProperty changes a setpoint, a schedule or an output. A BACnet/IP device receiving it has no means to check who sent it. Security researchers testing BACnet/IP deployments in 2025 reported unauthenticated read and write access to all objects, with no audit trail of setpoint changes.

The priority array adds a further consequence. BACnet lets a command at a higher priority override one at a lower priority. Someone who writes at a high priority can hold a value in place over your operators' commands until that priority is released. A technician who does not know to check the priority array will see a point that refuses to obey.

What the internet adds

The 2017 TUM study found 16,485 BACnet devices reachable from the internet, about 60% in the US and 20% in Canada. Most could also be abused to amplify denial-of-service traffic aimed at third parties. The authors notified operators through a CERT; the count fell only slightly.

That number is about ten years old, and the exact count today matters less than what it means. A BACnet device reachable from the internet is reachable by everyone, and the protocol will not tell them apart.

Where your effort should go

You cannot patch authentication into a 2008 controller. Accept that, and put your controls around the protocol instead of inside it.

  • Keep BACnet off the internet. No exception for a vendor's convenience. Remote access goes through a gateway you control, with multi-factor authentication.
  • Separate the BAS network from the corporate network. A laptop on an office port should not receive I-Am replies. Ask your integrator to run a Who-Is from an ordinary office port, with your IT team present. If controllers answer, your building network is flat.
  • Restrict the BACnet ports (UDP 47808 by default) at the firewall to the specific supervisory servers and workstations that need it.
  • Review BBMDs. BACnet Broadcast Management Devices pass broadcasts between subnets and can register devices from other networks. Know where yours are and who can reach them.
  • Watch the writes. If you add monitoring, alert on WriteProperty commands from addresses that are not your front-end or engineering workstation.

ASHRAE added BACnet Secure Connect in 2019, with TLS and certificates. It fixes much of what is described above, on the devices that support it. Most installed controllers do not, and they will stay in your buildings for decades. Your network design is what stands in for the authentication they never had.

Next in this series: BACnet Secure Connect, what it fixes and what it doesn't.

Frequently asked questions

Why is BACnet security a network design problem?

Most installed BACnet/IP devices do not check who sends a command, so the controls have to sit around them: keep BACnet off the internet, separate it from the corporate network and restrict the ports.

Can older BACnet controllers be patched to add authentication?

Not in practice. BACnet Secure Connect adds TLS and certificates, but only on devices that support it.

How can I tell if my building network is flat?

Ask your integrator to run a Who-Is from an ordinary office port, with your IT team present. If controllers answer, it is flat.

Other articles in this series

  • Part 2: BACnet Secure Connect: What It Fixes and What It Doesn't (coming)
  • Part 3: Which Building System Vulnerabilities Actually Matter (coming)
  • Part 4: Cloud-Connected BMS and Shared Responsibility (coming)

Related reading

Planning a new smart building, upgrading the systems in an existing one, or buying technology for a facility? Actimeta is an OT cybersecurity and technology advisory firm that helps owners get the design, the vendors and the security right from the start.

Book a free consultation

References

  1. BACnet Committee, History of BACnet: https://bacnet.org/history/
  2. Gasser et al., The Amplification Threat Posed by Publicly Reachable BACnet Devices, Journal of Cyber Security and Mobility 6(1), 2017: https://journals.riverpublishers.com/index.php/JCSANDM/article/view/5227
  3. Gasser et al., Security Implications of Publicly Reachable Building Automation Systems, IEEE S&P Workshops 2017: https://portal.fis.tum.de/en/publications/security-implications-of-publicly-reachable-building-automation-s/
  4. Zero Science Lab, Breaking BACnet: protocol stack vulnerabilities (October 14, 2025): https://www.zeroscience.mk/lablog/breaking-bacnet-protocol-stack-vulnerabilities.html
  5. BACnet Committee, BACnet/SC (Addendum bj to ASHRAE 135-2016) published (December 2019): https://bacnet.org/news/bacnet-sc-published-at-long-last/

‍

Author:
Editorial Team