This topic gives you an overview of Compliance Scanner for VMware Tanzu. This product provides platform operators and auditors an assessment of each Linux VM running on Xenial stemcells and, if it is compliant, with configuration guidelines.
The following VM types on an Operations Manager instance are skipped for scanning and do not have Compliance Scanner deployed on them:
Compliance Scanner for VMware Tanzu is certified by the Center for Internet Security (CIS). For more information about all the versions certified for CIS Benchmarks:
Benchmarks for existing commercial configuration scanners are intended for use against traditional Ubuntu servers. This means that running these benchmark scans against a stemcell results in numerous false positives.
Compliance Scanner addresses this issue by tuning industry-recognized Ubuntu configuration benchmarks for stemcells.
Compliance Scanner packages the following files for deployment on each BOSH-managed Linux VM:
Compliance Scanner is installed through Ops Manager. As part of the installation, it deploys each packaged component to each Linux VM and instantiates a new Linux VM,
oscap_store, for log retrieval.
Scans are errands that are triggered through Ops Manager. After a successful scan, operators can retrieve reports through the tile. Operators can download these reports to their local machine.
For more information on the tests, test coverage, and test criteria covered by these benchmarks, see the PDF files included on the Compliance Scanner release page on VMware Tanzu Network.
Compliance Scanner includes the following key features:
The following table provides version and version-support information about Compliance Scanner.
|Release date||January 25, 2023|
|Software component version||OpenSCAP 1.3.3|
|Compatible Ops Manager versions||3.0, 2.10, 2.9, and 2.7|
|Compatible VMware Tanzu Application Service for VMs versions||2.7 and later|
|IaaS support||AWS, Azure, GCP, and vSphere|
Compliance Scanner uses the following ports:
|oscap_store||The port used by
|VM with Compliance Scanner||The port used by the scanning server running on each of the VMs with Compliance Scanner installed. This starts the scan on the VM through the daemon client using the
|VM with Compliance Scanner||The port bound to the loopback interface. The scanning server that receives the request passes the request to the RPC server using the port that is doing the scan.||
Compliance Scanner has the following limitations:
Because of stemcell-related customization, benchmarks are not certified by a governing body.
Windows VMs are not supported at this time.
BOSH DNS cannot resolve the
oscap_store VM URL if there is any capitalization in the network name.
Note: Compliance Scanner can only scan Linux VMs running on Xenial stemcells 97.x and 170.x and later.