Details
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data.
It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access.
Application servers provide a web and/or a command line-based management functionality for managing the application server audit capabilities. In addition, subsets of audit tool components may be stored on the file system as jar or xml configuration files. The application server must ensure that in addition to protecting any web based audit tools, any file system-based tools are protected as well.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
1. Access AC
2. From ‘Domain Structure’, select ‘Security Realms’
3. Select realm to configure (default is ‘myrealm’)
4. Select ‘Users and Groups’ tab -> ‘Users’ tab
5. From ‘Users’ table, select a user that must not have audit tool configuration access
6. From users settings page, select ‘Groups’ tab
7. From the ‘Chosen’ table, use the shuttle buttons to remove the role – ‘Admin’
8. Click ‘Save’
9. Repeat steps 5-8 for all users that must not have audit tool configuration access
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-9
- CAT|II
- CCI|CCI-001493
- Rule-ID|SV-235957r628649_rule
- STIG-ID|WBLC-02-000098
- STIG-Legacy|SV-70517
- STIG-Legacy|V-56263
- Vuln-ID|V-235957