Best practices for securing Site Recovery Manager Server can protect your environment from possible security problems.

The secure operation of Site Recovery Manager depends on the proper configuration and maintenance of the Site Recovery Manager Server operating system.

  • Run Site Recovery Manager only on a supported host operating system, database, and hardware. If Site Recovery Manager is not running on a supported host operating system, Site Recovery Manager might not run properly.

  • Apply the latest operating system updates and patches to protect the host operating system from malicious attacks. Apply the latest Site Recovery Manager updates and patches to address any known issues with Site Recovery Manager.

  • Ensure the integrity of your Site Recovery Manager deployment when you run Site Recovery Manager as a VM. See the Virtual Machine Security Best Practices topic in the vSphere Security documentation.

  • Limit installation of software and disable services that Site Recovery Manager does not use, to free resources and to decrease the possibilities for server attacks. Unneeded software and services consume CPU, storage, memory, and bandwidth resources and increase the chance of server attacks.

  • Allow only administrators to access the server. To limit the number of accounts that an attacker can use, limit the number of accounts that can access the server.

  • Check the network ports that Site Recovery Manager uses and configure a firewall to protect your server.

  • Separate the Site Recovery Manager management network traffic from workload traffic to protect management servers from attacks.