Do not manually delete any Tanium content that includes Comply in the name for any reason. Deleting Tanium content can cause Comply to stop working correctly.
Due to an expired CIS certificate, all CIS-CAT engines supported by Comply 1.3.2 or earlier will fail signature validation, which causes the engine not to run.
To resolve this issue, upgrade to Comply 1.3.3 or later. The tools in Comply 1.3.3 and later provide a work-around for this issue. After deploying these tools, all versions of CIS-CAT will work correctly. Comply 1.3.3 and later also adds support for CIS-CAT 3.0.43, which contains code signed with a valid certificate.
If you are unable to upgrade Comply, contact your TAM.
Check for the following error messages if a deployment does not run as expected:
Some machines included in this deployment cannot be deployed to.
Ensure that targeted endpoints have enough disk space to accommodate deployments.
Some machines included in this deployment don't have the system utilities required to complete a scan.
Linux or macOS endpoints do not have the UNIX utilities installed that are required for Comply to work correctly.
You might need to collect a support bundle that includes logs associated with Comply for troubleshooting purposes when working with technical support or your TAM.
You must have the Comply Administrator role to collect the support bundle. For more information about Comply roles, see User role requirements.
- On the Comply Home page, click Help .
- On the Troubleshooting tab, in the Support Request section, click Create Package to download a support bundle of files to provide to your TAM or technical support.
You might need to locate log files on your endpoint
Endpoint log files
Comply log files are created on endpoints at the following path: <Tanium Client>\Tools\Comply\logs
Log files for each scan are keyed by report hash. Only the most recent file is kept.
Tanium Module Server log files
Comply log files are created on the Tanium Module Server at the following path: <Module Server>\services\comply-service\logs
Service log files are found here.
If a JRE encryption key is lost or overwritten, you can recreate the JRE encryption key.
- On the Comply Home page, click Settings .
- On the JRE Encryption Key tab, click Generate Random Key to generate a new JRE encryption key.
- Enter your credentials and click OK.
You can provide your own encryption key; however, as a best practice you should generate a random key.
If you have existing reports on endpoints with an encrypted JRE, those reports must be redeployed. In addition, all existing encrypted deployments must be redeployed so they are updated with the new key.
The following table lists contributing factors into why the Comply endpoints with critical or high vulnerabilities metric might be lower than expected, and corrective actions you can make.
|Contributing factor||Corrective action|
|Endpoints are missing from vulnerability reports||Ensure that those endpoints exist in correctly targeted computer groups and that those computer groups are explicitly targeted for vulnerability reports. Make sure that vulnerability reports run on a periodic schedule.|
|Vulnerability reports do not include endpoints that were offline at the time of the initial report schedule||Change your vulnerability report scheduling to use Using report age, and instead of running a weekly report, set the report result maximum age to 7 days. For more information, see Create a vulnerability report.
With this configuration, Comply continuously checks for and attempts to assess endpoints as they come online, as long as they do not already have findings that are newer than 7 days. This setting allows global organizations and "follow the sun" models to continuously scan managed endpoints as they come online around the world, regardless of timezone or the original scan execution time.
|OVAL checks do not align with locally developed guides or industry frameworks||
Use custom ID mapping and custom scoring to align CVEs to the frameworks on which you report.
For more information, see Customizing vulnerability results.
If you need to uninstall Comply, first clean up the Comply artifacts on endpoints and then uninstall Comply from the server.
Remove Comply content and tools from endpoints
- From the Main menu, click Interact.
- Ask a question to target the endpoints from which you want to remove Comply content and tools. For example, Get Comply - Tools Version from all machines returns all endpoints with the Comply tools installed.
- Select the endpoints from which you want to remove Comply content and tools.
- Click Deploy Action.
- On the Deploy Action page, enter Comply - Remove in the Enter package name here field.
- Select either the Comply - Remove Client Files - Windows or Comply - Remove Client Files - Unix action, as appropriate. For more information, see Tanium Platform User Guide: Managing Scheduled Actions.
- Check Remove ALL Comply files if you want to remove all Comply content and tools or select only the content and tools you want to remove.
- Click Show preview to continue.
- A results grid displays at the bottom of the page showing you the targeted endpoints for your action. If you are satisfied with the results, click Deploy Action.
Remove the Comply solution from the Tanium Module Server
- From the Main menu, click Tanium Solutions.
- In the Comply section, click Uninstall.
- Review the content that will be removed and click Uninstall.
- Depending on your configuration, enter your password or click Yes to start the uninstall process.
- Return to the Tanium Solutions page and verify that the Import button is available for Comply.
Last updated: 6/30/2020 4:15 PM | Feedback