Guide to the Secure Configuration of Java Runtime Environment

with profile Java Runtime Environment (JRE) STIG
The Java Runtime Environment (JRE) is a bundle developed and offered by Oracle Corporation which includes the Java Virtual Machine (JVM), class libraries, and other components necessary to run Java applications and applets. Certain default settings within the JRE pose a security risk so it is necessary to deploy system wide properties to ensure a higher degree of security when utilizing the JRE. The IBM Corporation also develops and bundles the Java Runtime Environment (JRE) as well as Red Hat with OpenJDK.
The SCAP Security Guide Project
https://www.open-scap.org/security-policies/scap-security-guide
This guide presents a catalog of security-relevant configuration settings for Java Runtime Environment. It is a rendering of content structured in the eXtensible Configuration Checklist Description Format (XCCDF) in order to support security automation. The SCAP content is is available in the scap-security-guide package which is developed at https://www.open-scap.org/security-policies/scap-security-guide.

Providing system administrators with such guidance informs them how to securely configure systems under their control in a variety of network roles. Policy makers and baseline creators can use this catalog of settings, with its associated references to higher-level security control catalogs, in order to assist them in security baseline creation. This guide is a catalog, not a checklist, and satisfaction of every item is not likely to be possible or sensible in many operational scenarios. However, the XCCDF format enables granular selection and adjustment of settings, and their association with OVAL and OCIL content provides an automated checking capability. Transformations of this document, and its associated automated checking content, are capable of providing baselines that meet a diverse set of policy objectives. Some example XCCDF Profiles, which are selections of items that form checklists and can be used as baselines, are available with this guide. They can be processed, in an automated fashion, with tools that support the Security Content Automation Protocol (SCAP). The DISA STIG for Java Runtime Environment, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
Do not attempt to implement any of the settings in this guide without first testing them in a non-operational environment. The creators of this guidance assume no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic.

Profile Information

Profile TitleJava Runtime Environment (JRE) STIG
Profile IDxccdf_org.ssgproject.content_profile_stig

CPE Platforms

  • cpe:/a:sun:jre:
  • cpe:/a:ibm:jre:
  • cpe:/a:redhat:openjdk:

Revision History

Current version: 0.1.63

  • draft (as of 2022-07-29)

Table of Contents

  1. Java
    1. Configure the exception.sites File
    2. Configure the deployment.config File

Checklist

Group   Guide to the Secure Configuration of Java Runtime Environment   Group contains 3 groups and 26 rules
Group   Java   Group contains 2 groups and 26 rules
[ref]   Java is a general-purpose computer programming language. It is intended to let application developers "write once, run anywhere." Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture. As such, the Java runtime environment (JRE) is required to be installed so that Java applications can run. This section provides settings for configuring Java policies to meet compliance settings for Java running on Red Hat Enterprise Linux systems.

Group   Configure the exception.sites File   Group contains 2 rules
[ref]   Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. The exception.sites file is used for ensuring that authorized software is allowed to be executed. To ensure that the Java /etc/.java/deployment/deployment.properties file is configured correctly, deployment.user.security.exception.sites must be configured to point to a valid exception.sites file.

Rule   The Java exception.sites File Exists   [ref]

By default, no exception.sites file exists which means that there is no prevention of unauthorized software. The exception.sites file is a text file containing single-line URLs for accepted risk sites. If the Java accepted sites list file does not exist, it can be added by running: 
$ sudo mkdir -p -m 755 /etc/.java/deployment
$ sudo touch /etc/.java/deployment/exception.sites
$ sudo chmod 644 /etc/.java/deployment/exception.sites
Rationale:
Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_accepted_sites_exists
Identifiers and References

References:  CCI-001774, CM-7(5)(b), SRG-APP-000386, JRE8-UX-000130


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000130
  - NIST-800-53-CM-7(5)(b)
  - configure_strategy
  - java_jre_accepted_sites_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Ensure Java exception.sites File Exists
  file:
    path: /etc/.java/deployment/exception.sites
    state: touch
    mode: '0644'
  tags:
  - DISA-STIG-JRE8-UX-000130
  - NIST-800-53-CM-7(5)(b)
  - configure_strategy
  - java_jre_accepted_sites_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_FILE="/etc/.java/deployment/exception.sites"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_FILE} ]; then
  touch ${JAVA_FILE} && chmod 644 ${JAVA_FILE}
fi

chmod 644 ${JAVA_FILE}

Rule   Configure the Path to the exception.sites File   [ref]

To ensure that the accepted sites list file is set in /etc/.java/deployment/deployment.properties, add or modify deployment.user.security.exception.sites to equal /etc/.java/deployment/exception.sites.
Rationale:
Without a proper path for the accepted sites list file, unauthorized software programs are able to be executed. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_accepted_sites_properties
Identifiers and References

References:  CCI-001774, CM-7(5)(b), SRG-APP-000386, JRE8-UX-000120


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000120
  - NIST-800-53-CM-7(5)(b)
  - configure_strategy
  - java_jre_accepted_sites_properties
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Configure the Path to the exception.sites File
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.user.security.exception.sites=.*
    line: deployment.user.security.exception.sites=/etc/.java/deployment/exception.sites
  tags:
  - DISA-STIG-JRE8-UX-000120
  - NIST-800-53-CM-7(5)(b)
  - configure_strategy
  - java_jre_accepted_sites_properties
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

JAVA_FILE="/etc/.java/deployment/exception.sites"

grep -q "^deployment.user.security.exception.sites=.*" ${JAVA_PROPERTIES} && \
sed -i "s;deployment.user.security.exception.sites=.*;deployment.user.security.exception.sites=${JAVA_FILE};g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.user.security.exception.sites=${JAVA_FILE}" >> ${JAVA_PROPERTIES}
fi
Group   Configure the deployment.config File   Group contains 3 rules
[ref]   The deployment.config file if used for specifying the System-level deployment.properties file. The System-level configuration for Java is configured in /etc/.java/deployment. By default, no deployment.config file exists. To ensure that the Java /etc/.java/deployment/deployment.config file is configured correctly, deployment.system.config and deployment.system.config.mandatory need to be set correctly.

Rule   The Java deployment.config File Exists   [ref]

If the Java deployment configuration file does not exist, it can be added by running: 
$ sudo mkdir -p -m 755 /etc/.java/deployment
$ sudo touch /etc/.java/deployment/deployment.config
$ sudo chmod 644 /etc/.java/deployment/deployment.config
Rationale:
By default no deployment.config file exists; thus, no system-wide deployment.properties file exists. The file must be created. The deployment.config file is used for specifying the location and execution of system-level properties for the Java Runtime Environment. Without the deployment.config file, setting particular options for the Java control panel is not possible.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_deployment_config_exists
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000010


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000010
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Ensure Java Config File Exists
  file:
    path: /etc/.java/deployment/deployment.config
    state: touch
    mode: '0644'
  tags:
  - DISA-STIG-JRE8-UX-000010
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_CONFIG="/etc/.java/deployment/deployment.config"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_CONFIG} ]; then
  touch ${JAVA_CONFIG} && chmod 644 ${JAVA_CONFIG}
fi

chmod 644 ${JAVA_CONFIG}

Rule   Configure The Java Deployment Mandatory Setting   [ref]

To configure the Java mandatory deployment setting, add or modify deployment.system.config.mandatory to equal true in /etc/.java/deployment/deployment.config.
Rationale:
Without a proper path for the properties file, deployment would not be possible. If the path specified does not lead to a properties file, the value of the deployment.system.config.mandatory key determines how to handle the situation. If the value of this key is true, JRE will not allow Java applications to run if the path to the properties file is invalid.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_deployment_config_mandatory
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000020


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000020
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_mandatory
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Configure The Java Deployment Mandatory Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.config
    regexp: ^\s*#?\s*deployment.system.config.mandatory=.*
    line: deployment.system.config.mandatory=true
  tags:
  - DISA-STIG-JRE8-UX-000020
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_mandatory
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_CONFIG="/etc/.java/deployment/deployment.config"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_CONFIG} ]; then
  touch ${JAVA_CONFIG} && chmod 644 ${JAVA_CONFIG}
fi

grep -q "^deployment.system.config.mandatory=.*" ${JAVA_CONFIG} && \
sed -i "s/deployment.system.config.mandatory=.*/deployment.system.config.mandatory=true/g" ${JAVA_CONFIG}
if ! [ $? -eq 0 ] ; then
  echo "deployment.system.config.mandatory=true" >> ${JAVA_CONFIG}
fi

Rule   Configure the Path to the deployment.properties File   [ref]

To ensure that the Java properties file is set in /etc/.java/deployment/deployment.config, add or modify deployment.system.config to equal /etc/.java/deployment/deployment.properties.
Rationale:
Without a proper path for the properties file, deployment would not be possible. If the path specified does not lead to a properties file, the value of the deployment.system.config.mandatory key determines how to handle the situation. If the value of this key is true, JRE will not allow Java applications to run if the path to the properties file is invalid.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_deployment_config_properties
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000020


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000020
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_properties
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Configure the Path to the deployment.properties File
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.config
    regexp: ^\s*#?\s*deployment.system.config=.*
    line: deployment.system.config=file:///etc/.java/deployment/deployment.properties
  tags:
  - DISA-STIG-JRE8-UX-000020
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_config_properties
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_CONFIG="/etc/.java/deployment/deployment.config"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_CONFIG} ]; then
  touch ${JAVA_CONFIG} && chmod 644 ${JAVA_CONFIG}
fi

JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"

grep -q "^deployment.system.config=.*" ${JAVA_CONFIG} && \
sed -i "s;deployment.system.config=.*;deployment.system.config=file:\/\/${JAVA_PROPERTIES};g" ${JAVA_CONFIG}
if ! [ $? -eq 0 ] ; then
  echo "deployment.system.config=file://${JAVA_PROPERTIES}" >> ${JAVA_CONFIG}
fi

Rule   Prevent the Download of Prohibited Mobile Code   [ref]

To ensure that Java prevents the download of prohibited mobile code, set deployment.security.blacklist.check to equal true in /etc/.java/deployment/deployment.properties.
Rationale:
Mobile code has the potential to cause damage to information systems within an organization if used maliciously. Therefore it is important to allow vetted mobile code and prevent potentially malicious execution of mobile code. Mobile code has the potential to cause damage to information systems within an organization if used maliciously. Therefore it is important to allow vetted mobile code and prevent potentially malicious execution of mobile code.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_blacklist_check
Identifiers and References

References:  CCI-001169, SC-18(3), SRG-APP-000209, JRE8-UX-000110


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000110
  - NIST-800-53-SC-18(3)
  - configure_strategy
  - java_jre_blacklist_check
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Prevent the Download of Prohibited Mobile Code
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.blacklist.check=.*
    line: deployment.security.blacklist.check=true
  tags:
  - DISA-STIG-JRE8-UX-000110
  - NIST-800-53-SC-18(3)
  - configure_strategy
  - java_jre_blacklist_check
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.blacklist.check=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.blacklist.check=.*/deployment.security.blacklist.check=true/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.blacklist.check=true" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Prohibited Mobile Code Setting   [ref]

To ensure that users cannot change the download of prohibited mobile code setting, add deployment.security.blacklist.check.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Mobile code has the potential to cause damage to information systems within an organization if used maliciously. Therefore, it is important to allow vetted mobile code and prevent potentially malicious execution of mobile code. As such, ensuring users cannot change the permission settings which control the downloading of prohibited mobile code contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_blacklist_check_locked
Identifiers and References

References:  CCI-001169, SC-18(3), SRG-APP-000209, JRE8-UX-000110


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000110
  - NIST-800-53-SC-18(3)
  - configure_strategy
  - java_jre_blacklist_check_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Prohibited Mobile Code Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.blacklist.check.locked
    line: deployment.security.blacklist.check.locked
  tags:
  - DISA-STIG-JRE8-UX-000110
  - NIST-800-53-SC-18(3)
  - configure_strategy
  - java_jre_blacklist_check_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.webjava.enabled.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.webjava.enabled.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Ensure yum Removes Previous Package Versions   [ref]

yum should be configured to remove previous versions of Java after new versions have been installed. To configure yum to remove the previous versions of Java after updating, set the clean_requirements_on_remove to 1 in /etc/yum.conf.
Rationale:
Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some adversaries.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_clean_previous_version
Identifiers and References

References:  CCI-002617, SI-2(6), SRG-APP-000454, JRE8-UX-000190


Complexity:low
Disruption:low
Strategy:restrict
- name: Ensure YUM Removes Previous Package Versions
  lineinfile:
    dest: /etc/yum.conf
    regexp: ^#?clean_requirements_on_remove
    line: clean_requirements_on_remove=1
    insertafter: \[main\]
    create: true
  tags:
  - DISA-STIG-JRE8-UX-000190
  - NIST-800-53-SI-2(6)
  - java_jre_clean_previous_version
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - restrict_strategy



if grep --silent ^clean_requirements_on_remove /etc/yum.conf ; then
        sed -i "s/^clean_requirements_on_remove.*/clean_requirements_on_remove=1/g" /etc/yum.conf
else
        echo -e "\n# Set clean_requirements_on_remove to 1 per security requirements" >> /etc/yum.conf
        echo "clean_requirements_on_remove=1" >> /etc/yum.conf
fi

Rule   The Java deployment.properties File Exists   [ref]

If the Java deployment properties file does not exist, it can be added by running: 
$ sudo mkdir -p -m 755 /etc/.java/deployment
$ sudo touch /etc/.java/deployment/deployment.properties
$ sudo chmod 644 /etc/.java/deployment/deployment.properties
Rationale:
Each option in the Java control panel is represented by property keys. These keys adjust the options in the Java control panel based on the value assigned to that key. By default no deployment.properties file exists; thus, no system-wide deployment exists. Without the deployment.properties file, setting particular options for the Java control panel is impossible.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_deployment_properties_exists
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000030


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000030
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_properties_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Ensure Java deployment.properties File Exists
  file:
    path: /etc/.java/deployment/deployment.properties
    state: touch
    mode: '0644'
  tags:
  - DISA-STIG-JRE8-UX-000030
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - java_jre_deployment_properties_exists
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

chmod 644 ${JAVA_PROPERTIES}

Rule   Disable Execution of Signed Java Applets From Untrusted Sources Setting   [ref]

To ensure that Java cannot execute from untrusted sources, set deployment.security.askgrantdialog.notinca to equal false in /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of signed Java applets from un-trusted sources may result in acquiring malware, and risks system modification, invasion of privacy, or denial of service. Block users from granting permissions to certificates that are not issued by a CA in the Root/JSSE CA certificate store.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_disable_untrusted_sources
Identifiers and References

References:  CCI-001695, SC-18 (3), SRG-APP-000112, JRE8-UX-000080


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000080
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_disable_untrusted_sources
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable Execution of Signed Java Applets From Untrusted Sources Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.askgrantdialog.notinca=.*
    line: deployment.security.askgrantdialog.notinca=false
  tags:
  - DISA-STIG-JRE8-UX-000080
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_disable_untrusted_sources
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.askgrantdialog.notinca=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.askgrantdialog.notinca=.*/deployment.security.askgrantdialog.notinca=false/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.askgrantdialog.notinca=false" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Disabling Untrusted Sources Setting   [ref]

To ensure that users cannot change the untrusted sources settings, add deployment.security.askgrantdialog.notinca.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of signed Java applets from un-trusted sources may result in malware running on the system, and risks system modification, invasion of privacy, or denial of service. As such, ensuring users cannot change the permission settings which control the execution of signed Java applets contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_disable_untrusted_sources_locked
Identifiers and References

References:  CCI-001695, SC-18 (3), SRG-APP-000112, JRE8-UX-000080


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000080
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_disable_untrusted_sources_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Disabling Untrusted Sources Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.askgrantdialog.notinca.locked
    line: deployment.security.askgrantdialog.notinca.locked
  tags:
  - DISA-STIG-JRE8-UX-000080
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_disable_untrusted_sources_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.askgrantdialog.notinca.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.askgrantdialog.notinca.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Enable Java Web Start Applications to Run   [ref]

To ensure that Java allows applets or Java Web Start (JWS) applications to run, set deployment.webjava.enabled to equal true in /etc/.java/deployment/deployment.properties.
Rationale:
Due to the popularity of Java Web Start (JWS) applications, denying these applications could have a negative impact to the user experience. Whitelisting, blacklisting, and signing of applications help mitigate the risk of running JWS applications.
Severity: 
high
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_enable_jws
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000070


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000070
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_enable_jws
  - low_complexity
  - low_disruption
  - no_reboot_needed

- name: Enable Java Web Start Applications to Run
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.webjava.enabled=.*
    line: deployment.webjava.enabled=true
  tags:
  - DISA-STIG-JRE8-UX-000070
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_enable_jws
  - low_complexity
  - low_disruption
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.webjava.enabled=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.webjava.enabled=.*/deployment.webjava.enabled=true/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.webjava.enabled=true" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Java Web Start Application Setting   [ref]

To ensure that users cannot change the Java Web Start (JWS) application setting, add deployment.webjava.enabled.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Due to the popularity of Java Web Start (JWS) applications, denying these applications could have a negative impact to the user experience. Whitelisting, blacklisting, and signing of applications help mitigate the risk of running JWS applications.
Severity: 
high
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_enable_jws_locked
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000070


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000070
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_enable_jws_locked
  - low_complexity
  - low_disruption
  - no_reboot_needed

- name: Disable User Access to Java Web Start Application Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.webjava.enabled.locked
    line: deployment.webjava.enabled.locked
  tags:
  - DISA-STIG-JRE8-UX-000070
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_enable_jws_locked
  - low_complexity
  - low_disruption
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.webjava.enabled.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.webjava.enabled.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Prompt User Prior to Executing Mobile Code   [ref]

To ensure that Java prevents mobile code from executing without prompting the user, set deployment.insecure.jres to equal PROMPT in /etc/.java/deployment/deployment.properties.
Rationale:
Mobile code has the potential to cause damage to information systems within an organization if used maliciously. It can execute without explicit action from, or notification to, a user. Requiring Java to enforce prompting the user prior to executing mobile code will strenghten the security posture of the system.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_insecure_prompt
Identifiers and References

References:  CCI-002460, SC-18(4), SRG-APP-000488, JRE8-UX-000170


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000170
  - NIST-800-53-SC-18(4)
  - configure_strategy
  - java_jre_insecure_prompt
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Prompt User Prior to Executing Mobile Code
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.insecure.jres=.*
    line: deployment.insecure.jres=PROMPT
  tags:
  - DISA-STIG-JRE8-UX-000170
  - NIST-800-53-SC-18(4)
  - configure_strategy
  - java_jre_insecure_prompt
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.insecure.jres=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.insecure.jres=.*/deployment.insecure.jres=PROMPT/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.insecure.jres=PROMPT" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Insecure Prompt of Mobile Code Setting   [ref]

To ensure that users cannot change the mobile code setting for insecure prompts, add deployment.insecure.jres.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Mobile code has the potential to cause damage to information systems within an organization if used maliciously. It can execute without explicit action from, or notification to, a user. Requiring Java to enforce prompting the user prior to executing mobile code will strengthen the security posture of the system. As such, ensuring users cannot change the permission settings which control the insecure prompts for mobile code execution contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_insecure_prompt_locked
Identifiers and References

References:  CCI-002460, SC-18(4), SRG-APP-000488, JRE8-UX-000170


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000170
  - NIST-800-53-SC-18(4)
  - configure_strategy
  - java_jre_insecure_prompt_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Insecure Prompt of Mobile Code Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.insecure.jres.locked
    line: deployment.insecure.jres.locked
  tags:
  - DISA-STIG-JRE8-UX-000170
  - NIST-800-53-SC-18(4)
  - configure_strategy
  - java_jre_insecure_prompt_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.insecure.jres.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.insecure.jres.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Lock Execution of Signed Java Applets From Untrusted Sources Setting   [ref]

To ensure that Java cannot execute from untrusted sources, set deployment.security.askgrantdialog.show to equal false in /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of signed Java applets from un-trusted sources may result in acquiring malware, and risks system modification, invasion of privacy, or denial of service. Block users from granting permissions to applets and JWS applications.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_lock_untrusted_sources
Identifiers and References

References:  CCI-001695, SC-18 (3), SRG-APP-000112, JRE8-UX-000090


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000090
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_lock_untrusted_sources
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Lock Execution of Signed Java Applets From Untrusted Sources Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.askgrantdialog.show=.*
    line: deployment.security.askgrantdialog.show=false
  tags:
  - DISA-STIG-JRE8-UX-000090
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_lock_untrusted_sources
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.askgrantdialog.show=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.askgrantdialog.show=.*/deployment.security.askgrantdialog.show=false/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.askgrantdialog.show=false" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Locking Untrusted Sources Setting   [ref]

To ensure that users cannot change the untrusted sources settings, add deployment.security.askgrantdialog.show.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of signed Java applets from un-trusted sources may result in malware running on the system, and risks system modification, invasion of privacy, or denial of service. As such, ensuring users cannot change the permission settings which control the execution of signed Java applets contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_lock_untrusted_sources_locked
Identifiers and References

References:  CCI-001695, SC-18 (3), SRG-APP-000112, JRE8-UX-000090


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000090
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_lock_untrusted_sources_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Locking Untrusted Sources Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.askgrantdialog.show.locked
    line: deployment.security.askgrantdialog.show.locked
  tags:
  - DISA-STIG-JRE8-UX-000090
  - NIST-800-53-SC-18 (3)
  - configure_strategy
  - java_jre_lock_untrusted_sources_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.askgrantdialog.show.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.askgrantdialog.show.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Enable Revocation Checks for Publisher Certificates   [ref]

To ensure that certificate revocation checks are enabled, set deployment.security.revocation.check to equal ALL_CERTIFICATES in /etc/.java/deployment/deployment.properties.
Rationale:
Certificates may be revoked due to improper issuance, compromise of the certificate, and failure to adhere to policy. Therefore, any certificate found on a CRL should not be trusted. Permitting execution of an applet published with a revoked certificate may result in spoofing, malware, system modification, invasion of privacy, and denial of service.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_security_revocation_check
Identifiers and References

References:  CCI-001991, IA-5(2)(d), SRG-APP-000401, JRE8-UX-000160


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000160
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_security_revocation_check
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Enable Revocation Checks for Publisher Certificates
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.revocation.check=.*
    line: deployment.security.revocation.check=ALL_CERTIFICATES
  tags:
  - DISA-STIG-JRE8-UX-000160
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_security_revocation_check
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.revocation.check=.*" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.revocation.check=.*/deployment.security.revocation.check=ALL_CERTIFICATES/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.revocation.check=ALL_CERTIFICATES" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Revocation Check Settings   [ref]

To ensure that users cannot change certificate revocation check settings, add deployment.security.revocation.check.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of an applet published with a revoked certificate may result in spoofing, malware, system modification, invasion of privacy, and denial of service. As such, ensuring users cannot change settings contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_security_revocation_check_locked
Identifiers and References

References:  CCI-001991, IA-5(2)(d), SRG-APP-000401, JRE8-UX-000160


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000160
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_security_revocation_check_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Revocation Check Settings
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.revocation.check.locked
    line: deployment.security.revocation.check.locked
  tags:
  - DISA-STIG-JRE8-UX-000160
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_security_revocation_check_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.revocation.check.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.revocation.check.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Disable Execution of Unsigned Applications   [ref]

To ensure that Java does not allow unsigned applications to run, set deployment.security.level to equal VERY_HIGH in /etc/.java/deployment/deployment.properties.
Rationale:
Unsigned applications could perform numerous types of attacks on a system. Applications that are signed with a valid certificate and include the permissions attribute in the manifest for the main JAR file are allowed to run with security prompts. All other applications are blocked.
Severity: 
high
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_unsigned_applications
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000060


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000060
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_unsigned_applications
  - low_complexity
  - low_disruption
  - no_reboot_needed

- name: Disable Execution of Unsigned Applications
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.level=.*
    line: deployment.security.level=VERY_HIGH
  tags:
  - DISA-STIG-JRE8-UX-000060
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_unsigned_applications
  - low_complexity
  - low_disruption
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.level=.*$" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.level=.*/deployment.security.level=VERY_HIGH/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.level=VERY_HIGH" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Unsigned Applications Setting   [ref]

To ensure that users cannot change the unsigned applications setting, add deployment.security.level.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Unsigned applications could perform numerous types of attacks on a system. As such, ensuring users cannot change the permission settings which control the execution of unsigned Java applications contributes to a more consistent security profile.
Severity: 
high
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_unsigned_applications_locked
Identifiers and References

References:  CCI-000366, CM-6(b), SRG-APP-000516, JRE8-UX-000060


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000060
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_unsigned_applications_locked
  - low_complexity
  - low_disruption
  - no_reboot_needed

- name: Disable User Access to Unsigned Applications Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.level.locked
    line: deployment.security.level.locked
  tags:
  - DISA-STIG-JRE8-UX-000060
  - NIST-800-53-CM-6(b)
  - configure_strategy
  - high_severity
  - java_jre_unsigned_applications_locked
  - low_complexity
  - low_disruption
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.level.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.level.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Ensure Java Patches Installed   [ref]

If the system is joined to the Red Hat Network, a Red Hat Satellite Server, or a yum server, run the following command to install updates: 
$ sudo yum update
If the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded and installed using rpm.

NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates.
Rationale:
Running an older version of the JRE can introduce security vulnerabilities to the system.
Severity: 
low
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_updated
Identifiers and References

References:  CCI-002605, SI-2(c), SRG-APP-000456, JRE8-UX-000180


Complexity:low
Disruption:high
Reboot:true
Strategy:patch
- name: Security patches are up to date
  package:
    name: '*'
    state: latest
  tags:
  - DISA-STIG-JRE8-UX-000180
  - NIST-800-53-SI-2(c)
  - high_disruption
  - java_jre_updated
  - low_complexity
  - low_severity
  - patch_strategy
  - reboot_required
  - skip_ansible_lint




yum -y update

Rule   Enable Use of Certificate Revocation Lists   [ref]

To ensure that certificate revocation lists are enabled, set deployment.security.validation.crl to equal true in /etc/.java/deployment/deployment.properties.
Rationale:
A certificate revocation list is a directory which contains a list of certificates that have been revoked for various reasons. Certificates may be revoked due to improper issuance, compromise of the certificate, and failure to adhere to policy. Therefore, any certificate found on a CRL should not be trusted. Permitting execution of an applet published with a revoked certificate may result in spoofing, malware, system modification, invasion of privacy, and denial of service.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_validation_crl
Identifiers and References

References:  CCI-001991, IA-5(2)(d), SRG-APP-000401, JRE8-UX-000150


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000150
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_validation_crl
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Enable Use of Certificate Revocation Lists
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.validation.crl=.*
    line: deployment.security.validation.crl=true
  tags:
  - DISA-STIG-JRE8-UX-000150
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_validation_crl
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.validation.crl=.*" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.validation.crl=.*/deployment.security.validation.crl=true/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.validation.crl=true" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Certificate Revocation List Settings   [ref]

To ensure that users cannot change certificate revocation list settings, add deployment.security.validation.crl.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Permitting execution of an applet published with a revoked certificate may result in spoofing, malware, system modification, invasion of privacy, and denial of service. This is why it is important to ensure to check against a Certificate Revocation List. As such, ensuring users cannot change settings contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_validation_crl_locked
Identifiers and References

References:  CCI-001991, IA-5(2)(d), SRG-APP-000401, JRE8-UX-000150


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000150
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_validation_crl_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Certificate Revocation List Settings
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.validation.crl.locked
    line: deployment.security.validation.crl.locked
  tags:
  - DISA-STIG-JRE8-UX-000150
  - NIST-800-53-IA-5(2)(d)
  - configure_strategy
  - java_jre_validation_crl_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.validation.crl.locked$" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.validation.crl.locked" >> ${JAVA_PROPERTIES}
fi

Rule   Enable Online Certificate Validation   [ref]

To ensure that online certificate verification is enabled, set deployment.security.validation.ocsp to equal true in /etc/.java/deployment/deployment.properties.
Rationale:
Online certificate validation provides a greater degree of validation of certificates when running a signed Java applet. Permitting execution of an applet with an invalid certificate may result in malware execution , system modification, invasion of privacy, and denial of service.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_validation_ocsp
Identifiers and References

References:  CCI-000185, IA-5(2)(a), SRG-APP-000175, JRE8-UX-000100


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000100
  - NIST-800-53-IA-5(2)(a)
  - configure_strategy
  - java_jre_validation_ocsp
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Enable Online Certificate Validation
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.validation.ocsp=.*
    line: deployment.security.validation.ocsp=true
  tags:
  - DISA-STIG-JRE8-UX-000100
  - NIST-800-53-IA-5(2)(a)
  - configure_strategy
  - java_jre_validation_ocsp
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.validation.ocsp=.*" ${JAVA_PROPERTIES} && \
sed -i "s/deployment.security.validation.ocsp=.*/deployment.security.validation.ocsp=true/g" ${JAVA_PROPERTIES}
if ! [ $? -eq 0 ] ; then
  echo "deployment.security.validation.ocsp=true" >> ${JAVA_PROPERTIES}
fi

Rule   Disable User Access to Online Certificate Validation Setting   [ref]

To ensure that users cannot change the online certificate verification setting, add deployment.security.validation.ocsp.locked to /etc/.java/deployment/deployment.properties.
Rationale:
Online certificate validation provides a greater degree of validation of certificates when running a signed Java applet. Permitting execution of an applet with an invalid certificate may result in malware execution , system modification, invasion of privacy, and denial of service. As such, ensuring users cannot change settings contributes to a more consistent security profile.
Severity: 
medium
Rule ID:xccdf_org.ssgproject.content_rule_java_jre_validation_ocsp_locked
Identifiers and References

References:  CCI-000185, IA-5(2)(a), SRG-APP-000175, JRE8-UX-000100


Complexity:low
Disruption:low
Strategy:configure
- name: Ensure Java Deployment Directory Exists
  file:
    path: /etc/.java/deployment
    state: directory
    mode: '0755'
  tags:
  - DISA-STIG-JRE8-UX-000100
  - NIST-800-53-IA-5(2)(a)
  - configure_strategy
  - java_jre_validation_ocsp_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Disable User Access to Online Certificate Validation Setting
  lineinfile:
    create: true
    mode: '0644'
    dest: /etc/.java/deployment/deployment.properties
    regexp: ^\s*#?\s*deployment.security.validation.ocsp.locked
    line: deployment.security.validation.ocsp.locked
  tags:
  - DISA-STIG-JRE8-UX-000100
  - NIST-800-53-IA-5(2)(a)
  - configure_strategy
  - java_jre_validation_ocsp_locked
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed


JAVA_PROPERTIES="/etc/.java/deployment/deployment.properties"
JAVA_DIR="/etc/.java/deployment"

if [ ! -d ${JAVA_DIR} ] ; then
  mkdir -p -m 755 ${JAVA_DIR}
fi

if [ ! -e ${JAVA_PROPERTIES} ]; then
  touch ${JAVA_PROPERTIES} && chmod 644 ${JAVA_PROPERTIES}
fi

grep -q "^deployment.security.validation.ocsp.locked$" ${JAVA_PROPERTIES}

if ! [ $? -eq 0 ] ; then
  echo "deployment.security.validation.ocsp.locked" >> ${JAVA_PROPERTIES}
fi
Red Hat and Red Hat Enterprise Linux are either registered trademarks or trademarks of Red Hat, Inc. in the United States and other countries. All other names are registered trademarks or trademarks of their respective companies.