Course contentsShow
← Security
Lesson 2787 of 3,05252. Embedded and IoT SecurityFree lesson

BACnet and Modbus Protocol Security

Building and industrial automation protocols, lack of native security, common attacks on SCADA systems, and securing legacy protocols.

BACnet and Modbus Protocol Security

What you'll learn: How legacy building and industrial automation protocols lack native security features and what attacks they face in modern SCADA environments.

The Industrial Protocol Problem

BACnet (Building Automation and Control Networks) and Modbus are foundational protocols in SCADA (Supervisory Control and Data Acquisition) systems—controlling everything from HVAC systems to power grid substations. Here's the critical issue: both were designed decades ago with zero security features, assuming trusted, isolated networks that no longer exist.

Think of it like leaving your house unlocked because you live in a small town. That worked in 1979, but not when the town connects to a global highway.

How They Work (Insecurely)

BACnet communicates building systems using simple request-response messages over IP, UDP, or serial lines. No authentication, no encryption—devices trust all commands.

Modbus uses a master-slave architecture where a controller (master) polls field devices (slaves) for readings or sends control commands. Originally serial (RS-485), Modbus TCP simply wraps these messages in TCP/IP—still plaintext, still unauthenticated.

Common Attacks on SCADA Systems

  • Command injection: Attacker sends forged Modbus commands to shut down equipment or manipulate sensors
  • Eavesdropping: Capture plaintext traffic to map system architecture and gather credentials
  • Replay attacks: Record legitimate commands and replay them later
  • Device impersonation: Pretend to be a master controller or sensor
  • Denial of service: Flood networks with malformed packets

Securing Legacy Protocols

Since you can't rebuild millions of deployed devices:

  • Network segmentation: Isolate SCADA networks from IT networks and the internet
  • VPN tunnels: Encrypt traffic between sites using IPsec or TLS wrappers
  • Protocol gateways: Insert security-aware proxies that validate commands
  • Anomaly detection: Monitor for unusual command patterns or timing
  • Physical security: Limit physical access to prevent serial port exploitation

Key Takeaway: BACnet and Modbus have no native security; protecting them requires defense-in-depth strategies focused on network isolation, encrypted tunnels, and behavioral monitoring rather than protocol-level security.