Open in the explorer

Set exclusions from Brute-Force Protection

Définir les exclusions de Brute-Force Protection

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › Windows Components › Microsoft Defender Antivirus › Remediation › Behavioral Network Blocks › Brute-Force Protection FR: Configuration ordinateur › Stratégies › Modèles d'administration › Composants Windows › Antivirus Microsoft Defender › Mise à jour › Blocs réseau comportementaux › protection Brute-Force
Supported on
At least Windows Server 2016, Windows 10 Version 1607 FR: Windows Server 2016, Windows 10 version 1607 ou versions supérieures
ADMX file
WindowsDefender.admx
Internal name
WindowsDefender/Remediation_BNB_BFP_BruteForceProtectionExclusions

Explanation

Specify IP addresses, subnets or workstation names to exclude from Brute-Force Protection. Excluded IP addresses will not be checked for possible brute force activity.

Note that attackers can spoof excluded addresses and names to bypass protection. Ensure the names are unique and unlikely to be guessed by attackers.

Enter each address or subnet on a new line as a name-value pair:
- Name column: Enter an IP address, subnet name, or workstation name. For example, "1.1.127.0" will exclude this IP address from getting blocked by BFP.
- Value column: Enter "0" for each item

French text from Windows 11 26H2

Spécifiez les adresses IP, les sous-réseaux ou les noms de station de travail à exclure de Brute-Force Protection. Les adresses IP exclues ne sont pas vérifiées pour une activité de force brute possible.

Notez que les attaquants peuvent usurper des adresses et des noms exclus pour contourner la protection. Vérifiez que les noms sont uniques et peu susceptibles d’être devinés par les attaquants.

Entrez chaque adresse ou sous-réseau sur une nouvelle ligne en tant que paire nom-valeur :
- Colonne Nom : entrez une adresse IP, un nom de sous-réseau ou un nom de station de travail. Par exemple, « 1.1.127.0 » empêche cette adresse IP d’être bloquée par BFP.
- Colonne valeur : entrez « 0 » pour chaque élément

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection
Value name
BruteForceProtection_Exclusions
StateValue written
Enablednot defined in the ADMX (see the options below)
Disablednot 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.

The ADMX does not specify the value written when enabled; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled). The commands below use 1/0 as an assumption.

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.

Enable

# Enable: WindowsDefender/Remediation_BNB_BFP_BruteForceProtectionExclusions
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'BruteForceProtection_Exclusions' -Value 1 -Type DWord  # assumed value (not defined in the ADMX)
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection\BruteForceProtectionExclusions'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Brute-Force Protection Exclusions
$items = @{
    '<name1>' = '<value1>'
    '<name2>' = '<value2>'
}  # Replace the values with your own
$items.GetEnumerator() | ForEach-Object { Set-ItemProperty -Path $k -Name $_.Key -Value $_.Value -Type String }

Disable

# Disable: WindowsDefender/Remediation_BNB_BFP_BruteForceProtectionExclusions
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'BruteForceProtection_Exclusions' -Value 0 -Type DWord  # assumed value (not defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": WindowsDefender/Remediation_BNB_BFP_BruteForceProtectionExclusions
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection'
Remove-ItemProperty -Path $k -Name 'BruteForceProtection_Exclusions' -ErrorAction SilentlyContinue
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection\BruteForceProtectionExclusions'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Brute-Force Protection ExclusionsExclusions de protection Brute-ForceRemediation_BNB_BFP_BruteForceProtectionExclusionsList (table)listSoftware\Policies\Microsoft\Windows Defender\Remediation\Behavioral Network Blocks\Brute Force Protection\BruteForceProtectionExclusionsName = value pairs · additiveREG_SZ (values under the key)

Availability

Windows 11

✓ 26H2✓ 25H2✓ 24H2— 23H2— 22H2— 21H2

Windows 10

— 22H2— 21H2— 21H1— 20H2— 2004— 1909— 1903— 1809— 1803— 1709— 1703— 1607— 1511— 1507

Windows Server

✓ 2025— 2022— 2016