Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

CMS-Enterprise/cms-ars-5.0-oracle-19c-cis-overlay

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

41 Commits
 
 
 
 
 
 
 
 

Repository files navigation

cms-ars-5.0-oracle-19c-cis-overlay

CMS’ ISPG (Information Security and Privacy Group) decided to discontinue funding the customization of MITRE’s Security Automation Framework (SAF) for CMS after September 2023. This repo is now in archive mode, but still accessible. For more information about SAF with current links, see https://security.cms.gov/learn/security-automation-framework-saf

InSpec profile overlay to validate the secure configuration of Oracle Database 19c against the Oracle Database 19c Benchmark version 1.0.0 CIS tailored for CMS ARS 5.0.

Getting Started

InSpec (CINC-auditor) setup

For maximum flexibility/accessibility, we’re moving to “cinc-auditor”, the open-source packaged binary version of Chef InSpec, compiled by the CINC (CINC Is Not Chef) project in coordination with Chef using Chef’s always-open-source InSpec source code. For more information: https://cinc.sh/

It is intended and recommended that CINC-auditor and this profile overlay be run from a "runner" host (such as a DevOps orchestration server, an administrative management system, or a developer's workstation/laptop) against the target. This can be any Unix/Linux/MacOS or Windows runner host, with access to the Internet.

For the best security of the runner, always install on the runner the latest version of CINC-auditor.

The simplest way to install CINC-auditor is to use this command for a UNIX/Linux/MacOS runner platform:

curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -P cinc-auditor

or this command for Windows runner platform (Powershell):

. { iwr -useb https://omnitruck.cinc.sh/install.ps1 } | iex; install -project cinc-auditor

To confirm successful install of cinc-auditor:

cinc-auditor -v

sample output: 4.24.32

Latest versions and other installation options are available at https://cinc.sh/start/auditor/.

Specify your BASELINE system categization as an environment variable:

(if undefined defaults to Moderate baseline)

# BASELINE (choices: Low, Low-HVA, Moderate, Moderate-HVA, High, High-HVA)
# (if undefined defaults to Moderate baseline)

on linux:
BASELINE=High

on Powershell:
$env:BASELINE="High"

Inputs: Tailoring your scan 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.

Example Inputs You Can Use

# Description: 'database user name'
user: 'SYSTEM'

# Description: 'database password'
password: 'password'

# Description: 'database hostname'
host: '127.0.0.1'

# Description: 'service name'
service: 'ORCLCDB'

# Description: 'Path of sqlplus binary on the runner'
sqlplus_bin: 'sqlplus'

# Description: 'Path of listener.ora on the runner'
listener_file: /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora

# Description: 'Flag to indicate whether the database is multi-tenant or single-tenant'
multitenant: false

# Description: 'Expected version for Oracle database'
version: '19.0.0.0.0'

# Description: 'List of listener interface names defined in listener.ora'
listeners: ['LISTENER']

Running This Overlay Directly from Github

Against a remote target using ssh (i.e., cinc-auditor installed on a separate runner host)

cinc-auditor exec https://github.com/cms-enterprise/cms-ars-5.0-oracle-19c-cis-overlay/archive/main.tar.gz -t ssh://<username>:TARGET_PASSWORD@TARGET_IP:TARGET_PORT --input-file <path_to_your_input_file/name_of_your_input_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json> 

Against a remote target using a pem key (i.e., cinc-auditor installed on a separate runner host)

cinc-auditor exec https://github.com/cms-enterprise/cms-ars-5.0-oracle-19c-cis-overlay/archive/main.tar.gz -t ssh://<username>@TARGET_IP:TARGET_PORT -i <PEM_KEY> --input-file <path_to_your_input_file/name_of_your_input_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>  

Against a locally-hosted instance (i.e., cinc-auditor installed on the target hosting the database)

cinc-auditor exec https://github.com/cms-enterprise/cms-ars-5.0-oracle-19c-cis-overlay/archive/main.tar.gz --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>

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

cinc-auditor exec https://github.com/cms-enterprise/cms-ars-5.0-oracle-19c-cis-overlay/archive/main.tar.gz -t docker://<instance_id> --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>

Different Run Options

Full exec options

Running This Overlay 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 overlay 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 overlay for the first time, follow these steps:

mkdir profiles
cd profiles
git clone https://github.com/cms-enterprise/cms-ars-5.0-oracle-19c-cis-overlay.git
cinc-auditor archive cms-ars-5.0-oracle-19c-cis-overlay
cinc-auditor exec <name of generated archive> --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 overlay and dependent profiles:

cd cms-ars-5.0-oracle-19c-cis-overlay
git pull
cd ..
cinc-auditor archive cms-ars-5.0-oracle-19c-cis-overlay --overwrite
cinc-auditor exec <name of generated archive> --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>

Using Heimdall for 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

Special Thanks

Contributing and Getting Help

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

NOTICE

© 2018-2022 The MITRE Corporation.

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

CIS Benchmarks are published by the Center for Internet Security (CIS), see: https://www.cisecurity.org/cis-benchmarks/.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages