Title

Production JBoss servers must log when successful application deployments occur. (Cat II impact)

Discussion

Without logging the enforcement of access restrictions against changes to the application server configuration, it will be difficult to identify attempted attacks, and a log trail will not be available for forensic investigation for after-the-fact actions. Configuration changes may occur to any of the modules within the application server through the management interface, but logging of actions to the configuration of a module outside the application server is not logged. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Log items may consist of lists of actions blocked by access restrictions or changes identified after the fact.

Check Content

Log on to the OS of the JBoss server with OS permissions that allow access to JBoss. Using the relevant OS commands and syntax, cd to the <JBOSS_HOME>/bin/ folder. Run the jboss-cli script. Connect to the server and authenticate. Run the command: ls /core-service=management/access=audit/logger=audit-log If "enabled" = false, this is a finding.

Fix Text

Launch the jboss-cli management interface substituting standalone or domain for <CONFIG> based upon the server installation. <JBOSS_HOME>/<CONFIG>/bin/jboss-cli connect to the server and run the following command: /core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true)

Additional Identifiers

Rule ID: SV-213544r955581_rule

Vulnerability ID: V-213544

Group Title: SRG-APP-000381-AS-000089

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.