
BACnet Secure Connect answers the question Part 1 left open: who sent this command? It does not answer the next one: should they be allowed to?
ASHRAE approved BACnet Secure Connect (BACnet/SC) in November 2019 as Addendum bj to Standard 135-2016, and folded it into 135-2020. It replaced the older network security clause in the standard, and it is the approach vendors now ship. If you are specifying a new building or a major controls upgrade, you will be asked whether you want it. You should know what you are buying.
BACnet/SC carries BACnet messages over WebSockets secured with TLS 1.3, and both ends of every connection must authenticate. Each device holds its own operational certificate, signed by a certificate authority (CA) that the other devices trust. A device without a valid certificate cannot join the network.
The topology changes too. Instead of UDP broadcasts, every node connects to a hub. The primary hub forwards messages between nodes and distributes broadcasts; a failover hub is optional. Devices can also open direct connections to each other, but they must stay connected to the hub.
Against the weaknesses in Part 1, that buys you a lot:
Authentication is not authorization. In BACnet/SC as originally published, every device admitted with a trusted certificate has equal authority. ASHRAE's own guidance puts it plainly: without an authorization mechanism, a successfully authenticated device can issue any BACnet request. A compromised front-end workstation with a valid certificate can still write any setpoint in the building. Addendum 135-2020cp, approved in November 2024 and included in 135-2024, adds per-request authorization with scopes such as view, adjust, control and override. It is new, and at the time of writing we found no BTL-listed products that support it.
Legacy segments stay legacy. Most buildings will run SC at the supervisory level and keep MS/TP and BACnet/IP controllers behind routers. SC protection ends at that router. Researchers presenting at NDSS 2026 crashed the device process of a vendor's SC-connected building management software with malformed MS/TP traffic, without a certificate.
Certificates expire. ASHRAE warns that if certificates are not replaced before they expire, devices cannot connect, and recovery may need vendor-proprietary tools. A wrong clock can do the same, and BACnet time synchronization has no authorization of its own. Revocation is left as a local matter: the standard defines no interoperable way to revoke a certificate, so removing a compromised device in practice means reissuing certificates to the devices that remain. One vendor described a site of more than 300 devices that chose 10-year certificates to avoid renewal work. That is a trade-off between labour and exposure, and you should make it on purpose.
The hub becomes critical infrastructure. Every message goes through it. Plan the failover hub, decide where both run, and protect them as critical assets.
For new construction and major retrofits, yes. BTL test packages include BACnet/SC (Test Package 23, December 2022), and the BTL listing for SC hubs includes products from 27 manufacturers, among them Siemens, Johnson Controls, Honeywell, Tridium, Schneider Electric, Distech and Delta. In the EU, the Cyber Resilience Act will require products with digital elements, based on their risk, to protect against unauthorized access and protect data in transit from December 11, 2027, and SC is one way building controller manufacturers can meet that. Saudi Arabia's OTCC already requires critical operators to protect OT data in transit according to its classification.
For existing buildings, do not rip out working controllers to get SC. Keep the segmentation and firewall rules from Part 1, and introduce SC where BACnet crosses shared IP networks first: between the front-end, supervisory controllers and routers.
Before you sign, settle four questions in the contract:
BACnet/SC tells you a command came from a device you trusted at commissioning. Keeping that trust current is now an operations job, not a protocol feature.
Next in this series: which building system vulnerabilities actually matter.
It is the ASHRAE-approved way to carry BACnet over TLS 1.3 WebSockets, with a certificate on every device and a hub that passes the messages. Both ends of every connection must authenticate.
Authorization, legacy MS/TP and BACnet/IP segments behind routers, certificate expiry and revocation, and the hub as a single point everything depends on.
Yes for new construction and major retrofits. In existing buildings, keep your segmentation and introduce SC first where BACnet crosses shared IP networks.
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.