Security configuration scenarios

Check what security options need to be enabled on the BigFix server and the BigFix Inventory server to achieve each of the supported security scenarios.

Hardening network security configuration: restrict incoming requests to selected HOSTS

By default, BigFix Server is configured to accept incoming traffic with any HTTP HOST header. For production use, it is recommended to limit the accepted hosts. Refer to Hardening network security configuration: restrict incoming requests to selected HOSTS for details.

TLS 1.2 and 1.3 protocol

To use the TLS 1.2 or TLS 1.3 protocol, perform the following configuration:

BigFix Inventory supports only the TLS 1.2 protocol for HTTPS inbound communications until version 10.0.12.

Starting from version 10.0.13, BigFix Inventory supports both TLS 1.2 and TLS 1.3 protocols for HTTPS inbound communications.

Since BigFix Inventory 10.0.13, it is possible to enforce TLS 1.3 protocol for inbound communication by adding the <ssl id="defaultSSLConfig" sslProtocol="TLSv1.3"/> line to the installation_directory/wlp/usr/servers/server1/customization.xml file.

You can enforce TLS 1.3 on BigFix Platform version 11. It is supported with BigFix Inventory version 10.0.9 and higher.

If FIPS is enabled, only TLS 1.2 protocol is supported. To enforce TLS 1.2 protocol, add the <ssl id="defaultSSLConfig" sslProtocol="TLSv1.2"/> line to the installation_directory/wlp/usr/servers/server1/customization.xml file.

FIPS 140-2

To achieve compliance with the FIPS 140-2 standard, perform the following configuration:For more information about the standard, see: Federal Information Processing Standard 140-2.

SP800-131

To achieve compliance with the SP800-131 standard, perform the following configuration: For more information about the standard, see: SP800-131 compliance.