Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The SLES for vRealize must generate audit records when successful/unsuccessful accesses to objects occur.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-240533 | VRAU-SL-001430 | SV-240533r671340_rule | Medium |
| Description |
|---|
| Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). |
| STIG | Date |
|---|---|
| VMware vRealize Automation 7.x SLES Security Technical Implementation Guide | 2023-09-22 |
Details
| Check Text ( C-43766r671338_chk ) |
|---|
| Verify the SLES for vRealize produces audit records by running the following command to determine the current status of the "auditd" service: # service auditd status If the service is "enabled", the returned message must contain the following text: Checking for service auditd running If the service is not "running", this is a finding. |
| Fix Text (F-43725r671339_fix) |
|---|
| Enable the "auditd" service by performing the following commands: # chkconfig auditd on # service auditd start |