Skip to content

Latest commit

 

History

History
54 lines (43 loc) · 4.04 KB

README.md

File metadata and controls

54 lines (43 loc) · 4.04 KB
Raw

Windows STIG & SCAP Toolkit

WHAT IS IT:

A PowerShell script that will take a GPO backup or SCAP XCCDF file and generate STIGs settings Then apply them to a Windows OS using Microsoft's LGPO.exe tool from their Security Compliance Manager Toolkit

HOW TO USE IT:

ApplySTIGAndGPOs.ps1 This is a more dynamic PowerShell script. This will detect roles, and features and even software and install the appropriate GPO backup.

ApplySTIGBySCAPs.ps1 STILL DEVELOPING: This is the most advanced PowerShell script. This script will be a lot like Linux's OpenSCAP, it will parse the XCCDF file from DISA and build a dataset of all STIG components and one by one it will apply the STIG based on the configuration files. Configuration files still need to be created, check out the README.md

RemoveSTIGAndGPOs.ps1 This script just removes the group policy folders and clear the security database.

REQUIREMENTS:

  • Modules need to be downloaded. Follow README.md instructions in modules folder
  • STIG Naming conventions is required for STIG Tools. Follow README.md instructions in GPO folder
  • CCI required for SCAP Tools. Follow README.md instructions in CCI folder
  • SCAP Benchmarks required for SCAP Tools. Follow README.md instructions in SCAP folder
  • LGPO executable required for all tools. Follow README.md instructions in Tools folder
  • Configs files for each STIG ID. Follow README.md instructions in Tools folder

WHAT IT DOES:

ApplySTIGAndGPOs.ps1: The script will read into the GPO's backup.xml inside each GUID and identify the name of the policy. Using that information it will determine if the name matches identified system information, roles, features and install products and apply them locally using Microsoft's Security Compliance Manager tool LGPO. This ultimately read the GPO settings, and builds a file with all the registry and security settings, then applies those settings within the local gpo. These settings can then be viewed using the systems gpedit.msc. All keys and settings are backed up in the temp folder and logged in log folder.

FOLDERS:

CCI\U_CCI_List.xml <-- Used with ApplySTIGBySCAPs.ps1. Control Correlation Identifier (CCI) provides a standard identifier and description for each of the singular, actionable statements that comprise an IA control or IA best practice			
Configs\	   <-- Used with ApplySTIGBySCAPs.ps1. Configuration files for each STIG ID. These are ini like files with commands for validation and remediation steps.			
Extensions\	   <-- Used with ApplySTIGBySCAPs.ps1. PowerShell extension folder provides additional PowerShell functions
Modules\	   <-- Additional PowerShell modules found in PowerShell Gallery and elsewhere
GPO\		   <-- Used with ApplySTIGAndGPOs.ps1. Follow README.md instructions in folder
Logs\		   <-- Output logs for LGPO and advanced logging (Use CMTRACE)
SCAP\		   <-- SCAP Benchmark files. Follow README.md instructions in folder
Temp\		   <-- Store generated LGPO config and pol files
Tools\		   <-- Tools used in scripts, such as LGPO
DSC\		   <-- NEW. The idea is to add dsc configuration files here and and apply them along with STIGS/SCAP

SOURCES: