System Requirements

Set up your deployment according to the system requirements to successfully deploy BigFix Compliance Analytics.

Configure your BigFix Compliance Analytics deployment according to the following requirements:

Table 1. Supported components and system requirements to deploy BigFix Compliance Analytics

Components Requirements
Supported browser versions
  • Internet Explorer v11.0
  • Firefox v31 and later
  • Firefox Extended Support Release (ESR) 24 and 31
  • Google Chrome v35.0 and later
  • Safari v13.1.1
Supported HCL BigFix component versions
  • Platform, console, client versions: 9.5, 10.0, 11.0
BigFix Compliance Analytics server operating system requirements
  • Microsoft Windows Server 2012
  • Microsoft Windows 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2022
    Note: Microsoft Windows Server 2022 is supported from version 2.0.10.
Note: BigFix Compliance Analytics supports operating systems with the 64-bit versions only.
BigFix Compliance Analytics database server requirements
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2022
  • SCA 2.0.10 and later versions utilize the SPLIT_STRING function, which is not available in SQL Server 2012/2014 versions and needs to be added manually. Refer to the BigFix Forum for more details
  • Ensure that the SQL Server has a compatibility level set to 130 or higher before performing an upgrade or the first import
    Note: Microsoft SQL Server 2022 is supported from version 2.0.10.
BigFix Compliance Analytics server You must have Administrator privileges on the target BigFix Compliance Analytics server.
BigFix Compliance Analytics database You must have dbcreator permissions on the target BigFix Compliance Analytics database server.
HCL BigFix database user permissions HCL BigFix database user permissions
SCM mastheads and Fixlet sites
  • You might have earlier BigFix Fixlets, and custom Fixlets for security compliance in your deployment. These Fixlets continue to function correctly, but only certain Fixlets display within the BigFix Compliance Analytics reports.
  • To view the current list of SCM checklist sites that are supported with BigFix Compliance Analytics, see SCM Checklists.
HCL BigFix database permissions for datasources You must have the following MSSQL and DB2 permissions to perform tasks related to datasource.
MSSQL
Note: MSSQL requires membership in the sysadmin fixed server role, or ownership of the database (dbo).
  • SELECT, EXECUTE
  • During set up or when upgrading: CREATE SCHEMA, CREATE TABLE, CREATE VIEW, CREATE FUNCTION
DB2
  • DATAACCESS
  • During set up or when upgrading: DBADM
Server API credentials for PCI DSS policy sites users Using the PCI DSS policy sites requires providing additional BigFix API user credentials for each datasource that uses PCI. Users must have master operator credentials or must meet the following minimum requirements:
  • Can use REST API
  • Have reader permission for the PCI DSS Reporting site

BigFix Compliance End of Support (EOS)

BFC Server is a BigFix Compliance application that has a versioning property. BigFix Compliance version is the official marketing version of BigFix Compliance. The BFC application version updates are independent of BigFix Compliance version. However, the EOS date of BFC is same as BigFix Compliance.

The following table lists the EOS date of BigFix Compliance (previously Security and Compliance) and the BFC Servers.

Table 2. End of Support date of BigFix Compliance (previously Security and Compliance) and BFC Server
BigFix Compliance versions BigFix Compliance Analytics/BFC versions End of Support date
8.2.x 1.4.x 2016-04-30
9.0.x 1.4.x 2016-04-30
9.1.x 1.5.x 2017-09-30
9.2.x 1.6.x, 1.7.x, 1.8.x 2020-03-31
Table 3. BFC Analytics and BES: Support Matrix
BigFix Compliance versions BigFix Compliance Analytics/BFC versions
9.5.x 1.8.x, 1.9.x, 1.10.x, 2.0.x
10.0.x 1.9.x, 1.10.x, 2.0.x
11.0.x 2.0.x