The HYCU virtual appliance must generate audit records when successful/unsuccessful attempts to access privileges occur.

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

HYCU Web UI user access accounts cannot be edited, only removed and readded from/to user groups in the Web UI Self-Service menu.

After adding a user to a group, log in to the HYCU Web UI, navigate into Events context, and search for message of category "USER_GROUP" and text "Successfully added user to group". If the message is not in Events, this is a finding.

Log in to the VM console and run the following command: chkconfig auditd

If the Audit Service is not in a running state, this is a finding.

Check the contents of the "/var/log/audit/audit.log" file. Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur.

If the audit log is not configured or does not have required contents, this is a finding.

Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur.

Log in to the HYCU VM console and run the following command: chkconfig auditd on

Log in to the HYCU VM console and load the STIG audit rules by using the following commands:

1. sudo cp /usr/share/audit/sample-rules/10-base-config.rules /usr/share/audit/sample-rules/30-stig.rules /usr/share/audit/sample-rules/31-privileged.rules /usr/share/audit/sample-rules/99-finalize.rules /etc/audit/rules.d/

2. sudo augenrules --load