File permissions must be configured to protect log information from any type of unauthorized read access.

If log data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve.

When not configured to use a centralized logging solution like a syslog server, the JBoss EAP application server writes log data to log files that are stored on the OS; appropriate file permissions must be used to restrict access.

Log information includes all information (e.g., log records, log settings, transaction logs, and log reports) needed to successfully log information system activity. Application servers must protect log information from unauthorized access.

Examine the log file locations and inspect the file permissions. Interview the system admin to determine log file locations. The default location for the log files is:

Standalone configuration: <JBOSS_HOME>/standalone/log/

Managed Domain configuration: <JBOSS_HOME>/domain/servers/<servername>/log/ <JBOSS_HOME>/domain/log/

Review the file permissions for the log file directories. The method used for identifying file permissions will be based upon the OS the EAP server is installed on.

Identify all users with file permissions that allow them to read log files.

Request documentation from system admin that identifies the users who are authorized to read log files.

If unauthorized users are allowed to read log files, or if documentation that identifies the users who are authorized to read log files is missing, this is a finding.

Configure the OS file permissions on the application server to protect log information from unauthorized read access.