|Finding ID||Version||Rule ID||IA Controls||Severity|
|Log data is essential in the investigation of events. If log data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve. In addition, access to log records provides information an attacker could potentially use to their advantage since each event record might contain communication ports, protocols, services, trust relationships, user names, etc. The web server must protect the log data from unauthorized read, write, copy, etc. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from access by non-privileged users.|
|Apache Server 2.4 UNIX Server Security Technical Implementation Guide||2020-09-25|
|Check Text ( C-15449r276965_chk )|
| Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: |
# httpd -V | egrep -i 'httpd_root|server_config_file'
Review the log file location.
To determine permissions for log files, from the command line, navigate to the directory where the log files are located and enter the following command:
Note the owner and group permissions on these files. Only system administrators and service accounts running the server should have permissions to the files.
If any users other than those authorized have read access to the log files, this is a finding.
|Fix Text (F-15447r276966_fix)|
|To protect the integrity of the data that is being captured in the log files, ensure that only the members of the Auditors group, Administrators, and the user assigned to run the web server software is granted permissions to read the log files.|