HTTPS must be enabled for JBoss web interfaces.

From JBoss EAP 6.3 Security Technical Implementation Guide

Part of SRG-APP-000015-AS-000010

Associated with: CCI-001453

SV-76705r1_rule HTTPS must be enabled for JBoss web interfaces.

Vulnerability discussion

Encryption is critical for protection of remote access sessions. If encryption is not being used for integrity, malicious users may gain the ability to modify the application server configuration. The use of cryptography for ensuring integrity of remote access sessions mitigates that risk.Application servers utilize a web management interface and scripted commands when allowing remote access. Web access requires the use of TLS, and scripted access requires using ssh or some other form of approved cryptography. Application servers must have a capability to enable a secure remote admin capability.FIPS 140-2 approved TLS versions include TLS V1.0 or greater.FIPS 140-2 approved TLS versions must be enabled, and non-FIPS-approved SSL versions must be disabled.NIST SP 800-52 specifies the preferred configurations for government systems.

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 /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=/subsystem=web/connector=" For a standalone system: "ls /subsystem=web/connector=" If "https" is not returned, this is a finding.

Fix text

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.1 or V1.2.

Pro Tips

Powered by sagemincer