administrative templatesUser ConfigurationNot configured

Configure SmartScreen for phishing detection

Enables real-time SmartScreen filter for phishing and malware detection. Critical security control for protecting client data and credentials.

10 May 20264 min —

Policy path: User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Phishing Filter
Supported on: Windows 10, Windows 11, Windows Server 2016 and later

Enables real-time SmartScreen filter for phishing and malware detection. Critical security control for protecting client data and credentials. Security baselines recommend setting it to 1.

Description

Configure SmartScreen for phishing detection is a Windows Group Policy setting located under User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Phishing Filter. It applies to the User Configuration branch and is classified as a Critical-level policy in the Internet Explorer / Edge Legacy category.

Enables real-time SmartScreen filter for phishing and malware detection. Critical security control for protecting client data and credentials.

Microsoft sets the default value to 1 while industry security baselines (CIS, NIST, DISA STIG) recommend 1.

Under the hood, this policy is enforced through the Windows registry at HKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter using the value name EnabledV9. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.

In-depth explanation

This is a critical security control. Misconfiguration creates an exploitable attack path that adversaries actively scan for, and a single overlooked endpoint can compromise the entire fleet. Treat it as a hard baseline requirement rather than an optional tuning knob.

The policy is grouped under Internet Explorer / Edge Legacy, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

Use cases

Apply organization-wide hardening of internet explorer / edge legacy on all domain-joined Windows endpoints.
Roll out a CIS Benchmark-aligned baseline targeting 'Configure SmartScreen for phishing detection' via a dedicated GPO.
Reduce attack surface for accounts that handle privileged credentials or sensitive data.
Standardize the configuration across multiple customer tenants for an MSP-managed fleet.

Security implications

Failing to enforce this policy creates a documented attack path that adversaries actively probe – think Pass-the-Hash, Kerberoasting, NTLM relay, RDP brute-force, LSASS dumping, or token impersonation, depending on the specific control. A single misconfigured endpoint can be enough to pivot to a Domain Admin compromise.

If this policy must remain at default for a legitimate compatibility reason, compensate with a strong detection rule in your EDR/SIEM, isolate the endpoint in its own VLAN, and document the exception with a target remediation date.

How to configure

Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
Create or edit a GPO linked to the OU containing the target user configurations. We recommend a dedicated baseline GPO (e.g. SEC – Internet Explorer / Edge Legacy) instead of editing Default Domain Policy.
Navigate to User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Phishing Filter.
Open Configure SmartScreen for phishing detection and set it to 1.
Click OK and close the editor.
On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Direct registry path: HKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter\EnabledV9. You can apply the same change with PowerShell:

New-Item -Path 'HKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter' -Force | Out-Null
Set-ItemProperty -Path 'HKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter' -Name 'EnabledV9' -Value <value> -Type DWord

Registry mapping

Registry pathHKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter

Value nameEnabledV9

Value typeREG_DWORD

Enabled value1

Disabled value1

Frequently asked questions

What does the Configure SmartScreen for phishing detection Group Policy do?

Enables real-time SmartScreen filter for phishing and malware detection. Critical security control for protecting client data and credentials.

Where do I find this setting in the GPO editor?

Open <code>gpmc.msc</code>, then navigate to <code>User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Phishing Filter</code> and look for <strong>Configure SmartScreen for phishing detection</strong>.

What is the Microsoft default value?

<code>1</code> on a fresh Windows install. Domain-joined machines may inherit a different value if a baseline GPO is already in place.

What value do security baselines recommend?

<code>1</code> – aligned with CIS, NIST, and DISA STIG guidance for current Windows versions.

Can I configure this without a GPO?

Yes, by writing to <code>HKCU\Software\Policies\Microsoft\Internet Explorer\PhishingFilter\EnabledV9</code> directly via <code>regedit</code>, PowerShell, or Intune. A GPO is preferred for centrally managed environments because it survives reimaging and is easier to audit.