BigFix
Purpose
Imports endpoint and patch-compliance data from HCL BigFix.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into SubImage's managed vault. See Secrets for details.
important
BigFix often sits behind a corporate firewall. If you run a SubImage Outpost inside your network, set tailscale_hostname to reach the internal endpoint. Otherwise expose the API over the internet.
Required Fields
| Field | Secret? | Description |
|---|---|---|
bigfix_username |
No | BigFix API username |
bigfix_password |
Yes | Password for the BigFix API user |
bigfix_root_url |
No | Base URL of the BigFix REST API, e.g. https://bigfix.example.com |
tailscale_hostname |
No | (Optional) Internal hostname resolved via Outpost |
Setup Steps
- Ensure the API account has at least Reader rights for the devices and sites you want to ingest.
- In SubImage, fill in
bigfix_username,bigfix_password(or its AWS Secret ARN),bigfix_root_url, and — if using Outpost —tailscale_hostname. - Save the module.
The integration authenticates with HTTP Basic over HTTPS.