This tool enables administrators and penetration testers
to review and audit the permissions of users on a windows
machine.
Windows Permission Identifier can check;
File ACLs
Folder ACLs
Registry ACLs
Services Permissions
Shares
Installation rights
Internet Access and so on.
The GUI enables the administrator to create policies that
can be saved in XML format. The windows machines permissions
are then checked against this policy. This enables administrators
to run checks against existing organizational windows security
baseline documents. Policies can be saved in XML format
and all results can be exported for further use. WARNING: The policy that is included is
a sample of the functionality of the tool. It is not a security
policy that should be followed.
Report
Bugs
& send your own policy files ::
nhouse[at]stationx.net - This is an early version so
please report bugs. I will upload the policy files you send
to me here. I hope to get a collection of good policies.
Sample
Policies :
Coming Soon.
Windows Permission Identifier Screen Shots :
Windows Permission Identifier :
Creating Policies
Windows Permission Identifier :
Running Policy Checks
Windows Permission Identifier :
Results of System Scan
Windows Permission Identifier :
Adding Registry Policy Checks
Windows Permission Identifier :
Editing Registry Permission
Windows Permission Identifier :
Viewing Registry Hives
Q. How do I use the Windows Permission Identifier?
You create a policy. Choose a user you wish to test. Click start.
Export data.
Q. What does it do?
Checks permissions. So if you have a user and you want to know
what that user can do on the machine. Run this tool. It does NOT
check the settings themselves. So for example it will not tell
you what value a registry hive has but what it will tell you is
it the user can change the value of the hive.
Q. How do I check group permissions
Create a user and give them just group access to the group you
want to check. Run the test against the user.
Q. This sample policy check suitable for my windows machine?
NO. The sample policy is a sample only. It does not reflect
that settings we recommend. Your policy should reflect the environment
and functionality of your windows machine. For example a desktop
PC for a standard office user may allow the user to have execute
permission to all the *.exe files within the "program files"
directory. A windows machine being used as an EPOS system my not
allow any permissions at all within the "programs file"
directory.