Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1134_access-token-manipulation
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls.
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 5 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our compliance audit requires an explicit tally of official MITRE ATT&CK mitigation strategies for T1134. How many distinct mitigations exist for access token manipulation, and what are their M-identifiers?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies exactly 2 official mitigations for access token manipulation. | Missed | Passed |
| Names M1018 as an applicable mitigation control. | Passed | Passed |
| Names M1026 as an applicable mitigation control. | Passed | Passed |
The instructions your model reads when the skill loads.
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls. Windows uses access tokens to determine the ownership of a running process. A user can manipulate access tokens to make a running process appear as though it is the child of a different process or belongs to someone other than the user that started the process. When this occurs, the process also takes on the security context associated with the new token.
An adversary can use built-in Windows API functions to copy access tokens from existing processes; this is known as token stealing. These token can then be applied to an existing process (i.e. Token Impersonation/Theft) or used to spawn a new process (i.e. Create Process with Token). An adversary must already be in a privileged user context (i.e. administrator) to steal a token. However, adversaries commonly use token stealing to elevate their security context from the administrator level to the SYSTEM level. An adversary can then use a token to authenticate to a remote system as the account for that token if the account has appropriate permissions on the remote system.
Any standard user can use the runas command, and the Windows API functions, to create impersonation tokens; it does not require access to an administrator account. There are also other mechanisms, such as Active Directory fields, that can be used to modify access tokens.
Platforms: Windows
Identify Attack Surface: Determine if the target environment is susceptible to Access Token Manipulation by examining the target platforms (Windows).
Assess Existing Defenses: Review whether mitigations for T1134 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.