Assessor will not advance past a certain point when run from a container image

Problem

Solution

As an example, Ubuntu Containers are missing a number of default system commands and tools that Assessor needs to run. These elements can be installed manually after the container is running, but there's no comprehensive list which CIS has assembled. You can use the CIS-CAT Pro Assessor logs to help identify which elements may be missing and thus blocking Assessor from completing Assessments.

You can produce the logs as follows in order to work through and make manual adjustments to your container image:

1. remove or rename existing log files from the Assessor\logs directory

   1. If there isn't a folder with that name, it's no problem, it will create it once you run CIS-CAT with increased logging.

2. Add command option --info to the end of the full command [for CLI How to increase Logging via CLI] or select increased logging of WARN, ERROR, or INFO [in the GUI How to increase Logging in the GUI]

3. Rerun a fresh scan

4. open the Assessor-CLI.logfrom the \Assessor\logs directory using a notepad tool (Ex. notepad ++ which is free and works well for log files)

5. Review what Assessor is attempting to do, why it is failing, and implement necessary changes until the scan is able to complete .
   
   

Keywords; Container CIS-CAT Pro Assessor CCPA

Content by Label