STIGQter STIGQter: STIG Summary: JBoss Enterprise Application Platform 6.3 Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 22 Jan 2021:

HTTPS must be enabled for JBoss web interfaces.

DISA Rule

SV-213495r615939_rule

Vulnerability Number

V-213495

Group Title

SRG-APP-000015-AS-000010

Rule Version

JBOS-AS-000015

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Follow procedure "4.4. Configure the JBoss Web Server to use HTTPS." The detailed procedure is found in the JBoss EAP 6.3 Security Guide available at the vendor's site, RedHat.com. An overview of steps is provided here.

1. Obtain or generate DoD-approved SSL certificates.
2. Configure the SSL certificate using your certificate values.
3. Set the SSL protocol to TLS V1.2 or greater.

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.

Review the web subsystem and ensure that HTTPS is enabled.
Run the command:

For a managed domain:
"ls /profile=<PROFILE_NAME>/subsystem=web/connector="

For a standalone system:
"ls /subsystem=web/connector="

If "https" is not returned, this is a finding.

Vulnerability Number

V-213495

Documentable

False

Rule Version

JBOS-AS-000015

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.

Review the web subsystem and ensure that HTTPS is enabled.
Run the command:

For a managed domain:
"ls /profile=<PROFILE_NAME>/subsystem=web/connector="

For a standalone system:
"ls /subsystem=web/connector="

If "https" is not returned, this is a finding.

Check Content Reference

M

Target Key

3987

Comments