Before you can configure integrity monitoring on your cameras, you must enable the Camera Integrity Monitor module and configure the Camera Integrity Monitor role.
Before you begin
- Your Security Center license must support camera integrity monitoring (Number of integrity-monitored cameras > 0). Both native and federated cameras are supported.
- For large systems, prepare additional servers to host the Camera Integrity Monitor role.
What you should know
- From the Config Tool home page, open the Video task.
- Click the Modules view.
- Set the Camera Integrity Monitor to ON.
From the Servers list, select the server to host the Camera
Integrity Monitor role.
Best Practice: We recommend that you host the Camera Integrity Monitor role on a different server than the Archiver role to avoid affecting the performance of the latter.
If required, assign additional servers to the role.
You can ignore the Force execution on highest priority server option. The workload is always distributed among all assigned servers.Best Practice: Because load distribution is not load balancing, always assign servers with equivalent capacities to avoid overloading one of them.Following the "recommended" server configuration described in our Security Center System Requirements Guide, a dedicated server for the Camera Integrity Monitor role can handle the load of 16 Archiver roles managing 300 cameras each, analyzing each camera once every day.
- From the Event storage list, select the Archiver role used to store the camera tampering events.
In the Persistence path field, enter the path to the folder
where the camera integrity analysis data (CIM files) are saved.
If multiple servers are assigned to the Camera Integrity Monitor role, you must use a network path that all servers have write access to.
From the Streaming source list, select the video stream that the role should use for its analysis.
Best Practice: We recommend using the default stream selection which is Low resolution because the optimal image size for camera integrity analysis is 320 pixels wide. Higher-resolution streams are downscaled for analysis and therefore waste bandwidth, unless an existing higher-resolution multicast stream is used for analysis.
Set the Maximum number of simultaneous camera analysis.
This setting (default = 10) is used to prevent load spikes at every scheduled analysis. For example, if you have 300 cameras to analyze, setting the maximum at 10 forces the role to analyze the cameras in small batches of 10 at a time.
In the Check all cameras every field, enter the check
The default check frequency is every hour. The Camera Integrity Monitor role builds a mathematical representation of the image (a CIM file) every time a camera is checked. Each new data model is compared to the previous one, and if the difference between them exceeds a certain threshold, the Camera tampered event is raised. If you get too many false positives because the scenes your cameras monitor change too rapidly, increase the frequency of the checks.
Add the cameras you want to monitor.
Do one of the following:
- In the Relationships section, click
Add () and
specify the cameras you want to monitor.
This is the better choice if all your cameras use the same settings. All cameras using the same sensitivity preset can be added with a single action here.
- Configure integrity
monitoring individually on each camera.
This is the better choice if you need different settings for each camera, and if you want to set the camera thumbnail at the same time.
- In the Relationships section, click Add () and specify the cameras you want to monitor.