BOOK SIX · CHAPTER 8
The Camera Still Has to Record

The Camera Still Has to Record
Blocking the attacker is only half the job.
Too many security teams call it a win the moment the bad connection is blocked. In a government building, that's halftime.
A camera can be safe and no longer recording. A door can be locked down and no longer open for the staff. A vendor link can be gone and the heating system can stop reporting its faults. An intercom can be protected and unable to reach the security desk.
Each of those failures is silent. Nobody notices until someone needs the thing that broke.
The service still has to work.
The Findavi workflow calls for two checks after each supported action. Some service checks require the system owner on site.
Notice who does what. Findavi checks what it can see on the network: the path is closed, the video arrives, the badge events land. Some checks need a person on site. Only someone standing at the door can confirm the door opened. Findavi records those checks too, and keeps the issue open until they're done.
Core idea: If the path is closed but the service isn't proven, the job isn't done.
Ask your team: After our last security change to a camera, reader or building system, what proved nothing quietly broke?
| Device | Security check | Service check |
|---|---|---|
| Camera | Risky path is blocked. Old credentials fail, where tested. | New video reaches the approved recorder. |
| Badge reader | Unapproved connection is cut. | Events reach access control. The owner tests a valid badge at the door. |
| Gate / intercom | Unexpected connection is closed. | Calls reach the desk; the gate opens on approval. |
| Building controller | Vendor access is restricted to approved use. | Facilities checks the equipment and monitoring. |
| Alarm / sensor | Risky connection is removed. | Alerts reach the response team. |