Traditionally I have used NTFS permissions to restrict access for standard user accounts to certain executable files.
Most notably is reg.exe, when providing a managed workstation (SOE) to prevent standard users from accessing the registry. When coupled with Group Policy to restrict access to registry editing tools (regedit) it is effective in preventing access.
One alternative I had overlooked until recently was Software Restriction Policies. These can be applied as per most policies at the local or Group Policy level.
Summary:
A user with full permissions to a directory can be blocked from executing files using the Software Restriction Policies.
Using the "Disallowed" Security level, prevents execution regardless of the NTFS permissions the user holds, using Unrestricted honours the user account NTFS permissions.
Example:
User has Full Control of the folder C:\Test
Create a New Path rule by running GPEdit.msc
Local Security Policy / Software Restriction Policies / Additional Rules (Same location for a GPO)
New Path Rule
Path: C:\Test
Security Level: Disallowed
When the user executes a file from the path, the system prevents execution of the file.
C:\test\notepad.exe
The system cannot execute the specified program.
This could be applied to the SOE reg.exe scenario outlined earlier.
Another use I can see for this is to have a "scripts / tools" directory that the system can execute from Using a local System scheduled task, but those pesky users can't.
The following Microsoft articles list there purported uses of the facility, but this is interesting if nothing else and provides another tool for SOE builds that I hadn't considered using before.
Other rules can be specified to identify software including
Hash. A cryptographic fingerprint of the file
Certificate. A software publisher certificate used to digitally sign a file
Path. The local or universal naming convention (UNC) path of where the file is stored
See also "Registry Paths" as outlined in the reference documents.
Zone. Internet Zone
Using Software Restriction Policies to Protect Against Unauthorized Software
http://technet.microsoft.com/en-us/library/bb457006(TechNet.10).aspx
How Software Restriction Policies Work
http://technet2.microsoft.com/windowsserver/en/library/d24bc8c8-27cc-47ba-9b02-78d9d801e9371033.mspx?mfr=true
Blog Index
-
▼
2008
(40)
-
►
May
(10)
- Powershell WMI one-liners
- Installing device drivers without the device being...
- Effective permissions may be reported incorrectly
- MDT 2008 Storage Drivers - 0x0000007B error
- NVIDIA Screen resolution resets
- Mandatory ZTI advertisement does not run
- You receive message "Please wait while the domain ...
- Decrypt / Encrypt string in ROT-13
- Understanding the Most Frequently Used (MFU) regis...
- Windows XP reboots during setup
-
►
April
(24)
- Access a Network Resource Alias using Computer Acc...
- ZTI DefaultDomainName setting lost
- ZTITattoo.wsf - OSD clears TaskSequence registry e...
- PowerShell appears to "hang" when executed from a ...
- Need to move the Microsoft Deployment Distribution...
- Fix Broken Windows Scripting Host
- Set Location in "Regional and Language Options" co...
- Dial up connections do not use LAN proxy settings
- Ever needed an Automated RunAs?
- LTI deployment fails with error "A connection to t...
- ZTI PreInstall phase fails with error 214700057
- ZTI Package update leaves .$M$ file(s)
- Error creating ZTI CD when using local SMS Console...
- Various WMIC commands
- Various DSQUERY commands
- Using ImageX to compress a WIM file after modifica...
- When installing Windows XP on ESX you may receive ...
- VMWare Workstation - After WinPE deploy of sysprep...
- Pre-Stage Computer resource record in SMS
- Windows Path issues may prevent Group Policy from ...
- Hiding or Displaying Default Desktop icons
- ImportGPO.wsf may not import GPO's using a Migrati...
- Permissions for Moving a Computer Account
- Cached logons are available by default on a domain...
-
►
May
(10)
Wednesday, June 25, 2008
Preventing users from executing files using Software Restriction Policies
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment