This page documents specific steps on specific Operating Systems to enable FIPS support which is available from Opsview Monitor 6.5.4.
# RHEL 8 Java
While the rest of the Opsview system will happily work on a FIPS enabled server running RedHat Enterprise Linux 8 (RHEL 8), the Opsview Reporting Module requires a Java Runtime configured to not run in FIPS mode due to the incompatibility with FIPS standards that the keystore algorithm (JCEKS) Jasperserver uses.
There are two workarounds to this issue:
Install a new JRE just for Opsview to run in a non-FIPS compliant mode. This will allow any other Java applications on the system to continue running in FIPS mode while allowing the Reporting Module to run.
Configure the currently installed JRE on the Orchestrator machine to run in a non-FIPS compliant mode. This will have the side effect of allowing non-FIPS compliant Java applications on the system.
Note that if there is no Java runtime located on the orchestrator machine, one of the workarounds must be performed so that the Reporting Module has a valid Java installation to use.
## To install an Opsview specific Java (Recommended)
Note: these instructions will need to be modified if a later version of the JRE is released
Get the URL of the latest 1.8 OpenJDK release from [Red Hat](🔗).
Download the OpenJDK tarball from the above site and transfer it to the Orchestrator host
Create the Opsview Java directory
Extract the OpenJDK tarball in the newly created Java directory
Set security.useSystemPropertiesFile to false in the new Java installation’s java.security file
Run the check-deploy playbook to ensure that Java is now correctly configured. Note that from 6.6.5 onwards this playbook will additionally set up python on all systems used.
Please note that this Java install is currently not managed by Opsview in any way. This means that any security updates will have to be manually installed by rerunning the manual steps listed above.
## To configure the System Java to run in in a FIPS non-compliant mode
Run the check-deploy playbook in Opsview Deploy. This will detect the Java runtime that Jasper server will choose to use and raise an alarm if it is not configured as needed. (Note that from 6.6.5 onwards this playbook will additionally set up python on all systems used).
Edit the configuration file in the specified Java directory. The following sed command creates a backup named java.security.bk.
Rerun the check_deploy playbook as per step 1 to ensure that Java is now correctly configured.
# RHEL 8 Opsview-Agent (NRPE) ciphers
Opsview Agent Deprecation
The Opsview Agent and the steps below are now deprecated, and we instead recommend use of the [ITRS Infrastructure Agent](🔗) which works by default in a RHEL8 FIPS environment.
The default anonymous ciphers configured on the Orchestrator and used to communicate with `
opsview-agent` on monitored devices need to be replaced with higher security ones in order for `
check_nrpe` based checks to work in a RHEL8 FIPS environment. The easiest way to accomplish this is to replace the ciphers listed in the `
NRPE_CIPHERS` global variable (Menu => Configuration => Advanced => Variables) with `
AECDH-AES256-SHA:AECDH-AES128-SHA` and run an `
Customers need to ensure that the `
opsview-agent` on the monitored hosts allows this new cipher configuration (see [Opsview Agent Security](🔗) for more details) - they will work with all recent versions of the `
opsview-agent` (v6.0.0 and newer) using the default configuration. This change is not necessary if customers already use authenticated ciphers exclusively.
The need for this change is brought about by the tighter security standards enforced by RHEL8 FIPS ( see [Strong crypto defaults in RHEL 8 and deprecation of weak crypto algorithms - Red Hat Customer Portal](🔗) ). These new ciphers make use of Elliptic-Curve Cryptography (ECC) which provides enhanced security as well as improved performance.