Details
JVM logs are logs used to store application and runtime related events, rather than audit related events. They are mainly used to diagnose application or runtime bugs. But sometimes they may be useful in providing more context when correlated with audit related events.
The proper management of log records not only dictates proper archiving processes and procedures be established, it also requires allocating enough storage space to maintain the logs online for a defined period of time.
If adequate online log storage capacity is not maintained, intrusion monitoring, security investigations, and forensic analysis can be negatively affected.
It is important to keep a defined amount of logs online and readily available for investigative purposes. The logs may be stored on the application server until they can be archived to a log system or, in some instances, a Storage Area Networks (SAN). Regardless of the method used, log record storage capacity must be sufficient to store log data when the data cannot be offloaded to a log system or SAN.
Solution
Identify JVM log size and history retention based on component log policy.
Document those values in the System Security Plan.
From the administrative console, navigate to Troubleshooting >> Logs and Trace.
Select each [server name].
Click ‘JVM’ Logs.
Under ‘System.out’, ‘Log Rotation’, select ‘File size’ in the ‘Maximum Size’ entry field, enter the maximum log size based on policy.
Under ‘System.err’, ‘Log Rotation’, select ‘File Size’ in the ‘Maximum Size’ entry field, enter the maximum log size based on policy.
Click ‘OK’.
Click ‘Save’.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.
References
- 800-53|AU-4
- CAT|II
- CCI|CCI-001849
- Rule-ID|SV-95953r1_rule
- STIG-ID|WBSP-AS-000580
- Vuln-ID|V-81239