Comply requirementsReview the requirements before you install and use Comply.
In addition to a license for the Comply product module, make sure that your environment meets the following requirements.
|Platform||7.2.314.2831 or later|
|Tanium Client||See Tanium Client Deployment Guide: Requirements for the supported Tanium Client versions for each operating system.|
Scan engines are used to evaluate OVAL or SCAP content and generate configuration compliance and vulnerability reports. At least one scan engine is required to use Comply.
Comply 2.3 and later includes Tanium Scan Engine (powered by JovalCM) and Amazon Coretto Java Runtime Environment (JRE). If you want to use this scan engine and JRE (or the existing JREs on endpoints), you do not need to upload any engines.
If you want to use a different scan engine or JRE, you can upload them to Comply. Tanium Scan Engine (which is included by default), CIS-CAT, and SCC scan engines are currently supported by Comply.
The supported versions of the scan engines are listed in the Import Engine window. Typically the most recent version plus the two previous versions are supported.
CIS-CAT and Tanium Scan Engine also require PowerShell and do not work if PowerShell is in the ConstrainedLanguage language mode.
For more information, see Working with scan engines and JREs.
Specific ports and processes are needed to run Comply. If security software is in use in the environment to monitor and block unknown host system processes, your security administrator must create exclusions to allow the Tanium processes to run without interference. Comply leverages third-party compliance engines to conduct compliance and vulnerability scans against supported endpoints.
|Module Server||<Module Server>\services\comply-service\node.exe|
|Windows endpoints||<Tanium Client>\Tools\Comply\TaniumExecWrapper.exe|
|Linux/macOS/AIX endpoints||<Tanium Client>/Tools/Comply/TaniumExecWrapper|
|Tanium Scan Engine||<Tanium Client>/Tools/Comply/joval/Joval4Tanium.jar|
|CIS-CAT engine||<Tanium Client>/Tools/Comply/cis-cat/CIS-CAT.jar|
|<Tanium Client>/Tools/Comply/cis-cat/CIS-CAT.sh (Linux only)|
|<Tanium Client>/Tools/Comply/cis-cat/CIS-CAT.BAT (Windows only)|
|SCC engine - Windows endpoints||<Tanium Client>\Tools\Comply\scc\cscc.exe|
|SCC engine - Linux/macOS endpoints||<Tanium Client>/Tools/Comply/scc/cscc|
For remote vulnerability reports, see Tanium Discover User Guide: Host and network security requirements for Nmap security exclusions.
For best results, add a recursive security exclusion for the Tanium Client directory:
- Windows endpoints: <Tanium Client>
This path is usually C:\Program Files (x86)\Tanium\Tanium Client.
- Linux endpoints: /opt/Tanium/TaniumClient
If a recursive exclusion is not possible, ensure that your exclusion for the TaniumExecWrapper process includes child processes. The path to this process is listed for each operating system in the preceding table. Some engines use child processes to run scans, and those child processes must be allowed for Comply to function.
Consult your Technical Account Manager (TAM) to confirm that the appropriate security exclusions are in place in your environment.
Role-based access control (RBAC) permissions control access to the Comply workbench. Comply provides these predefined roles:
Has all privileges in Comply, including collecting support bundles and managing Comply Application Settings.
Comply Deployment Administrator
Can upload engines and distribute them via deployment; can read and write report content.
Comply Report Content Administrator
Can read and write the following:
- Configuration compliance benchmarks
- Vulnerability sources
- All custom compliance and vulnerability content except custom checks
Comply Report Administrator
Can read custom report content including benchmarks, vulnerability sources, and all custom content; can read report results; only role (other than Comply Administrator) that can create and delete reports.
Comply Report Reviewer
Can read custom content, reports, and report results.
Comply Custom Check Writer
Only role (other than Comply Administrator) that can create and delete custom checks; can read custom content.
|Privilege||Comply Administrator||Comply Deployment Administrator||Comply Report Content Administrator||Comply Report Administrator||Comply Report Reviewer||Comply Custom Check Writer|
View the Comply workbench
Comply Report Read
Review report results.
Comply Report Write
Comply Report Content Read
Read benchmarks, custom checks, custom ID mappings, custom profiles, and vulnerability sources.
Comply Report Content Write
Manage benchmarks, vulnerability sources, custom ID mappings, and custom profiles.
Comply Deployment Read
Comply Deployment Write
Manage deployments and engines.
Comply Custom Check Write
Manage custom checks.
1 To install Comply, you must have the reserved role of Administrator.
2 Denotes an implicit permission that is provided by a privilege with a higher permission level. For example, a write permission provides an implicit read permission.
|Permission||Content Set for Permission||Comply Administrator||Comply Deployment Administrator||Comply Report Content Administrator||Comply Report Administrator||Comply Report Reviewer||Comply Custom Check Writer|
|Ask Dynamic Questions|
|Read Sensor||Comply Deployment|
|Read Sensor||Comply Reporting|
|Read Action||Comply Deployment|
|Read Action||Comply Reporting|
|Write Action||Comply Deployment|
|Write Action||Comply Reporting|
|Write Action For Saved Question||Comply Reporting|
|Write Package||Comply Deployment|
|Write Package||Comply Reporting|
|Read Saved Question||Comply Reporting|
|Write Saved Question||Comply Deployment|
|Write Saved Question||Comply Reporting|
Last updated: 1/15/2020 9:32 AM | Feedback