Best practices for system resilience - Security Center 5.7 - 5.12

Security Center Best Practices - Enterprise

Applies to
Security Center 5.7 - 5.12
Last updated
2023-08-15
Content type
Best practices
Language
English
Product
Security Center
Version
5.12
5.11
5.10
5.9
5.8
5.7

Resilience refers to your system's ability to withstand major disruptions and protect its critical functions. Use the following checklist to configure and maintain your system so it can better detect, respond, and recover from disruptions.

  • Follow the recommendations in the Security Center Hardening Guide .

    This guide outlines our security-related best practices, such as setting up partitions and access rights, enabling fusion stream encryption to protect your video, using third-party authentication, and refusing basic authentication for video units.

  • Set up failover and load balancing.

    High availability features such as failover and load balancing ensure that there is uninterrupted access and data protection for your system. You should set up failover for the Directory role and any other role that needs to remain available when their primary server fails.

  • Back up your databases on a regular schedule.

    If your system is wiped and your backup is stored on the impacted server, you will lose your database information. To protect your data in case of a security incident, hard drive failure, or other major disruption, regularly back up your databases to a secure location separate from your main server. For example, you can store the backup on a shared network drive.

  • Monitor the disk space available on your server drives.

    Filling up your drives can cause issues with your system's performance, making your drives unusable or even causing system failures. Regularly monitor your disk usage and free up as much space as possible.

  • Configure email notifications for when your database reaches a certain size threshold.

    Filling up your database can cause issues with your system's performance or server connectivity. You can configure different roles to send email notifications when their available disk space or database usage reaches a threshold. The size limit for the Directory database in SQL Server 2012 Express and later is 10 GB.

  • Sign up for the System Availability Monitor Agent.

    The System Availability Monitor (SAM) Agent enables you to collect health information and view the health status of your Security Center systems so that you can prevent and proactively resolve technical issues.

  • Monitor the health status and availability of entities.

    Monitoring the status of resources such as servers, roles, video units, door controllers, intrusion detection panels, and so on, can help you identify instabilities and even prevent critical system failures. You can use the Health statistics report to check the availability statistics of your system entities and monitor the health of your system.

  • Customize the default Health dashboard or create your own to monitor in real time the health of your system.

    For more information, see About dashboards.

  • Check your Genetec - Event Viewer logs for any errors.

    You can use Windows Event Viewer to review your event and application logs and troubleshoot issues on your system.

  • Synchronize time across your network components.

    Time synchronization helps you avoid issues related to missing or non-functioning features, server connections, error messages, and inaccurate timestamps. If your network does not have a domain-controller, you need to configure your network components manually for time synchronization.

  • Configure and periodically edit user privileges.

    To reduce the impact of user security breaches, grant the minimum privileges necessary for users to perform their tasks. After upgrading Security Center versions, check for new or re-organized privileges. You can use the Privilege troubleshooter tool to examine how privileges are allocated in your system, and help you to verify user permissions and fix issues.

  • Control user access to your resources using partitions.

    You can use partitions to group related assets and control which users or user groups can access each partition. The best practice is to create a special partition for low-privileged operators that only need to view video.