Security descriptor

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Security descriptors are data structures of security information for securable Windows objects, that is objects that can be identified by a unique name. Security descriptors can be associated with any named objects, including files, folders, shares, registry keys, processes, threads, named pipes, services, job objects and other resources.[1]

Security descriptors contain discretionary access control lists (DACLs) that contain access control entries (ACEs) that grant and deny access to trustees such as users or groups. They also contain a system access control list (SACLs) that control auditing of object access.[2][3] ACEs may be explicitly applied to an object or inherited from a parent object. The order of ACEs in an ACL is important, with access denied ACEs appearing higher in the order than ACEs that grant access. Security descriptors also contain the object owner.

Mandatory Integrity Control is implemented through a new type of ACE on a security descriptor.[4]

Files and folder permissions can be edited by various tools including Windows Explorer, WMI, command line tools like Cacls, XCacls, ICacls, SubInACL,[5] the freeware Win32 console FILEACL,[6][7] the free software utility SetACL, and other utilities. To edit a security descriptor, a user needs WRITE_DAC permissions to the object,[8] a permission that is usually delegated by default to administrators and the object's owner.

See also[edit]

References[edit]

  1. ^ "Securable Objects". Microsoft. 2008-04-24. Retrieved 2008-07-16. 
  2. ^ "What Are Security Descriptors and Access Control Lists?". Microsoft. Retrieved 2008-07-16. 
  3. ^ "DACLs and ACEs". Microsoft. 2008-04-24. Retrieved 2008-07-16. 
  4. ^ http://msdn.microsoft.com/en-us/library/bb625957.aspx What is the Windows Integrity Mechanism?
  5. ^ SubInACL home page
  6. ^ FILEACL home page
  7. ^ "FILEACL v3.0.1.6". Microsoft. 2004-03-23. Retrieved 2008-07-25. [dead link]
  8. ^ "ACCESS_MASK Data Type". Microsoft. 2008-04-24. Retrieved 2008-07-23. 

External links[edit]