STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to JBoss Enterprise Application Platform 6.3 Security Technical Implementation Guide

V-213495

CAT II (Medium)

HTTPS must be enabled for JBoss web interfaces.

Rule ID

SV-213495r960762_rule

STIG

JBoss Enterprise Application Platform 6.3 Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001453

Discussion

Encryption is critical for protection of web-based traffic. If encryption is not being used to protect the application server's web connectors, malicious users may gain the ability to read or modify the application traffic while it is in transit over the network. The use of cryptography on web connectors secures web-based traffic and mitigates that risk. HTTPS and Transport Layer Security (TLS) are the means in which cryptographic protections are applied to web connectors. FIPS 140-2 approved TLS versions include TLS V1.2 or greater.

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 <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.

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.2 or greater.