VMware vSphere 6.7 Virgo-Client Security Technical Implementation Guide

The VMware vSphere 6.7 Virgo-Client Security Technical Implementation Guide (V1 R2) has 30 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

30STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R2

CurrentPublished Wed Jul 26 2023

vSphere Client application files must be verified for their integrity.

VMware vSphere 6.7 Virgo-Client Security Technical Implementation Guide

Assessment Title

Rule Text

vSphere Client application files must be verified for their integrity.

Description

Discussion Text

Verifying that vSphere Client application code is unchanged from its shipping state is essential for file validation and non-repudiation of vSphere Client. There is no reason that the MD5 hash of the rpm original files should be changed after installation, excluding configuration files.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-239753

Rule

SV-239753r879584_rule

Severity

medium

Rule Version

VCFL-67-000012

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

At the command prompt, execute the following command:

# rpm -V vsphere-client|grep "^..5......"|grep -E "\.war|\.jar|\.sh|\.py"

If there is any output, this is a finding.

Implementation Procedure

Fix Text

Reinstall the VCSA or roll back to a snapshot. 

Modifying the vSphere Client installation files manually is not supported by VMware.

STIG check 11 of 30 in the VMware vSphere 6.7 Virgo-Client STIG checklist

← Previous · V-239752vSphere Client must generate log records during Java startup and shutdown.Next · V-239754 →vSphere Client must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.