KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

Security-ADMX

★ 103 Open GitHub ↗

Custom ADMX template focused on hardening Windows 10 & Windows 11 systems

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Security-ADMX

Custom ADMX template focused on hardening Windows 10 and Windows 11 systems.

## Release status

[![Linting](https://github.com/Harvester57/Security-ADMX/actions/workflows/linting.yml/badge.svg)](https://github.com/Harvester57/Security-ADMX/actions/workflows/linting.yml)
[![Latest release](https://img.shields.io/github/v/release/Harvester57/Security-ADMX)](https://github.com/Harvester57/Security-ADMX/releases)

## Table of contents

- [System policies](#system-policies)
- [Network policies](#network-policies)
- [User policies](#user-policies)
- [Debugging policies](#debugging-policies)
- [Installation procedure](#installation-procedure)

## Installation procedure

### Automatic installation

You can automatically install the ADMX and ADML files to your local machine (Active Directory Central Store is not supported by the script) using the `install.ps1` PowerShell script.

1. Open a PowerShell terminal as Administrator.
2. Navigate to the directory where you downloaded the project.
3. Run the script:
   ```powershell
   .\install.ps1
   ```

### Manual installation

#### Active Directory PolicyDefinitions store

To make the policies available to all the machines in your domain, you need to copy the files to the Central Store configuration of your domain controller.

1. Locate the Central Store: `\\yourdomain.com\SYSVOL\yourdomain.com\Policies\PolicyDefinitions`.
2. Copy the `.admx` files to the root of the `PolicyDefinitions` folder.
3. Copy the `.adml` files (located in the `en-US` and `fr-FR` folders) to the corresponding language-specific subfolders in the Central Store.

#### Local PolicyDefinitions folder

To install the policies on a standalone machine or for testing purposes:

1. Locate the Local Store: `C:\Windows\PolicyDefinitions`.
2. Copy the `.admx` files to the root of the `PolicyDefinitions` folder.
3. Copy the `.adml` files (located in the `en-US` and `fr-FR` folders) to the corresponding language-specific subfolders in the Local Store.

## Available policies

### System policies

<details>
<summary>Enable secure mode for batch file processing</summary>

- **Registry path(s):** SOFTWARE\Microsoft\Command Processor
- **Registry key(s):** LockBatchFilesWhenInUse
- **Values:** 0/1
- **Description:** This policy gives administrators additional controls over the processing of batch files and CMD scripts.

If you enable this policy, a more secure mode for processing batch files is enabled, which ensures they do not change during execution by holding an opportunistic lock. This enhances the performance and security of batch file processing when Code Integrity is enabled, as signature validation will only be required to be performed a single time, instead of per statement executed in the batch file.

Note: This functionality is supported on Windows 11 Insider Preview Build 26300.7939 or later.

</details>

<details>
<summary>Enable Microsoft Vulnerable Driver Blocklist</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\CI\Config
- **Registry key(s):** VulnerableDriverBlocklistEnable
- **Values:** 0/1
- **Description:** This policy setting configures whether the Microsoft Vulnerable Driver Blocklist is enabled on the system.

The vulnerable driver blocklist is a security feature designed to prevent known insecure, kernel-mode third-party drivers from loading.

If you enable this policy setting, the Vulnerable Driver Blocklist is enabled.

If you disable this policy setting, the Vulnerable Driver Blocklist is disabled, allowing known vulnerable drivers to load. Note: Disabling this feature reduces system security.

</details>

<details>
<summary>Enable Virtualization-Based Security in Mandatory mode</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\DeviceGuard
- **Registry key(s):** Mandatory
- **Values:** 0/1
- **Description:** This policy will enable the Virtualization-Based Security (VBS) function in Mandatory mode.

Mandatory mode is a new functionnality introduced to prevent the Windows Downdate attack (and other related dowgrading attacks) by forcing the verification of the components of the Secure Kernel and the hypervisor at boot time. Consequently, enabling this functionnality can lead to boot failure (and a denial of service) in case of a modification of a core component of Secure Kernel, hypervisor or a related dependant module.

NOTE: if you already have Virtualization-Based Security enabled with UEFI Lock, this setting will not do anything, as the VBS configuration is already written and locked in a UEFI variable. This variable needs to be deleted using the bcdedit.exe tool before deploying the Mandatory flag and the UEFI Lock. Guidance and more information about this procedure are available here:

<https://learn.microsoft.com/en-us/windows/security/identity-protection/credential-guard/configure?tabs=reg#disable-virtualization-based-security>

Enabling this policy will set the Mandatory flag and force the verification of the VBS components at boot time.

Enabling this policy with UEFI Lock already enabled wil do nothing.

Disabling this policy will disable the verification of the components, only if the UEFI Lock is not enabled. Otherwise, disabling this policy will do nothing.

</details>
<details>
<summary>Enable Generative AI features in Acrobat and Acrobat Reader</summary>

- **Registry path(s):** SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown
- **Registry key(s):** bEnableGentech
- **Values:** 0/1
- **Description:** The generative AI features in Acrobat and Acrobat Reader are turned on by default. This policy controls the state of the feature.

Enabling this policy will enable the Generative AI feature.

Disabling this policy will disable the Generative AI feature. For privacy purposes, it is recommended to set this policy to Disabled.

</details>
<details>
<summary>Configure the Windows Sudo command behavior</summary>

- **Registry path(s):** SOFTWARE\Policies\Microsoft\Windows\Sudo
- **Registry key(s):** Enabled
- **Values:** 0/1/2/3
- **Description:** This policy configures the behavior of the Sudo command introduced in Windows 11 24H2.

Possible choices are:

- Force a new elevated window to open (default behavior)
  - Disable inputs to the elevated process
  - Run in the current window
  - Disable the functionnality

It is recommended to use the default behavior and let the Sudo command open a new elevated window.

</details>
<details>
<summary>Enable Secure Boot/Code Integrity mitigations for BlackLotus (CVE-2023-24932)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Secureboot
- **Registry key(s):** AvailableUpdates
- **Values:** 64/256/128/512
- **Description:** This policy sets the Registry keys needed to apply the updated Secure Boot denylist (DBX), the new signing certificate in the allowlist (DB), the anti-rollback mecanisme (SVN) and the Code Integrity Boot Policy, to prevent untrusted/vulnerable Windows boot managers from loading when Secure Boot is turned on.

IMPORTANT: carefully read the Microsoft documentation associated with this protection, as it can render your device unable to boot if you do not follow the pre-required steps:

- <https://support.microsoft.com/en-us/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d>
 - <https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-24932>

In particular, you should read all the steps descriptions present in the list and the associated manual operations you need to perform (reboots, additional checks, ...) for each of them in the section of the documentation:

</details>
<details>
<summary>Prevent standard users to install root certificates</summary>

- **Registry path(s):** SOFTWARE\Policies\Microsoft\SystemCertificates\Root\ProtectedRoots
- **Registry key(s):** Flags
- **Values:** 0/1
- **Description:** This policy prevent standard (non-administrators) users to install root certificate authorities to their user-specific trust store.

Enabling this policy can help prevent code signing certificate cloning attacks. It is recommended to enable this policy.

</details>
<details>
<summary>Block drivers co-installers applications</summary>

- **Registry path(s):** SOFTWARE\Microsoft\Windows\CurrentVersion\Device Installer
- **Registry key(s):** DisableCoInstallers
- **Values:** 0/1
- **Description:** A co-installer is a user-mode Win32 DLL that typically writes additional configuration information to the registry, or performs other installation tasks that require information that is not available when an INF is written.

If you enable this setting, co-installers execution will be prevented, and additional configuration software for specific devices (mouses, gaming keyboards, etc) must be downloaded and manually installed from the manufacturer website.

If you disable this setting, co-installers execution will be permitted, which is a significant security risk (potentially dangerous code execution).

</details>
<details>
<summary>Limits print driver installation to Administrators</summary>

- **Registry path(s):** Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint
- **Registry key(s):** RestrictDriverInstallationToAdministrators
- **Values:** 0/1
- **Description:** Determines whether users that aren't Administrator can install print drivers on this computer.

By default, users that aren't Administrators can't install print drivers on this computer.

If you enable this setting or do not configure it, the system will limit installation of print drivers to Administrators of this computer.

If you disable this setting, the system will not limit installation of print drivers to this computer.

Additional information: <https://support.microsoft.com/en-us/topic/kb5005010-restricting-installation-of-new-printer-drivers-after-applying-the-july-6-2021-updates-31b91c02-05bc-4ada-a7ea-183b129578a7>

</details>
<details>
<summary>Enable the strict Authenticode signature verification mechanism</summary>

- **Registry path(s):**
 - Software\Microsoft\Cryptography\Wintrust\Config
 - Software\Wow6432Node\Microsoft\Cryptography\Wintrust\Config
- **Registry key(s):** EnableCertPaddingCheck
- **Values:** 1/`<delete>`
- **Description:** The strict Authenticode signature verification mechanism disallow to add extraneous information in the WIN_CERTIFICATE structure.

</details>
<details>
<summary>Enable AMSI Authenticode signature verification</summary>

- **Registry path(s):** SOFTWARE\Microsoft\AMSI
- **Registry key(s):** FeatureBits
- **Values:** 2/1
- **Description:** This policy enables the verification of the Authenticode signature of the AMSI provider.

If you enable this policy, the AMSI provider must be signed by a trusted certificate.

If you disable or do not configure this policy, the signature verification is disabled (default behavior).

</details>
<details>
<summary>Disable standard users in Safe-Boot mode</summary>

- **Registry path(s):** SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- **Registry key(s):** SafeModeBlockNonAdmins
- **Values:** 0/1
- **Description:** An adversary with standard user credentials that can boot into Microsoft Windows using Safe Mode, Safe Mode with Networking or Safe Mode with Command Prompt options may be able to bypass system protections and security functionalities. To reduce this risk, users with standard credentials should be prevented from using Safe Mode options to log in.

Enabling this policy will prevent standard users to open a session in Safe Mode.

Disabling this policy will allow standard users to open a session in Safe Mode.

</details>
<details>
<summary>Enable additional LSA process hardening</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa
- **Registry key(s):** RunAsPPL
- **Values:** 0/1
- **Description:** Enable this option to allow the LSA process to run as a PPL (Protected Process Light), in order to disallow its debugging.

</details>
<details>
<summary>Disable the SAM server TCP listener</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa
- **Registry key(s):** SamDisableListenOnTCP
- **Values:** 0/1
- **Description:** By default, the SAM server (lsass.exe) is constantly listening on a random TCP port, bound to all network interfaces.

Enabling this policy will disable the TCP listener.

</details>
<details>
<summary>Enable PowerShell Constrained Language Mode</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager\Environment
- **Registry key(s):** __PSLockdownPolicy
- **Values:** 4/0
- **Description:** Enable the Constrained Language Mode for Powershell. This mode disallow several language elements that can be leveraged by attackers to perform sensitive APIs calls.

NOTE: since this policy is only rewritting the __PSLockdownPolicy environment variable, this is not a secure way to enable CLM, and this is intended for defense-in-depth only. CLM can only be securely enforced by AppLocker and/or WDAC.

</details>
<details>
<summary>Allow custom DLL loading list for application processes</summary>

- **Registry path(s):** Software\Microsoft\Windows NT\CurrentVersion\Windows
- **Registry key(s):** LoadAppInit_DLLs
- **Values:** 0/1
- **Description:** The list is located in the registry key HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WindowsAppInit_DLLs

</details>
<details>
<summary>Number of PBKDF2 iterations for cached logons credentials hashing</summary>

- **Registry path(s):** SECURITY\Cache
- **Registry key(s):** NL$IterationCount
- **Values:** 1 to 200000000
- **Description:** For domains logons, if credentials caching is enabled, credentials are stored as MSCacheV2 hashes, derived using the PBKDF2-SHA1 hashing algorithm.

The number of iterations for the PBKDF2-SHA1 algorithm used for hashing operations can be controlled with this policy, with the following logic:

- For a value lower than or equal to 10240, the setting acts as a 1024-mutiplier (for example, setting it to 20 will result in 20480 iterations).
  - For a value greater than 10240, the setting acts as the chosen value (modulo 1024).

The recommended value depends on the target environment, the CPU power available and the performance hit you are willing to tolerate at logon (a high value can incur a net performance penalty for the logon process).

When the policy is enabled, the default value configured is 1954 (2 000 896 rounds). This is the recommended value (at the time of December 2022) for the PBKDF2-HMAC-SHA1 algorithm, considering the compute power of a RTX 4090 GPU in a offline bruteforce attack model.

More information:
 - <https://tobtu.com/minimum-password-settings/>
 - <https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html#pbkdf2>

</details>
<details>
<summary>Disable administrative shares for workstations</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
- **Registry key(s):** AutoShareWks
- **Values:** 0/1
- **Description:** Not recommended, except for highly secure environments.

</details>
<details>
<summary>Disable administrative shares for servers</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
- **Registry key(s):** AutoShareServer
- **Values:** 0/1
- **Description:** Not recommended, except for highly secure environments.

</details>
<details>
<summary>Enable Spectre and Meltdown mitigations</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
  - SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization
- **Registry key(s):**
  - FeatureSettingsOverride
  - FeatureSettingsOverrideMask
  - MinVmVersionForCpuBasedMitigations
- **Values:**
  - 72/8264/8/0/1/64/3
  - 3
  - 1.0
- **Description:** The FeatureSettingsOverride registry key in Windows, typically found under SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management and often managed alongside FeatureSettingsOverrideMask, provides administrators with granular control over software-based mitigations for CPU speculative execution vulnerabilities like Spectre and Meltdown.

These vulnerabilities can potentially allow unauthorized access to sensitive data. Windows implements various mitigations to counter these threats, but they can sometimes introduce performance overhead. The FeatureSettingsOverride key allows for a tailored approach, enabling administrators to selectively enable or disable specific mitigations—such as those for different variants of Spectre (like v2 or Speculative Store Bypass - SSB) and Meltdown—or even to disable all of them if the performance impact is deemed too high for a particular environment, or to apply specific configurations like disabling Hyper-Threading on Intel CPUs in conjunction with these mitigations.

This policy also allows to enable Hyper-V mitigations for virtual machines below version 8.0 (MinVmVersionForCpuBasedMitigations).

Available options:
  - Intel and AMD: enable all available mitigations
  - Intel: enable all mitigations (with Hyper-Threading disabled)
  - Intel: enable mitigations for Spectre v2, Meltdown, and SSB
  - Intel: enable mitigations for Spectre v2 and Meltdown
  - Intel: enable mitigations for Meltdown only
  - AMD and ARM: enable mitigations for Spectre v2
  - Disable all mitigations

</details>
<details>
<summary>Enable Structured Exception Handling Overwrite Protection (SEHOP)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager\kernel
- **Registry key(s):** DisableExceptionChainValidation
- **Values:** 0/1
- **Description:** SEHOP blocks exploits that use the Structured Exception Handling overwrite technique, a common buffer overflow attack.

This policy is only effective on 32 bits systems.

</details>
<details>
<summary>Enable Network Level Authentication (NLA) for RDP connections</summary>

- **Registry path(s):** SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
- **Registry key(s):**
  - SecurityLayer
  - UserAuthentication
  - MinEncryptionLevel
- **Values:**
  - 2
  - 1
  - 3
- **Description:** This policy enable Network Level Authentication for RDP connections, with the following settings:

- TLS is required for server authentication and link encryption.
  - High level of encryption (128 bits) for the data link.
  - User authentication is required at connection time.

Disabling this policy does nothing.

</details>
<details>
<summary>Harden network logons and authentication security</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa
- **Registry key(s):** LmCompatibilityLevel
- **Values:** 5/1
- **Description:** Enable this policy to disable LM and NTLM authentication modes, and enable use of NTLMv2 only.

Disable this policy to restore LM and NTLMv1 capabilities, in addition to NTLMv2.

</details>
<details>
<summary>Disable WDigest protocol</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest
- **Registry key(s):**
  - UseLogonCredential
  - Negotiate
- **Values:**
  - 0
  - 0
- **Description:** Enabling this policy will disable the WDigest protocol, now considered obsolete.

Keeping WDigest enabled could allow an attacker to retrieve plain-text passwords stored in the LSA service with a tool such as Mimikatz, and it is therefore recommended to enable this policy.

</details>
<details>
<summary>Domain credentials caching hardening</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
  - SYSTEM\CurrentControlSet\Control\Lsa
- **Registry key(s):**
  - CachedLogonsCount
  - TokenLeakDetectDelaySecs
- **Values:**
  - 2
  - 30
- **Description:** Enabling this policy modifiy two settings related to how the local system handles domain-related credentials:

- Reduce the caching count (2 cached credentials) of domain-related credentials for offline authentication if no domain controller is available
  - The delay before the credentials are cleared from memory after a logoff is set to 30 seconds.

Those settings reduce the exposure time of credentials to attack tools such as Mimikatz.

NOTE: those settings can prevent a new session opening, if the network is not available, or if a domain controler is not reachable.

</details>
<details>
<summary>Force the randomization of relocatable images (ASLR)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- **Registry key(s):** MoveImages
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling this policy will enable ASLR even for relocatable images that do not explicitly expose this capability.

Disabling this policy will explicitly disable the ASLR mechanism.

</details>
<details>
<summary>Additional registry fix for CVE-2015-6161</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_ALLOW_USER32_EXCEPTION_HANDLER_HARDENING
  - SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_ALLOW_USER32_EXCEPTION_HANDLER_HARDENING
- **Registry key(s):** iexplore.exe
- **Values:** 0/1
- **Description:** Enable this policy to change the registry value FEATURE_ALLOW_USER32_EXCEPTION_HANDLER_HARDENING to 1.

This modification is necessary to fully fix an ASLR bypass vulnerability (CVE-2015-6161). For more information, refer to the MS15-124 security bulletin (<https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2015/ms15-124>).

</details>
<details>
<summary>Additional registry fix for CVE-2017-8529</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX
  - SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX
- **Registry key(s):** iexplore.exe
- **Values:** 0/1
- **Description:** Enable this policy to change the registry value FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX to 1.

This modification is necessary to fully fix an information disclosure vulnerability in Microsoft browsers (CVE-2017-8529). For more information, refer to the related security update guide (<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8529>).

</details>
<details>
<summary>Enable kernel-level shadow stacks</summary>

- **Registry path(s):** SOFTWARE\Policies\Microsoft\Windows\DeviceGuard
- **Registry key(s):** ConfigureKernelShadowStacksLaunch
- **Values:** 0/1
- **Description:** The policy enable kernel-level shadow stacks, also known as Intel CET (Control-flow Enforcement Technology) or AMD Shadow Stack.

Please note that this security function require specific hardware support (AMD Zen 3 or Intel 11th Gen. processors) and OS support (Windows 21H2 or newer).

</details>
<details>
<summary>Disable the WPBT functionnality</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager
- **Registry key(s):** DisableWpbtExecution
- **Values:** 0/1
- **Description:** This policy disable the Windows Platform Binary Table (WPBT) functionnality, that can be used for persistence through an UEFI implant.

</details>
<details>
<summary>Disable Time-Travel Debugging</summary>

- **Registry path(s):** SOFTWARE\Microsoft\TTD
- **Registry key(s):** RecordingPolicy
- **Values:** 0/2
- **Description:** This policy disable the Time-Travel Debugging (TTD) functionnality, that can be used to dump sensitive processes memory content, and to launch third-party executables.

</details>
<details>
<summary>Remove current working directory from DLL search</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager
- **Registry key(s):** CWDIllegalInDllSearch
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** The CWDIllegalInDllSearch registry entry is used to remove the current working directory (CWD) from the DLL search order.

</details>
<details>
<summary>Enable Windows Defender sandbox</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager\Environment
- **Registry key(s):** MP_FORCE_USE_SANDBOX
- **Values:** 0/1
- **Description:** This policy enables the sandbox (content process) for the main process of Windows Defender.

The new content processes, which run with low privileges, aggressively leverage all available mitigation policies to reduce the attack surface. They enable and prevent runtime changes for modern exploit mitigation techniques such as Data Execution Prevention (DEP), Address space layout randomization (ASLR), and Control Flow Guard (CFG). They also disable Win32K system calls and all extensibility points, as well as enforce that only signed and trusted code is loaded.

More information: <https://www.microsoft.com/en-us/security/blog/2018/10/26/windows-defender-antivirus-can-now-run-in-a-sandbox/>

</details>

### Network policies

<details>
<summary>TLS cipher suites configuration</summary>

- **Registry path(s):** SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002
- **Registry key(s):** Functions
- **Values:**
  - TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_CCM_SHA256
  - TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_CCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
  - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  - TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_CCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- **Description:** This policy allows you to select between several TLS cipher suites configuration profiles.

NOTE: for profiles listed with TLS 1.3, please verify that your OS version support TLS 1.3 (Windows 10 v1903 and up) and that TLS 1.3 support is enabled in the Schannel "Protocols" section, otherwise you could break TLS support on your system.

Changing this setting will require a restart of the computer before the setting will take effect. You can check the applied configuration with the Get-TlsCiphersuite cmdlet in a PowerShell session.

Ciphers enabled for each profile, in order of preference:

**Modern (TLS 1.3 only)**

TLS_AES_256_GCM_SHA384
    TLS_AES_128_GCM_SHA256
    TLS_CHACHA20_POLY1305_SHA256
    TLS_AES_128_CCM_SHA256

**Modern (TLS 1.3 and 1.2)**

TLS_AES_256_GCM_SHA384
    TLS_AES_128_GCM_SHA256
    TLS_CHACHA20_POLY1305_SHA256
    TLS_AES_128_CCM_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_CCM
    TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256

**Standard (TLS 1.2 only)**

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_CCM
    TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256

**Backward compatible (TLS 1.3, 1.2, 1.1 and 1.0)**
    TLS_AES_256_GCM_SHA384
    TLS_AES_128_GCM_SHA256
    TLS_CHACHA20_POLY1305_SHA256
    TLS_AES_128_CCM_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_CCM
    TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

**Backward compatible (TLS 1.2, 1.1 and 1.0)**

</details>
<details>
<summary>Configure the IP source routing protection level</summary>

- **Registry path(s):** System\CurrentControlSet\Services\Tcpip\Parameters
- **Registry key(s):** DisableIPSourceRouting
- **Values:** 0/1/2
- **Description:** Allows to choose a protection for source-routed packets.

</details>
<details>
<summary>Configure the IP source routing protection level for IPv6</summary>

- **Registry path(s):** System\CurrentControlSet\Services\Tcpip6\Parameters
- **Registry key(s):** DisableIPSourceRouting
- **Values:** 0/1/2
- **Description:** Allows to choose a protection for source-routed packets.

</details>
<details>
<summary>Enable Kerberos events logging</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
- **Registry key(s):** LogLevel
- **Values:** 0/1
- **Description:** Enable logging of debug events related to Kerberos in the System Event log.

If disabled, this policy disable Kerberos-related events logging (this is the default behavior). Enabling this option is only recommended for debugging purposes. Security auditing of events related to Kerberos events should be configured with Advanced Auditing policies.

</details>
<details>
<summary>Disable IAKerb (Initial and Pass-Through Authentication using Kerberos)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
- **Registry key(s):** DisableIAKerb
- **Values:** 0/1 (0 = Enabled/Default, 1 = Disabled)
- **Description:** Disable the IAKerb feature, which allows Kerberos authentication to function when the client has no direct connectivity to a Domain Controller.

If disabled (registry value set to 0), IAKerb is enabled, allowing target services to proxy Kerberos exchanges. If enabled (registry value set to 1), IAKerb is disabled, potentially falling back to NTLM.

</details>
<details>
<summary>Disable Local KDC (Local Key Distribution Center)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
- **Registry key(s):** DisableLocalKDC
- **Values:** 0/1 (0 = Enabled, 1 = Disabled/Default)
- **Description:** Disable the Local KDC feature, which brings Kerberos-based authentication to local accounts.

If disabled (registry value set to 0), Local KDC is enabled, extending Kerberos semantics to local account scenarios. If enabled (registry value set to 1), Local KDC is disabled, which defaults authentication for local accounts back to NTLM.

</details>
<details>
<summary>Disable SMB 1.0 support (client and server)</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  - SYSTEM\CurrentControlSet\services\mrxsmb10
- **Registry key(s):**
  - SMB1
  - Start
- **Values:**
  - 0
  - 4
- **Description:** Disable SMB 1.0 support (client and server)

</details>
<details>
<summary>Configure the minimum SMB2/3 client dialect supported</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
- **Registry key(s):** MinSMB2Dialect
- **Values:** 514/528/768/770/785/`<delete>`
- **Description:**This policy allows you to configure the minimum SMB2/3 version supported when acting as a client.

It is recommended to select the minimal version supported by your environment.

NOTE: if you select a version above what the remote server can, handle, you will not be able to connect to the remote file share.

Supported versions:
  - SMB 2.0.2
  - SMB 2.1.0 (Windows 7)
  - SMB 3.0.0 (Windows 8)
  - SMB 3.0.2 (windows 8.1)
  - SMB 3.1.1 (Windows 10, Windows Server 2016)

</details>
<details>
<summary>Configure the maximum SMB2/3 client dialect supported</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
- **Registry key(s):** MaxSMB2Dialect
- **Values:**
- **Description:** This policy allows you to configure the maximum SMB2/3 version supported when acting as a client.

It is recommended to not configure this policy and to let the system negociate the most suitable version.

NOTE: do not configure this policy with a value below the one selected in the "Configure minimum SMB2 client dialect supported" policy, otherwise you could break SMB support on your system.

Supported versions:
  - SMB 2.0.2
  - SMB 2.1.0 (Windows 7)
  - SMB 3.0.0 (Windows 8)
  - SMB 3.0.2 (windows 8.1)
  - SMB 3.1.1 (Windows 10, Windows Server 2016)

</details>
<details>
<summary>Enable support for TLS 1.2 only in WinHTTP</summary>

- **Registry path(s):**
 - SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
 - SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
- **Registry key(s):** DefaultSecureProtocols
- **Values:** 2048/`<delete>`
- **Description:** Enabling this policy will enable the support for TLS 1.2 only for applications based on WinHTTP and specifying the WINHTTP_OPTION_SECURE_PROTOCOLS flag.

Disabling this policy will remove the DefaultSecureProtocols value, and restore the default behavior of WinHTTP.

NOTE: for Windows 7, Windows Server 2008 R2, Windows Server 2012 and Windows 8 Embedded, you need to install the KB3140245 update before enabling this policy.

</details>
<details>
<summary>Enable advanced logging for Schannel</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL
- **Registry key(s):** EventLogging
- **Values:** 1/2/3/4/5/6/7/0
- **Description:** Enabling this policy will enable detailed Schannel events generation. You can choose the desired level of verbosity.

Logged events are available in the System event log.

</details>
<details>
<summary>Disable the strong-name bypass feature</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\.NETFramework
  - SOFTWARE\Wow6432Node\Microsoft\.NETFramework
- **Registry key(s):** AllowStrongNameBypass
- **Values:** 0/1
- **Description:** Starting with the .NET Framework version 3.5 Service Pack 1 (SP1), strong-name signatures are not validated when an assembly is loaded into a full-trust xref:System.AppDomain object, such as the default xref:System.AppDomain for the MyComputer zone. This is referred to as the strong-name bypass feature. In a full-trust environment, demands for xref:System.Security.Permissions.StrongNameIdentityPermission always succeed for signed, full-trust assemblies regardless of their signature.

The only restriction is that the assembly must be fully trusted because its zone is fully trusted. Because the strong name is not a determining factor under these conditions, there is no reason for it to be validated. Bypassing the validation of strong-name signatures provides significant performance improvements.

</details>
<details>
<summary>.NET Framework 4: enable strong cryptographic support</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\.NETFramework\v4.0.30319
  - SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
- **Registry key(s):**
  - SchUseStrongCrypto
  - SystemDefaultTlsVersions
- **Values:**
  - 0/1
  - 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.1 and TLS 1.2 in .NET Framework 4.

If this setting is left unconfigured, TLS 1.1 and TLS 1.2 will be enabled by default for applications targeting .NET Framework 4.6 or higher and disabled otherwise.

</details>
<details>
<summary>.NET Framework 2: enable strong cryptographic support</summary>

- **Registry path(s):**
  - SOFTWARE\Microsoft\.NETFramework\v2.0.50727
  - SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727
- **Registry key(s):**
  - SchUseStrongCrypto
  - SystemDefaultTlsVersions
- **Values:**
  - 0/1
  - 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.1 and TLS 1.2 in .NET Framework 2.

If this setting is left unconfigured, TLS 1.1 and TLS 1.2 will be disabled by default.

</details>
<details>
<summary>Multi-Protocol Unified Hello</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\Multi-Protocol Unified Hello\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\Multi-Protocol Unified Hello\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for Multi-Protocol Unified Hello. This protocol will never be used by Schannel SSP.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>PCT 1.0</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for PCT 1.0. This protocol will never be used by Schannel SSP.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>SSL 2.0</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for SSL 2.0. By default for Windows clients, SSL 2.0 is disabled.

Note that SSL 2.0 is insecure and should not be enabled.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>SSL 3.0</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for SSL 3.0.

SSL 3.0 is insecure and considered obsolete, and therefore should not be used. TLS 1.2 or better should be used instead, if possible.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>TLS 1.0</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.0.

TLS 1.0, while historically considered secure, is now being deprecated by Microsoft and should be disabled. However, it may be required for backward compatibility.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>TLS 1.1</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.1.

TLS 1.1, while historically considered secure, is now being deprecated by Microsoft and should be disabled. However, it may be required for backward compatibility.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>TLS 1.2</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.2. TLS 1.2 has no known security issues, and it is recommended to enable it.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>TLS 1.3</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for TLS 1.3. TLS 1.3 has no known security issues, and it is recommended to enable it.

!! WARNING: This setting is only compatible with Windows 10 v1903 and later. Enabling this setting on older OS versions will break Schannel, and you will need to manually remove the SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3 key in the registry to fix it.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>DTLS 1.0</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.0\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.0\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for DTLS 1.0. Supported by Windows 7, Windows Server 2008 R2 and above.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>DTLS 1.2</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.2\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.2\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for DTLS 1.2. Supported by Windows 10 v1607 and above.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>DTLS 1.3</summary>

- **Registry path(s):**
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.3\Client
  - SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\DTLS 1.3\Server
- **Registry key(s):**
  - Enabled
  - DisabledByDefault
- **Values:** 0/1
- **Description:** Enabling or disabling this policy will respectively enable or disable support for DTLS 1.3. Supported by Windows 10 v1903 and above.

Changing this setting will require a restart of the computer before the setting will take effect.

</details>
<details>
<summary>NULL</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\NULL
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for NULL encryption ciphers. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_RSA_WITH_NULL_SHA
    TLS_RSA_WITH_NULL_SHA256

</details>
<details>
<summary>DES 56/56</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\DES 56/56
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for DES 56/56. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_RSA_WITH_DES_CBC_SHA
    TLS_RSA_WITH_DES_CBC_SHA

</details>
<details>
<summary>RC2 40/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC2 40/128. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
    TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5

</details>
<details>
<summary>RC2 56/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 56/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC2 56/128. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_RSA_WITH_DES_CBC_SHA
    TLS_RSA_WITH_DES_CBC_SHA

</details>
<details>
<summary>RC2 128/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 128/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC2 128/128. This is a weak cipher and should not be enabled.

</details>
<details>
<summary>RC4 40/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC4 40/128. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_RSA_EXPORT_WITH_RC4_40_MD5
    TLS_RSA_EXPORT_WITH_RC4_40_MD5

</details>
<details>
<summary>RC4 56/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC4 56/128. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_RSA_EXPORT1024_WITH_RC4_56_SHA

</details>
<details>
<summary>RC4 64/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 64/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC4 64/128. This is a weak cipher and should not be enabled.

</details>
<details>
<summary>RC4 128/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for RC4 128/128. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_RSA_WITH_RC4_128_MD5
    SSL_RSA_WITH_RC4_128_SHA
    TLS_RSA_WITH_RC4_128_MD5
    TLS_RSA_WITH_RC4_128_SHA

</details>
<details>
<summary>Triple DES 168</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for Triple-DES 168. This is a weak cipher and should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_CK_DES_192_EDE_CBC_WITH_MD5
    TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
    TLS_RSA_WITH_3DES_EDE_CBC_SHA

</details>
<details>
<summary>AES 128/128</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\AES 128/128
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for AES 128/128. Note that in order for Windows 2003 to support AES-128, hotfix KB948963 must be installed.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_DHE_DSS_WITH_AES_128_CBC_SHA
    TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521
    TLS_RSA_WITH_AES_128_CBC_SHA
    TLS_RSA_WITH_AES_128_CBC_SHA256

</details>
<details>
<summary>AES 256/256</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\AES 256/256
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for AES 256/256.  Note that in order for Windows 2003 to support AES-256, hotfix KB948963 must be installed.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_DHE_DSS_WITH_AES_256_CBC_SHA
    TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521
    TLS_RSA_WITH_AES_256_CBC_SHA
    TLS_RSA_WITH_AES_256_CBC_SHA256

</details>
<details>
<summary>MD5</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\MD5
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the MD5 hashing algorithm. This is a weak hash algorithm, and it should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

SSL_CK_DES_192_EDE3_CBC_WITH_MD5
    SSL_CK_DES_64_CBC_WITH_MD5
    SSL_CK_RC4_128_EXPORT40_MD5
    SSL_CK_RC4_128_WITH_MD5
    TLS_RSA_EXPORT_WITH_RC4_40_MD5
    TLS_RSA_WITH_NULL_MD5
    TLS_RSA_WITH_RC4_128_MD5

</details>
<details>
<summary>SHA</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\SHA
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the SHA hashing algorithm. This is a weak hash algorithm, and it should not be enabled.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
    TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
    TLS_DHE_DSS_WITH_AES_128_CBC_SHA
    TLS_DHE_DSS_WITH_AES_256_CBC_SHA
    TLS_DHE_DSS_WITH_DES_CBC_SHA
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521
    TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
    TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
    TLS_RSA_WITH_3DES_EDE_CBC_SHA
    TLS_RSA_WITH_AES_128_CBC_SHA
    TLS_RSA_WITH_AES_256_CBC_SHA
    TLS_RSA_WITH_DES_CBC_SHA
    TLS_RSA_WITH_NULL_SHA
    TLS_RSA_WITH_RC4_128_SHA

</details>
<details>
<summary>SHA-256</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\SHA256
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the SHA-256 hashing algorithm.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
    TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521
    TLS_RSA_WITH_AES_128_CBC_SHA256
    TLS_RSA_WITH_AES_256_CBC_SHA256
    TLS_RSA_WITH_NULL_SHA256

</details>
<details>
<summary>SHA-384</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\SHA384
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the SHA-384 hashing algorithm.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521

</details>
<details>
<summary>SHA-512</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\SHA512
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the SHA-512 hashing algorithm.

It is recommended to enable it.

</details>
<details>
<summary>Diffie-Hellman</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the Diffie-Hellman key exchange algorithm.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
    TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
    TLS_DHE_DSS_WITH_AES_128_CBC_SHA
    TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
    TLS_DHE_DSS_WITH_AES_256_CBC_SHA
    TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
    TLS_DHE_DSS_WITH_DES_CBC_SHA

</details>
<details>
<summary>Diffie-Hellman Server-side Key Size</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman
- **Registry key(s):** ServerMinKeyBitLength
- **Values:** 2048/3072/4096
- **Description:** Sets the minimum Diffie-Hellman ephemeral key size for TLS server.

Please see Microsoft Security Advisory 3174644 for more information on DH modulus length. 4096 is the currently recommended minimum value.

</details>
<details>
<summary>Diffie-Hellman Client-side Key Size</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman
- **Registry key(s):** ClientMinKeyBitLength
- **Values:** 2048/3072/4096
- **Description:** Sets the minimum Diffie-Hellman ephemeral key size for TLS client.

Please see Microsoft Security Advisory 3174644 for more information on DH modulus length. 4096 is the currently recommended minimum value.

</details>
<details>
<summary>PKCS</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\PKCS
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the PKCS key exchange algorithm.

It is recommended to enable it.

</details>
<details>
<summary>PKCS Client-side Key Size</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\PKCS
- **Registry key(s):** ClientMinKeyBitLength
- **Values:** 2048/3072/4096
- **Description:** Sets the minimum PKCS ephemeral key size for TLS client.

Please see Microsoft Security Advisory 3174644 or https://support.microsoft.com/en-us/help/3174644/microsoft-security-advisory-updated-support-for-diffie-hellman-key-exc for more information on PKCS modulus length. 4096 is the currently recommended minimum value.

</details>
<details>
<summary>ECDH</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\ECDH
- **Registry key(s):** Enabled
- **Values:** 4294967295 (0xFFFFFFFF)/0
- **Description:** Enabling or disabling this policy will respectively enable or disable support for the Elliptic-Curve Diffie-Hellman key exchange algorithm.

It is recommended to enable it.

Changing this setting will have an effect on whether the following ciphers can be selected for use:

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521

</details>

<details>
<summary>Restrict anonymous access to SAM and Named Pipes/Shares</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
- **Registry key(s):** RestrictNullSessAccess
- **Values:** 0/1
- **Description:** This policy controls whether standard anonymous users (null sessions) can access the SAM database and named pipes/shares.

Enabling this policy restricts anonymous access (value 1).

</details>

### User policies

<details>
<summary>Show file extensions for known file types</summary>

- **Registry path(s):** HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
- **Registry key(s):** HideFileExt
- **Values:** 0/1
- **Description:** By default, Windows Explorer hides file extensions for known file types, which can allow attackers to disguise malicious executable files using fake extensions or icon spoofing.

If you enable this policy setting, Windows Explorer will display file extensions for all known file types (Registry DWORD HideFileExt set to 0).

If you disable this policy setting, Windows Explorer will hide file extensions for known file types (Registry DWORD HideFileExt set to 1).

</details>

<details>
<summary>Disable WPAD Override (User Preference)</summary>

- **Registry path(s):** Software\Microsoft\Windows\CurrentVersion\Internet Settings\Wpad
- **Registry key(s):** WpadOverride
- **Values:** 0/1
- **Description:** This policy controls whether the current user is restricted from using WPAD auto-discovery proxy overrides.

Enabling this policy sets WpadOverride to 1, disabling WPAD-based proxy automatic override behaviors to mitigate spoofing/poisoning risks.

</details>

### Debugging policies

<details>
<summary>Enable Kernel Address Sanitizer</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\Session Manager\Kernel
- **Registry key(s):** KasanEnabled
- **Values:** 0/1
- **Description:** The Kernel Address Sanitizer (KASAN) is a bug detection technology supported on Windows kernel drivers that enables you to detect several classes of illegal memory accesses, such as buffer overflows and use-after-free events.

It requires you to enable KASAN on your system, and recompile your kernel driver with a specific MSVC compiler flag.

This policy controls the support of KASAN in the kernel. Enabling this polic will enable the support of KASAN. Disabling this policy will disable the support of KASAN.

</details>
<details>
<summary>Enable detailed Blue Screens of Death (BSOD)</summary>

- **Registry path(s):** SYSTEM\CurrentControlSet\Control\CrashControl
- **Registry key(s):** DisplayParameters
- **Values:** 0/1
- **Description:** This policy controls whether detailed information is displayed during a Blue Screen of Death (BSOD):

- If this policy is disabled, Windows will not display detailed stop error information on the blue screen (default).
    - If this policy is enabled, Windows will display detailed information, similar to older versions of Windows, which can be useful for troubleshooting the cause of the BSOD.

</details>

## Credits

- The Schannel configuration part is taken almost as-is from the [Crosse/SchannelGroupPolicy](https://github.com/Crosse/SchannelGroupPolicy) repository, a big kudo to him for his work :)
- The legacy MSS and the settings from the Microsoft Security Guide are imported from the Microsoft Security Compliance Toolkit as-is
 - More information: <https://www.microsoft.com/en-us/download/details.aspx?id=55319>
- The Windows Defender Attack Surface Reduction section is ported from Michael Grafnetter's [project](<https://github.com/MichaelGrafnetter/defender-asr-admx>).

Security-ADMX

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README