This is a hardening checklist that can be used in private and business environments for hardening Windows 10. The checklist can be used for all Windows versions, but in Windows 10 Home the Group Policy Editor is not integrated and the adjustment must be done directly in the registry.
The settings should be seen as security and privacy recommendation and should be carefully checked whether they will affect the operation of your infrastructure or impact the usability of key functions. It is important to weigh security against usability.
Policy Analzyer reads out and compares local registry and local policy values to a defined baseline. The PolicyRule file from aha-181 contains all rules which are needed to check Group Policy and Registry settings that are defined in the Windows 10 Hardening checklist.
Policy Analyzer supports the Hardening checklist up to version 0.2.0, additional entries are not yet supported.
HardeningKitty supports hardening of a Windows system. The configuration of the system is retrieved and assessed using a finding list. In addition, the system can be hardened according to predefined values. HardeningKitty reads settings from the registry and uses other modules to read configurations outside the registry.
Attention: HardeningKitty has a dependency for the tool AccessChk by Mark Russinovich. This must be present on the computer and defined in the script accordingly.
The script was developed for English systems. It is possible that in other languages the analysis is incorrect. Please create an issue if this occurs.
Run the script with administrative privileges to access machine settings. For the user settings it is better to execute them with a normal user account. Ideally, the user account is used for daily work.
Download HardeningKitty and copy it to the target system (script and lists). Additionally, AccessChk (tested with version 1.6.2) must be available on the target system. The path of the variable $BinaryAccesschk must be modified accordingly. After that HardeningKitty can be imported and executed:
PS C:\> Import-Module Invoke-HardeningKitty.ps1
PS C:\> Invoke-HardeningKitty -EmojiSupport
=^._.^=
_( )/ HardeningKitty
[*] 5/28/2020 4:39:16 PM - Starting HardeningKitty
[*] 5/28/2020 4:39:16 PM - Getting machine information
[*] Hostname: w10
[*] Domain: WORKGROUP
...
[*] 5/28/2020 4:39:21 PM - Starting Category Account Policies
[😺] ID 1100, Account lockout duration, Result=30, Severity=Passed
[😺] ID 1101, Account lockout threshold, Result=5, Severity=Passed
[😺] ID 1102, Reset account lockout counter, Result=30, Severity=Passed
...
[*] 5/28/2020 4:39:23 PM - Starting Category Advanced Audit Policy Configuration
[😼] ID 1513, Kernel Object, Result=, Recommended=Success and Failure, Severity=Low
...
[*] 5/28/2020 4:39:24 PM - Starting Category System
[😿] ID 1614, Device Guard: Virtualization Based Security Status, Result=Not available, Recommended=2, Severity=Medium
...
[*] 5/28/2020 4:39:25 PM - Starting Category Windows Components
[🙀] ID 1708, BitLocker Drive Encryption: Volume status, Result=FullyDecrypted, Recommended=FullyEncrypted, Severity=High
...
[*] 5/28/2020 4:39:34 PM - HardeningKitty is done
Each Passed finding gives 4 points, a Low finding gives 2 points, a Medium finding gives 1 point and a High Finding gives 0 points.
The formula for the HardeningKitty Score is (Points achieved / Maximum points) * 5 + 1.
Score | Rating Casual | Rating Professional |
---|---|---|
6 | 😹 Excellent | Excellent |
5 | 😺 Well done | Good |
4 | 😼 Sufficient | Sufficient |
3 | 😿 You should do better | Insufficient |
2 | 🙀 Weak | Insufficient |
1 | 😾 Bogus | Insufficient |
HardeningKitty can be used to audit systems against the following baselines / benchmarks:
Name | System Version | Version |
---|---|---|
0x6d69636b (Machine) | 2009 | |
0x6d69636b (User) | 2009 | |
CIS Microsoft Windows 10 Enterprise (Machine) | 2004 | 1.9.1 |
CIS Microsoft Windows 10 Enterprise (User) | 2004 | 1.9.1 |
CIS Microsoft Windows Server 2019 (Machine) | 1809 | 1.1.0 |
CIS Microsoft Windows Server 2019 (User) | 1809 | 1.1.0 |
Microsoft Security baseline for Microsoft Edge | 87 | Final |
Microsoft Security baseline for Windows 10 version 2004 | 2004 | Final |
Microsoft Security baseline for Windows 10 version 2009 | 2009 | Final |
Microsoft Security baseline for Windows Server version 2004 (DC) | 2004 | Final |
Microsoft Security baseline for Windows Server version 2004 (Member) | 2004 | Final |
Microsoft Security baseline for Windows Server 10 version 2009 (DC) | 2009 | Final |
Microsoft Security baseline for Windows Server 10 version 2009 (Member) | 2009 | Final |
Microsoft Security baseline for Office 365 ProPlus (Machine) | Sept 2019 | Final |
Microsoft Security baseline for Office 365 ProPlus (User) | Sept 2019 | Final |
- CIS Benchmarks for Microsoft Windows 10 Enterprise Release 1909 v1.8.1
- CIS Benchmarks for Microsoft Windows 10 Enterprise Release 2004 v1.9.1
- CIS Benchmarks for Microsoft Windows Server 2019 RTM Release 1809 v1.1.0
- Security baseline (FINAL): Windows 10 and Windows Server, version 2004
- Security baseline (DRAFT): Windows 10 and Windows Server, version 20H2
- Kernel DMA Protection for Thunderbolt 3
- BitLocker Countermeasures
- Blocking the SBP-2 driver and Thunderbolt controllers to reduce 1394 DMA and Thunderbolt DMA threats to BitLocker
- Manage Windows Defender Credential Guard
- Reduce attack surfaces with attack surface reduction rules
- Configuring Additional LSA Protection
- Securely opening Microsoft Office documents that contain Dynamic Data Exchange (DDE) fields
- DDE registry settings
- Sysmon
- SwiftOnSecurity/sysmon-config
- Dane Stuckey - @cryps1s Endpoint Isolation with the Windows Firewall
- Microsoft Security Compliance Toolkit 1.0
- Policy Analyzer
- Security baseline for Office 365 ProPlus (v1908, Sept 2019) - FINAL
- mackwage/windows_hardening.cmd
- Security baseline for Microsoft Edge version 87
- Microsoft Edge - Policies
- A hint for Office 365 Telemetry
- BSI: Microsoft Office Telemetry Analysis report
- Use policy settings to manage privacy controls for Microsoft 365 Apps for enterprise