OpenControls Logo

STIG Viewer

STIGViewer Support

The HYCU virtual appliance must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-268251HYCU-ND-000390SV-268251r1038695_ruleCCI-001849medium
Description
To ensure network devices have a sufficient storage capacity in which to write the audit logs, they must be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it can be modified.
STIGDate
HYCU Protege Security Technical Implementation Guide2024-10-29

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-04Event Log Storage Capacity
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (14) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-12Audit Record Generation
1.00
AU-14(1)System Start-up
1.00
AU-3Content of Audit Records
1.00
AU-3(1)Additional Audit Information
1.00
AU-4Audit Log Storage Capacity
1.00
AU-4(1)Transfer to Alternate Storage
1.00
AU-5Response to Audit Logging Process Failures
1.00
AU-5(1)Storage Capacity Warning
1.00
AU-5(2)Real-time Alerts
1.00
AU-7Audit Record Reduction and Report Generation
1.00

+4 more (top 10 by confidence shown)

CCI1 mapping
CCI-001849
1.00

Details

Check Text (C-268251r1038695_chk)

Log in to the HYCU VM console. Review the /etc/audit/auditd.conf file and verify that the settings are in accordance with organizational policies. If it is not configured in accordance with organizational policies, this is a finding. Check for the value of the "max_log_file_action" option in "/etc/audit/auditd.conf" with the following command: sudo grep max_log_file_action /etc/audit/auditd.conf If the "max_log_file_action" value is not set to "ROTATION", this is a finding.

Fix Text (F-72175r1038452_fix)

Configure the operating system to enforce log rotation and restrict log file size to an organization-defined value by editing "/etc/audit/auditd.conf" files using the following command: sudo vi /etc/audit/auditd.conf Add or modify the following lines to have the required value for the organization. Refer to the sample below: max_log_file_action = ROTATION max_log_file = 6