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

JBoss must be configured to use an approved cryptographic algorithm in conjunction with TLS.

DISA Rule

SV-213548r615939_rule

Vulnerability Number

V-213548

Group Title

SRG-APP-000440-AS-000167

Rule Version

JBOS-AS-000655

Severity

CAT II

CCI(s)

• CCI-002421 - The information system implements cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission unless otherwise protected by organization-defined alternative physical safeguards.

Weight

10

Fix Recommendation

Reference section 4.6 of the JBoss EAP 6.3 Security Guide located on the Red Hat vendor's website for step-by-step instructions on establishing SSL encryption on JBoss.

The overall steps include:

1. Add an HTTPS connector.
2. Configure the SSL encryption certificate and keys.
3. Set the Cipher to an approved algorithm.

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.

Validate that the TLS protocol is used for HTTPS connections.
Run the command:

"ls /subsystem=web/connector=https/ssl=configuration"

Review the cipher suites. The following suites are acceptable as per NIST 800-52r1 section 3.3.1 - Cipher Suites. Refer to the NIST document for a complete list of acceptable cipher suites. The source NIST document and approved encryption algorithms/cipher suites are subject to change and should be referenced.

AES_128_CBC
AES_256_CBC
AES_128_GCM
AES_128_CCM
AES_256_CCM

If the cipher suites utilized by the TLS server are not approved by NIST as per 800-52r1, this is a finding.

Vulnerability Number

V-213548

Documentable

False

Rule Version

JBOS-AS-000655

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.

Validate that the TLS protocol is used for HTTPS connections.
Run the command:

"ls /subsystem=web/connector=https/ssl=configuration"

Review the cipher suites. The following suites are acceptable as per NIST 800-52r1 section 3.3.1 - Cipher Suites. Refer to the NIST document for a complete list of acceptable cipher suites. The source NIST document and approved encryption algorithms/cipher suites are subject to change and should be referenced.

AES_128_CBC
AES_256_CBC
AES_128_GCM
AES_128_CCM
AES_256_CCM

If the cipher suites utilized by the TLS server are not approved by NIST as per 800-52r1, this is a finding.

Check Content Reference

M

Target Key

3987

Comments