WDevSec 1.2
There are many ways to customize security of non-volatile objects (files, folders, services, registry keys etc.
|
There are many ways to customize security of non-volatile objects (files, folders, services, registry keys etc.) on Windows systems. However when it comes to volatile Windows kernel objects which are created mainly by drivers and services (allowing them to be contacted via these objects) and recreated every time the creator driver/process starts the situation is much worse.
There are some GUI tools (e.g. WinObj and WinObjEx) which can change access permissions (DACLs) of these objects, but tools for automated securing of them seem to be pretty rare. This is what WDevSec does.
WDevSec is a command line utility able to view and change access permissions (DACLs) on Windows kernel objects. It can be used with Task Scheduler or Group Policy startup scripts to automate execution of it and set appropriate access permissions on every system startup.
WDevSec can process devices, named pipes, files, sections, events, mutants (mutexes), semaphores, timers, event pairs, I/O completion ports, registry keys, directory objects, folders, symbolic links and other objects (including LPC ports) with /A option.
WDevSec can also run in background and automatically set DACLs when it receives device change notification or on specified time intervals.
With WDevSec comes with another utility - WDevList. This utility can list Windows kernel objects and (optionally) execute WDevSec on them. WDevList can be used in situations where several objects with similar names exist and they all need to be secured. WDevList can also provide bare listing as output for processing by other programs (such as batch scripts).
WDevSec uses SDDL strings containing only DACL. All account names in these strings are automatically turned to SIDs.
WDevSec may be a great solution to customize access to some Windows features as well as to third party software components. Almost every software which provides some kind of services to other programs accepts communication via some Windows kernel objects. Drivers normally create device objects, user mode software usually uses named pipes (objects in \??\PIPE\ device), Windows components often uses LPC ports.
tags
kernel objects windows kernel access permissions can also lpc ports wdevlist can other programs some windows named pipes wdevsec can objects and these objects change access

Download WDevSec 1.2
Similar software
WDevSec 1.2
Dâvis Moðenkovs
There are many ways to customize security of non-volatile objects (files, folders, services, registry keys etc.
PC Power Sweeper 2.0.0.1
Malware Sweeper
PC Power Sweeper - control various messengers and browsers options, repair registry keys, shred files and folders to free disk space, and much, much more.
AccessChk 1.03
Mark Russinovich
As a part of ensuring that they've created a secure environment Windows administrators often need to know what kind of accesses specific users or groups have to resources including files, directories, Registry keys, and Windows services.
Registry Trash Keys Finder 3.9.4.0
SNC
Registry Trash Keys Finder is a useful registry trash finder utility that will help you very much.
System Protector 1.9
MSoft
Powerfull Windows XP Tweaker!
Using this program, you can customize your Windows, System folders, security and more.
RegdatXP 2.2
H.Ulbrich
RegdatXP reads non active WinNT/2K/XP/2K3 registry files like Ntuser.
RegCool 3.106
Kurt Zimmermann
RegCool is a full-featured Registry editor and manager.
X-Ways Security 1.3
X-Ways Software
X-Ways Security is the shredder for the digital age.
Winalysis 3.1
Winalysis Software Inc
Winalysis is a useful monitor utility for changes to files, the registry, users, services, groups, security policies, and more.
AccessEnum 1.32
Bryce Cogswell
While the flexible security model employed by Windows NT-based systems allows full control over security and file permissions, managing permissions so that users have appropriate access to files, directories and Registry keys can be difficult.