Group
Guide to the Secure Configuration of JBoss EAP 6
Group contains 1 group and 49 rules |
Group
JBoss Enterprise Application Platform 6
Group contains 49 rules |
[ref]
JBoss Enterprise Application Platform is a popular Java
Enterprise Edition application server platform by Red Hat. It is based
on the open-source JBoss Application Server, Community Edition.
Leveraging robust container architecture, JBoss EAP is capable of
hosting a wide variety of applications - anything from simple, static
HTML pages all the way to distributed, transaction-based Java Enterprise
Edition applications. JBoss EAP is known for being dependable, fast,
flexible, and cost-effective. This section provides settings for
configuring the JBoss Enterprise Application Platform running on
Red Hat Enterprise Linux systems. |
Rule
Enable the Java Security Manager
[ref] | For a domain installation:
Enable the respective JAVA_OPTS flag in both the
domain.conf and the domain.conf.bat files.
For a standalone installation:
Enable the respective JAVA_OPTS flag in both the standalone.conf and the
standalone.conf.bat files. | Rationale: | The Java Security Manager is a java class that manages the external boundary of
the Java Virtual Machine (JVM) sandbox, controlling how code executing within
the JVM can interact with resources outside the JVM.
The Java Security Manager
uses a security policy to determine whether a given action will be
permitted or
denied.
To protect the host system, the JBoss application server must be run
within the Java Security Manager. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_security_manager | Identifiers and References | Identifiers:
CCE-80453-4 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000030, SV-76715r1_rule | |
|
Rule
Configure JBoss Log Directory Permissions
[ref] | Configure file permissions on the JBoss log folder to protect from unauthorized
access. | Rationale: | If the application provides too much information in error logs and
administrative messages to the screen, this could lead to compromise. The
structure and content of error messages need to be carefully considered by the
organization and development team. The extent to which the information system is
able to identify and handle error conditions is guided by organizational policy
and operational requirements.
Application servers must protect the error
messages that are created by the application server. All application server
users' accounts are used for the management of the server and the applications
residing on the application server. All accounts are assigned to a certain role
with corresponding access rights. The application server must restrict access to
error messages so only authorized users may view them. Error messages are
usually written to logs contained on the file system. The application server
will usually create new log files as needed and must take steps to ensure that
the proper file permissions are utilized when the log files are created. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_logs_permissions | Identifiers and References | Identifiers:
CCE-80485-6 References:
CCI-001314, SRG-APP-000267-AS-000170, JBOS-AS-000425, SV-76791r1_rule | |
|
Rule
Enable HTTPS for JBoss Web Interface
[ref] | 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. | Rationale: | 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. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_https | Identifiers and References | Identifiers:
CCE-80451-8 References:
CCI-001453, SRG-APP-000015-AS-000010, JBOS-AS-000015, SV-76705r1_rule | |
|
Rule
Disable Network Access to the Admin Console
[ref] | Run the <JBOSS_HOME>/bin/jboss-clii command line interface utility.
Connect to
the JBoss server and run the following command.
/core-service=management/management-interface=httpinterface/:write-attribute(name=console-enabled,value.)
Successful command execution returns
{"outcome" => success"} ,
and future attempts to access the management console via web
browser at SERVERNAME:9990 will result in no access to the admin console. | Rationale: | When configuring JBoss application servers into a domain configuration, HTTP
management capabilities are not required on domain member servers as management
is done via the server that has been designated as the domain controller.
Leaving HTTP management capabilities enabled on domain member servers increases
the attack surfaces; therefore, management services on domain member servers
must be disabled and management services performed via the domain
controller. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_disable_domain_admin_console | Identifiers and References | Identifiers:
CCE-80486-4 References:
CCI-002322, SRG-APP-000316-AS-000199, JBOS-AS-000470, SV-76793r1_rule | |
|
Rule
Use Approved Ciphers
[ref] | 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. | Rationale: | Preventing the disclosure or modification of transmitted information requires
that application servers take measures to employ approved cryptography in order
to protect the information during transmission over the network. This is usually
achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPSec
tunnel.
If data in transit is unencrypted, it is vulnerable to disclosure and
modification. If approved cryptographic algorithms are not used, encryption
strength cannot be assured.
FIPS 140-2 approved TLS versions include TLS V1.0
or greater.
TLS must be enabled, and non-FIPS-approved SSL versions must be
disabled. NIST SP 800-52 specifies the preferred configurations for government
systems. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_use_approved_ciphers | Identifiers and References | Identifiers:
CCE-80494-8 References:
CCI-002421, SRG-APP-000440-AS-000167, JBOS-AS-000655, SV-76813r2_rule | |
|
Rule
Restrict JBoss Account
[ref] | Run the JBoss server with non-admin rights. | Rationale: | JBoss EAP application server can be run as the OS admin, which is not advised.
Running the application server with admin privileges increases the attack
surface by granting the application server more rights than it requires in order
to operate. If the server is compromised, the attacker will have the same
rights as the application server, which in that case would be admin rights. The
JBoss EAP server must not be run as the admin user. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_unprivileged_mode | Identifiers and References | Identifiers:
CCE-80467-4 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000230, SV-76755r1_rule | |
|
Rule
Disable Google Analytics
[ref] | Using the EAP web console, log on using admin credentials.
On the bottom right-hand side of the screen, select Settings ,
uncheck the Enable Data Usage Collection box, and save the
configuration. | Rationale: | The Google Analytics feature aims to help Red Hat EAP team understand how
customers are using the console and which parts of the console matter the most
to the customers. This information will, in turn, help the team to adapt the
console design, features, and content to the immediate needs of the customers.
Sending analytical data to the vendor introduces risk of unauthorized data
exfiltration. This capability must be disabled. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_disable_analytics | Identifiers and References | Identifiers:
CCE-80466-6 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000225, SV-76753r1_rule | |
|
Rule
JBoss System Is Patched
[ref] | Configure the operating system and the application server to use a patch
management system or process that ensures security-relevant updates are
installed within the time period directed by the ISSM. | Rationale: | The JBoss product is available as Open Source; however, the Red Hat vendor
provides updates, patches and support for the JBoss product. It is imperative
that patches and updates be applied to JBoss in a timely manner as many attacks
against JBoss focus on unpatched systems. It is critical that support be
obtained and made available. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_system_up_to_date | Identifiers and References | Identifiers:
CCE-80496-3 References:
CCI-002605, SRG-APP-000456-AS-000266, JBOS-AS-000685, SV-76817r1_rule | |
|
Rule
Enable Role Based Access Control (RBAC)
[ref] | Run the following command.
<JBOSS_HOME>/bin/jboss-cli.sh -c -> connect -> cd
/core-service=management/access-authorization :write-attribute(name=provider,
value=rbac)
Restart JBoss.
Map users to roles by running the following
command. Upper-case words are variables.
role-mapping=ROLENAME/include=ALIAS:add(name-USERNAME, type=USER ROLE) | Rationale: | By default, the JBoss server is not configured to utilize role based access
controls (RBAC). RBAC provides the capability to restrict user access to their
designated management role, thereby limiting access to only the JBoss
functionality that they are supposed to have. Without RBAC, the JBoss server is
not able to enforce authorized access according to role. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_enable_rbac | Identifiers and References | Identifiers:
CCE-80454-2 References:
CCI-000213, CCI-002235, SRG-APP-000033-AS-000024, SRG-APP-000340-AS-000185, JBOS-AS-000035, SV-76717r1_rule | |
|
Rule
Disable Automatic Deployment
[ref] | Determine the JBoss server configuration as being either standalone or domain.
Launch the relevant jboss-cli management interface substituting standalone or
domain for CONFIG
<JBOSS_HOME>/CONFIG/bin/jboss-cli
connect to the server and run the command:
/subsystem=deployment-scanner/scanner=default:write-attribute(name=scan-enabled,value.) | Rationale: | When dealing with access restrictions pertaining to change control, it should
be noted that any changes to the software and/or application server
configuration can potentially have significant effects on the overall security
of the system.
Access restrictions for changes also include application
software libraries.
If the application server provides automatic code
deployment capability, (where updates to applications hosted on the application
server are automatically performed, usually by the developers' IDE tool), it
must also provide a capability to restrict the use of automatic application
deployment. Automatic code deployments are allowable in a development
environment, but not in production. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_disable_automatic_deployment | Identifiers and References | Identifiers:
CCE-80489-8 References:
CCI-001813, SRG-APP-000380-AS-000088, JBOS-AS-000545, SV-76801r1_rule | |
|
Rule
Roll Over and Transfer JBoss Logs
[ref] | Open the web-based management interface by opening a browser and pointing it to
HTTPS://EAP_SERVER:9990/
Authenticate as a user with Admin rights.
Navigate
to the Configuration tab.
Expand + Subsystems.
Expand + Core.
Select
Logging .
Select the Handler tab.
Select Periodic .
If a
periodic file handler does not exist, reference JBoss admin guide for
instructions on how to create a file handler that will rotate logs on a daily
basis.
Create scripts that package and off-load log data at least weekly. | Rationale: | Information stored in one location is vulnerable to accidental or incidental
deletion or alteration. Protecting log data is important during a forensic
investigation to ensure investigators can track and understand what may have
occurred. Off-loading should be set up as a scheduled task but can be
configured to be run manually, if other processes during the off-loading are
manual.
Off-loading is a common process in information systems with limited log
storage capacity. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_roll_over_transfer_logs | Identifiers and References | Identifiers:
CCE-80498-9 References:
CCI-001851, SRG-APP-000515-AS-000203, JBOS-AS-000735, SV-76835r1_rule | |
|
Rule
Secure the JBoss Management Interfaces
[ref] | Identify the security realm used for management of the system. By default,
this is called Management Realm .
If a management security realm is not
already available, reference the Jboss EAP 6.3 system administration guide for
instructions on how to create a security realm for management purposes. Create
the management realm, and assign authentication and authorization access
restrictions to the management realm.
Assign the management interfaces to the management realm. | Rationale: | JBoss utilizes the concept of security realms to secure the management
interfaces used for JBoss server administration. If the security realm
attribute is omitted or removed from the management interface definition, access
to that interface is no longer secure. The JBoss management interfaces must be
secured. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_security_realm | Identifiers and References | Identifiers:
CCE-80458-3 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000075, SV-76719r1_rule | |
|
Rule
Configure JBoss Log Permissions
[ref] | Configure the OS file permissions on the application server to protect log
information from unauthorized access. | Rationale: | If log data were to become compromised, then competent forensic analysis and
discovery of the true source of potentially malicious system activity is
difficult, if not impossible, to achieve.
When not configured to use a
centralized logging solution like a syslog server, the JBoss EAP application
server writes log data to log files that are stored on the OS; appropriate file
permissions must be used to restrict access.
Log information includes all
information (e.g., log records, log settings, transaction logs, and log reports)
needed to successfully log information system activity. Application servers must
protect log information from unauthorized access. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_log_permissions | Identifiers and References | Identifiers:
CCE-80462-5 References:
CCI-000162, CCI-000163, CCI-000164, SRG-APP-000118-AS-000078, SRG-APP-000119-AS-000079, SRG-APP-000120-AS-000080, JBOS-AS-000165, SV-76741r1_rule | |
|
Rule
Restrict the JBoss Account
[ref] | Use the relevant OS commands to restrict JBoss user account from interactively
logging on to the console of the JBoss system.
For Windows systems, use GPO.
For UNIX like systems using ssh DenyUsers account id or follow established
procedure for restricting access. | Rationale: | JBoss does not require admin rights to operate and should be run as a regular
user. In addition, if the user account was to be compromised and the account
was allowed interactive logon rights, this would increase the risk and attack
surface against the JBoss system. The right to interactively log on to the
system using the JBoss account should be limited according to the OS
capabilities. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_restrict_jboss_account | Identifiers and References | Identifiers:
CCE-80465-8 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000220, SV-76751r1_rule | |
|
Rule
Use Approves TLS version
[ref] | Reference section 4.6 of the JBoss EAP 6.3 Security Guide located on the Red
Hat vendor's web site 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 protocol to TLS V1.1 or V1.2. | Rationale: | Preventing the disclosure of transmitted information requires that the
application server take measures to employ some form of cryptographic mechanism
in order to protect the information during transmission. This is usually
achieved through the use of Transport Layer Security (TLS).
JBoss relies on
the underlying SSL implementation running on the OS. This can be either Java
based or OpenSSL. The SSL protocol setting determines which SSL protocol is
used. SSL has known security vulnerabilities, so TLS should be used instead.
If data is transmitted unencrypted, the data then becomes vulnerable to
disclosure. The disclosure may reveal user identifier/password combinations,
website code revealing business logic, or other user personal information.
FIPS 140-2 approved TLS versions include TLS V1.0 or greater.
TLS must be enabled,
and non-FIPS-approved SSL versions must be disabled. NIST SP 800-52 specifies
the preferred configurations for government systems. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_use_tls | Identifiers and References | Identifiers:
CCE-80493-0 References:
CCI-002418, SRG-APP-000439-AS-000155, JBOS-AS-000650, SV-76811r2_rule | |
|
Rule
Remove the JMX Subsystem
[ref] | 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 to start the Command Line Interface (CLI).
Connect to the server and authenticate.
For a Managed Domain configuration you
must check each profile name:
For each PROFILE NAME, run the command:
/profile=PROFILE NAME/subsystem=jmx/remoting-connector=jmx:remove
For a Standalone configuration:
/subsystem=jmx/remoting-connector=jmx:remove | Rationale: | The JMX subsystem allows you to trigger JDK and application management
operations remotely. In a managed domain configuration, the JMX subsystem is
removed by default. For a standalone configuration, it is enabled by default and
must be removed. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_remove_jmx | Identifiers and References | Identifiers:
CCE-80469-0 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000240, SV-76759r1_rule | |
|
Rule
Configure mgmt-users.properties File Permissions
[ref] | Configure the file permissions to allow access to authorized users only.
Owner can be full access. Group can be full access.
All others must have execute
permissions only. | Rationale: | The mgmt-users.properties file contains the password hashes of all users who
are in a management role and must be protected. Application servers have the
ability to specify that the hosted applications utilize shared libraries. The
application server must have a capability to divide roles based upon duties
wherein one project user (such as a developer) cannot modify the shared library
code of another project user. The application server must also be able to
specify that non-privileged users cannot modify any shared library code at
all. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_user_permissions | Identifiers and References | Identifiers:
CCE-80464-1 References:
CCI-001499, SRG-APP-000133-AS-000092, JBOS-AS-000210, SV-76749r1_rule | |
|
Rule
Require Password Authentication
[ref] | Configure the LDAP Security Realm using default settings that sets allow-empty-values
to .. LDAP Security Realm creation is described in
section 11.9 -Add an LDAP Security Realm in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document. | Rationale: | Passwords need to be protected at all times, and encryption is the standard
method for protecting passwords during transmission. If passwords are not
encrypted, they can be plainly read (i.e., clear text) and easily compromised.
Application servers have the capability to utilize either certificates (tokens)
or user IDs and passwords in order to authenticate. When the application server
transmits or receives passwords, the passwords must be encrypted. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_require_password_access | Identifiers and References | Identifiers:
CCE-80480-7 References:
CCI-000197, SRG-APP-000172-AS-000120, JBOS-AS-000305, SV-76781r1_rule | |
|
Rule
Configure JBoss Auditing and Logging
[ref] | Launch the jboss-cli management interface.
Connect to the server by typing
connect , authenticate as a user in the Superuser role, and run the
following command:
For a Managed Domain configuration:
host=master/server/SERVERNAME/core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true)
For a Standalone
configuration:
/core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true) | Rationale: | Log records can be generated from various components within the JBoss
application server. The minimum list of logged events should be those
pertaining to access and authentication events to the management interface as
well as system startup and shutdown events.
By default, JBoss does not log
management interface access but does provide a default file handler. This
handler needs to be enabled. Configuring this setting meets several STIG
auditing requirements. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_auditing | Identifiers and References | Identifiers:
CCE-80459-1 References:
CCI-000130, CCI-000131, CCI-000132, CCI-000133, CCI-000134, CCI-000169, CCI-000172, CCI-001464, SRG-APP-000089-AS-000050, SRG-APP-000092-AS-000053, SRG-APP-000095-AS-000056, SRG-APP-000096-AS-000059, SRG-APP-000096-AS-000060, SRG-APP-000098-AS-000061, SRG-APP-000099-AS-000062, SRG-APP-000495-AS-000220, SRG-APP-000499-AS-000224, SRG-APP-000499-AS-000224, SRG-APP-000503-AS-000228, SRG-APP-000504-AS-000229, SRG-APP-000505-AS-000230, SRG-APP-000506-AS-000231, SRG-APP-000509-AS-000234, JBOS-AS-000080, SV-76721r1_rule | |
|
Rule
Encrypt JBoss Keystore Passwords
[ref] | Configure the application server to mask the java keystore password as per the
procedure described in section 11.13.3 -Password Vault System in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document. | Rationale: | Access to the JBoss Password Vault must be secured, and the password used to
access must be encrypted. There is a specific process used to generate the
encrypted password hash. This process must be followed in order to store the
password in an encrypted format.
The admin must utilize this process in order
to ensure the Keystore password is encrypted. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_encrypt_keystore_passwords | Identifiers and References | Identifiers:
CCE-80479-9 References:
CCI-000196, SRG-APP-000171-AS-000119, JBOS-AS-000300, SV-76779r1_rule | |
|
Rule
Configure Multi-Factor Authentication
[ref] | Configure the application server to authenticate privileged users via
multifactor/certificate-based authentication mechanisms when using network
access to the management interface. | Rationale: | Multifactor authentication creates a layered defense and makes it more
difficult for an unauthorized person to access the application server. If one
factor is compromised or broken, the attacker still has at least one more
barrier to breach before successfully breaking into the target. Unlike a simple
username/password scenario where the attacker could gain access by knowing both
the username and password without the user knowing his account was compromised,
multifactor authentication adds the requirement that the attacker must have
something from the user, such as a token, or to biometrically be the user.
Multifactor authentication is defined as: using two or more factors to achieve
authentication.
Factors include:
(i) something a user knows (e.g.,
password/PIN);
(ii) something a user has (e.g., cryptographic identification
device, token); or
(iii) something a user is (e.g., biometric). A CAC or PKI
Hardware Token meets this definition.
A privileged account is defined as an
information system account with authorizations of a privileged user. These
accounts would be capable of accessing the web management interface.
When
accessing the application server via a network connection, administrative access
to the application server must be PKI Hardware Token enabled or a DoD-approved
soft certificate. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_multifactor_authentication | Identifiers and References | Identifiers:
CCE-80474-0 References:
CCI-000765, SRG-APP-000149-AS-000102, JBOS-AS-000265, SV-76769r1_rule | |
|
Rule
Disable or Replace the JBoss Welcome Page
[ref] | Use the Management CLI script $JBOSS_HOME/bin/jboss-cli.sh to run the following
command. You may need to change the profile to modify a different managed domain
profile, or remove the /profile=default portion of the command for a
standalone server.
/profile=default/subsystem=web/virtual-server=default-host:writeattribute(name=enable-welcome-root,value.)
To configure
your web application to use the root context (/) as its URL address, modify the
applications jboss-web.xml, which is located in the applications META-INF/ or
WEB-INF/ directory. Replace its <context-root> directive with one that looks
like the following:
/ | Rationale: | The Welcome to JBoss web page provides a redirect to the JBoss admin console,
which, by default, runs on TCP 9990 as well as redirects to the Online User
Guide and Online User Groups hosted at locations on the Internet. The welcome
page is unnecessary and should be disabled or replaced with a valid web
page. | Severity: | low | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_disable_replace_welcome_page | Identifiers and References | Identifiers:
CCE-80470-8 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000245, SV-76761r1_rule | |
|
Rule
Enable HTTPS for Management Sessions
[ref] | Follow the specific instructions in the Red Hat Security Guide for EAP version
6.3 to configure the management console for HTTPS.
This involves the following steps.
1. Create a keystore in JKS format.
2. Ensure the management console binds to HTTPS.
3. Create a new Security Realm.
4. Configure Management Interface to use new security realm.
5. Configure the management console to use the keystore.
6. Restart the EAP server. | Rationale: | Types of management interfaces utilized by the JBoss EAP application server
include web-based HTTP interfaces as well as command line-based management
interfaces. In the event remote HTTP management is required, the access must be
via HTTPS.
This requirement is in conjunction with the requirement to isolate
all management access to a restricted network. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_secure_management_access | Identifiers and References | Identifiers:
CCE-80450-0 References:
CCI-000068, SRG-APP-000014-AS-000009, JBOS-AS-000010, SV-76563r1_rule | |
|
Rule
Remove Silent Authentication - Application Security Realm
[ref] | 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.
Remove the local element from the Application Realm.
For standalone servers, run
the following command:
/core-service=management/securityrealm=ApplicationRealm/authentication=local:remove
For managed domain installations,
run the following command:
/host=HOST_NAME/core-service=management/securityrealm=ApplicationRealm/authentication=local:remove | Rationale: | Silent Authentication is a configuration setting that allows local OS users
access to the JBoss server and a wide range of operations without specifically
authenticating on an individual user basis. By default $localuser is a
Superuser. This introduces an integrity and availability vulnerability and
violates best practice requirements regarding accountability. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_application_authentication | Identifiers and References | Identifiers:
CCE-80456-7 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000045, SV-76711r1_rule | |
|
Rule
Enable Logging to syslog
[ref] | 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.
Run
the command:
Standalone configuration:
ls /subsystem=logging/syslog-handler=
Domain configuration:
ls /profile=default/subsystem=logging/syslog-handler=
If no values are returned, this is a finding. | Rationale: | Information system logging capability is critical for accurate forensic
analysis. Log record content that may be necessary to satisfy the requirement of
this control includes, but is not limited to, time stamps, source and
destination IP addresses, user/process identifiers, event descriptions,
application-specific events, success/fail indications, filenames involved,
access control or flow control rules invoked.
Off-loading is a common process
in information systems with limited log storage capacity.
Centralized
management of log records provides for efficiency in maintenance and management
of records, as well as the backup and archiving of those records. Application
servers and their related components are required to off-load log records onto a
different system or media than the system being logged. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_syslog | Identifiers and References | Identifiers:
CCE-80488-0 References:
CCI-001851, SRG-APP-000358-AS-000064, JBOS-AS-000505, SV-76799r1_rule | |
|
Rule
JBoss Version Is Vendor Supported
[ref] | Obtain vendor support from Red Hat. | Rationale: | The JBoss product is available as Open Source; however, the Red Hat vendor
provides updates, patches and support for the JBoss product. It is imperative
that patches and updates be applied to JBoss in a timely manner as many attacks
against JBoss focus on unpatched systems. It is critical that support be
obtained and made available. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_vendor_supported | Identifiers and References | Identifiers:
CCE-80495-5 References:
CCI-002605, SRG-APP-000456-AS-000266, JBOS-AS-000680, SV-76815r1_rule | |
|
Rule
Use DoD Approved Certificates
[ref] | Configure the application server to use DoD- or CNSS-approved Class 3 or Class
4 PKI certificates. | Rationale: | Class 3 PKI certificates are used for servers and software signing rather than
for identifying individuals. Class 4 certificates are used for business-to-
business transactions. Utilizing unapproved certificates not issued or approved
by DoD or CNS creates an integrity risk. The application server must utilize
approved DoD or CNS Class 3 or Class 4 certificates for software signing and
business-to-business transactions. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_use_dod_approved_certs | Identifiers and References | Identifiers:
CCE-80497-1 References:
CCI-002450, SRG-APP-000514-AS-000137, JBOS-AS-000730, SV-76833r1_rule | |
|
Rule
Configure JBoss Log Off-Loading Frequency
[ref] | Configure the application server to off-load log records every seven days onto
a different system or media from the system being logged. | Rationale: | JBoss logs by default are written to the local file system. A centralized
logging solution like syslog should be used whenever possible; however, any log
data stored to the file system needs to be off-loaded. JBoss EAP does not
provide an automated backup capability. Instead, reliance is placed on OS or
third-party tools to back up or off-load the log files.
Protection of log data
includes assuring log data is not accidentally lost or deleted. Off-loading log
records to a different system or onto separate media from the system the
application server is actually running on helps to assure that, in the event of
a catastrophic system failure, the log records will be retained. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_offloading_max | Identifiers and References | Identifiers:
CCE-80463-3 References:
CCI-001348, SRG-APP-000125-AS-000084, JBOS-AS-000195, SV-76747r1_rule | |
|
Rule
Configure LDAP
[ref] | Follow steps in section 11.8 - Management Interface Security in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document.
1. Create an outbound connection to the LDAP server.
2. Create an LDAP-enabled security realm.
3. Reference the new security domain in the Management Interface. | Rationale: | To assure accountability and prevent unauthorized access, application server
users must be uniquely identified and authenticated. This is typically
accomplished via the use of a user store that is either local (OS-based) or
centralized (Active Directory/LDAP) in nature. It should be noted that JBoss
does not specifically mention Active Directory since AD is LDAP aware.
To
ensure accountability and prevent unauthorized access, the JBoss Server must be
configured to utilize a centralized authentication mechanism. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_ldap | Identifiers and References | Identifiers:
CCE-80473-2 References:
CCI-000764, SRG-APP-000148-AS-000101, JBOS-AS-000260, SV-76767r1_rule | |
|
Rule
Separate JBoss Management Network
[ref] | Refer to Section 4.9 of the JBoss EAP 6.3 Installation guide for detailed
instructions on how to start JBoss as a service.
Use the following command line
parameters to assign the management interface to a specific management network.
These command line flags must be added both when starting JBoss as a service and
when starting from the command line.
Substitute your actual network address for
the 10.x.x.x addresses provided as an example below.
For a standalone
configuration:
JBOSS_HOME/bin/standalone.sh -bmanagement=10.2.2.1 -b 10.1.1.1
JBOSS_HOME/bin/domain.sh -bmanagement=10.2.2.1 -b 10.1.1.1
If a management
network is not available, you may substitute localhost/127.0.0.1 for management
address. This will force you to manage the JBoss server from the local host. | Rationale: | JBoss provides multiple interfaces for accessing the system. By default,
these are called public and management. Allowing non-
management traffic to access the JBoss management interface increases the
chances of a security compromise. The JBoss server must be configured to bind
the management interface to a network that controls access. This is usually a
network that has been designated as a management network and has restricted
access. Similarly, the public interface must be bound to a network that is not
on the same segment as the management interface. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_management_network | Identifiers and References | Identifiers:
CCE-80476-5 References:
CCI-000778, SRG-APP-000158-AS-000108, JBOS-AS-000285, SV-76773r1_rule | |
|
Rule
Configure JBoss Application File Permissions
[ref] | Configure file permissions on the JBoss folder to protect from unauthorized
access. | Rationale: | The JBoss EAP Application Server is a Java-based AS. It is installed on the OS
file system and depends upon file system access controls to protect application
data at rest. The file permissions set on the JBoss EAP home folder must be
configured so as to limit access to only authorized people and processes. The
account used for operating the JBoss server and any designated administrative or
operational accounts are the only accounts that should have access.
When data
is written to digital media such as hard drives, mobile computers,
external/removable hard drives, personal digital assistants, flash/thumb drives,
etc., there is risk of data loss and data compromise. Steps must be taken to
ensure data stored on the device is protected. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_file_permissions | Identifiers and References | Identifiers:
CCE-80484-9 References:
CCI-001199, SRG-APP-000231-AS-000133, JBOS-AS-000400, SV-76789r1_rule | |
|
Rule
Log Application Deployments
[ref] | Launch the jboss-cli management interface substituting standalone or domain for
CONFIG based upon the server installation.
<JBOSS_HOME>/CONFIG/bin/jboss-cli
connect to the server and run the following command:
/core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true) | Rationale: | Without logging the enforcement of access restrictions against changes to the
application server configuration, it will be difficult to identify attempted
attacks, and a log trail will not be available for forensic investigation for
after-the-fact actions. Configuration changes may occur to any of the modules
within the application server through the management interface, but logging of
actions to the configuration of a module outside the application server is not
logged.
Enforcement actions are the methods or mechanisms used to prevent
unauthorized changes to configuration settings. Enforcement action methods may
be as simple as denying access to a file based on the application of file
permissions (access restriction). Log items may consist of lists of actions
blocked by access restrictions or changes identified after the fact. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_log_deployments | Identifiers and References | Identifiers:
CCE-80490-6 References:
CCI-001814, SRG-APP-000381-AS-000089, JBOS-AS-000550, SV-76803r1_rule | |
|
Rule
Configure JBoss Logging Level
[ref] | 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 to start the Command Line Interface (CLI).
Connect to the server and authenticate.
The PROFILE NAMEs included with a
Managed Domain JBoss configuration are:
default , full , full-ha , or ha
For a Managed Domain configuration, you must check
each profile name:
For each PROFILE NAME, run the command:
/profile=PROFILE NAME/subsystem=logging/root-logger=ROOT:write-attribute(name=level,value=INFO)
For a Standalone configuration:
/subsystem=logging/root-logger=ROOT:write-attribute(name=level,value=INFO) | Rationale: | 800 records less data and may result in an insufficient amount of information
being logged by the ROOT logger. This can result in failed forensic
investigations. The ROOT logger level must be INFO level or lower to provide
adequate log information. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_logging_level | Identifiers and References | Identifiers:
CCE-80461-7 References:
CCI-001487, SRG-APP-000100-AS-000063, JBOS-AS-000135, SV-76739r1_rule | |
|
Rule
Remove JBoss Group Acount Access
[ref] | Configure the application server so required users are individually
authenticated by creating individual user accounts. Utilize an LDAP server that
is configured according to DOD policy. | Rationale: | To assure individual accountability and prevent unauthorized access,
application server users (and any processes acting on behalf of application
server users) must be individually identified and authenticated.
A group
authenticator is a generic account used by multiple individuals. Use of a group
authenticator alone does not uniquely identify individual users.
Application
servers must ensure that individual users are authenticated prior to
authenticating via role or group authentication. This is to ensure that there is
non-repudiation for actions taken. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_remove_group_accounts | Identifiers and References | Identifiers:
CCE-80475-7 References:
CCI-000770, SRG-APP-000153-AS-000104, JBOS-AS-000275, SV-76771r1_rule | |
|
Rule
Configure JBoss Auditor Role
[ref] | Obtain documented approvals from ISSM, and assign the appropriate personnel
into the Auditor role. | Rationale: | The JBoss server must be configured to select which personnel are assigned the
role of selecting which loggable events are to be logged.
In JBoss, the role
designated for selecting auditable events is the Auditor role.
The
personnel or roles that can select loggable events are only the ISSM (or
individuals or roles appointed by the ISSM). | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_auditor_roles | Identifiers and References | Identifiers:
CCE-80460-9 References:
CCI-000171, SRG-APP-000090-AS-000051, JBOS-AS-000085, SV-76723r1_rule | |
|
Rule
Configure LDAP for Management Interfaces
[ref] | Follow steps in section 11.8 - Management Interface Security in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document.
1. Create an outbound connection to the LDAP server.
2. Create an LDAP-enabled security realm.
3. Reference the new security domain in the Management Interface. | Rationale: | JBoss EAP provides a security realm called ManagementRealm. By default, this
realm uses the mgmt-users.properties file for authentication. Using file-based
authentication does not allow the JBoss server to be in compliance with a wide
range of user management requirements such as automatic disabling of inactive
accounts as per DoD policy. To address this issue, the management interfaces
used to manage the JBoss server must be associated with a security realm that
provides centralized authentication management. Examples are AD or LDAP.
Management of user identifiers is not applicable to shared information system
accounts (e.g., guest and anonymous accounts). It is commonly the case that a
user account is the name of an information system account associated with an
individual. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_management_ldap | Identifiers and References | Identifiers:
CCE-80477-3 References:
CCI-000795, SRG-APP-000163-AS-000111, JBOS-AS-000290, SV-76775r1_rule | |
|
Rule
Remove Unnecessary Applications
[ref] | Identify, authorize, and document all applications that are deployed to the
application server. Remove unauthorized applications. | Rationale: | Extraneous services and applications running on an application server expands
the attack surface and increases risk to the application server. Securing any
server involves identifying and removing any unnecessary services and, in the
case of an application server, unnecessary and/or unapproved applications. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_remove_unnecessary_apps | Identifiers and References | Identifiers:
CCE-80471-6 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000250, SV-76763r1_rule | |
|
Rule
Restrict Access to the JBoss Keystore
[ref] | Configure the application server OS file permissions on the corresponding
private key to restrict access to authorized accounts or roles. | Rationale: | The cornerstone of the PKI is the private key used to encrypt or digitally sign
information.
If the private key is stolen, this will lead to the compromise of
the authentication and non-repudiation gained through PKI because the attacker
can use the private key to digitally sign documents and can pretend to be the
authorized user.
Both the holders of a digital certificate and the issuing
authority must protect the computers, storage devices, or whatever they use to
keep the private keys. Java-based application servers utilize the Java keystore,
which provides storage for cryptographic keys and certificates. The keystore is
usually maintained in a file stored on the file system. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_secure_keystore_permissions | Identifiers and References | Identifiers:
CCE-80482-3 References:
CCI-000186, SRG-APP-000176-AS-000125, JBOS-AS-000320, SV-76785r1_rule | |
|
Rule
Use Separate Management and Application Networks
[ref] | Start the application server with a -bmanagement and a -b flag so that admin
management functionality and hosted applications are separated.
Refer to
section 4.9 in the JBoss EAP 6.3 Installation Guide for specific instructions on
how to start the JBoss server as a service. | Rationale: | The application server consists of the management interface and hosted
applications. By separating the management interface from hosted applications,
the user must authenticate as a privileged user to the management interface
before being presented with management functionality. This prevents non-
privileged users from having visibility to functions not available to the user.
By limiting visibility, a compromised non-privileged account does not offer
information to the attacker or functionality and information needed to further
the attack on the application server.
JBoss is designed to operate with
separate application and management interfaces.
The JBoss server is started via
a script. To start the JBoss server in domain mode, the admin will execute the
/bin/domain.sh or domain.bat script.
To start the JBoss server in standalone
mode, the admin will execute /bin/standalone.bat or standalone.sh.
Command line
flags are used to specify which network address is used for management and which
address is used for public/application access. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_service_separate_networks | Identifiers and References | Identifiers:
CCE-80483-1 References:
CCI-001082, SRG-APP-000211-AS-000146, JBOS-AS-000355, SV-76787r1_rule | |
|
Rule
Use Approved DoD Certificate Authorities
[ref] | Locate the cacerts file for the JVM. This can be done using the appropriate
find command for the OS and change to the directory where the cacerts file is
located.
Remove the certificates that have a CA that is non-DoD approved, and
import DoD CA-approved certificates. | Rationale: | Untrusted Certificate Authorities (CA) can issue certificates, but they may be
issued by organizations or individuals that seek to compromise DoD systems or by
organizations with insufficient security controls. If the CA used for verifying
the certificate is not a DoD-approved CA, trust of this CA has not been
established.
The DoD will only accept PKI certificates obtained from a DoD-
approved internal or external certificate authority. Reliance on CAs for the
establishment of secure sessions includes, for example, the use of SSL/TLS
certificates. The application server must only allow the use of DoD PKI-
established certificate authorities for verification. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_use_approved_ca_cert | Identifiers and References | Identifiers:
CCE-80491-4 References:
CCI-002470, SRG-APP-000427-AS-000264, JBOS-AS-000625, SV-76807r1_rule | |
|
Rule
Configure JBoss Management and Application Ports
[ref] | Open the EAP web console by pointing a web browser to HTTPS://Servername:9990
Log on to the admin console using admin credentials
Select the
Configuration tab
Expand the General Configuration sub
system by clicking on the +
Select Socket Binding
Select the
View option next to standard-sockets
Select
Inbound
Select the port that needs to be reconfigured and select
Edit . | Rationale: | Some networking protocols may not meet organizational security requirements to
protect data and components.
Application servers natively host a number of
various features, such as management interfaces, httpd servers and message
queues. These features all run on TCPIP ports. This creates the potential that
the vendor may choose to utilize port numbers or network services that have been
deemed unusable by the organization. The application server must have the
capability to both reconfigure and disable the assigned ports without adversely
impacting application server operation capabilities. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_ports | Identifiers and References | Identifiers:
CCE-80472-4 References:
CCI-000382, SRG-APP-000142-AS-000014, JBOS-AS-000255, SV-76765r1_rule | |
|
Rule
Configure Host Access Restrictions for Applications
[ref] | Configure the Java security manager to enforce access restrictions to the host
system resources in accordance with application design and resource
requirements. | Rationale: | The Java Security Manager is a java class that manages the external boundary of
the Java Virtual Machine (JVM) sandbox, controlling how code executing within
the JVM can interact with resources outside the JVM.
The JVM requires a
security policy in order to restrict application access. A properly configured
security policy will define what rights the application has to the underlying
system. For example, rights to make changes to files on the host system or to
initiate network sockets in order to connect to another system. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_host_access_restrictions | Identifiers and References | Identifiers:
CCE-80452-6 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000025, SV-76707r1_rule | |
|
Rule
Configure JBoss User Roles
[ref] | Document approved management users and their roles. Configure the application
server to use RBAC and ensure users are placed into the appropriate roles. | Rationale: | Security realms are a series of mappings between users and passwords and users
and roles. There are 2 JBoss security realms provided by default; they are
management realm and application realm .
Management realm
stores authentication information for the management API, which provides
functionality for the web-based management console and the management command
line interface (CLI).
mgmt-groups.properties stores user to group mapping for
the ManagementRealm but only when role-based access controls (RBAC) is enabled.
If management users are not in the appropriate role, unauthorized access to
JBoss resources can occur. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_user_roles | Identifiers and References | Identifiers:
CCE-80455-9 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000040, SV-76709r1_rule | |
|
Rule
Remove JBoss Quickstarts
[ref] | Delete the QuickStarts folder. | Rationale: | JBoss QuickStarts are demo applications that can be deployed quickly. Demo
applications are not written with security in mind and often open new attack
vectors. QuickStarts must be removed. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_remove_quickstarts | Identifiers and References | Identifiers:
CCE-80468-2 References:
CCI-000381, SRG-APP-000141-AS-000095, JBOS-AS-000235, SV-76757r1_rule | |
|
Rule
Remove Silent Authentication - Management Security Realm
[ref] | 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.
Remove the local element from the Management Realm.
For standalone servers run
the following command:
/core-service=management/securityrealm=ManagementRealm/authentication=local:remove
For managed domain installations run the following command:
/host=HOST_NAME/core-service=management/securityrealm=ManagementRealm/authentication=local:remove | Rationale: | Silent Authentication is a configuration setting that allows local OS users
access to the JBoss server and a wide range of operations without specifically
authenticating on an individual user basis. By default $localuser is a
Superuser. This introduces an integrity and availability vulnerability and
violates best practice requirements regarding accountability. | Severity: | high | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_management_authentication | Identifiers and References | Identifiers:
CCE-80457-5 References:
CCI-000213, SRG-APP-000033-AS-000024, JBOS-AS-000050, SV-76713r1_rule | |
|
Rule
Use Secure Standard LDAP Port
[ref] | Follow steps in section 11.8 - Management Interface Security in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document.
1. Create an outbound connection to the LDAP server.
2. Create an LDAP-enabled security realm.
3. Reference the new security domain in the Management Interface. | Rationale: | Passwords need to be protected at all times, and encryption is the standard
method for protecting passwords during transmission.
Application servers have
the capability to utilize LDAP directories for authentication. If LDAP
connections are not protected during transmission, sensitive authentication
credentials can be stolen. When the application server utilizes LDAP, the LDAP
traffic must be encrypted. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_use_secure_ldap_port | Identifiers and References | Identifiers:
CCE-80481-5 References:
CCI-000197, SRG-APP-000172-AS-000121, JBOS-AS-000310, SV-76783r1_rule | |
|
Rule
Audit JBoss Privileged Actions
[ref] | Launch the jboss-cli management interface substituting standalone or domain for
CONFIG based upon the server installation.
<JBOSS_HOME>/CONFIG//bin/jboss-cli
connect to the server and run the following command:
/core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true) | Rationale: | In order to be able to provide a forensic history of activity, the application
server must ensure users who are granted a privileged role or those who utilize
a separate distinct account when accessing privileged functions or data have
their actions logged.
If privileged activity is not logged, no forensic logs
can be used to establish accountability for privileged actions that occur on the
system. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_audit_privileged_actions | Identifiers and References | Identifiers:
CCE-80487-2 References:
CCI-002234, SRG-APP-000343-AS-000030, JBOS-AS-000480, SV-76797r1_rule | |
|
Rule
Configure Load Balancing (LB) or High Availability (HA)
[ref] | Configure the application server to provide LB or HA services for the hosted
application. | Rationale: | A MAC I system is a system that handles data vital to the organization's
operational readiness or effectiveness of deployed or contingency forces. A MAC
I system must maintain the highest level of integrity and availability. By HA
clustering the application server, the hosted application and data are given a
platform that is load-balanced and provides high availability. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_ha_lb | Identifiers and References | Identifiers:
CCE-80492-2 References:
CCI-002385, SRG-APP-000435-AS-000069, JBOS-AS-000640, SV-76809r1_rule | |
|
Rule
Enable the JBoss Keystore
[ref] | Configure the application server to use the java keystore and JBoss vault as
per section 11.13.1 -Password Vault System in the
JBoss_Enterprise_Application_Platform-6.3
-Administration_and_Configuration_Guide-en-US document.
1. Create a java keystore.
2. Mask the keystore password and initialize the password vault.
3. Configure JBoss to use the password vault. | Rationale: | JBoss EAP 6 has a Password Vault to encrypt sensitive strings, store them in an
encrypted keystore, and decrypt them for applications and verification systems.
Plain-text configuration files, such as XML deployment descriptors, need to
specify passwords and other sensitive information. Use the JBoss EAP Password
Vault to securely store sensitive strings in plain-text files. | Severity: | medium | Rule ID: | xccdf_org.ssgproject.content_rule_jboss_eap_configure_keystore | Identifiers and References | Identifiers:
CCE-80478-1 References:
CCI-000196, SRG-APP-000171-AS-000119, JBOS-AS-000295, SV-76777r1_rule | |
|