Home
Security
Configure different security features to adequately protect business assets and resources in the data model when using BigFix Inventory.
Configuring secure communication
To ensure secure communication, BigFix Inventory uses public key cryptography, which is based on algorithms that use two separate keys, a private key and a public key. This key pair is used to encrypt and decrypt communication.
Enabling TLS 1.2 in IBM Java
By default, IBM Java has TLS 1.0 enabled. To enable TLS 1.2, change the value of the Dcom.ibm.jsse2.overrideDefaultTLS parameter to true in the jvm.options file.

Security
Configure different security features to adequately protect business assets and resources in the data model when using BigFix Inventory.
- Flow of data
  There are several different interactions that occur between the components of the BigFix Inventory infrastructure and between the user and tool.
- 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.
- Configuring secure communication
  To ensure secure communication, BigFix Inventory uses public key cryptography, which is based on algorithms that use two separate keys, a private key and a public key. This key pair is used to encrypt and decrypt communication.
  - Step 1: Creating private keys and certificates
    To improve security, create your own private key and a certificate instead of using the self-signed ones that are available in BigFix Inventory by default. You can use openSSL to create a private key and a certificate signing request (CSR) that can be transformed into a certificate after it is signed by a certificate authority (CA).
  - Step 2: Signing certificates
    Your certificate signing request (CSR) must be signed by a certificate authority (CA) to be transformed into a certificate that can be uploaded to BigFix Inventory. You can use the openSSL cryptographic library to create a private CA and sign your request.
  - Step 3: Enabling secure communication
    You can enable encrypted communication (HTTPS) to ensure secure communication between your server and all users that access it. You can base your communication on self-signed certificates that are provided by default in BigFix Inventory, but these certificates are not intended for production environments. To improve security, create your own private key and certificate, and upload them to BigFix Inventory.
  - Enabling TLS 1.2 in IBM Java
    By default, IBM Java has TLS 1.0 enabled. To enable TLS 1.2, change the value of the Dcom.ibm.jsse2.overrideDefaultTLS parameter to true in the jvm.options file.
- Assuring compliance with federal encryption standards
  You can configure BigFix Inventory to be compliant with the Federal Information Processing Standard requirements that are related to encryption.
- Authenticating users with LDAP
  BigFix Inventory supports authentication through a Lightweight Directory Access Protocol server. To use this feature, you must configure the BigFix Inventory server.
- Configuring and enabling single sign-on
  Available from 9.2.1. You can now use the two-factor authentication and use single sign-on to log on to BigFix Inventory and maintain login consistency with other applications in the enterprise. You can configure BigFix Inventory to use two-factor authentication with single sign-on based either on the exchange of Security Assertion Markup Language (SAML 2.0) token and Microsoft™ Active Directory Federation Services as Identity Provider or you can use the IBM Lightweight Third-Party Authentication (LTPA) technology and IBM Security Access Manager for Web as the authentication service.
- Configuring passwords and encryption mechanisms
  To improve the application security, define a security policy for user passwords. You can also configure passwords and encryption mechanisms for the keystore in which the passwords are stored, and the BigFix Inventory database.
- Configuring user account lockout
  Available from 9.2.8. By default, user account is locked for 5 minutes after the user attempts to log in to BigFix Inventory more than 10 times within 5 minutes. You can change the default settings or disable the user account lockout.
- Configuring VM Manager Tool to accept trusted VM manager certificates
  By default, the VM Manager Tool accepts all VM manager certificates regardless of whether they are trusted or not. You can change the default behavior to ensure that only trusted certificates are accepted by the VM Manager Tool.
- Relays
  Relays lighten both upstream and downstream burdens on the server. Rather than communicating directly with a server, clients can instead be instructed to communicate with designated relays, considerably reducing both server load and client and server network traffic.

Enabling TLS 1.2 in IBM Java

By default, IBM Java has TLS 1.0 enabled. To enable TLS 1.2, change the value of the Dcom.ibm.jsse2.overrideDefaultTLS parameter to true in the jvm.options file.

Before you begin

Starting from application update 9.2.13, TLS 1.2 is enabled in IBM Java by default.

Procedure

Go to the computer where the BigFix Inventory server is installed.
Go to one of the following directories and open the jvm.options file.
- C:\Program Files\ibm\BFI\wlp\usr\servers\server1\
- /opt/ibm/BFI/wlp/usr/servers/server1/
Set the value of the -Dcom.ibm.jsse2.overrideDefaultTLS to true.
```
-Dcom.ibm.jsse2.overrideDefaultTLS=true
```
Restart the BigFix Inventory server.
1. Stop the server.
2. Start the server.