After an incident, the first proposal that lands on an executive’s desk is almost always a camera upgrade. It is easy to understand, easy to price, and easy to point to afterward as evidence that leadership acted. I have reviewed many of these proposals over my career, and I have watched organizations spend real money on them and end up with the same exposure they had before, now recorded in higher resolution. If you are weighing a camera investment right now, I want to explain why cameras do not fix bad security, so that you spend the money where it will change the outcome.
None of this is an argument against cameras. They are a legitimate part of a program, and I have specified plenty of them. The argument is that a camera is a tool inside a system, and when the system is broken, the tool records the failure without preventing it. Understanding the difference is one of the most valuable things a leader without a security background can learn.
What a Camera Actually Does
A camera does three things. It records what happened in its field of view, which is valuable for investigation after the fact. It may deter a person who notices it and who cares about being identified, which describes some offenders and not others. And, if someone is watching the feed in real time and has the means to respond, it can shorten the time between an event and a reaction. That third function is the one organizations imagine they are buying and the one they almost never actually get, because live monitoring with a real response behind it is expensive and most systems are simply recording to a hard drive that nobody reviews until something goes wrong.
A camera does not lock a door, does not check a credential, does not stop a former contractor from walking in with a badge that still works, and does not notice that an employee has been talking about a grudge for three weeks. It does not enforce a visitor policy that the receptionist was never trained on, and it does not fix a guard contract that says one thing while the officers do another. Every one of those is a security failure I have seen far more often than any failure that a better camera would have prevented.
Why Cameras Do Not Fix Bad Security
Bad security is almost always a failure of ownership, process, or discipline rather than a failure of equipment. The access list has not been reviewed in years. Nobody owns the function, so decisions are made locally and information does not travel. Policies exist on paper and are not followed because they were never trained or tested. The guard vendor is managed by an invoice rather than by a person. Cameras sit on top of all of this and change none of it. In the organizations I have assessed, the footage from the incident usually shows exactly how the process failed, in clear detail, which is useful for the insurance claim and useless for the person who was harmed.
There is also a quieter cost. A camera upgrade gives leadership a feeling of having addressed the problem, and that feeling reduces the pressure to address the actual problem. I have seen organizations postpone an access review, a threat assessment process, or a guard contract renegotiation for a year or more because the camera project was the security initiative and it was done. The equipment became a reason to stop asking questions.
The Questions to Ask Before You Sign
When a camera proposal reaches you, ask what specific incident or risk it is meant to address and how a camera would have changed the outcome. Ask who will watch the feed, when, and what they are authorized to do when they see something. Ask how long footage is retained and who has reviewed any of it in the past six months. Ask whether the doors in the camera’s view actually lock and whether the people walking through them are supposed to be there. If the answers are thin, the proposal is addressing the appearance of security rather than security itself.
Also ask who evaluated the proposal. Integrators sell cameras, and their recommendation will reflect that. An evaluation by someone whose compensation does not depend on the answer, whether an internal security leader or a fractional security director, tends to produce a shorter list and a better one.
Where the Money Should Go First
In most mid-sized organizations, the highest-return security work costs a fraction of a camera system. Reconcile the access control list against the current employee and contractor roster and remove everyone who should not be on it. Write the visitor management process down and train the people at the front desk on it. Read the guard contract and the post orders and go watch whether the officers do what the documents say. Name a person who owns security and give them the authority to hold other departments to the process. Build a threat assessment team so that concerning behavior has somewhere to go. Each of these prevents incidents rather than recording them.
Once those disciplines are in place, cameras earn their place. They should be positioned based on a real assessment of where the risk is, with a defined purpose for each one, a retention policy, and a named person responsible for review. A camera with a purpose is a tool. A camera bought to make a problem feel handled is a receipt.
Test What You Already Have
Before buying anything new, find out whether the existing system works. Pull footage from a specific time and see how long it takes and whether the image is usable. Check whether every camera on the diagram is actually recording. Walk to a door in view of a camera after hours and see whether anyone notices. This is the principle I built the P.R.O.O.F. framework around in Until Tested: Security Is Only Assumed. A great many organizations discover that half the value they thought they had bought already was never delivered, and that discovery reshapes the next purchase.
The organizations that get security right are the ones that fix the system first and then equip it. Do the unglamorous work, put someone in charge of it, and let the cameras support a program that actually functions.
Go Deeper
Evaluating vendor proposals with an independent eye is a core part of security leadership, and it is one of the reasons the role pays for itself. For the full picture of what a part-time security executive does, start with What Is a Fractional Security Director? The Complete Guide. My book Fractional Security Director expands on how to prioritize security spending in a mid-sized organization.
Commissioner William Epps is a former elected Fire Commissioner, federal law-enforcement supervisor, and firefighter since 2006, with instructor credentials in Hazardous Materials response, Active Shooter preparedness, and Stop the Bleed®. He spent seven years in federal law enforcement in physical security, executive protection, and incident command, and now serves organizations as a Fractional Security Director. He is the author of The Spirit of Saul, The Spirit of Pharaoh, and other practical books on security, leadership, and faith, built around one idea: knowledge should be practical enough to use when it matters.
Leave a Reply