ThisCalculator

Everyday

Segment Building Automation from IT Networks

Updated · Standard formula, shown below

This guide explains how to separate building automation systems (BAS) from corporate IT networks to improve security, reliability, and compliance. You’ll learn the steps to create a network segmentation strategy, implement it with VLANs and firewalls, and maintain it over time. This approach reduces the risk of cyberattacks spreading from IT to building systems and prevents operational disruptions.

What You’ll Need

  • Network diagram of your current IT and BAS infrastructure
  • Inventory of all BAS devices (controllers, sensors, actuators, gateways) with IP addresses and communication protocols (e.g., BACnet, Modbus, LonWorks)
  • Access to your network switches, routers, and firewalls (admin credentials)
  • Knowledge of your BAS vendor’s communication requirements (ports, protocols)
  • A change management process (to schedule downtime and approvals)
  • Optional: a network access control (NAC) solution for device authentication

Step-by-Step

  1. Inventory all BAS devices and traffic. List every device that communicates with the BAS, including controllers, supervisory devices, workstations, and remote access points. Note their IP addresses, MAC addresses, and which protocols they use (BACnet/IP, Modbus TCP, etc.). Use packet capture or a network analyzer to map actual communication flows.
  2. Define security zones. Create at least three zones: a corporate IT zone (user workstations, servers), a BAS zone (controllers, sensors, actuators), and a DMZ (demilitarized zone) for services that need to be accessed from both sides (e.g., a BAS server that IT monitors). If you have multiple buildings, consider separate BAS zones per building or campus.
  3. Design the VLAN architecture. Assign each zone to a separate VLAN. For example, VLAN 10 for IT, VLAN 20 for BAS, and VLAN 30 for DMZ. Use private IP subnets (e.g., 192.168.10.0/24, 192.168.20.0/24). Ensure that BAS devices are not on the same subnet as IT devices.
  4. Configure switches and VLANs. On your managed switches, create the VLANs and assign ports to the appropriate VLAN. For BAS devices, connect them to ports that are in the BAS VLAN. If a BAS device has a built-in switch (e.g., a router), disable that switch or segment it as well. Use port security or 802.1X to prevent unauthorized devices from joining the BAS VLAN.
  5. Set up firewall rules between zones. Place a firewall between the IT zone and the BAS zone, and between the DMZ and both zones. Define rules that allow only necessary traffic. For example, allow the BAS server in the DMZ to communicate with BAS controllers on specific ports (e.g., BACnet/IP uses UDP 47808). Block all other traffic by default. Do not allow the BAS zone to initiate connections to the IT zone unless absolutely required.
  6. Implement remote access controls. If remote access to the BAS is needed, route it through a VPN that terminates in the DMZ, not directly into the BAS zone. Use multi-factor authentication (MFA) for remote access. Avoid using port forwarding from the internet to BAS devices.
  7. Test the segmentation. After configuration, test that BAS devices can communicate with each other and with the BAS server, but cannot reach IT resources unless explicitly allowed. Test that IT devices cannot reach BAS controllers directly. Use tools like ping, traceroute, and port scans from each zone to verify.
  8. Document and monitor. Update your network diagram and documentation with the new VLANs, subnets, and firewall rules. Implement logging and monitoring for the firewall and BAS network. Set up alerts for unusual traffic patterns or unauthorized access attempts.
  9. Establish maintenance procedures. Create a process for adding new BAS devices (they must be added to the correct VLAN), changing firewall rules (with approval), and reviewing logs regularly. Schedule periodic security audits of the segmentation.

Common Mistakes

  • Putting BAS and IT on the same VLAN – even if they are on different subnets, if they share a VLAN, broadcast traffic can cross and security is weaker.
  • Allowing too much traffic through the firewall – avoid rules that permit “any to any” or broad port ranges; be specific.
  • Forgetting about wireless BAS devices – if you have wireless sensors or controllers, they must be on a separate wireless network (SSID) with its own VLAN, not the corporate Wi-Fi.
  • Ignoring legacy devices – some older BAS devices may not support VLAN tagging or modern security; you may need to put them on a separate physical network or use a gateway.
  • Not testing after changes – always verify that the BAS still functions correctly after segmentation; a misconfigured rule can stop HVAC or lighting.

Tips

  • Use a “default deny” approach on the firewall: allow only what is explicitly required, block everything else.
  • If your BAS uses BACnet, consider using BACnet/SC (Secure Connect) which adds encryption and authentication, but it requires compatible devices.
  • Consider using a network access control (NAC) solution to automatically assign devices to the correct VLAN based on their MAC address or certificate.
  • Keep firmware and software on BAS devices updated, but test updates in a lab environment first because they can affect operations.
  • Work with your BAS vendor to understand which ports and protocols are truly necessary; they can provide a list.

Troubleshooting

  • BAS devices cannot communicate after segmentation. Check that the firewall rules allow the required protocols and ports. Verify that the VLANs are correctly configured on the switches and that the devices have the correct IP addresses and subnet masks. Use packet capture to see if packets are being dropped.
  • BAS server cannot reach controllers. Ensure the server is in the DMZ and the firewall allows traffic from the DMZ to the BAS zone on the required ports. Check that the controllers are responding to pings from the server.
  • IT users cannot access the BAS dashboard. If you have a web interface for the BAS, it should be in the DMZ. Make sure the firewall allows HTTPS (port 443) from the IT zone to the DMZ, and that the BAS server is configured to allow that access.
  • Unusual traffic or alarms. Check the firewall logs for denied traffic. If you see attempts from the BAS zone to the IT zone, investigate the source device – it may be compromised. Also check for any broadcast storms that could indicate a loop or misconfiguration.
  • Performance issues. If BAS communication becomes slow, check for network congestion or firewall throughput limits. Consider using a dedicated firewall for the BAS if the main firewall is overloaded.

Frequently Asked Questions

Why is it important to segment BAS from IT?

Segmentation limits the blast radius of a cyberattack. If an IT computer is compromised, the attacker cannot easily reach building controllers, which could be used to disable HVAC, unlock doors, or cause physical damage.

Can I use VLANs alone for segmentation?

VLANs provide logical separation, but they are not a security boundary by themselves. You need a firewall or router with access control lists to enforce rules between VLANs.

What protocols are commonly used in BAS?

Common protocols include BACnet (often over IP), Modbus, LonWorks, and KNX. Each has different port and communication requirements; your firewall rules must accommodate them.

How do I handle BAS devices that don’t support VLANs?

Place them on a separate physical switch that is connected to the firewall, and treat that switch as a separate zone. Alternatively, use a gateway that can translate between the legacy protocol and modern IP.

Should I put the BAS server in the DMZ?

Yes, if the server needs to be accessed by both IT and BAS, placing it in a DMZ allows you to control traffic to and from it without exposing the entire BAS zone.

How often should I review the segmentation rules?

At least annually, or whenever there are significant changes to your network or BAS. Also review after any security incident to ensure rules still align with your security policy.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.