Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

BACnet protocol security: why building automation runs unauthenticated, and what BACnet/SC changes

Last updated:

BACnet (Building Automation and Control Networking protocol) is the dominant protocol behind commercial building automation — HVAC, lighting, access control, fire and life-safety systems all speak it — and its most common transport, BACnet/IP, broadcasts commands over UDP with no authentication or encryption by default, standardized as ANSI/ASHRAE Standard 135. A secure option, BACnet/SC, exists since a 2019 addendum, but a decade of CISA ICS advisories against building-automation vendors shows that most documented BACnet failures are implementation bugs and exposed web interfaces, not breaks in that secure option itself — largely because most deployed BACnet equipment doesn't run it.

Key takeaways

  • Authentication on ordinary reads and writes.
  • A handful of discovery, write and device-control services.
  • A TLS 1.3 stack, certificate handling and a real factory reset.
  • The ones in the protocol decoders, because they ship inside many controllers.

What does ASHRAE Standard 135 leave open?

Authentication on ordinary reads and writes. BACnet's application layer is defined by ANSI/ASHRAE Standard 135, under continuous maintenance by ASHRAE's Standing Standard Project Committee 135 and currently at edition ANSI/ASHRAE 135-2024. It covers the services a device uses to discover peers (Who-Is/I-Am), read and write properties, and exchange alarms and schedules. ReadProperty and WriteProperty requests carry no credential or signature. The only password in the base protocol is an optional field of 1 to 20 characters on two device-management services, and it travels in clear text (see the next section). BACnet/IP's addressing model relies on UDP broadcasts that any device on the same segment can listen to and, in many deployments, answer. That design reflects BACnet's origin on physically isolated building-controls networks. It has aged the same way Modbus and pre-2012 DNP3 have: the traffic now runs over general-purpose IP networks and remote-access VPNs, and in a meaningful number of documented cases it is reachable directly from the internet.

Which BACnet messages matter for security on the wire?

A handful of discovery, write and device-control services. BACnet/IP wraps every message in a BACnet Virtual Link Control (BVLC) header and commonly uses UDP port 47808. The service names below come from the open-source bacnet-stack library and CISA's ICSNPP BACnet parser for Zeek, which logs each one:

Message What it does Why it matters
Who-Is / I-Am, Who-Has / I-Have Broadcast discovery of device instances and objects Gives anyone on the segment a full device list with no request to a server
ReadProperty / ReadPropertyMultiple Reads any object property, including model name and firmware revision Fingerprinting and reconnaissance, unauthenticated
WriteProperty / WritePropertyMultiple Changes setpoints, schedules, output values A direct process change; the decoders for these services are where recent stack CVEs sit
ReinitializeDevice Restarts the device or changes its backup/restore state Optional password, sent in clear text
DeviceCommunicationControl Tells a device to stop answering for a set number of minutes The same optional clear-text password; a denial of service by design if misused
BVLC Register-Foreign-Device Lets a host outside the subnet join its broadcast domain through a BBMD A remote host can receive every broadcast if the BBMD accepts any registration

ICSNPP's bacnet_device_control.log records the password field for the two device-control services, which shows how much protection it gives: anyone with a mirror port can read it.

Is BACnet/SC a real fix, if it's actually running?

BACnet Secure Connect (BACnet/SC) is a secure datalink-layer option first introduced through Addendum 135-2016bj — which went through ASHRAE's standard 45-day public review (21 June–5 August) before adoption — and later folded into Annex AB of the ASHRAE 135-2020 edition. Rather than patching UDP broadcast, BACnet/SC replaces it with a connection-oriented transport over WebSockets and TLS: devices authenticate each other with certificates and encrypt the BACnet messages they exchange, so, per BACnet International's own description, "no device on the network can determine the content of secure messages unless they have the appropriate encryption keys." Subsequent addenda rounded out the mechanics — Addendum 135-2020cd defines the TLS 1.3 cipher-suite profile BACnet/SC uses, Addendum 135-2020cc updated the Network Port object so a device can represent and configure its BACnet/SC state, and Addendum 135-2020cs defined an offline certificate-exchange file format for sites that can't run a live certificate authority. Critically, BACnet/SC changes the transport, not the application layer: a device running it still exposes the same objects and services a BACnet/IP device does, just over an authenticated, encrypted channel instead of a broadcast one. BACnet International itself frames adoption as still maturing, noting it built a reference implementation and test bench specifically "to help suppliers gain in-house technical knowledge" — language that reads as an acknowledgment that BACnet/SC support in deployed equipment remains a minority, similar to DNP3 Secure Authentication's described uptake.

What does BACnet/SC require from a controller maker?

A TLS 1.3 stack, certificate handling and a real factory reset. Addendum 135-2016bj spells out the device side:

  1. TopologyEvery BACnet/SC node keeps one connection to a hub function, with a failover hub for redundancy. Direct node-to-node connections are optional and need a "node switch" function.
  2. TransportOnly TLS-secured WebSocket connections (wss) are used, and "Support of TLS V1.3 is required." A node must refuse to connect to a URI with any other scheme.
  3. Mutual authenticationBoth peers check that the other's operational certificate is well formed, current, not revoked where that information exists, and "directly signed by one of the locally configured CA certificates." Name checks are off by default and only run "if specifically enabled."
  4. CredentialsEach device holds a unique operational certificate, its private key and a CA certificate store. A device that can generate its own key pair must not expose the private key; otherwise a configuration tool generates it, and the key "shall only be transferred in a secured environment, or over communication secured by TLS."
  5. Factory defaultsA reset must "erase all operational certificates and respective private keys and all CA certificates" plus other sensitive data, through an out-of-band mechanism for which physical access is recommended. Merely blocking access to old data is not allowed.

For a product team, items 4 and 5 are the ones that need hardware decisions: key storage, a physical reset path, and erase routines that really erase. The same themes appear as component requirements in IEC 62443-4-2.

Where do documented BACnet failures sit?

Advisory Vendor / product CVE(s) CVSS What it actually allowed
ICSA-16-126-01 (2016, rev. 2018) KMC Controls Conquest BAC-5051E router CVE-2016-4494, CVE-2016-4495 5.3 / 5.3 (v3) Missing-authentication and CSRF flaws let an unauthorized remote user read configuration data from a file
ICSA-17-285-05 (Update A) Siemens APOGEE PXC / TALON TC BACnet field panels CVE-2017-9946, CVE-2017-9947 7.5 / 5.3 Authentication bypass on the integrated web server (download sensitive data); path traversal exposing file-system structure
ICSA-25-135-03 Siemens BACnet ATEC devices (550-440/441/445/446) CVE-2025-40556 7.1 (v4) / 6.5 (v3.1) Crafted BACnet MSTP message from the same network causes denial of service; no vendor fix scheduled

The pattern across nine years of these advisories is consistent: the authentication and path-traversal bugs sit in vendor web management interfaces bolted onto BACnet field panels, not in BACnet/SC's TLS handshake, and the most recent finding — CISA's ICSA-25-135-03 — is a denial-of-service in MSTP message parsing that Siemens has stated it will not patch — meaning network access control is not a stopgap there, it's the only control. A building network that segments BACnet traffic from the general IT network, and keeps vendor and contractor remote-access paths off that segment, stops most of what these advisories describe regardless of whether BACnet/SC is deployed.

Which open-source BACnet stack CVEs should firmware teams track?

The ones in the protocol decoders, because they ship inside many controllers. bacnet-stack describes itself as an "open source protocol stack C library for embedded systems", and NVD lists a run of decoder bugs in it:

CVE Published (NVD) Issue Affected versions
CVE-2019-12480 30 May 2019 Malformed requests crash the server (DoS); CVSS 3.0 7.5 through 0.8.6
CVE-2023-51773 29 Feb 2024 APDU buffer over-read in bacapp_decode_application_data before 1.3.2
CVE-2026-26264 13 Feb 2026 Truncated WriteProperty request causes a length underflow and crash before 1.4.3rc2 and 1.5.0rc4
CVE-2026-41475 24 Apr 2026 Truncated WritePropertyMultiple request reads 1–7 bytes past the buffer; NVD CVSS 3.1 9.1 before 1.4.3

All four are reachable without authentication on plain BACnet/IP. A controller vendor that forked the stack years ago needs to know which version each product line carries, which is what a firmware SBOM records.

How do you monitor BACnet passively?

With Zeek and the ICSNPP BACnet plugin on a mirror port. It writes four logs: bacnet.log (headers), bacnet_discovery.log (Who-Is, I-Am, Who-Has, I-Have), bacnet_property.log (ReadProperty and WriteProperty) and bacnet_device_control.log (ReinitializeDevice and DeviceCommunicationControl). Useful alert rules for a building network:

  • any ReinitializeDevice or DeviceCommunicationControl request outside a maintenance window;
  • WriteProperty from a host that is not the building management server or a known engineering laptop;
  • a Register-Foreign-Device from an address outside the site;
  • BACnet/IP to or from a public IP address;
  • a BACnet/SC-capable device still answering plain BACnet/IP after migration.

Worked example: what does a BACnet review of one building find?

Synthetic example, not a real site. An office building has one supervisory server, eight field controllers and a BBMD for a second floor subnet. A one-week capture shows:

Observation Why it matters Action
A laptop on the guest Wi-Fi sends Who-Is and gets eight I-Am replies BACnet is reachable from the guest network Move BACnet to its own VLAN behind a firewall
DeviceCommunicationControl from the integrator's laptop, password in the log The password is visible to anyone on the mirror Rotate it, restrict the service by source address
Controllers report firmware with a bacnet-stack version below 1.4.3 (vendor release notes) CVE-2026-41475 and CVE-2026-26264 apply Ask the vendor for patched firmware
The supervisory server lists BACnet/SC support; no wss traffic seen Support on paper, not in use Plan hub and certificate rollout

What should a building owner or integrator do first?

  1. Find out what's actually reachableBACnet/IP's broadcast model and the routine practice of opening remote access for HVAC vendors make internet-exposed building controllers a recurring, documented finding — confirm nothing on the BACnet segment is reachable from outside the building network before anything else.
  2. Patch field panels and routers on current firmwareThe KMC Controls and Siemens findings above are implementation bugs independent of BACnet/SC; a secure transport option doesn't patch an authentication-bypass bug in a device's web server.
  3. Check whether BACnet/SC is actually negotiated, not just supported on a datasheet, on devices capable of it — unenabled support provides no protection, the same caveat that applies to DNP3 Secure Authentication.
  4. Segment regardless of the aboveIsolate BACnet/IP traffic (commonly UDP port 47808) behind firewalls from business and guest networks, consistent with CISA's standing recommendation across every advisory cited here — including the one Siemens has said it will not fix.
  5. Treat building automation as part of the same OT architecture discipline as industrial controlThe Purdue Model and NIST SP 800-82 apply to a BACnet-driven building network the same way they do to a Modbus- or DNP3-driven industrial one. Supervisory platforms such as Niagara add their own protocol; see Niagara Fox security.

What are the common pitfalls?

  • Treating the DeviceCommunicationControl password as access control. It is a clear-text string.
  • Leaving a BBMD to accept foreign-device registrations from anywhere.
  • Counting a BACnet/SC datasheet line as deployment, without a hub, certificates and a CA store on every node.
  • A factory reset that keeps old keys or site data, which Addendum bj forbids.
  • Patching the web interface but not the embedded BACnet stack.

What does a SoftWSP OT Snapshot show for BACnet?

SoftWSP's OT Snapshot works from Zeek and CISA ICSNPP logs of a passive capture taken off a mirror port. It builds a host-by-port inventory, lists interactive remote-access sessions (SSH, Telnet, RDP, VNC) that cross from outside the private address range, and labels hosts that answer BACnet as BACnet devices. A capture does not give a controller's model or firmware with certainty, so an engineer confirms those. With a component list or firmware SBOM, Device & Firmware Security matches them against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories. AI drafts the plain-language summary, cites the log line or record behind each finding, and an engineer reviews it before it goes into a report.

This guide draws on ASHRAE's published addendum PDFs, BACnet International's description of BACnet/SC, the bacnet-stack and ICSNPP source repositories, NVD records and CISA's published ICS advisories. It is not a substitute for ASHRAE Standard 135 itself, CISA's own advisories, or an integrator's assessment of a specific site's configuration and patch level.

Put this guide to work

Frequently asked questions

Does BACnet have authentication or encryption built in?

The base protocol does not. BACnet (Building Automation and Control Networking protocol) is standardized as ANSI/ASHRAE Standard 135, maintained on continuous maintenance by ASHRAE's Standing Standard Project Committee 135, with the current edition ANSI/ASHRAE 135-2024. Its most common transport, BACnet/IP, relies on UDP broadcasts to discover and address devices, and its read and write requests carry no credential, session key or message signature (the only password, an optional field on the ReinitializeDevice and DeviceCommunicationControl services, travels in clear text) — any device that can reach a BACnet/IP segment can issue a Who-Is, Read-Property or Write-Property request that a controller will act on. That gap is structurally the same one Modbus and, before its 2012 revision, DNP3 have: a protocol built for a trusted, physically isolated network, now commonly running on IP infrastructure that isn't isolated at all.

What is BACnet/SC, and does it actually close that gap?

BACnet Secure Connect (BACnet/SC) is a secure datalink-layer option added via Addendum 135-2016bj — introduced through ASHRAE's standard addendum process, with a 45-day public review running 21 June to 5 August of that review cycle — and later formally incorporated into Annex AB of the ASHRAE 135-2020 edition. Per BACnet International's own description, BACnet/SC replaces BACnet/IP's UDP broadcast model with a connection-oriented transport built on WebSockets and TLS, using certificates to perform peer authentication and encrypt messages so "no device on the network can determine the content of secure messages unless they have the appropriate encryption keys." Later addenda extended it further: Addendum 135-2020cd specifies the TLS 1.3 cipher-suite application profile BACnet/SC uses, Addendum 135-2020cc updated the Network Port object so a device can represent and configure its BACnet/SC settings, and Addendum 135-2020cs defined an offline certificate-exchange file format. It closes the gap for devices and links that actually implement, configure and run it — exactly like DNP3's Secure Authentication and OPC UA's security model, it changes nothing for a controller still running plain BACnet/IP alongside it, which is the common case on a mixed or legacy building network.

What do real, documented BACnet security failures actually look like?

A mix of implementation bugs in vendor web interfaces and firmware, and denial-of-service findings in the protocol-handling code — not breaks of BACnet/SC's cryptography. CISA's ICSA-16-126-01 (published 5 May 2016, last revised 23 August 2018) covers KMC Controls' Conquest BAC-5051E BACnet router, where independent researcher Maxim Rupp found that its web interface let an unauthorized user read configuration data from a file via a missing-authorization check (CVE-2016-4495, CWE-306, CVSS v3 5.3) or via a cross-site request forgery attack (CVE-2016-4494, CWE-352, CVSS v3 5.3), both exploitable remotely with low attacker skill. CISA's ICSA-17-285-05 (Update A, originally published 12 October 2017, last revised 16 June 2022) covers Siemens APOGEE PXC and TALON TC BACnet field panels: CVE-2017-9946 (CWE-288, Authentication Bypass Using Alternate Path, CVSS 7.5) let an attacker with network access to the integrated web server bypass authentication and download sensitive information, and CVE-2017-9947 (CWE-22, Path Traversal, CVSS 5.3) let a remote attacker read the device's file-system structure. Most recently, CISA's ICSA-25-135-03 (published 15 May 2025) covers Siemens BACnet ATEC devices (models 550-440, 550-441, 550-445, 550-446): CVE-2025-40556 (CWE-20, Improper Input Validation, CVSS v4 7.1 / v3.1 6.5) lets an attacker already on the same BACnet network send a specially crafted MSTP message that forces a power cycle to recover from — and as of that advisory, Siemens has no plan to fix it, leaving network-layer controls as the only mitigation. None of these are failures of BACnet/SC itself; they are bugs and design gaps in devices that, in most deployments, have no Secure Connect layer enabled to even gate who can reach them.

What should a building owner or integrator actually check first?

Three things, roughly in order of what stops the most realistic incident. First, whether the BACnet/IP network is reachable from anything other than the building controls it needs to talk to — CISA's standing advice across every advisory above is network segmentation and keeping control-system devices off the public internet, and this matters more for BACnet than for most OT protocols because building-automation gear is routinely connected for remote vendor access or cloud dashboards. Second, whether field devices and web interfaces are on current firmware: the KMC Controls and Siemens findings above are patchable implementation bugs, not something BACnet/SC configuration fixes. Third, whether BACnet/SC is actually available and negotiated on devices that support it — a controller's datasheet listing BACnet/SC support is not the same claim as a live, certificate-provisioned BACnet/SC connection running in the field, the same distinction that matters for [DNP3 Secure Authentication](/guides/dnp3-protocol-security-ot-ics/) and [Modbus Security](/guides/modbus-protocol-security-ot-ics/). Where BACnet/SC isn't yet deployed across a site, the [Purdue Model](/guides/purdue-model-ot-ics-network-architecture/)'s segmentation layer and [NIST SP 800-82](/guides/nist-sp-800-82-ot-security/)'s compensating-control guidance are the same answer this guide's companion protocol guides give: the network has to hold the weight an unauthenticated field protocol doesn't.

Sources

  1. BACnet International: BACnet Secure Connect (BACnet/SC)
  2. ASHRAE: Addendum bj to ANSI/ASHRAE Standard 135-2016 (BACnet Secure Connect Datalink Layer Option, PDF)
  3. ASHRAE: Addendum cc to ANSI/ASHRAE Standard 135-2020 (Network Port object updates for BACnet/SC, PDF)
  4. CISA ICS Advisory ICSA-16-126-01: KMC Controls Conquest BACnet Router Vulnerabilities (last revised 23 August 2018; CVE-2016-4494, CVE-2016-4495)
  5. CISA ICS Advisory ICSA-17-285-05 (Update A): Siemens BACnet Field Panels (last revised 16 June 2022; CVE-2017-9946, CVE-2017-9947)
  6. CISA ICS Advisory ICSA-25-135-03: Siemens BACnet ATEC Devices (15 May 2025; CVE-2025-40556)
  7. bacnet-stack: open-source BACnet protocol stack C library (GitHub)
  8. CISA ICSNPP-BACnet: Zeek parser for BACnet (GitHub)
  9. NVD: CVE-2026-41475 (bacnet-stack WritePropertyMultiple out-of-bounds read)
  10. NVD: CVE-2026-26264 (bacnet-stack WriteProperty length underflow)
Was this guide helpful?

In this cluster

BACnet protocol security: why building automation runs unauthenticated, and what BACnet/SC changes