Transport Layer Security (TLS) 1.3 introduces significant cryptographic performance and privacy improvements over TLS 1.2 by eliminating legacy insecure cipher suites and enforcing forward secrecy across every handshake. In Windows 11, the native Schannel security support provider enables TLS 1.3 by default. Enterprise administrators can audit, prioritize, and restrict specific TLS 1.3 cipher suites via PowerShell to comply with strict regulatory encryption standards.
Understanding TLS 1.3 Cipher Suite Architecture in Windows
Unlike TLS 1.2, which combined authentication, key exchange, and bulk encryption into monolithic strings, TLS 1.3 standardizes on streamlined, modern AEAD cipher suites:
TLS_AES_256_GCM_SHA384: 256-bit AES encryption in Galois/Counter Mode with SHA-384 message authentication (highest security level).TLS_AES_128_GCM_SHA256: 128-bit AES-GCM with SHA-256 (standard balance of speed and security).TLS_CHACHA20_POLY1305_SHA256: Modern stream cipher optimized for hardware lacking dedicated AES acceleration.
Auditing Active TLS Cipher Suites via PowerShell
Launch PowerShell as Administrator and query the system cipher suite order:
# Retrieve current system cipher suite list
Get-TlsCipherSuite | Select-Object -Property Name, Certificate, Cipher, Hash
To inspect only TLS 1.3 cipher suites:
Get-TlsCipherSuite | Where-Object { $_.Name -like "TLS_AES*" -or $_.Name -like "TLS_CHACHA*" }
Prioritizing TLS 1.3 Cipher Suites via PowerShell
To prioritize AES-256-GCM as the premier cipher suite across all outbound client connections:
# Prioritize TLS_AES_256_GCM_SHA384 at the top of the suite order
Enable-TlsCipherSuite -Name "TLS_AES_256_GCM_SHA384" -Position 0
# Set TLS_AES_128_GCM_SHA256 as secondary preferred suite
Enable-TlsCipherSuite -Name "TLS_AES_128_GCM_SHA256" -Position 1
Enforcing TLS 1.3 Protocol Activation in Schannel Registry
Confirm that TLS 1.3 client and server protocols are explicitly enabled in the Schannel registry:
# Define Schannel TLS 1.3 client registry path
$Tls13ClientPath = "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client"
# Ensure path exists
if (-not (Test-Path $Tls13ClientPath)) {
New-Item -Path $Tls13ClientPath -Force | Out-Null
}
# Enable TLS 1.3 client protocol
New-ItemProperty -Path $Tls13ClientPath -Name "Enabled" -Value 1 -PropertyType DWord -Force
New-ItemProperty -Path $Tls13ClientPath -Name "DisabledByDefault" -Value 0 -PropertyType DWord -Force
Verifying TLS 1.3 Outbound Handshakes
Test TLS 1.3 negotiation against modern HTTPS endpoints:
# Test TLS 1.3 handshake via .NET SslStream
$TcpClient = New-Object System.Net.Sockets.TcpClient("cloudflare.com", 443)
$SslStream = New-Object System.Net.Security.SslStream($TcpClient.GetStream())
$SslStream.AuthenticateAsClient("cloudflare.com")
# Display negotiated protocol and cipher suite
[PSCustomObject]@{
SslProtocol = $SslStream.SslProtocol
CipherAlgorithm = $SslStream.CipherAlgorithm
CipherStrength = $SslStream.CipherStrength
}
$TcpClient.Close()
The output confirms negotiation over Tls13 with full 256-bit encryption active.