IoT and building automation
Protection for the systems that run the building, and for every network they touch.
Building automation controllers, utility meters and environmental sensors were designed to work, not to defend themselves. LayereDefense designs, builds and operates the network, server, cloud and monitoring layers that protect these Internet of Things (IoT) and operational technology (OT) systems, and has done so since 2017 at more than 150 government facilities around the world.
- Since 2017Designed, built and still operated
- 150+ locationsGovernment facilities around the world
- AuthorizedCarried through federal security authorization
- Zero TrustEvery device, user and connection is verified
What gets protected
Three kinds of system, one kind of risk.
Each of these systems reports to the people who run a facility. Each is also a path into the facility's network if it is connected without care.
-
Building automation
Controllers and supervisors
The supervisors and controllers that run heating, cooling and power keep working for decades and are rarely patched. They are placed on their own network, reached only through controlled paths and signed in to with more than a password. The Windows and Linux servers that the building software runs on are hardened and kept current.
- Windows and Linux supervisor servers, hardened and migrated
- Multi-factor sign-in for operators
- Contractor access through a controlled gateway
-
Utility metering
Meters and gateways
Metering data has to leave the building to be useful. Each site gets the same tested build of firewall, routers, switches and the servers the system needs, and the data travels to the cloud over an encrypted path with a short, written list of what may pass.
- One repeatable build for every site
- Encrypted site-to-cloud connections
- Dynamic routing between sites and cloud
-
Sensors and telematics
Devices in the field
Air quality monitors and vehicle telematics units sit where nobody watches them. They ship from a hardened image, identify themselves with certificates and send their readings to cloud services built for that one job.
- Hardened device images
- Certificates in place of shared passwords
- Dedicated cloud services for device data
How it is protected
Six layers between a device and everything else.
This is Zero Trust applied to building systems. No device, user or connection is trusted because of where it sits, and each layer assumes that the one before it has already failed.
-
Segmentation
Devices live on their own network, apart from the enterprise network and apart from each other where the system allows. The aim is that a compromised meter reaches its own gateway and nothing else.
-
Controlled paths
Every connection out of a site passes a firewall with a short, written list of what is allowed. Administration runs through a jump gateway and never directly from the internet.
-
Identity and certificates
Devices and services prove who they are with certificates from a managed certificate authority. Operators sign in with multi-factor authentication.
-
Hardened servers and cloud
The Windows and Linux servers that run the building software are configured to a security baseline and patched on a schedule. The cloud side is built in Microsoft Azure or Amazon Web Services (AWS), in a government region where the system requires one. It is built from code, so that it can be reviewed, rebuilt and shown to an assessor line by line.
-
Monitoring
Firewalls, gateways and servers send their logs to one place. Health checks and alerts flag a failed device or an unexpected connection.
-
Hunting and forensics
Logs are searched for signs of intrusion, not only kept. When something looks wrong, the evidence is collected from the devices before it is lost.
Ways to engage
From an audit of what exists to a system run for years.
-
Audit
Map what is really connected and measure the network against published federal and industry standards. The result is a ranked list of fixes.
-
Design
Draw the segments, the paths and the cloud landing for a new system, or for an existing one that has to pass a security review.
-
Build
Configure and test the firewall, routers, switches, gateways and servers for each site before they ship, and stand up the cloud side from code.
-
Operate
Monitor, patch and upgrade the system for as long as it runs, and carry it through each security authorization and assessment.
Straight answers
Questions that come up first.
Does LayereDefense replace the building automation contractor?
No. The controls contractor installs and programs the building systems. LayereDefense designs and runs the network and security around them, and works alongside the contractor and the facility's IT staff.
Can a system that is already installed be assessed?
Yes. An audit starts with a map of what is really connected, which is often not what the drawings show, and measures it against the standards that apply. It ends with a ranked list of fixes.
Is this only for government facilities?
No. The approach was built in government facilities, where the requirements are strictest. It applies wherever building systems, meters or sensors connect to a network.
Do the devices have to be replaced?
Rarely. Most of the protection sits in the network, the servers, the cloud and the monitoring around the devices, so existing controllers and meters can usually stay.
Contact
Tell us what is connected.
Describe the systems, the number of sites and what has to be reviewed or built. A short message is enough to start a conversation.
info@layeredefense.com501 E Kennedy Blvd, Suite 1400
Tampa, FL 33602