BMS cyber hygiene evidence for NHS, public and data-centre clients
A few years ago, the security of a building management system was rarely discussed outside specialist circles. Now an integrator bidding for NHS, public sector or data-centre work can expect questions about it in the tender, at the contract start and at every audit: what is on the network, who can reach it, how remote access works, and whether anything is exposed to the internet.
Most of those questions are not about advanced attacks. They are about basic hygiene, and the evidence for it. An integrator that can hand over a clear, current pack - without being asked twice - stands out, and makes the client's security lead's job easier. This article sets out what that pack contains and how it lines up with the frameworks clients work to. It is a practical guide, not security certification advice; where a client has its own standards, those come first.
Why the questions are coming now
Three things have changed for the clients integrators serve:
- NHS organisations complete the Data Security and Protection Toolkit (DSPT), which has been aligned to the National Cyber Security Centre's Cyber Assessment Framework (CAF) since September 2024 (DSPT). Commentators read its scope as covering operational technology as well as IT, which brings building systems into view, even though the toolkit text found does not name them.
- Central government and NHS buyers can require Cyber Essentials or Cyber Essentials Plus from suppliers under Procurement Policy Note 014 (GOV.UK PPN 014). Tier 1 FM providers often pass the same requirement down to their subcontractors.
- Data centres were designated critical national infrastructure in September 2024 (GOV.UK). The Cyber Security and Resilience Bill, introduced in November 2025, would bring larger colocation and enterprise data centres under NIS duties, including incident reporting and supply-chain risk management (Gowling WLG). Check the Bill's current status before relying on it.
In 2025 the NCSC and partner agencies published joint guidance on operational technology, including an asset inventory guide (joint asset inventory guidance) and principles for keeping a definitive view of an OT architecture. Together they give a ready-made structure for BMS evidence.
The asset inventory
Everything else depends on knowing what is there. For a BMS, an inventory worth handing over lists, for every networked device:
- what it is - supervisor, controller, router, gateway, meter interface, third-party integration;
- where it is - building, plant room, panel;
- its network identity - IP address and subnet, or MS/TP network and address;
- firmware and software versions, and whether they are still supported;
- the protocols and ports it uses;
- who owns it, and who maintains it.
Keeping it current is the hard part. Tie updates to the service visit: when a controller is replaced or firmware is updated, the inventory changes the same day. An inventory that was accurate at handover five years ago is evidence of nothing.
The architecture view
An inventory says what is there; an architecture view shows how it connects. A clear drawing - not a vendor schematic - should show:
- how the BMS network is separated from the corporate network, and where the boundary sits;
- every route in and out - remote access, links to other systems, cloud services, metering bureaux;
- where field buses (MS/TP, Modbus, M-Bus) join the IP network;
- which connections are permanent and which are on demand.
The joint guidance stresses that the view must be definitive - one maintained version that everyone works from. In practice that means the integrator and the client's IT team agree it together, and both keep it up to date.
Remote access
Remote access is the area most likely to draw an audit finding, and the area where integrators have the most influence. Good evidence shows:
- one agreed method, approved by the client's IT team, rather than a mix of tools added over the years;
- named individual accounts for each engineer, never shared logins;
- multi-factor authentication where the method supports it;
- on-demand access that the client enables, or that is logged and time-limited;
- a log of who connected, when and why, available to the client;
- a leavers process - when an engineer leaves, their access goes the same day.
For school clients, remote access also reduces site visits and with them the safeguarding overhead - but the same approval applies.
Internet exposure
A BMS supervisor or controller reachable directly from the internet is one of the most common and most avoidable problems. The 2025 guidance on preventing unintentional OT exposure is clear that devices should not be published to the internet by accident. Evidence that nothing is exposed might include:
- a check of the site's public addresses for BMS services, done with the client's agreement;
- confirmation that any port forwarding left from commissioning has been removed;
- a list of every outbound connection the BMS makes, and why.
Accounts, backups and changes
The rest of the pack is ordinary good practice, written down:
- Accounts. No default passwords; a list of local accounts on supervisors and controllers, reviewed at each visit.
- Backups. Tested backups of every supervisor and controller program, held where the client can reach them, with dates.
- Change records. What was changed, by whom, when and why - which also helps with energy evidence and with the client's own change control.
- Patching. Firmware and software updates assessed at each visit, applied under the client's change process, and recorded in the inventory.
Mapping the pack to what clients work to
- NHS - DSPT and the CAF. The inventory, architecture view and remote access evidence support the CAF themes on asset management, secure configuration, identity and access, and supply chain. Give the trust's DSPT lead the pack, and ask which assertions they want it mapped to.
- Public sector - Cyber Essentials. Cyber Essentials covers firewalls, secure configuration, user access, malware protection and patching. It is a floor, not an OT security standard, and the scheme does not claim to stop targeted attacks - so pair the certificate with the BMS-specific evidence above.
- Data centres - CNI and NIS. Expect the client's change advisory board to ask for the same evidence before any remote access or firmware change, and to fold BMS suppliers into supply-chain reviews. Data hall cooling inside the envelope covers working under a method of procedure.
Making it part of service
None of this needs a separate security project. Build it into the service contract: the inventory and architecture view refreshed at each visit, the remote access log reviewed quarterly, backups tested, and a short annual statement to the client's security lead. Clients notice, and it is one of the clearest ways to show that a service contract delivers more than a walk-round.
For the service pattern, see The BMS service visit that pays for itself and Selling BMS service. For hospital governance more widely, see Which HTM governs which BMS point, and for the network basics, BACnet, Modbus, M-Bus and KNX explained.
Related tools and training: the MS/TP and IP planner and naming convention builder in tecTools help keep addresses and names documented, and the MS/TP and BACnet basics course is in tecTraining.
Guidance mentioned: NHS Data Security and Protection Toolkit (CAF-aligned since September 2024); NCSC Cyber Assessment Framework; PPN 014, Cyber Essentials (2025); joint NCSC and partner guidance on OT asset inventory, architecture and exposure (2025); data centre CNI designation (2024); Cyber Security and Resilience Bill (introduced November 2025 - check its status). This article is general guidance, not security certification advice.