Deny all access to Removable Storage using Intune

-
 

The Removable Storage Access Control feature enables you to apply policy by using OMA-URI or by using Intune user interface to either user or device, or both. Until now, I have been using Endpoint security profiles to implement device control settings to manage write access to removable drives like USB. However, recently I needed to block access to removable storage altogether and I couldn't make it work using Endpoint security ASR Device control profile. As of writing this blog, these are relevant settings that are available in the Device control profile.


I expected Block Removable storage to work, but it didn't. I couldn't find any obvious errors so decided to do some research.

One way is to use OMA-URI CSPs which are broadly broken down into following categories -


Using Default Enforcement, you can set the default access (Deny or Allow) for all Device Control features (RemovableMediaDevices, CdRomDevices, WpdDevices, PrinterDevices). 

Another way is to use device storage class to block installation, but I wanted to find a better way to administratively manage this.

The method that I found most suitable was 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 and select for 'Removable storage access' as shown below.


9. Select 'All Removable Storage classes: Deny all access'

10. Assign to a device group.

End result

After the policy applies, access to removable storage will be denied.


Deny All registry against RemovableStorageDevices registry key will get configured as expected.



Intune should report compliant against the policy as well.


Happy days..

Comments

  1. AnonymousFebruary 25, 2023 at 9:08 AM

    Simple and useful!

    ReplyDelete
  2. Mack JohnMarch 8, 2023 at 9:35 AM

    You can use Microsoft Intune to configure a policy that denies all access to removable storage devices for managed devices running Windows 10. Here are the steps:

    Sign in to the Microsoft Endpoint Manager admin center.

    Go to Devices > Configuration profiles and click on the "Create profile" button.

    Select "Windows 10 and later" as the platform and "Device restrictions" as the profile type.

    Give the policy a name and description, then select "Removable storage" from the list of available restrictions.

    Set the "Configure removable storage access" setting to "Block all".

    Save and assign the policy to the appropriate devices or groups of devices.

    Once the policy is applied, users will not be able to access any removable storage devices, including USB flash drives, external hard drives, and SD cards. They will receive an error message when trying to access them.

    Note that this policy may impact certain business operations that rely on removable storage devices. Therefore, it is recommended to evaluate the business impact before implementing this policy. Also, make sure to thoroughly test the policy on a small group of devices before deploying it widely.

    ReplyDelete
  3. himajaSeptember 14, 2024 at 6:43 AM

    I truly appreciate the information you’ve shared; it has been incredibly insightful and I highly recommend exploring this c language Online Training It offers comprehensive training that could enhance your skills significantly. Thank you

    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