HCL BigFix manages and patches the endpoints in your estate. This guide shows you how to prepare a BigFix operator account and gather the values you need to configure the integration.
Before you begin, ensure that you have:
- Access to the BigFix console as an operator who can create and configure other operators
- The address of your BigFix server's REST API
Grant these to the BigFix operator account the integration will use. A non-master operator has everything the integration needs.
| Permission | Purpose |
|---|---|
| Can use REST API | Authenticate against the BigFix REST API |
| Can Submit Query | Read devices, compliance findings, and installed applications. Every read runs as a relevance query |
| Action rights (optional) | Remediate, update, and restart devices. Without these the integration only reads |
| Reader access on a content site | Return the devices and findings on that site. A device on a site the operator cannot read is left out of results, with no error |
For more information on operator permissions, see the HCL BigFix user permissions docs page
Device hardware fields, such as manufacturer, model, serial number, CPU and RAM, and installed application data come from BigFix retrieved properties. Those properties are backed by analyses, and an analysis returns nothing until you activate it.
Activate the hardware and application information analyses on each Fixlet site whose devices you want to see. Do this for each platform you run, such as Windows and Linux. An analysis that is not activated leaves its fields empty.
To configure a new BigFix integration, provide each of the values as defined below:
| Integration Parameter | Description |
|---|---|
| Username | The username of the BigFix operator account you prepared |
| Secret | The password of that operator account |
| Base URL | The address of your BigFix server's REST API. The server root or the full API path both work Example https://bigfix.example.com:8443 or https://bigfix.example.com:8443/api |
| Integration Parameter | Description |
|---|---|
| Skip TLS Verification | Turn this on only when your BigFix server presents a self-signed or internally issued certificate. It stops certificate checking for every request to the server |