The VMM must produce audit records containing information to establish what type of events occurred.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-207352	SRG-OS-000037	SRG-OS-000037-VMM-000150	SV-207352r958412_rule	2024-12-06	2

Description
Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process/VM identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the VMM audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured VMM.

Description

Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process/VM identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the VMM audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured VMM.

ℹ️ Check
Verify the VMM produces audit records containing information to establish what type of events occurred. If it does not, this is a finding.

✔️ Fix
Configure the VMM to produce audit records containing information to establish what type of events occurred.