Anti-Virus for VMware Tanzu
Note: Pivotal Platform is now part of VMware Tanzu. In v2.2 and later, Pivotal Anti-Virus is named Anti-Virus for VMware Tanzu.
Page last updated:
This topic is an overview of Anti-Virus for VMware Tanzu.
Overview
Anti-Virus for VMware Tanzu might be necessary for regulatory purposes if your compliance auditor requires antivirus protection within your Ops Manager environment.
For example, auditors sometimes expect that antivirus protection is present in an environment that must comply with standards such as the Payment Card Industry Data Security Standard (PCI DSS) or Health Insurance Portability and Accountability Act (HIPAA).
Anti-Virus for VMware Tanzu complies with the U.S. Department of Defense STIG rule SV-92701r1_rule, version UBTU-16-030900, which belongs to group SRG-OS-000480-GPOS-00227.
Product Snapshot for Anti-Virus for VMware Tanzu
The following table provides version and version-support information about Anti-Virus for VMware Tanzu.
Element | Details |
---|---|
Version | 2.2.8 |
Release date | June 19, 2020 |
Software component version | Open Source ClamAV 0.101.4 |
Compatible Ops Manager versions | 2.10, 2.9, 2.8, 2.7, 2.6, and 2.5 |
Compatible VMware Tanzu Application Service for VMs (TAS for VMs) versions | 2.10, 2.9, 2.8, 2.7, 2.6, and 2.5 |
Compatible Enterprise VMware PKS (Enterprise PKS) versions | 1.3, 1.4, 1.5, 1.6, 1.7, 1.8 and 1.9 |
Compatible BOSH stemcells | Ubuntu Xenial and Windows (2019, 1803, and 2016) |
IaaS support | vSphere, GCP, AWS, Azure, and OpenStack |
Product Snapshot for Anti-Virus Mirror for VMware Tanzu
The following table provides version and version-support information about Anti-Virus Mirror for VMware Tanzu.
Element | Details |
---|---|
Version | 2.2.8 |
Release date | June 19, 2020 |
Compatible Ops Manager versions | 2.5, 2.6, 2.7, and 2.8 |
Compatible VMware Tanzu Application Service for VMs (TAS for VMs) versions | 2.5, 2.6, 2.7, and 2.8 |
Compatible Enterprise VMware PKS (Enterprise PKS) versions | 1.3, 1.4, 1.5, 1.6, 1.7, 1.8 and 1.9 |
Compatible BOSH stemcells | Ubuntu Xenial and Windows (2019, 1803, and 2016) |
IaaS support | vSphere, GCP, AWS, Azure, and OpenStack |
Features
- Includes open source ClamAV packaged as part of the tile for installation.
- Contains a private Anti-Virus Mirror tile for deployment and providing VMs to the foundation.
- Anti-Virus Mirror serves both air-gapped and non-air-gapped environments.
- The tile authenticates and validates publicly downloaded database definition files for added security.
- Ability to scan VMs and containers for foundations with TAS for VMs and Enterprise PKS.
- Supports scheduled scans to reduce workload during peak operation hours.
- Permits adding known signatures to an allowlist.
- Allows you to configure CPU and memory usage limits on VMs of the foundation.
Anti-Virus Architecture
How Virus Definitions Propagate to VMs
Virus definitions on the internal Anti-Virus Mirror update automatically or manually depending on whether your Ops Manager is on an online or air-gapped network, as described in Updating Virus Definitions on an Anti-Virus Mirror. The automatic and manual processes store new virus definitions to the Anti-Virus Mirror VM’s database of unverified viruses as follows:
- Automatic update: The
freshclam
daemon process on the Anti-Virus Mirror VM downloads the virus definitions and stores them in the internal mirror VM’s unverified database. - Manual update: The operator runs
bosh scp
to directly copy the virus definitions to the internal mirror’s database of unverified viruses.
From the unverified internal mirror database, virus definitions then propagate to BOSH VMs as follows:
The database verifier process on the Anti-Virus Mirror verifies the date, format, and integrity of the new virus definitions.
- To verify integrity, the verifier checks bytecode signatures against signatures in the external ClamAV database, using the external database public key.
- If verification fails or if the virus definitions are not new, the mirror VM generates an error. See Virus Database Update Issues.
The internal Anti-Virus Mirror VM saves verified virus definitions to its verified database and serves them to the
freshclam
processes of BOSH VMs.On each BOSH-managed VM:
- The
freshclam
daemon process regularly queries the internal Anti-Virus Mirror for new virus definitions.- You can configure the query frequency in the Anti-Virus for VMware Tanzu tile > ClamAV Configuration > Number of database checks per day field.
- When
freshclam
retrieves new definitions, it:- Notifies the
clamd
daemon process that there are new definitions, and - Saves the virus definitions in the BOSH VM’s own virus database.
- Notifies the
- The
clamd
process loads the new virus definitions into active memory to enable fast scanning by theclamscan
process.
- The
The diagrams below illustrate how new virus definitions propagate from an external ClamAV database to Ops Manager managed BOSH VMs, in online and air-gapped installations.
Online Network (Diagram)
This diagram illustrates how virus definitions propagate to BOSH VMs with Anti-Virus Mirror using mutual TLS (mTLS):
Air-Gapped Network (Diagram)
This diagram illustrates how virus definitions propagate to BOSH VMs with Anti-Virus Mirror using mTLS: