As a security best practice, you must secure the vRealize Operations console and manage Secure Shell (SSH), administrative accounts, and console access. Ensure that your system is deployed with secure transmission channels.
What to read next
Activating FIPS 140-2 vRealize Operations 8.4 and above uses cryptographic algorithms or protocols that are allowed by the United States Federal Information Processing Standards (FIPS). FIPS mode turns on the cipher suites that comply with FIPS 140-2. Security related libraries that are shipped with vRealize Operations 8.4 and above are FIPS 140-2 certified. However, the FIPS 140-2 mode is not activated by default. FIPS 140-2 mode can be activated if there is a security compliance requirement to use FIPS certified cryptographic algorithms with the FIPS mode activated. Secure the vRealize Operations Console vRealize Operations , you must log in for the first time and secure the console of each node in the cluster. Change the Root Password vRealize Operations primary or data node at any time by using the console. Managing Secure Shell, Administrative Accounts, and Console Access Set Boot Loader Authentication Monitor Minimal Necessary User Accounts Monitor Minimal Necessary Groups Resetting the vRealize Operations Manager Administrator Password vRealize Operations admin password for vApp installations. Configure NTP on vRealize Operations Deactivate the TCP Timestamp Response on Linux TLS for Data in Transit Activating TLS on Localhost Connections Application Resources That Must be Protected Apache Configuration Deactivate Configuration Modes vRealize Operations , you can modify the configuration or settings to activate troubleshooting and debugging of your installation. Managing Nonessential Software Components vRealize Operations Manager host machines. Additional Secure Configuration Activities
