Skip to content

An InSpec Profile for evaluating a Windows 2016 server to the DISA STIGs

License

Notifications You must be signed in to change notification settings

mitre/microsoft-windows-server-2016-stig-baseline

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

82 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

microsoft-windows-server-2016-stig-baseline

InSpec profile to validate the secure configuration of Microsoft Windows Server 2016, against DISA's Microsoft Windows Server 2016 Security Technical Implementation Guide (STIG) Version 1, Release 7.

Getting Started

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.

The 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.

- List of authorized users in the Backup Operators Group
backup_operators:

- List of authorized users in the local Administrators group
administrators:

- List of authorized users in the local Administrators domain group
administrators_domain:

- List of temporary accounts on the system
temp_account:

- List of emergency accounts on the system
emergency_account:

- List of authorized users in the local Administrators domain group
administrator_domain_group:

- List of shared accounts on the system
shared_accounts:

- Set to true server has the ftp server role
has_ftp_server_role:

- Domain Controller forrest name
forrest:

- Default administator account
admin_account:

- Set to true if the system is dedicated to the management of Active Directory
is_AD_only_system:

- Set flag to true if the target system is unclassified
is_unclassified_system:

- List of DoD Interoperability Root Certificates
dod_certificates:

- List of DoD Interoperability Root Certificates
dod_cceb_certificates:

- Default account name for Built-In Administrator
built_in_admin_account:

- A list of all manually managed Application and Service account names
manually_managed_app_service_accounts:

Running This Baseline Directly from Github

# How to run
inspec exec https://github.com/mitre/microsoft-windows-server-2016-stig-baseline/archive/master.tar.gz --target 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>

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/microsoft-windows-server-2016-stig-baseline
inspec archive microsoft-windows-server-2016-stig-baseline
inspec exec <name of generated archive> --target 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-windows-server-2016-stig-baseline
git pull
cd ..
inspec archive microsoft-windows-server-2016-stig-baseline --overwrite
inspec exec <name of generated archive> --target 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>

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

About

An InSpec Profile for evaluating a Windows 2016 server to the DISA STIGs

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages