Home
Configuration Guide
Learn how to configure BigFix according to your needs.
Security Configuration Scenarios
Starting from Version 11, BigFix provides the capability to configure several security options.
On Windows Systems
You can enforce the SHA-384 for all digital signatures by performing the following steps:

Configuration Guide
Learn how to configure BigFix according to your needs.
- Introduction
  This guide explains additional configuration steps that you can run in your environment after installation.
- BigFix Site Administrator and Console Operators
  In BigFix there are two basic classes of users.
- Integrating with LDAP or Microsoft Entra ID
  You can add Identity Providers associations to BigFix.
- Enabling SAML V2.0 authentication for identity provider operators
  BigFix supports SAML V2.0 authentication via LDAP-backed SAML identity providers.
- Disabling local operators
  Starting from BigFix Version 10.0.8, this feature provides a mechanism where the creation and use of any local operator is prohibited in favor of LDAP-based operators.
- Using multiple servers (DSA)
  Some important elements of multiple server installations.
- Server object IDs
  The BigFix server generates unique ids for the objects that it creates: Fixlets, tasks, baselines, properties, analysis, actions, roles, custom sites, computer groups, management rights, subscriptions.
- Customizing HTTPS for Gathering
- Using the DHE/ECDHE key exchange method
  By default, BigFixVersion 11 components use the DHE/ECDHE key exchange method if the version of the BigFix component on the other side of the SSL communication allows it.
- Configuring secure communication
- Real Time AV Exclusions
  BigFix Console, Server and Relay components of the architecture perform high volume file operations. This activity is a substantial part of the functionality that these BigFix architecture components provide.
- Downloading files in air-gapped environments
  In air-gapped environments, to download and transfer files to the main BigFix server, use the Airgap utility and the BES Download Cacher utility.
- Getting client information by using BigFix Query
  The BigFix Query feature allows you to retrieve information and run relevance queries on client workstations from the WebUI BigFix Query Application or by using REST APIs.
- The Plugin Portal
  The Plugin Portal is a new component introduced in BigFix 10 to help manage cloud devices as well as modern devices such as Windows 10 and MacOS endpoints enrolled to BigFix. For details on modern client management, see Modern Client Management.
- Extending BigFix management capabilities
  BigFix 11 delivers a few significant new functions for enhancing the visibility and management of devices on your network regardless of whether the devices are physical or virtual.
- Persistent connections
  The capability to establish persistent connections was added to the product.
- Relays in DMZ
  The capability to establish a persistent TCP connection between the parent relay in the more secure zone and its child relay inside the DMZ network was added to the product. This allows you to manage systems in a demilitarized zone (DMZ network).
- Working with PeerNest
  The BigFix Client includes a new feature named PeerNest, that allows to share binary files among Clients located in the same subnet. The feature is available starting from BigFix Version 9.5 Patch 11.
- Archiving Client files on the BigFix Server
  You can collect multiple files from BigFix clients into an archive and move them through the relay system to the server.
- BigFix Configuration Settings
  A number of advanced BigFix configuration settings are available that can give you substantial control over the behavior of the BigFix suite. These options allow you to customize the behavior of the BigFix server, relays, and clients in your network.
- Additional configuration steps
  These topics explain additional configuration steps that you can run in your environment.
- Migrating the BigFix Server (Windows/MS-SQL)
  This section details the steps and operational procedures necessary for migrating the BigFix Server from existing hardware onto new computer systems.
- Migrating the BigFix Server (Linux)
  This section provides basic information on migrating your BigFix Server from existing Linux hardware onto new systems.
- Server audit logs
  The BigFix Server generates a server audit log file which contains the access information (login/logout) and information about the actions performed through the Console or the WebUI by the different users.
- List of advanced options
  The following lists show the advanced options.
- Security Configuration Scenarios
  Starting from Version 11, BigFix provides the capability to configure several security options.
  - On Windows Systems
    You can enforce the SHA-384 for all digital signatures by performing the following steps:
  - On Linux Systems
    You can enforce SHA-384 after you install BigFix V11 or upgrade it to V11, by running the following command as super user:
- Client certificate
  To comply with the modern industry standards, starting from product version 10.0.7, the client certificate of the BigFix Agent will have a validity period of 13 months.
- Client Authentication
  Client Authentication (introduced in version 9) extends the security model used by BigFix to encompass trusted client reports and private messages.
- Maintenance and Troubleshooting
  If you are subscribed to the Patches for Windows site, you can ensure that you have the latest upgrades and patches to your SQL server database servers.

On Windows Systems

You can enforce the SHA-384 for all digital signatures by performing the following steps:

Run the Administration Tool by clicking Start > All Programs > BigFix > BigFix Administration Tool.
Browse to the location of your site license (license.pvk) and click OK.
Select the Security tab. The following window is displayed:

You can now enforce the SHA-384 for all digital signatures.
If the SHA-384 option is greyed out, a warning at the bottom of the page will inform you about the issues.

When clicking the link in the warning, a pop up will be displayed with a list of conditions that must be satisfied in order to be able to enforce SHA-384.

If the Gather an updated license from HCL is not satisfied, click Gather license now so that your updated license is gathered from the HCL site and is distributed to the BigFix clients. This step ensures that you use the updated license authorizations if you specified an existing license file during the installation steps.
If the Run BESAdmin on the following replication servers is not satisfied, it means that one of these conditions regarding all the BigFix servers involved in a Disaster Server Architecture (DSA) is not satisfied:
- They are at Version 11.
- They have the updated license.
If the Unsubscribe from sites which do not support SHA-384 is not satisfied, click the link to see the list of sites which do not support SHA-384. To solve the issue you need to unsubscribe these sites from the BigFix Console.

In this example, 2 sites must be unsubscribed.

If the Rotate WebUI certificates to enable SHA-384 is not satisifed, you need to regenerate all WebUI certificates created before upgrading to Version 11.

SHA-256 Downloads

To ensure that data has not changed after you download it using the SHA-256 algorithm click Require . If you do not select this option, the integrity check of the downloaded files is run using the SHA-1 algorithm.