Code Monkey home page Code Monkey logo

oracle-mysql-ee-5.7-cis-baseline's Introduction

oracle-mysql-ee-5.7-cis-baseline

InSpec profile to validate the secure configuration of Oracle MySQL Enterprise Edition version 5.7, against CIS's Oracle MySQL Enterprise Edition 5.7 CIS Benchmark.

Container-Ready: Profile updated to adapt checks when the running against a containerized instance of MySQL, based on reference container: (docker pull registry1.dso.mil/ironbank/opensource/mysql/mysql-5.7:5.7.35)

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.

# username MySQL DB Server
user: ''

# password MySQL DB Server
password: ''

# hostname of MySQL DB Server
host: ''

# port MySQL DB Server
port: 3306

# approved version expected to be installed
approved_mysql_version: ''

# List of mysql database users
mysql_users: []

# Set to true if the mysql server has a slave configured
is_mysql_server_slave_configured: true

# List of mysql administrative users
mysql_administrative_users: []

# List of mysql users allows to modify or create data structures
mysql_users_allowed_modify_or_create: []

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-mysql-ee-5.7-cis-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-mysql-ee-5.7-cis-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-mysql-ee-5.7-cis-baseline
inspec archive oracle-mysql-ee-5.7-cis-baseline
inspec exec <name of generated archive> --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>

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

cd oracle-mysql-ee-5.7-cis-baseline
git pull
cd ..
inspec archive oracle-mysql-ee-5.7-cis-baseline --overwrite
inspec exec <name of generated archive> --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>

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-2020 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

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

oracle-mysql-ee-5.7-cis-baseline's People

Contributors

aaronlippold avatar asturtevant avatar ejaronne avatar hackershark avatar karikarshivani avatar rx294 avatar superyarick avatar yarick avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

oracle-mysql-ee-5.7-cis-baseline's Issues

Control 1.3 - fix logic to parse array

Currently this code does not parse the history_file variable and does not test correctly:

 history_file = command("find / -name '.mysql_history'").stdout.strip.split("\n")

  describe "The MySql history file: #{history_file}" do
    subject { file(history_file.to_s) }
    its('link_path') { should eq '/dev/null' }
  end

Recommend update to:

history_file = command("find / -name '.mysql_history'").stdout.strip.split("\n")

history_file.each do |files|
  describe "The MySql history file: #{files}" do
    subject { file(files) }
    its('link_path') { should eq '/dev/null' }
  end
  only_if { os.linux? }
end

don't change desc field during skips

For the following 12 controls, when determining that the test is not applicable, do not change the desc field. only set the skip message:

2.3
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
8.2
9.2

3.9, 6.5-9 Logic should switch to require manual review if nil

Applies to controls 3.3, and 6.5 through 6.9

Currently, if the "audit_"* parameters are not defined (i.e., auditing isn't installed or the profile is run against a community rather than enterprise edition, the describe block is not contained and produces a profile error, for example:
ERROR 1193 (HY000) at line 1: Unknown system variable 'audit_log_file'

If this happens, add logic similar to this:

describe "Since the audit parameter is not defined, perform a manual review to ensure auditing is configured."  do
      skip "Since the audit parameter is not defined, perform a manual review to ensure auditing is configured."

check 7.6 logic

Some final tests showed that all the answers it pulls back seem to be nul. Please check.

Add sample data

Add folder with sample data for hardened and unhardened results

3.3 logic should switch to manual review if log_error is set to none or stderr

If "select @@log_error" returns nil or "stderr", require a manual review instead:

 describe "Since the @@log_error destination is either not set or set to stderr, perform a manual review to ensure permissions on the final destination are secured."  do
      skip "Since the @@log_error destination is either not set or set to stderr, perform a manual review to ensure permissions on the final destination are secured."

7.3 contain profile error if client.password is undefined

Applies to control 7.3:

If client password isn't defined in the my.cnf file, current logic gives a profile error:

undefined method password' for nil:NilClass`

The logic should capture this as one of the conditions for a passing test result instead of an error.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.