November 17, 2026

BACnet Secure Connect: What It Fixes and What It Doesn't

BACnet Secure Connect: What It Fixes and What It Doesn't

Securing the Smart Building Stack Part 2: BACnet Secure Connect, What It Fixes and What It Doesn't

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.

What changes on the wire

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:

  • Discovery is no longer open. A laptop plugged into an office port cannot send Who-Is and map your building, because it cannot connect without a certificate.
  • Traffic is encrypted and tamper-evident. Object names, values and commands cannot be read or altered in transit.
  • Writes have a known source. A WriteProperty arrives over a connection from an authenticated device, not from any address that can reach UDP 47808.
  • It fits ordinary IP networks. Because broadcasts travel through the hub over TLS connections rather than as UDP broadcasts, SC does not need the BBMDs that BACnet/IP uses to pass broadcasts between subnets.

What it doesn't fix

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.

Should you specify it?

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:

  • Who runs the CA? If your integrator holds the CA and leaves, you inherit a certificate system nobody can renew.
  • What certificate lifetime, and who renews? Put the renewal date in your maintenance plan.
  • Where do the hubs run, and what happens when the primary fails?
  • What is the vendor's plan for 135-2020cp authorization?

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.

Frequently asked questions

What is BACnet Secure Connect?

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.

What does BACnet/SC not fix?

Authorization, legacy MS/TP and BACnet/IP segments behind routers, certificate expiry and revocation, and the hub as a single point everything depends on.

Should I specify BACnet/SC in a new building?

Yes for new construction and major retrofits. In existing buildings, keep your segmentation and introduce SC first where BACnet crosses shared IP networks.

Other articles in this series

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.

  • Consulting: deciding where to use BACnet/SC, and planning certificates, hubs and segmentation.
  • Procurement: contract terms for who runs the CA, certificate lifetime, hubs and authorization.
  • Project management: commissioning and certificate renewal dates delivered and tracked.

Book a free consultation

References

  1. ASHRAE, Addendum bj to ANSI/ASHRAE Standard 135-2016 (BACnet/SC), approved November 18, 2019: https://www.ashrae.org/File%20Library/Technical%20Resources/Standards%20and%20Guidelines/Standards%20Addenda/135_2016_bj_20191118.pdf
  2. ASHRAE, Addendum cp to ANSI/ASHRAE Standard 135-2020 (Authentication and Authorization), approved November 29, 2024: https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/135_2020_cp_20241129.pdf
  3. BACnet Committee, ANSI/ASHRAE 135-2024 now published: https://bacnet.org/news/ansi-ashrae-135-2024-now-published/
  4. ASHRAE, Managed BACnet Guidance Volume 1: Manufacturer's Guide (August 2025): https://www.ashrae.org/file%20library/technical%20resources/bookstore/managedbacnet.pdf
  5. Zhang et al., BACnet or "BADnet"?, NDSS Symposium 2026: https://www.ndss-symposium.org/wp-content/uploads/2026-s794-paper.pdf
  6. BACnet Testing Laboratories, BTL Test Package 23: https://bacnet.org/news/bacnet-testing-laboratories-btl-working-group-releases-new-btl-test-package-23/
  7. BTL Listing, BACnet Secure Connect Hub (accessed November 7, 2026): https://www.bacnetinternational.net/btl/index.php?pr=32
  8. Veridify (vendor), Improving BACnet/SC deployment with automated certificate management (February 21, 2024): https://www.veridify.com/article/improving-bacnet-secure-connect-bacnet-sc-deployment-with-automated-certificate-management/
  9. Regulation (EU) 2024/2847, Cyber Resilience Act: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng
  10. National Cybersecurity Authority (Saudi Arabia), OTCC-1:2022: https://cdn.nca.gov.sa/ar/otcc_en.pdf

‍

Author:
Editorial Team