STIGQter: STIG Summary: VMware vSphere 6.7 vCenter Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 09 Mar 2021:

The vCenter Server must provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events.

DISA Rule

SV-243078r719644_rule

Vulnerability Number

V-243078

Group Title

SRG-APP-000108

Rule Version

VCTR-67-000008

Severity

CAT II

CCI(s)

• CCI-000139 - The information system alerts designated organization-defined personnel or roles in the event of an audit processing failure.

Weight

10

Fix Recommendation

From the vSphere Client, go to Hosts and Clusters >> select a vCenter Server >> Configure >> More >> Alarm Definitions.

Click "Add".

Provide an alarm name and description.

Select "Hosts" from the "Target type" dropdown menu.

Click "Next".

Paste "esx.problem.vmsyslogd.remote.failure" in the line after IF and press "Enter".

Select "Show as Warning" for severity.

Click "Next".

Configure any other options as desired, enable alarm, and finish.

Note: This alarm will only trigger if syslog is configured for TCP or SSL connections and not UDP.

Check Contents

From the vSphere Client, go to Hosts and Clusters >> select a vCenter Server >> Configure >> More >> Alarm Definitions.

Verify there is an alarm created to alert if an ESXi host can no longer reach its syslog server. The alarm definition will have a rule for the "Remote logging host has become unreachable" event.

or

From a PowerCLI command prompt while connected to the vCenter server, run the following command:

Get-AlarmDefinition | Where {$_.ExtensionData.Info.Expression.Expression.EventTypeId -eq "esx.problem.vmsyslogd.remote.failure"} | Select Name,Enabled,@{N="EventTypeId";E={$_.ExtensionData.Info.Expression.Expression.EventTypeId}}

If an alarm is not created and enabled to alert when syslog failures occur, this is a finding.

Vulnerability Number

V-243078

Documentable

False

Rule Version

VCTR-67-000008

Severity Override Guidance

From the vSphere Client, go to Hosts and Clusters >> select a vCenter Server >> Configure >> More >> Alarm Definitions.

Verify there is an alarm created to alert if an ESXi host can no longer reach its syslog server. The alarm definition will have a rule for the "Remote logging host has become unreachable" event.

or

From a PowerCLI command prompt while connected to the vCenter server, run the following command:

Get-AlarmDefinition | Where {$_.ExtensionData.Info.Expression.Expression.EventTypeId -eq "esx.problem.vmsyslogd.remote.failure"} | Select Name,Enabled,@{N="EventTypeId";E={$_.ExtensionData.Info.Expression.Expression.EventTypeId}}

If an alarm is not created and enabled to alert when syslog failures occur, this is a finding.

Check Content Reference

M

Target Key

5399

Comments