ACE entry
- ACE entry (
is:|is not:)AccessControlType is(Allow|Deny)IdentityReference(is|is not) domain\user literal string or domain\group literal stringIdentityReference(like|not like) domain\user wildcard expression or domain\group wildcard expressionIdentityReference(matches|not matches) domain\user regular expression or domain\group regular expressionIdentityReference(exists|does not exist)IdentityReference is(enabled|is not enabled)IsInherited is(True|False)InheritanceFlags(is|contains|not contains) comma-separated list of inheritance flags:None,ContainerInherit, andObjectInheritPropagationFlags(is|contains|not contains) comma-separated list of inheritance flags:None,InheritOnly, andNoPropagateInheritFileSystemRights(contains|not contains) comma-separated list of file system rights listed below
Purpose
Indicates the complete set of properties which should be set simultaneously in one or more ACEs. Each operator will check for at least one matching ACE in the relevant ACL:
Notes
This requirement may be repeated in the same section. Properties listed below may be repeated in the same requirement unless otherwise noted.In compound requirements (requirements that allow multiple command/operator/argument triads), semicolons are used as separators. To include a semicolon in the value, quote the value.
For example:AccountName is example; IdentityReference is "semicolon;text".
Each ACE entry requirement will check for matching ACEs in the relevant ACL:
ACE entry is: requirements looks for at least one ACE matching the description given and warns if no matching ACE is found.
ACE entry is not: requirements looks for at least one matching ACE and warns if a matching ACE is found.
| Property | Allowed values | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AccessControlTypeThis property may be used only once in this requirement. |
Example configuration
Example outputLine 7: No ACE in [\\my-unit-fileserver.ad.uillinois.edu\MyShare\] ACL matches AccessControlType is deny. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IdentityReference | An AD user or AD group.
Example configuration[folder:\\my-unit-fileserver.ad.uillinois.edu\MyShare\*]
ACE entry is not: IdentityReference is BUILTIN\Administrators
Example outputLine 5: 1 ACE in [\\jbn-windows.ad.uillinois.edu\MyShare\jbn] ACL matches IdentityReference is BUILTIN\Administrators. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
FileSystemRights | A comma-separated set of permission names from either the basic permissions or the advanced permissions. The table shows the relationship between the basic and advanced permission—each basic permission consists of the following advanced permissions. For example, the basic Write permission on a directory is equivalent to the CreateFiles, CreateDirectories, WriteAttributes, WriteExtendedAttributes, ReadPermissions, and Synchronize advanced permissions.
Advanced permission combination equivalencies
Operators
Example configuration[folder:\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo]
ACE entry is not: FileSystemRights contains FullControl
Example outputLine 5: 3 ACEs in [\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo] ACL match FileSystemRights contains FullControl:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IsInheritedThis property may be used only once in this requirement. |
Example configuration[folder:\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo]
ACE entry is not: IsInherited is True
Example outputLine 5: 3 ACEs in [\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo] ACL match IsInherited is True:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
InheritanceFlags |
The following table lists the equivalent settings for specifying inheritance and/or propagation flags if you want to match the scope listed in the Windows advanced permissions panel user interface. For example, if you want the equivalent scope of the Windows advanced permissions “Subfolders and Files only” scope, then set
Example configuration[folder:\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo]
ACE entry is: InheritanceFlags is None
Example outputLine 5: No ACE in [\\my-unit-fileserver.ad.uillinois.edu\MyShare\foo] ACL matches InheritanceFlags is None. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PropagationFlagsThis property may be used only once in this requirement. |
The following table lists the equivalent settings for specifying inheritance and/or propagation flags if you want to match the scope listed in the Windows advanced permissions panel user interface. For example, if you want the equivalent scope of the Windows advanced permissions “Subfolders and Files only” scope, then set
|
Examples
# No unit staff group should be granted full control. ACE entry is not: AccessControlType is Allow; FileSystemRights contains FullControl; IdentityReference matches ^UOFI\\MyUnit .+ staff$ ACE entry is not: AccessControlType is Allow; FileSystemRights contains FullControl; IdentityReference is UOFI\MyUnit-Storage share users
# Admin users/groups should be granted full control. ACE entry is: AccessControlType is Allow; FileSystemRights contains FullControl; IdentityReference is UOFI\MyUnit Admins ACE entry is: AccessControlType is Allow; FileSystemRights contains FullControl; IdentityReference is NT AUTHORITY\SYSTEM ACE entry is: AccessControlType is Allow; FileSystemRights contains FullControl; IdentityReference is BUILTIN\Administrators
# UOFI\MyUnit Deny Access (the ne'er-do-well group) must be denied all permissions. ACE entry is: AccessControlType is Deny; FileSystemRights contains FullControl; IdentityReference is UOFI\MyUnit Deny Access
