When upgrading the Compliance Scanner for VMware Tanzu from version 1.3.6 to 1.3.29 and running the "CIS Ubuntu Linux 22.04 LTS - Level 2" benchmark, administrators may notice that several SSH forwarding compliance checks are no longer evaluated.
Specifically, the following four rules present in version 1.3.6 are missing in version 1.3.29:
Simultaneously, a new rule may appear and report as a failure (red) under the Access, Authentication and Authorization category:
Compliance Scanner for VMware Tanzu v1.3.6
Compliance Scanner for VMware Tanzu v1.3.29
Ubuntu 22.04 LTS (Jammy) Stemcells
This change is expected behavior and is the result of upstream updates to the underlying CIS (Center for Internet Security) Benchmark data streams.
In newer CIS benchmark versions utilized by scanner v1.3.29, granular checks for X11 and TCP forwarding have been consolidated to eliminate redundancy. In OpenSSH, the DisableForwarding directive acts as a master override switch; setting it to yes automatically disables X11, TCP, Agent, and Tun device forwarding. Therefore, the four legacy rules were deprecated in favor of the single, comprehensive Ensure sshd DisableForwarding is enabled rule.
If this new rule is failing, it is because the target BOSH VM does not explicitly have DisableForwarding yes defined in its SSH daemon configuration (/etc/ssh/sshd_config or /etc/ssh/sshd_config.d/), causing OpenSSH to default to allowing forwarding.
No issue in the removal of those 4 rules, as they are now comprised in one rule within the new "CIS Ubuntu Linux 22.04 LTS - Level 2" benchmark in Compliance Scanner for VMware Tanzu v1.3.29.
Apart from this, the "Ensure sshd DisableForwarding is enabled" rule will fail for BOSH-managed VMs. Below is the reason: