STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Nutanix Acropolis GPOS Security Technical Implementation Guide

V-279562

CAT II (Medium)

Nutanix OS must generate audit records when concurrent logons to the same account occur from different sources.

Rule ID

SV-279562r1192301_rule

STIG

Nutanix Acropolis GPOS Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000172

Discussion

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).

Check Content

1. Verify Nutanix AOS generates audit records when concurrent logons to the same account occur using the following command.

$ sudo grep dir /etc/security/faillock.conf
# The directory where the user files with the failure records are kept.
dir = /var/log/faillock

2. Using the location of the faillock log file, check that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules".

$ sudo grep -w faillock /etc/audit/audit.rules 
-w /var/log/faillock -p wa -k logins

If the commands do not return a line, or the lines are commented out, this is a finding.

Fix Text

1. For AOS, configure the audit rules.

$ sudo salt-call state.sls security/CVM/auditCVM

2. For Prism Central, configure the audit rules.

$ sudo salt-call state.sls security/PCVM/auditPCVM

3. For Files, configure the audit rules.

$ sudo salt-call state.sls security/AFS/auditAFS

4. For AHV, configure the audit rules.

$ sudo salt-call state.sls security/KVM/auditKVM