How The Security Shortlist reaches a verdict
A verdict here begins with one person asking for one piece of work. A dispatcher needs a timely alert. An investigator needs a sequence from several views. A purchasing officer needs a price that will still make sense once a second site opens. We give a product the edge when its documented design answers the named request, and we explain what would change our choice.
| Criterion | Evidence the desk accepts | Question the buyer can settle |
|---|---|---|
| Detection and nuisance alerts | Defined activity, eligible reference events, matches, missed events and unmatched alerts | What happens at the actual entrance on the intended shift? |
| Camera compatibility | Model, stream, firmware and network path for each retained feed | Can the proposed system consume the stream behind this firewall? |
| Evidence and continuity | Where recordings live, how far back search works and how gaps appear | What can a supervisor produce on day nineteen? |
| Response and integration | Documented route, recipient and permissions for the plan | Who receives an alert, and who owns it an hour later? |
| Cost | Hardware, licensed units, retention, term, installation and ongoing fees | How much cash is due before staff can use the system? |
| Administration | User limits, identity management, audit history and deletion controls | Can the administrator remove access and explain what data remains? |
How we use sources
Numbered links point to primary material sitting alongside the feature, price or limitation it supports. Published limits belong to the stated configuration; a model maximum and an estimate for a particular deployment carry different weight from a contractual promise. Where a product uses quote-based pricing, the comparison names the variables a buyer should put on the request. We show arithmetic wherever a documented formula makes it possible.
The desk makes conditional recommendations from documentation, and scenarios are illustrative. We hold no common set of field results for these products. A claim that one product detects more accurately than another would need a comparable operating threshold and independently annotated events. The glossary gives our definitions and a worked example. For comparison with a formal video-activity evaluation, see NIST’s treatment of missed activity and false alarms. M01 · NIST activity evaluation plan
What breaks a tie
A missing must-have eliminates a proposal for that job. Where both designs qualify, we favor the one that lets the named employee complete the whole task on the quoted plan. The next question is what work remains with the buyer. If a recommendation depends on an existing recorder, a second license or an operator staying at a console, the reader should see that condition before deciding. Our ownership page identifies who commissioned the publication.