Details
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.2 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.
Solution
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.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system Unix.
References
- 800-53|AC-17(2)
- CAT|II
- CCI|CCI-001453
- Rule-ID|SV-213495r615939_rule
- STIG-ID|JBOS-AS-000015
- STIG-Legacy|SV-76705
- STIG-Legacy|V-62215
- Vuln-ID|V-213495