The Fix That Breaks the Street
Shut down the problem. Keep the corner running.
ILLUSTRATIVE · A COMPOSITE SCENE, NOT A REAL EVENT
School just let out. A mom in a gray minivan waits at Main and 5th. Behind her, a fire truck is trying to get through.
The light goes red. Then all four directions start flashing.
Nobody hacked anything to make it happen. Somebody fixed something.
Ten minutes earlier, the city's security team found a controller at that corner talking to the open internet. They did the right thing. They cut it off.
They cut off a little too much. The controller lost its link to the traffic center and fell back to flashing red, in every direction, at the busiest hour of the day.
The security ticket says: Resolved.
The street says otherwise.
So two people stand in the same room and ask two different questions.
The security lead asks: "Is the door closed?"
The traffic engineer asks: "Is the street still working?"
Most tools only answer the first one.
OBSERVED · CUSTOMER DETAILS REMOVED
This book has no traffic agency result to share yet. The closest proof we can publish comes from another place where a controller runs something people depend on: a water plant.
During a pilot at a live water site, the team ran a simulated attack on the screens operators use to control the plant. Findavi blocked the attacking connection and isolated a port. Then it ran two checks. The way in was closed. And the controls kept running for the operator.
The attacker lost. The plant never stopped.
Seven steps, every time
1. Spot. See behavior that doesn't fit the device.
2. Check the rules. Is this action allowed for this device, at this time?
3. Ask. If a person must approve, send one clear recommendation and wait.
4. Act. Block the device, isolate a port, push a configuration change, or push a block rule to your firewall, for supported devices only. Findavi never writes new signal timing.
5. Check security. Test the path again. Is it closed?
6. Check service. Is the device still doing its job?
7. Record. Keep the finding, the approval, the action and both results in one place.
You decide how much Findavi does on its own
| Observe | Approve | Autonomous |
|---|---|---|
| Findavi finds problems and recommends fixes. It changes nothing. | Findavi proposes the fix. A person says yes before it runs. | Findavi acts on its own, within limits your team set in advance. |
You choose the mode for each device and each action. For signal controllers, we recommend starting in Observe or Approve. Your team can stop or switch off any Findavi agent at any time, and every action is recorded.
Core idea: Close the path. Keep the street moving.
Ask your team: If one controller acted strangely tonight, could we cut off just that controller? Or would we have to take down the whole corridor to be safe?