Chrome Browser Enterprise Security Controls using Intune

-

Just like Microsoft provides security benchmark for Edge, Google does the same for Chrome. Well sort of.

While Microsoft provides .admx templates along with readily importable GPO xml files, Google just provides admx templates. Unless you manage chrome browser settings using Google's own browser cloud management service, you are pretty much left with the task of configuring these settings manually.

I recently configured the settings as part of security hardening process for browsers in general and thought of sharing the details here to make it convenient for others. Let's see how you can configure these settings using Intune.

ADMX template in Intune

Ever since Microsoft added Google's admx templates in Intune settings catalog in March 2022, things have never been simpler. If you are unfamiliar with this addition then you can head over to one of my previous blog posts to know more about it.

Chrome Browser Enterprise Security Controls

Google has shared an enterprise security configuration guide that breaks down the settings under the following 3 broad categories:

1. Threat Prevention
2. Privacy
3. Management and Performance

In this blog, I will focus on the first 2 categories as part of the security configuration for the Chrome browser ie. Threat Prevention and Privacy. For convenience, I have extracted the settings in the table below -


Note: To get a complete list of settings, refer to the enterprise security configuration guide.

Intune Settings Catalog

Now we create device configuration policy using settings catalog.

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. Use the policy table provided above in this blog and enable as per your organization's requirements.
Here is a list of settings that I have configured.








7. Assign to a device or user based group.

End Result

Navigate to the chrome://policy on the browser to bring up the list of policy settings applied.


You can click on individual settings to bring up description and other details.


Settings can also be verified in registry under HKLM\Software\Policies\Google\Chrome hive. 


To check the compliance status against each of the settings in Intune, click on 'Per setting status' report.


Conclusion

While Chrome is designed to be a secure browser, organizations can still configure further for added threat prevention. By standardizing default Google Chrome's behavior, users can’t override it and this way organizations can manage settings to reduce security threats and also ensure security for the users personally identifiable information (PII).

It would have been nice if Google released importable baselines just like Microsoft does, but for now one will need do the manual way.

Security all the way..

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

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