BACnet/IP exposure in building automation: what it means and how to check
BACnet/IP lets HVAC, lighting and access-control systems in a building talk to each other over UDP port 47808, and it has no built-in authentication — any device that can reach that port can send it commands. AdminKit's port-check tool only probes TCP today, so this guide explains how to check your UDP exposure manually.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- BACnet/IP carries building automation traffic (HVAC, lighting, access control) over UDP, normally port 47808. IANA registers 47808 for BACnet on both UDP and TCP.
- The original BACnet/IP transport has no authentication. Anyone who can send packets to a controller can read and, in many cases, write its points.
- BACnet Secure Connect (BACnet/SC) adds TLS and certificates, but it sits alongside BACnet/IP rather than replacing it, and most installed controllers still use the original transport.
- AdminKit’s port check tests TCP only. Check UDP/47808 by hand from outside the building network, preferably with a BACnet-aware probe, then segment the network and route remote access through an authenticated gateway.
What is BACnet/IP, and why is it worth checking for?
BACnet (Building Automation and Control Networks) is the dominant interoperability standard for commercial building systems — it’s how an HVAC unit from one manufacturer, a lighting controller from another, and a central building-management workstation from a third can all read and write the same shared data points. BACnet/IP is the variant that runs the protocol over standard IP networks using UDP, typically on port 47808, rather than the dedicated serial or ARCNET wiring the original 1995 standard assumed. CISA’s Internet Exposure Reduction Guidance lists “47808/TCP – BACnet: Building automation and control networks” explicitly among the ports organizations should check when looking for unintended internet exposure of operational technology.
Why is a missing password on BACnet/IP such a big deal?
BACnet/IP was designed on the assumption that a building automation network would be physically isolated — connected only to the building’s own equipment, with no path to any outside network. Under that assumption, authenticating every command made little practical sense, so the protocol simply doesn’t include it: any device that can send a BACnet/IP packet to a controller can issue commands to it, and the controller has no built-in way to verify the sender is authorized. That design choice was reasonable for a standalone 1990s building network; it’s a significant liability once the same network is bridged, even informally, to a corporate IT network or the internet.
The industry’s answer to this gap is BACnet Secure Connect (BACnet/SC), documented by BACnet International, the organization that maintains the BACnet standard — added as an addendum that carries BACnet traffic over a TLS-encrypted, certificate-authenticated connection instead of the original unauthenticated broadcast transport. It’s a genuine fix where deployed — but it sits alongside the original BACnet/IP in the standard rather than replacing it, and most installed building systems, often running on controllers expected to last a decade or more, still speak the original, unauthenticated protocol.
What a BACnet client can ask a controller to do
BACnet models every device as a set of objects (analog inputs, binary outputs, schedules, the device itself), each with properties. Clients work with those objects through standard services defined in ANSI/ASHRAE Standard 135, the BACnet standard that BACnet International and ASHRAE maintain. A few services matter most when you think about exposure:
| Service | What it does | Why it matters if reachable from the internet |
|---|---|---|
| Who-Is / I-Am | Asks devices to announce themselves; devices reply with their identity | Lets anyone list the controllers behind an address |
| ReadProperty / ReadPropertyMultiple | Reads values such as temperatures, states, names, vendor and model | Leaks the building’s layout, equipment and firmware |
| WriteProperty | Changes a value, such as a setpoint, a schedule or an output command | Changes how the building behaves, with no login |
| DeviceCommunicationControl / ReinitializeDevice | Silences or restarts a device; may be protected by a device password, depending on the product | Can take controllers offline |
None of these are flaws. They are how building systems are supposed to be integrated, on a network where every sender is trusted. That is why the fix is to control who can reach the port, not to wait for a patch.
BBMDs and foreign devices
BACnet relies heavily on broadcasts, such as a Who-Is sent to every device on a subnet. Routers do not forward broadcasts, so BACnet/IP sites spanning several subnets use a BACnet Broadcast Management Device (BBMD) to relay them. A BBMD can also accept registrations from “foreign devices”: single hosts elsewhere on the network that ask to receive the site’s broadcasts. That feature is useful for a remote engineering workstation. On a BBMD reachable from the internet, it can give an outside host a view of the whole BACnet network, not just the one controller at the forwarded address. If your site uses a BBMD, treat its address as the most sensitive BACnet endpoint you have.
How does BACnet exposure actually happen?
Building operators rarely intend to put automation controls on the public internet. Exposure tends to come from a few recurring patterns:
- Convergence with the general IT network. Many newer buildings deliberately connect BACnet segments to the corporate network for centralized monitoring and remote facilities management — a reasonable design that depends entirely on correct network segmentation to stay safe.
- Remote-access tools configured too broadly. A remote support or monitoring tool set up for a vendor’s convenience can end up forwarding more of the network than intended, especially when the rule was added once and never revisited.
- Multi-tenant or multi-site buildings with flat networking. A single misconfigured router or VPN in one part of a larger network can expose building controls that were assumed to be isolated behind it.
How do I check my own BACnet exposure?
- Identify your public IP using AdminKit’s what is my IP tool as the starting point for any exposure test.
- Test whether port 47808 responds from outside your network. AdminKit’s port check tool probes TCP on a fixed list of nine ports — BACnet/IP’s UDP port 47808 isn’t on that list, so run a UDP-aware check such as
nc -u -vz your-public-ip 47808instead, only against systems you own or are authorized to test. - If it responds, trace why — check firewall rules, router port-forwarding configuration, and any remote-access or monitoring tool connected to the building network, rather than assuming the exposure is deliberate.
- Segment building automation networks from general IT and the internet using VLANs or a dedicated firewall, and treat any remaining remote-access need as something to route through a managed, authenticated gateway rather than a direct port forward.
A BACnet-aware check and how to read it
A plain nc -u test is weak for UDP, because a silent port could be open or filtered. A probe that speaks BACnet gives a clear answer. The Nmap bacnet-info script sends standard BACnet requests and, according to its documentation, “discovers and enumerates BACNet devices” and “collects device information based off standard requests.” Run it from outside the site against your own public address only (a documentation address is shown):
sudo nmap -sU -Pn -p 47808 --script bacnet-info 203.0.113.40
| Result | Meaning | Next step |
|---|---|---|
| Script output with device fields (vendor, model, firmware, object name) | A BACnet device answers from the internet and discloses its identity | Treat as urgent: remove the forward or firewall rule today |
| Port reported open, with a BACnet error response | A BACnet device is reachable but did not answer the standard requests; the script notes this still “positively identifies the device as a BACNet device” | Same as above |
open|filtered with no script output | No BACnet reply was received | Likely not exposed; repeat once and record the result |
closed | The host answered with ICMP port unreachable | Not exposed on 47808 |
Also check whether your building network uses a non-default UDP port; some sites move BACnet/IP to 47809 or nearby ports for separate networks, and a test of 47808 alone will miss them.
Segmenting the building network
Once you know what is reachable, the network-side fix usually looks like this on the firewall between the building automation VLAN and everything else:
# Building automation (BAS) VLAN: 10.20.0.0/24
allow udp 10.30.5.10 (BMS workstation) -> 10.20.0.0/24 port 47808
allow udp 10.20.0.0/24 -> 10.30.5.10 port 47808
deny udp any -> 10.20.0.0/24 port 47808
deny any internet -> 10.20.0.0/24
# No port forward from the WAN to any BAS address
The exact syntax depends on your firewall, but the shape stays the same: only the systems that need BACnet can reach it, and nothing on the internet can. Vendors who need remote access get it through an authenticated, logged path that terminates outside the BACnet VLAN, not a forwarded UDP port.
Keep in mind that a reachability test from outside only means as much as your network’s own addressing allows — if the gateway’s public IP is dynamic or shared via Carrier-Grade NAT, see our CGNAT guide for why that can affect whether a given result still applies the next time you check.
What should I ask my building automation vendor?
Much of a building network is set up and maintained by integrators, so the questions below are often the fastest way to find out where you stand:
- Which of our controllers, BBMDs and workstations are reachable from outside the building automation VLAN, and through what path?
- How do your technicians connect remotely, and is that path authenticated, logged and switched off when not in use?
- Do any of our controllers support BACnet/SC, and what would a move to it involve for this site?
- Which firmware versions are installed, and how are updates delivered?
Write the answers into the same record as your exposure checks, so the next person can see what was agreed.
Where AdminKit fits for ongoing OT access
Checking for exposure once tells you today’s state; building automation networks change as equipment is added, replaced, or reconfigured by different vendors over the building’s lifetime — see using port check to inventory IoT and OT device exposure for turning a one-off check like this into a dated record you can compare against next time. If you need remote access to a building system without that exposure, OT Remote Access is a Netbase custom engagement that gives facilities and integrators outbound-only, recorded remote sessions to OT networks like BACnet/IP without exposing the underlying protocol directly to the internet — talk to our team about your site, or see our factories and facilities page for the free checks and the services around them.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
What does BACnet/IP actually control?
Building Automation and Control Networks — HVAC systems, lighting schedules, access-control door controllers, fire and life-safety monitoring points, and similar building-management equipment. It's an industry-standard way for devices from different manufacturers to interoperate on the same building network.
Why doesn't BACnet/IP have authentication built in?
BACnet originated as a serial-based protocol designed when building automation networks were physically isolated from other systems and the internet entirely — there was no perceived need for authentication on a network nobody outside the building could reach. That assumption no longer holds once the same network gets connected to the internet, directly or indirectly, but the base protocol's lack of authentication hasn't changed.
Has this actually been fixed?
Partially — the BACnet standard added BACnet Secure Connect (BACnet/SC) as an addendum, which carries traffic over an encrypted, certificate-authenticated connection instead of the original unauthenticated UDP broadcast. It's additive, not a replacement: most existing BACnet/IP installations still run the original, unauthenticated version, and migrating a deployed building system is a significant undertaking most facilities haven't done.
What can someone do if they reach an exposed BACnet/IP device?
Read and write points on the building automation network — for example, changing HVAC setpoints, disabling alarms, or manipulating access-control points — without any credential check, because the protocol has no concept of authenticating who's allowed to send a given command.
Why would a BACnet device ever be reachable from the internet in the first place?
Usually indirectly: a building's BACnet network gets bridged to a general IT network for remote monitoring or vendor support convenience, and a misconfigured router, firewall rule, or remote-access tool meant for one purpose ends up exposing the BACnet segment more broadly than intended — not because anyone deliberately decided to put building controls on the open internet.
How do I check if a BACnet device is reachable externally?
AdminKit's [port check](/tools/port-check/) tool probes TCP ports on a fixed list of nine, and BACnet/IP's UDP port 47808 isn't among them. Confirm this one manually with a UDP-aware scanner (e.g. `nc -u -vz your-public-ip 47808`) run from outside your network — the direct way to confirm whether a building automation segment is reachable where it shouldn't be.
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.