oracle-java-runtime-environment-8-unix-stig-baseline

InSpec profile to validate the secure configuration of JRE 8, against DISA's JRE 8 Security Technical Implementation Guide (STIG).

Container-Ready: Profile updated to adapt checks when the running against a containerized instance of JRE8, based on reference container: (docker pull registry1.dso.mil/ironbank/opensource/gradle/gradle-jre8@latest)

Getting Started

For the best security of the runner, always install on the runner the latest version of InSpec and supporting Ruby language components.

Latest versions and installation options are available at the InSpec site.

Tailoring to Your Environment

The following inputs must be configured in an inputs ".yml" file for the profile to run correctly for your specific environment. More information about InSpec inputs can be found in the InSpec Profile Documentation.

# Set to true if this system is on the SIPRNET
is_on_siprnet: false

# Java version allowed
java_version: ''

# Java deployment.config file
deployment_config_file: ''

# Java deployment.properties file
deployment_properties_file: ''

# Java deployment/exception.sites file
deployment_exception_sites_file: ''

Running This Baseline Directly from Github

Against a locally-hosted instance (i.e., InSpec installed on the target)

inspec exec https://github.com/mitre/oracle-java-runtime-environment-8-unix-stig-baseline/archive/master.tar.gz --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter json:<path_to_your_output_file/name_of_your_output_file.json>

Against a docker-containerized instance (i.e., InSpec installed on the node hosting the container):

inspec exec https://github.com/mitre/oracle-java-runtime-environment-8-unix-stig-baseline/archive/master.tar.gz -t docker://instance_id --input-file <path_to_your_input_file/name_of_your_input_file.yml> --reporter json:<path_to_your_output_file/name_of_your_output_file.json>

Different Run Options

Full exec options

Running This Baseline from a local Archive copy

If your runner is not always expected to have direct access to GitHub, use the following steps to create an archive bundle of this baseline and all of its dependent tests:

(Git is required to clone the InSpec profile using the instructions below. Git can be downloaded from the Git site.)

When the "runner" host uses this profile baseline for the first time, follow these steps:

mkdir profiles
cd profiles
git clone https://github.com/mitre/oracle-java-runtime-environment-8-unix-stig-baseline
inspec archive oracle-java-runtime-environment-8-unix-stig-baseline
inspec exec <name of generated archive> --target=ssh://<your_target_host_name_or_ip_address> --user=<target_account_with_administrative_privileges> --password=<password_for_target_account> --sudo --sudo-password=<sudo_password_for_target_if_required> --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>

For every successive run, follow these steps to always have the latest version of this baseline:

cd oracle-java-runtime-environment-8-unix-stig-baseline
git pull
cd ..
inspec archive oracle-java-runtime-environment-8-unix-stig-baseline --overwrite
inspec exec <name of generated archive> --target=ssh://<your_target_host_name_or_ip_address> --user=<target_account_with_administrative_privileges> --password=<password_for_target_account> --sudo --sudo-password=<sudo_password_for_target_if_required> --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>

Viewing the JSON Results

The JSON results output file can be loaded into heimdall-lite for a user-interactive, graphical view of the InSpec results.

The JSON InSpec results file may also be loaded into a full heimdall server, allowing for additional functionality such as to store and compare multiple profile runs.

Authors

Alicia Sturtevant - asturtevant

Special Thanks

Mohamed El-Sharkawi - HackerShark
Shivani Karikar - karikarshivani

Contributing and Getting Help

To report a bug or feature request, please open an issue.

NOTICE

Approved for Public Release; Distribution Unlimited. Case Number 18-3678.

NOTICE

MITRE hereby grants express written permission to use, reproduce, distribute, modify, and otherwise leverage this software to the extent permitted by the licensed terms provided in the LICENSE.md file included with this project.

NOTICE

This software was produced for the U. S. Government under Contract Number HHSM-500-2012-00008I, and is subject to Federal Acquisition Regulation Clause 52.227-14, Rights in Data-General.

No other use other than that granted to the U. S. Government, or to those acting on behalf of the U. S. Government under that Clause is authorized without the express written permission of The MITRE Corporation.

For further information, please contact The MITRE Corporation, Contracts Management Office, 7515 Colshire Drive, McLean, VA 22102-7539, (703) 983-6000.

NOTICE

DISA STIGs are published by DISA IASE, see: https://iase.disa.mil/Pages/privacy_policy.aspx

V-66935 Previous version of JRE installed (Possibly manual control)

This controls becomes complicated because there are several ways to install JRE and will be hard to be captured on an automated test

  describe.one do
    describe 'The number of previous versions of JRE installed' do
      subject { get_previous_jreversions_installed }
      it { should cmp 0 }
    end

    describe 'The number of jre versions installed' do
      subject { command('ps -ef | grep -I jre | wc -l').stdout }
      it { should eq 1 }
    end
    describe 'The number of previous versions of JRE installed' do
      subject { get_previous_jreversions_installed2 }
      it { should eq '0' }
    end
  end

The condition should not be wrapped in an describe.one condition because any one of them could initicate a fail

command ps -ef | grep -I jre | wc -l will always return atleast 1
and the count of 1 refers to grep process itself

[vagrant@localhost deployment]$ ps -ef | grep -I jre | wc -l
1
[vagrant@localhost deployment]$ ps -ef | grep -I jre
vagrant  13605   886  0 19:53 pts/0    00:00:00 grep --color=auto -I jre

Highly recommended that this control be marked manual.

mitre / oracle-java-runtime-environment-8-unix-stig-baseline Goto Github PK