The Intersection Still Has to Work
Blocking the attacker is only half the job.
Too many security teams call it a win the moment the bad connection is blocked. On a city street, that's halftime.
A controller can be safe and cut off from the traffic center. A camera can be locked down and no longer feed detection. An emergency receiver can be protected and no longer turn the light green for the fire truck. A radio link can be secured and the next three intersections can go dark.
Each of those failures is quiet. Nobody notices until someone needs the thing that broke.
So Findavi runs two checks after every action.
| Device | Security check | Service check |
|---|---|---|
| Signal controller | The unapproved path is closed. The old login fails. | The controller still reports to the traffic center and runs its approved timing plan. |
| Detection camera | The risky connection is blocked. | Video and vehicle detection still reach the controller and the traffic center. |
| Emergency vehicle priority | The unexpected connection is closed. | A technician confirms a test call still turns the light green. |
| Device | Security check | Service check |
|---|---|---|
| Radio link or cellular modem | Unknown devices are off the link. | The link to the next intersection and the traffic center stays up. |
| Cabinet network switch | The risky port is isolated. | Every approved device in the cabinet still talks to what it needs. |
Notice who does what. Findavi checks what it can see on the network: the path is closed, the controller reports in, the video arrives. Some checks need a person on the street. Only someone standing at the corner can confirm the fire truck got its green. Findavi records those checks too, and keeps the issue open until they're done.
If either check fails, the issue stays open. Somebody gets told. If Findavi made the move on its own, it undoes it on its own. Putting a controller's settings back always waits for a person. Nobody gets a green checkmark for a dark intersection.
Two checks. One human.
And if the service check fails?
Findavi shows your engineer what changed and what the last approved settings looked like. One person reviews it at the traffic center console. One person approves it. Then Findavi puts the settings back.
One honest limit. Findavi restores settings. It doesn't reinstall firmware. If the controller's own software has been tampered with, a restore won't clean it. That job belongs to your technicians and the equipment maker.
A human presses undo. Findavi makes undo possible.
You set the rules. Always.
Core idea: If the path is closed but the intersection isn't proven, the job isn't done.
Ask your team: After our last change to a controller or signal network, what proved nothing quietly broke?