Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is KNX Building Automation Security?

KNX is the European building automation bus standard used for lighting, blinds, heating, and sometimes door control, and in its original form any device on the bus can command any other.

Illustration for the cybersecurity term KNX Building Automation Security
Home / Blog / Cybersecurity Terms / What Is KNX Building Automation Security?
17 November 2026

What Is KNX Building Automation Security?

What Is KNX Building Automation Security?

KNX is the building automation standard most common in European construction, published as ISO/IEC 14543-3 and as the EN 50090 series. It controls lighting, blinds and shading, heating and cooling zones, ventilation, and in some installations door release and alarm integration, in everything from apartments to hotels, hospitals, and office towers. If a building was fitted out by a European electrical contractor in the past twenty-five years, there is a reasonable chance KNX is behind the wall switches.

How It Works

The classic medium is a twisted pair bus running alongside the mains at 9,600 bits per second, which is deliberately slow and extremely reliable. There are also radio and powerline variants, and KNXnet/IP, which tunnels or routes KNX over Ethernet so that a building can be commissioned and supervised from a workstation.

Devices are addressed in two ways. Each has an individual address used for configuration, and functions are tied together by group addresses: a switch writes to a group address, and every actuator subscribed to it responds. The entire configuration is produced in the Engineering Tool Software, and the resulting project file is the complete description of the installation.

Crucially, in classic KNX there is no authentication. A telegram sent to a group address is executed by whatever listens to it. The bus was designed on the assumption that anyone able to touch the wiring is already inside the building.

Where That Assumption Fails

Two ways, both common.

The first is network exposure. KNXnet/IP uses UDP port 3671, and the moment a building wants remote supervision or a contractor wants remote access, that port tends to appear on the internet. Internet-wide scans have repeatedly found thousands of unauthenticated KNX gateways reachable from anywhere, controlling residential, commercial, and public buildings. No exploit is required; the protocol does what it is told.

The best-known demonstration came at Black Hat USA in 2014, when a researcher staying in a Chinese luxury hotel reverse engineered the room automation tablet, discovered unauthenticated KNX over IP behind it, and showed that he could control lighting, blinds, temperature, and do-not-disturb signs in more than two hundred rooms from his own device. The point was not the hotel. The point was that a guest-facing tablet shared a flat network with the building’s control bus.

The second is physical. KNX cabling frequently runs to places outside the protected perimeter: outdoor pushbuttons, car park controls, external lighting, and intercom panels. A pair of wires reachable from a car park gives an attacker bus access to the whole installation unless the topology isolates it.

KNX Secure

The standards body addressed this with two complementary mechanisms. KNX Data Secure authenticates and encrypts telegrams at the group object level using AES-128 in counter mode with message authentication, adding freshness so that captured telegrams cannot be replayed. KNX IP Secure protects the IP side, wrapping tunnelling and routing in authenticated encryption with a backbone key.

Deployment requires compatible devices, a current version of the engineering tool, and handling of the device certificates, which are supplied as printed codes on each unit and must be captured during installation and kept with the project documentation. Lose them and the device must be factory reset. That administrative detail is the main reason installers skip Secure, so it belongs in the specification and in the handover checklist rather than being left to goodwill.

Practical Steps

  1. Nothing on the internet. Port 3671 should never be exposed. Remote access for the integrator goes through a monitored gateway with multi-factor authentication and recorded sessions.
  2. Separate networks. Guest Wi-Fi, room tablets, digital signage, and the building bus do not share a network. This single control would have prevented the hotel demonstration, and it is the same principle applied to CCTV and access control systems.
  3. Specify Secure for new work. On refurbishments and new build, require KNX Data Secure and IP Secure, with certificate handling defined in the handover documentation.
  4. Protect the project file. The ETS project describes every device and function in the building, and it is routinely emailed and left on contractor laptops. Password protect it, version it, and record who holds copies.
  5. Isolate exposed cabling. Use line couplers so that a bus segment reaching an outdoor panel cannot write to the segments controlling the rest of the building.
  6. Know what KNX controls. Lighting is an inconvenience; door release, smoke vent control, and critical area cooling are not. Classify by consequence and treat the serious functions as a separate zone under IEC 62443 principles.

For the wider estate, the same governance problems described under building management system security apply: unclear ownership, contractor-held credentials, and no entry in the asset register. KNX is usually a layer beneath a supervisory platform that also speaks BACnet, and the two should be assessed together.

At Privia Security, we test building automation networks and their gateways through our Network Security Services.

FAQ – Frequently Asked Questions

Does KNX Have Any Authentication by Default?

Classic KNX has none. Any device able to place a telegram on the bus, or to reach a KNXnet/IP gateway over the network, can write to any group address and operate whatever is subscribed to it. Authentication and encryption arrived with KNX Data Secure and KNX IP Secure, which use AES-128 with message authentication and freshness, but they must be specified and configured.

What Was the Hotel KNX Hack?

A researcher presented work at Black Hat USA in 2014 showing that the room automation tablet in a luxury Chinese hotel communicated with unauthenticated KNX over IP on a network shared with guest devices. From his own equipment he could control lighting, blinds, temperature, and room signage across more than two hundred rooms. The flaw was the flat network, not a software bug.

Is KNX Used for Security-Critical Functions?

Sometimes, which is why classification matters. Lighting and blinds are comfort functions; door release, smoke vent operation, and cooling for a comms room or laboratory are not. Where KNX touches a function with safety, security, or continuity consequences, that part of the installation should be isolated into its own segment with Secure enabled.

How Do I Check Whether My Building’s KNX Is Exposed?

Scan your own public address ranges for UDP port 3671 and check what your sites look like in public internet scanning data. Then ask the integrator how they connect for support, because the answer often reveals a router, a forwarded port, or a remote access tool that the network team has never been told about.

Related Terms

You May Be Interested In These

What Is Spyware?

Cybersecurity Terms

13 September 2021

What Is Spyware?

Read More
How Do You Build a Security Team?

Cybersecurity Terms

17 November 2026

How Do You Build a Security Team?

Read More
What Is SMB Protocol Security?

Cybersecurity Terms

17 November 2026

What Is SMB Protocol Security?

Read More