
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.
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.
Three features make a BACnet network easy to integrate. Each one also helps whoever else gets onto that network.
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.
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.
You cannot patch authentication into a 2008 controller. Accept that, and put your controls around the protocol instead of inside it.
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.
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.
Not in practice. BACnet Secure Connect adds TLS and certificates, but only on devices that support it.
Ask your integrator to run a Who-Is from an ordinary office port, with your IT team present. If controllers answer, it is flat.
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.