Prefer specific encryption cipher algorithms for TLS
Explanation
This policy configures Brave to order its preferred encryption ciphers in TLS 1.3 to reflect a preference for algorithms that have been approved by a specific compliance regime.
Setting this policy does not guarantee that any specific algorithms will be negotiated.
This policy exists to allow server operators who wish to support clients with and without compliance requirements to differentiate between those clients, and only use certain non-default algorithms with increased cryptographic strength for those explicitly configured to prefer them.
Setting the policy to 'cnsa' configures Brave to prefer ciphers required for compliance with the Commercial National Security Algorithm Suite versions 1.0 and 2.0 (CNSA 1.0 and 2.0).
Not setting the policy, or setting it to 'default', configures Brave to use its default ciphers.
Setting this policy is not required for security. The default cryptography used by Brave is strong enough to withstand a brute force attack using the entire power of the Sun.
Setting this policy will cause Brave to be slower when accessing websites.
This policy only affects TLS 1.3 and QUIC; it does not affect earlier versions of TLS.
This policy can be set for the machine and for the user. If set for the user, this policy only affects network requests initiated by the user profile, and may not affect network requests made by Brave to carry out browser-wide background tasks; those are controlled by the machine-level value. If this policy is set at both the machine level and the user level, the machine-level value applies, unless the policy precedence order has been changed by the CloudUserPolicyOverridesCloudMachinePolicy policy.
For versions 155 and below, this policy is machine-wide only.
Example value: cnsa
Registry
HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\BraveHKEY_CURRENT_USER\Software\Policies\BraveSoftware\Brave- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: brave/PreferSlowCiphers
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Prefer specific encryption cipher algorithms for TLS
# Possible options:
# Prefer ciphers satisfying the requirements of CNSA 1.0 and 2.0 = cnsa
# Use Brave's default cipher order = default
Set-ItemProperty -Path $k -Name 'PreferSlowCiphers' -Value 'cnsa' -Type StringDisable
# Disable: brave/PreferSlowCiphers
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": brave/PreferSlowCiphers
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave'
Remove-ItemProperty -Path $k -Name 'PreferSlowCiphers' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Prefer specific encryption cipher algorithms for TLSPreferSlowCiphers | Drop-down listenum | PreferSlowCiphers | REG_SZ |
|
Application
Brave (Brave Software) — November 2026 templates
Official templates downloaded on November 12, 2026.