Secure Host Baseline
About the Secure Host Baseline
The Secure Host Baseline (SHB) provides an automated and flexible approach for assisting the DoD in deploying the latest releases of Windows 10 using a framework that can be consumed by organizations of all sizes.
The DoD CIO issued a memo on November 20, 2015 directing Combatant Commands, Services, Agencies and Field Activities (CC/S/As) to rapidly deploy the Windows 10 operating system throughout their respective organizations with the objective of completing deployment by the end of January 2017. The Deputy Secretary of Defense issued a memo on February 26, 2016 directing the DoD to complete a rapid deployment and transition to Microsoft Windows 10 Secure Host Baseline by the end of January 2017.
Formal product evaluations also support the move to Windows 10. The National Information Assurance Partnership (NIAP) and National Institute of Standards and Technology (NIST) oversees evaluations of commercial IT products for use in National Security Systems.
- Common Criteria evaluation of Windows 10 against NIAP Protection Profile for General Purpose Operating Systems completed April 5, 2016.
- Common Criteria evaluation of Windows 10 against NIAP Protection Profile for Mobile Device Fundamentals completed January 29, 2016.
- Common Criteria evaluation of Windows 10 against NIAP Protection Profile for IPsec Virtual Private Network (VPN) Clients completed November 10, 2016.
- NIST FIPS 140-2 validation of Windows 10 cryptographic modules was completed on June 2, 2016 (see certificate numbers 2600, 2601, 2602, 2603, 2604, 2605, 2606, and 2607).
Using a Secure Host Baseline is one of NSA Information Assurance top 10 mitigation strategies. The DoD Secure Host Baseline also exemplifies other IAD top 10 mitigation strategies such as using application whitelisting, enabling anti-exploitation features, and using the latest version of the operating system and applications.
About this repository
This repository hosts Group Policy objects, compliance checks, and configuration tools in support of the DoD Secure Host Baseline (SHB) framework for Windows 10. Administrators of National Security Systems, such as those who are part of the Defense Industrial Base, can leverage this repository in lieu of access to the DoD SHB framework for Windows 10 which requires a Common Access Card (CAC) or Personal Identification Verification (PIV) smart card to access.
Group Policy Objects
- The Adobe Reader folder contains Adobe Reader DC Computer and User policies for the latest version of Adobe Reader DC.
- The AppLocker folder contains AppLocker Computer policy for the latest version of Windows 10.
- The BitLocker folder contains BitLocker Computer policy for the latest version of Windows 10.
- The Certificates folder contains Computer policy for distributing the DoD Root and Intermediate Certificate Authorities.
- The Chrome folder contains Chrome browser Computer policy for the latest version of Chrome.
- The EMET folder contains EMET 5.5 Computer policy for any version of Windows.
- The Internet Explorer folder contains Internet Explorer 11 Computer and User policies for latest version of Windows 10.
- The Office folder contains Office 2013 and Office 2016 policy.
- The Windows folder contains Windows 10 User and Computer policies for the latest version of Windows 10.
- The Windows Firewall folder contains Windows Firewall Computer policy for the latest version of Windows 10.
Scripts and tools
Scripts for aiding users with the SHB are located in the Scripts sub folders of each component. Scripts available for use so far:
Nessus (aka ACAS in the DoD) audit files are included in this repository. Compliance checks are available for:
Instructions for running the compliance checks in a domain or standalone environment can be found on the Compliance page.
To get started using the tools:
- Download the repository as a zip file
- Configure PowerShell
- Load the code
- Apply the policies
- Check compliance
Downloading the repository
Download the current code to your Downloads folder. It will be saved as Secure-Host-Baseline-master.zip by default.
Configuring the PowerShell environment
The PowerShell commands are meant to run from a system with at least PowerShell 3.0 installed. PowerShell may need to be configured to run the commands.
Changing the PowerShell execution policy
Users may need to change the default PowerShell execution policy. This can be achieved in a number of different ways:
- Open a command prompt and run powershell.exe -ExecutionPolicy Unrestricted and run scripts from that PowerShell session.
- Open a PowerShell prompt and run Set-ExecutionPolicy Unrestricted -Scope Process and run scripts from the current PowerShell session.
- Open an administrative PowerShell prompt and run Set-ExecutionPolicy Unrestricted and run scripts from any PowerShell session.
Unblocking the PowerShell scripts
Users will need to unblock the downloaded zip file since it will be marked as having been downloaded from the Internet which PowerShell will block from executing by default. Open a PowerShell prompt and run the following commands to unblock the PowerShell code in the zip file:
Unblock-File -Path '.\Secure-Host-Baseline-master.zip'
Running the PowerShell scripts inside the zip file without unblocking the file will result in the following warning:
Security warning Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\users\user\Downloads\script.ps1? [D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"):
If the downloaded zip file is not unblocked before extracting it, then all the individual PowerShell files that were in the zip file will have to be unblocked. You will need to run the following command after Step 5 in the Loading the code section:
Get-ChildItem -Path '.\Secure-Host-Baseline' -Recurse -Include '*.ps1','*.psm1' | Unblock-File -Verbose
See the Unblock-File command's documentation for more information on how to use it.
Loading the code
Now extract the downloaded zip file and load the PowerShell code used for apply the policies.
- Right click on the zip file and select Extract All
- At the dialog remove Secure-Host-Baseline-master from the end of the path since it will extract the files to a Secure-Host-Baseline-master folder by default
- Click the Extract button
- Rename the Secure-Host-Baseline-master folder to Secure-Host-Baseline
- Open a PowerShell prompt as an administrator
- Import the Group Policy PowerShell module to load the code into the PowerShell session:
Import-Module -Name .\Secure-Host-Baseline\Scripts\GroupPolicy.psm1
Applying the policies
The Invoke-ApplySecureHostBaseline command found in the Group Policy PowerShell module is the main command for applying policies. By default this command will:
- Import both Computer and User policies. Use the -PolicyScopes option and specify only the 'User' or 'Computer' value to import only User or Computer policies.
- Import policies, that have an audit option (e.g. AppLocker), in audit mode. To import those policies in enforcement mode, use the -PolicyMode option and specify the 'Enforced' value.
- Make a backup copy of existing imported SHB Group Policy objects (and Group Policy templates if the -UpdateTemplates option is used) if they exist. The backups will be in a directory located at %UERPROFILE%\Desktop\Backup_yyyyMMddHHmmss corresponding to the time when the command was executed. To change this location use the -BackupPath option and specify a path to an existing folder where the Backup_yyyyMMddHHmmss will be created.
- not update the Group Policy template files that correspond to the applied Group Policy objects. Use the -UpdateTemplates option to update the Group Policy templates.
Options for the command are:
- -Path - Required. The path to the folder containing the downloaded and extracted GitHub SHB repository.
- -PolicyNames - Required. The names of the policies to apply. Can be 1 or more policy names. Available names: 'Adobe Reader', 'AppLocker', 'BitLocker', 'Certificates', 'Chrome', 'EMET', 'Internet Explorer', 'Office 2013', 'Office 2016', 'Windows', 'Windows Firewall'.
- -PolicyScopes - Optional. The scope of the policies to apply. Available scopes: 'Computer', 'User'. Defaults to 'Computer','User'.
- -PolicyType - Optional. The type of policies to apply. Available types: 'Domain', 'Local'. Defaults to 'Domain' when joined to a domain. Defaults to 'Local' when not joined to a domain.
- -PolicyMode - Optional. The mode of policies to apply, if supported by the specific policy. For example, AppLocker supports audit and enforcement modes. Available modes: 'Audit', 'Enforced'. Defaults to 'Audit'.
- -BackupPath - Optional. The path to a folder to save backups of existing imported SHB Group Policy objects (and Group Policy templates if the -UpdateTemplates option is used) if they exist in case a rollback is needed. Defaults to $env:USERPROFILE\Desktop\Backup_yyyyMMddHHmmss corresponding to when the script was executed.
- -ToolPath - Optional. The path to the LGPO tool. Required when PolicyType is 'Local'.
- -UpdateTemplates - Optional. Update Group Policy templates that correspond to the applied Group Policy objects.
Type man Invoke-ApplySecureHostBaseline at a PowerShell prompt for more help and examples or submit a question to the repository issue tracker.
Applying the SHB policies to a standalone system
Invoke-ApplySecureHostBaseline -Path '.\Secure-Host-Baseline' -PolicyNames 'Adobe Reader','AppLocker','Certificates','Chrome','EMET','Internet Explorer','Office 2013','Office 2016','Windows','Windows Firewall' -ToolPath '.\LGPO\lgpo.exe'
Applying the SHB policies to a domain
If applying the SHB policies to a domain, note that the Group Policy objects are only loaded into Active Directory. The policies are not linked to any OUs so the settings do not automatically take affect.
Invoke-ApplySecureHostBaseline -Path '.\Secure-Host-Baseline' -PolicyNames 'Adobe Reader','AppLocker','Certificates','Chrome','EMET','Internet Explorer','Office 2013','Office 2016','Windows','Windows Firewall'
Once the policies have been applied (and linked to appropriate OUs in the domain case), see the Compliance page for instructions on how to check compliance to the policies.