Create Process with Token
Parent: T1134
Description
Adversaries may create a new process with an existing token to escalate privileges and bypass access controls. Processes can be created with the token and resulting security context of another user using features such as <code>CreateProcessWithTokenW</code> and <code>runas</code>.(Citation: Microsoft RunAs) Creating processes with a token not associated with the current user may require the credentials of the target user, specific privileges to impersonate that user, or access to the token to be used. For example, the token could be duplicated via [Token Impersonation/Theft](https://attack.mitre.org/techniques/T1134/001) or created via [Make and Impersonate Token](https://attack.mitre.org/techniques/T1134/003) before being used to create a process. While this technique is distinct from [Token Impersonation/Theft](https://attack.mitre.org/techniques/T1134/001), the techniques can be used in conjunction where a token is duplicated and then used to create a new process.
Mapped SPARTA techniques
No techniques mapped to this control.
Cross-framework references
Relationships published by the source frameworks themselves, reproduced here with attribution. They are not SafeMode Space mappings and carry no confidence rating of ours.
Countered by 13 in MITRE D3FEND (Defensive Techniques)
- D3-AEMApplication Exception Monitoring
- D3-ANCIAuthentication Cache Invalidation
- D3-CCSACredential Compromise Scope Analysis
- D3-CHCredential Hardening
- D3-CRCredential Revocation
- D3-CROCredential Rotation
- D3-CTSCredential Transmission Scoping
- D3-DUCDecoy User Credential
- D3-MFAMulti-factor Authentication
- D3-OPMOperational Process Monitoring
- D3-RICReissue Credential
- D3-TBToken Binding
- D3-TBAToken-based Authentication
Cite as SafeMode Space, mitre-attack-enterprise T1134.002.