JBOS-AS-000285 - The JBoss server must be configured to bind the management interfaces to only management networks.


JBoss provides multiple interfaces for accessing the system. By default, these are called 'public' and 'management'. Allowing non-management traffic to access the JBoss management interface increases the chances of a security compromise. The JBoss server must be configured to bind the management interface to a network that controls access. This is usually a network that has been designated as a management network and has restricted access. Similarly, the public interface must be bound to a network that is not on the same segment as the management interface.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.


Refer to Section 4.9 of the JBoss EAP 6.3 Installation guide for detailed instructions on how to start JBoss as a service.

Use the following command line parameters to assign the management interface to a specific management network.

These command line flags must be added both when starting JBoss as a service and when starting from the command line.

Substitute your actual network address for the 10.x.x.x addresses provided as an example below.

For a standalone configuration:
JBOSS_HOME/bin/standalone.sh -bmanagement= -b

JBOSS_HOME/bin/domain.sh -bmanagement= -b

If a management network is not available, you may substitute localhost/ for management address. This will force you to manage the JBoss server from the local host.

See Also


Item Details


References: 800-53|CM-6b., 800-53|IA-3, CAT|II, CCI|CCI-000366, CCI|CCI-000778, Rule-ID|SV-217099r615939_rule, STIG-ID|JBOS-AS-000285, STIG-Legacy|SV-76773, STIG-Legacy|V-62283, Vuln-ID|V-217099

Plugin: Unix

Control ID: 5b873c682bbb11690cbb11c1bb00afa96ed50bf08d4c1a4e5a3875d7644bba72