Enable Enhanced Phishing Protection on Windows 11 22H2 using Intune

-
 

Microsoft recently released next version of  Windows 11 known as 22H2. This feature update comes with many new security capabilities and one of such capability is Enhanced Phishing Protection.

As part of Microsoft Defender SmartScreen, Enhanced Phishing Protection helps in protecting Microsoft school or work passwords against phishing and unsafe usage on sites and apps. It currently supports the following 3 scenarios:

1. If users type their work or school password on any Chromium browser, into a site deemed malicious by Microsoft Defender SmartScreen, Enhanced Phishing Protection will alert them. It will also prompt them to change their password so attackers can't gain access to their account.

2. Reusing work or school passwords on sites and apps will prompt them to change their password.

3. Storing plaintext passwords in text editors such as Notepad or Office applications like Word, will result in a warning and a recommendation for removing the password from the file.

If you are an organization that still uses passwords for Windows sign-in or in early stage of password-less journey and an early adopter of Windows 11 22h2, then it is a no brainer to enable this feature.

Luckily Enhanced Phishing Protection works with both Group Policy and mobile device management (MDM) settings. Based on how you set up Enhanced Phishing Protection, you can customize which phishing protection scenarios will show users warning dialogs. Now by default, Enhanced Phishing Protection is deployed in audit mode, preventing notifications to the users for any protection scenarios. However, lets see what all settings are available.


As of writing this blog, currently these settings are not available in the Endpoint security. However, they are available in Settings catalog or can be configured as a custom policy using OMA-URI. I chose to use Settings catalog. Here is how you can do it -

2. Browse to Devices – Windows – Configuration Profiles
3. Click Create Profile
4. Select Platform as Windows 10 and later
5. Select Profile as Settings catalog
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search for 'Phishing' and select the following.


9. Assign to a group of devices or users. (Note: Since this feature is only available with Windows 11 22h2, the settings will only apply to this build)

End Result

Once the policy applies, the user will start seeing relevant warnings.

When user tries to save the Windows logon password in Notepad

When user tries to save the Windows logon password in Word

When user tries to reuse the Windows logon password on a website.

Event Viewer will show events of policy being applied successfully.





Last but not the least, compliance against the settings can be validated in Intune.


Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Intune: UAC Elevation Prompt Behavior for Standard Users

-
Image
Implementing and maintaining a good security posture is an integral part of overall IT security governance for most organizations now. While you want to harden the security of infrastructure and give least number of privileges to your end users, sometimes you may need to cut back on the restrictions to ensure a good user experience and an effective IT support process. Recently, I had a requirement where the customer wanted to ease the restriction on the end user devices to make the helpdesk support process more efficient. This involved easing the UAC level access for the Standard users and if you are managing your devices using Intune, then this blog may just help you. Let us see what all is involved and some of the ways that you can use to implement this easily. Policy CSP – LocalPoliciesSecurityOptions LocalPoliciesSecurityOptions has many CSP settings and if you are managing these settings at an individual level, then the CSP that we need to concern ourselves with here is U
Read more