The Building That Runs the Cloud
Contain the Controller, Keep the Hall Cool
A secure controller that no longer runs the cooling is a failure.
This chapter shows how Findavi handles the 1:42 a.m. moment, step by step.
The night, replayed
ILLUSTRATIVE
At 1:42 a.m., Findavi sees the cooling controller reach for an address it has never contacted. It compares that with the controller's normal pattern. Building management system, yes. System for recording readings, yes. Approved vendor service, only during its window. This new address matches none of them.
Findavi checks the site's rules for this device. Facilities and security agreed on them weeks ago. For this controller, the rule says: restrict, don't disconnect, and ask a person first.
It recommends one narrow action. Keep the controller connected to its building management system, its monitoring tools and its management console. Block everything else.
The on-call engineer gets the request on her phone at 1:44. She reads the evidence and approves at 1:46.
Findavi pushes the change.
Then it runs the security check. Can the controller still reach the unknown address? No. The path is closed.
Then it runs the service check. Is the controller still sending temperature readings? Yes. Are the alarms still live? Yes. Is it still talking to the building management system? Yes.
At 2:00, the hall is right where it should be.
Findavi records all of it. What it saw, what it recommended, who approved, what changed, both checks, and anything left to investigate in the morning.
Contain the controller. Keep the data center.
What Findavi can actually do
The available actions depend on the equipment and the approved connections at your site.
For supported devices, Findavi can block a device, isolate a network port, or change a setting. We confirm the supported models, software versions and connections at your site before enabling an action. Each action must follow your rules and pass both a security check and a service check.
Those changes cover the connections and devices around your building controls, like passwords and network access. Findavi doesn’t change how the cooling plant runs. Control and safety decisions stay with your facilities team.
You can stop, undo or switch off any agent at any time. Every action is recorded so you can audit it.
Three modes, your choice.
Every site, and every device type, gets the mode its owners are comfortable with.
Observe. Findavi watches, learns and reports. It changes nothing. Most sites start here.
Approve. Findavi recommends a specific action with its evidence. A named person says yes or no.
Autonomous. For narrow situations you’ve approved ahead of time, Findavi acts on its own, then runs both checks and reports.
A camera in the parking lot might run in Autonomous. A cooling controller might stay in Approve for a long time. Both are good answers. You decide.
From our own work
OBSERVED
In a controlled demonstration for a logistics customer, Findavi detected and stopped an attack on a heating and cooling system.
In a pilot at a live water site, our team ran a simulated attack on the plant's controller screens. Findavi blocked the attacking connection and isolated a port. Both the security check and the service check passed. The controls kept running for the operator.8
OBSERVED IN AN AUTHORIZED TEST, POWER GENERATION
During an authorized test at a power-generation facility, NetOps IQ recorded a blocked attacking connection and an available camera feed. The cameras kept recording throughout the test. The result applies to the equipment and scope tested.
Those tests were in logistics, water and power generation, not an AI data center. They show the method: close the attack path, then check that the service still works. They do not establish support for a liquid-cooling pump, leak sensor or controller. We must confirm support for the equipment at your site.