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 HYCU Protege Security Technical Implementation Guide

V-268241

CAT II (Medium)

The HYCU virtual appliance must generate audit records when successful/unsuccessful login attempts occur.

Rule ID

SV-268241r1038672_rule

STIG

HYCU Protege Security Technical Implementation Guide

Version

V1R2

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 network device (e.g., module or policy filter).

Check Content

Check the contents of the "/var/log/audit/audit.log" file.

Verify the audit log contains records showing when successful/unsuccessful login attempts occur.

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

HYCU also maintains Event (Audit) information in the "HYCU Web UI Events" menu. Log in with correct and incorrect credentials and check the HYCU Events.

If the HYCU events of category "SECURITY" are not logged for each of the attempts, status is not "Success" for the correct credentials and status is not "Warning" for the incorrect credentials, this is a finding.

Fix Text

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

1. 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. augenrules --load