InSpec profile to validate the secure configuration of Microsoft SQL Server 2014 *Database, against DISA's Microsoft SQL Server 2014 Database Security Technical Implementation Guide (STIG) Version 1, Release 6.
*In the Microsoft SQL Server domain, a database (often abbreviated as DB) is a logical collection of data stored in files and managed not by the operating system alone but by the Database Management System (DBMS). Multiple databases may exist under one DBMS instance. There are always at least four system databases supporting an instance, and there will normally be one database (possibly more) supporting an application.
It is intended and recommended that InSpec run this profile from a "runner" host (such as a DevOps orchestration server, an administrative management system, or a developer's workstation/laptop) against the target remotely over winrm.
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.
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 MSSQL DB Server
user: ''
# password MSSQL DB Server
password: ''
# hostname MSSQL DB Server
host: ''
# instance name MSSQL DB Server
instance: ''
# port MSSQL DB Server
port: 49789
# name of the specific DB being evaluated within the MSSQL server
db_name: ''
# Changes in categorized information must be tracked
server_trace_or_audit_required: true
# Set to true If SQL Server Trace is in use for audit purposes
server_trace_implemented: true
# Set to true If SQL Server Audit is in use for audit purposes
server_audit_implemented: true
# Specify if SQL Server Audit is not in use at the database level
server_audit_at_database_level_required: true
# User with `ALTER ANY DATABASE AUDIT` or `CONTROL` permission
approved_audit_maintainers: []
# name of the timed job that automatically checks all system and user-defined procedures for being modified
track_stored_procedures_changes_job_name: ''
# name of the timed job that automatically checks all system and user-defined triggers for being modified
track_triggers_changes_job_name: ''
# name of the timed job that automatically checks all system and user-defined functions for being modified
track_functions_changes_job_name: ''
# identify SQL Server accounts authorized to own database objects
authorized_principals: []
# Set to true if data at rest encryption is required
data_at_rest_encryption_required: true
# Set to true if full disk encryption is in place
full_disk_encryption_inplace: false
# Set to true if security labeling is required
security_labeling_required: true# How to run
inspec exec https://github.com/mitre/microsoft-sql-server-2014-database-stig-baseline/archive/master.tar.gz -t winrm://<hostip> --user '<admin-account>' --password=<password> --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>
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/microsoft-sql-server-2014-database-stig-baseline
inspec archive microsoft-sql-server-2014-database-stig-baseline
inspec exec <name of generated archive> -t winrm://<hostip> --user '<admin-account>' --password=<password> --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 microsoft-sql-server-2014-database-stig-baseline
git pull
cd ..
inspec archive microsoft-sql-server-2014-database-stig-baseline --overwrite
inspec exec <name of generated archive> -t winrm://<hostip> --user '<admin-account>' --password=<password> --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>
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.
- Rony Xavier - rx294
- Mohamed El-Sharkawi - HackerShark
- Shivani Karikar - karikarshivani
To report a bug or feature request, please open an issue.
© 2018-2020 The MITRE Corporation.
Approved for Public Release; Distribution Unlimited. Case Number 18-3678.
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.
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.
DISA STIGs are published by DISA IASE, see: https://iase.disa.mil/Pages/privacy_policy.aspx