Enable Safe Browsing in Google Chrome using Intune in Windows Devices

-

 


While working with Google Chrome admx policies, a feature called Safe Browsing caught my attention. After doing some research I decided to blog my thoughts on it and how it can be enabled using Intune.

What is Safe Browsing?

Safe Browsing helps in protecting against phishing, social engineering, malware, unwanted software, malicious ads, intrusive ads, and abusive websites or extensions. Chrome contacts Google's servers periodically or real-time (depending on the protection level) to download the most recent Safe Browsing list of unsafe sites and is stored locally in the system. Chrome checks the URL of each site visited or file that is downloaded against this local list. 

When Chrome starts, and on each update of the Safe Browsing list, Chrome scans extensions installed in the browser against the Safe Browsing list. If an extension on the list is found, Chrome will disable the extension.

Different levels of Protection are - 

Enhanced protection (Recommended)

-Automatically warns you about potentially risky sites, downloads, and extensions.
-Automatically warns you about leaked passwords.
-Sends additional info to Google about your activity. Learn more about safe browsing protection.
-Inspects the safety of your downloads and warns you when a file may be dangerous. 
-You can choose to send this file to Google to be scanned for added security.

Standard protection (Default)

-Automatically warns you about potentially risky sites, downloads, and extensions.
-You can choose to get warned about leaked passwords. 
-To improve security on the web for everyone, you can choose to send additional info to Google.

No protection

-Safe Browsing is turned off. 
-Features used in the other protection levels are turned off.
-Safe Browsing might still be turned on in other Google services, like Gmail.

How can you enable it in Intune?

With Google Chrome admx template built into Intune, configuring Google Chrome browser settings have never been easier.

2. Under Devices -> Windows -> Configuration profiles -> Create profile.
3. Under Platform, select Windows 10 & later.
4. Under Profile types, select Templates -> Settings Catalog.
5. Give a name.
6. Configure the following setting and value.


7. Assign to a device or user based group.

Testing & end Results

After the policy is applied, setting for Safe Browsing will come under enterprise management through Intune.



One can simulate the tests by accessing the following URLs.

Malware warning test page



Social engineering\Phishing warning test page -



Conclusion

Safe Browsing provides protection from phishing and malware sites across multiple OS platforms including Windows, iOS and Android. Together with Microsoft Defender for Endpoint, this is a great security addition and highly recommended.

Comments

  1. sonasreeSeptember 30, 2024 at 12:51 PM

    Great post! I really enjoyed reading your perspective. Looking forward to more posts like this.
    Amazon Seller Central UAE
    Best Water Park in Dubai

    ReplyDelete
  2. Margarita MatthewsOctober 12, 2024 at 12:38 PM

    This was such an uplifting read! I’m grateful for the positivity and knowledge you share. Can’t wait for more!

    ReplyDelete

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

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more