Processing at the Edge or in the Cloud
Where the analysis runs determines what leaves the building, which is a privacy decision before it is an architectural one.
Analysis
Running it
Where the analysis runs determines what leaves the building. Plus the alert arithmetic that decides whether anyone reads the output, and the systems nobody remembered to turn off.
9 notes
Retention and Deletion
Storage limitation is the obligation most often written and least often enforced. What to keep, for how long, and how to prove it is gone.
Procedure
Who Can Look
A video system is a capability to observe people, and the controls on who may exercise it are the ones that get tested by an incident.
Procedure
Alert Fatigue
Every warning system degrades with volume. The arithmetic that predicts it, and the design choices that prevent a system from becoming background noise.
Analysis
Using It in an Investigation
The moment the system earns its keep, and the moment it is most likely to be misread or misused. Preserving, scoping and interpreting.
Procedure
Turning It Off
Systems are commissioned carefully and abandoned casually. What has to happen when a deployment ends, and what happens when it does not.
Procedure
Knowing What You Have
Most organisations cannot say how many analytics deployments they run or what each does. The register that makes every other control possible.
Procedure
How These Deployments Fail
The recurring failures, each visible early and each with a specific correction.
Analysis
The Report Worth Producing
One page that says whether the system works, whether it is being acted on, and whether the governance is real.
Reference