STIGQter STIGQter: STIG Summary: JBoss EAP 6.3 Security Technical Implementation Guide Version: 1 Release: 4 Benchmark Date: 25 Oct 2019: JBoss management interfaces must be secured.

DISA Rule

SV-76719r1_rule

Vulnerability Number

V-62229

Group Title

SRG-APP-000033-AS-000024

Rule Version

JBOS-AS-000075

Severity

CAT I

CCI(s)

Weight

10

Fix Recommendation

Identify the security realm used for management of the system. By default, this is called "Management Realm".

If a management security realm is not already available, reference the Jboss EAP 6.3 system administration guide for instructions on how to create a security realm for management purposes. Create the management realm, and assign authentication and authorization access restrictions to the management realm.

Assign the management interfaces to the management realm.

Check Contents

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.

Identify the management interfaces. To identity the management interfaces, run the following command:

For standalone servers:
"ls /core-service=management/management-interface="

For managed domain installations:
"ls /host=HOST_NAME/core-service=management/management-interface="

By default, JBoss provides two management interfaces; they are named "NATIVE-INTERFACE" and "HTTP-INTERFACE". The system may or may not have both interfaces enabled. For each management interface listed as a result of the previous command, append the name of the management interface to the end of the following command.

For a standalone system:

"ls /core-service=management/management-interface=<MANAGEMENT INTERFACE NAME>"

For a managed domain:

"ls /host=HOST_NAME/core-service=management/management-interface=<MANAGEMENT INTERFACE NAME>"

If the "security-realm=" attribute is not associated with a management realm, this is a finding.

Vulnerability Number

V-62229

Documentable

False

Rule Version

JBOS-AS-000075

Severity Override Guidance

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.

Identify the management interfaces. To identity the management interfaces, run the following command:

For standalone servers:
"ls /core-service=management/management-interface="

For managed domain installations:
"ls /host=HOST_NAME/core-service=management/management-interface="

By default, JBoss provides two management interfaces; they are named "NATIVE-INTERFACE" and "HTTP-INTERFACE". The system may or may not have both interfaces enabled. For each management interface listed as a result of the previous command, append the name of the management interface to the end of the following command.

For a standalone system:

"ls /core-service=management/management-interface=<MANAGEMENT INTERFACE NAME>"

For a managed domain:

"ls /host=HOST_NAME/core-service=management/management-interface=<MANAGEMENT INTERFACE NAME>"

If the "security-realm=" attribute is not associated with a management realm, this is a finding.

Check Content Reference

M

Target Key

2923

Comments