Understanding the output of Environment Setup task

With UNIX content, endpoint scans are accomplished using a series of shell or Powershell scripts, that provide greater accessibility to system administrators.

In most BigFix content, Fixlets continuously evaluate conditions on each endpoint. The console shows the results when the relevance clause of the Fixlet evaluates to true or false. However, for UNIX content, an Environment Setup Task triggers a scan of the endpoints. This task can be executed on-demand whenever a scan is needed or scheduled as a recurring policy from the console.

The endpoint scan is performed using a series of Shell/Powershell scripts available within individual checks or Fixlets. These scripts write collected data to individual Result files, which are then accessed by the corresponding Fixlet checks for evaluation. Once the results files are written to disk, the Fixlets read each results file and show the results in the console.

After running the Environment Setup Task from the Security Checklist, the scripts execute and generate multiple files for each check, including a script file, a log file, and a result file:
Table 1. File paths for Logs and results
File Name Path in MacOS Path in AIX and Solaris Content
Environment_Setup_Task.log /Library/Application Support/BigFix/BES Agent/SCM/<ProjectID>/<CIS/DISA>/ /var/opt/BESClient/SCM/<ProjectID>/<CIS/DISA>/ Execution details of Task and individual checks.
<sourceID.log> /Library/Application Support/BigFix/BES Agent/SCM/SCM/<ProjectID>/<CIS/DISA>/Logs /var/opt/BESClient/SCM/<ProjectID>/<CIS/DISA>/Logs Logs for execution of particular fixlet/Check
<sourceID.Result> /Library/Application Support/BigFix/BES Agent/SCM/SCM/<ProjectID>/<CIS/DISA>/Results /var/opt/BESClient/SCM/<ProjectID>/<CIS/DISA>/Results Compliance status of particular fixlet/Check
<sourceID.sh> /Library/Application Support/BigFix/BES /var/opt/BESClient/SCM/<ProjectID>/<CIS/D Individual scripts for all the checks in the site
Agent/SCM/SCM/<ProjectID>/<CIS/DISA>/Scripts ISA>/Scripts
Note: If an individual Fixlet contains a parameter, then it will be added in a file named Parameter.txt, which is then stored in the custom site folder.