Details
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be considered sensitive and in need of protection.
Successful exploit of an application server vulnerability may well be logged by monitoring or audit processes when it occurs. Writing log and audit data to a separate partition where separate security contexts protect them may offer the ability to protect this information from being modified or removed by the exploit mechanism.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Update the EDSP.
Configure the audit log location to be on a partition drive separate from the application.
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 Windows.
References
- 800-53|AU-9(2)
- CAT|II
- CCI|CCI-001348
- Rule-ID|SV-221215r612603_rule
- STIG-ID|EX16-ED-000140
- STIG-Legacy|SV-95221
- STIG-Legacy|V-80511
- Vuln-ID|V-221215