When you remove administrative rights for applications using the Remove Administrative Rightsremove administrative rights action, there is an advanced feature that allows you to apply restricted Security Identifiers (SIDs), which further restricts access to securable objects.
What is a
...
restricted SID?
A Restricted restricted ID is an access token that modifies a user's access to securable objects and controls a user's ability to perform various system-related operations on the local computer.
When a restricted process or thread tries to access a securable object, the system performs two access checks: one using the token's enabled SIDs, and another using the list of restricted SIDs. Access is granted only if both access checks allow the requested access rights. (For more information about restricted SIDs, go to to the Microsoft Developer Network Library at https://msdn.microsoft.com/en-us/library/windows/desktop/aa379316(v=vs.85).aspx.)
When to
...
use restricted ID
Use a restricted SID to further restrict the applications in the sandbox. This is , which you can use as another method of Orangelisting: completely protecting yourself from something that’s new and unknown. Now it may not run correctly within a sandbox but the point being you’re protecting yourself orangelisting. In other words, this is a way to protect yourself against unknown applications if you don’t don't want to go the full level of implement blacklisting.
...
The restricted SID will allow only Read access to the user registry
...
but not to the local machine registry
...
. Also, restricted processes do not have rights to open any network-based resource, such as file servers. As a result, the restricted SID will be able to do very little and
...
apps may not work correctly under this model.
...
The Restricted SID is not new in Windows Server 2008 and Windows Vista, but the access checks based on the token are more significant.-- A Restricted SID denotes (means, or shows) any process that presents (bring, give, or offer) a restricted token. A restricted token has one or more restricting SIDs (SIDs that are used in a separate access check). When restricting SIDs are present, Windows performs two access checks: first is the normal access check, and then the second access check performs the same access check but only against the restricting SIDs in the token. Both access checks must pass to allow the process to access the object.
Access control is the process of authorizing users, groups, and computers to access objects on the network by using permissions, user rights, and object auditing.
access token
An access token contains the security information for a logon session. The system creates an access token when a user logs on, and every process executed on behalf of the user has a copy of the token. The token identifies the user, the user's groups, and the user's privileges. The system uses the token to control access to securable objects and to control the ability of the user to perform various system-related operations on the local computer. There are two kinds of access token, primary and impersonation.
Our restricted process option leverages the Windows functionality that prevents restricted SID's from having Write access to protected resources. (For more details, go to Restricted Tokens on the Windows Dev Center.) Another benefit of this is that Restricted Processes do not have rights to open any network-based resource, such as file servers.
...
Ultimately, apps in the sandbox that have restricted SID applied to them will be severely locked down.
Apply restricted SID
To apply restricted SID, do the following steps:
- In the Thycotic Security Manager Console, click the Policies tab.
- In the file library in the left pane, navigate to Arellia Thycotic Solutions > Application Control > Actions > Process Rights > Remove Administrative Rights.
- In the right pane under Action Type, select the Apply Restricted SID (advanced) check box.
- Click the Save button.
Related
...
links
Process Rights
What is this thing called SID?