STIGQter STIGQter: STIG Summary: HYCU Protege Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 01 Jul 2026:

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

DISA Rule

SV-268241r1038672_rule

Vulnerability Number

V-268241

Group Title

SRG-APP-000503-NDM-000320

Rule Version

HYCU-ND-000250

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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

Check Contents

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.

Vulnerability Number

V-268241

Documentable

False

Rule Version

HYCU-ND-000250

Severity Override Guidance

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.

Check Content Reference

M

Target Key

5660