Куда я попал?

SECURITM это SGRC система, автоматизирующая процессы в службах информационной безопасности. SECURITM помогает построить и управлять ИСПДн, КИИ, ГИС, СМИБ/СУИБ, банковскими системами защиты.
А еще SECURITM это место для обмена опытом и наработками для служб безопасности.

Подробнее

Access Token Manipulation

Sub-techniques (5)

ID	Name
.001	Token Impersonation/Theft
.002	Create Process with Token
.003	Make and Impersonate Token
.004	Parent PID Spoofing
.005	SID-History Injection

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.(Citation: Pentestlab Token Manipulation) 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.

ID: T1134

Sub-techniques: .001 .002 .003 .004 .005

Tactic(s): Defense Evasion, Privilege Escalation

Platforms: Windows

Permissions Required: Administrator, User

Data Sources: Active Directory: Active Directory Object Modification, Command: Command Execution, Process: OS API Execution, Process: Process Creation, Process: Process Metadata, User Account: User Account Metadata

Version: 2.0

Created: 14 Dec 2017

Last Modified: 03 May 2022

Name	Description
Procedure Examples
HermeticWiper	HermeticWiper can use `AdjustTokenPrivileges` to grant itself privileges for debugging with `SeDebugPrivilege`, creating backups with `SeBackupPrivilege`, loading drivers with `SeLoadDriverPrivilege`, and shutting down a local system with `SeShutdownPrivilege`.(Citation: Qualys Hermetic Wiper March 2022)(Citation: Crowdstrike DriveSlayer February 2022)
SUNSPOT	SUNSPOT modified its security token to grants itself debugging privileges by adding `SeDebugPrivilege`.(Citation: CrowdStrike SUNSPOT Implant January 2021)
PowerSploit	PowerSploit's `Invoke-TokenManipulation` Exfiltration module can be used to manipulate tokens.(Citation: GitHub PowerSploit May 2012)(Citation: PowerSploit Documentation)
AppleSeed	AppleSeed can gain system level privilege by passing `SeDebugPrivilege` to the `AdjustTokenPrivilege` API.(Citation: Malwarebytes Kimsuky June 2021)
Sliver	Sliver has the ability to manipulate user tokens on targeted Windows systems.(Citation: Bishop Fox Sliver Framework August 2019)(Citation: GitHub Sliver C2)
FIN6	FIN6 has used has used Metasploit’s named-pipe impersonation technique to escalate privileges.(Citation: FireEye FIN6 Apr 2019)
Blue Mockingbird	Blue Mockingbird has used JuicyPotato to abuse the `SeImpersonate` token privilege to escalate from web application pool accounts to NT Authority\SYSTEM.(Citation: RedCanary Mockingbird May 2020)
SslMM	SslMM contains a feature to manipulate process privileges and tokens.(Citation: Baumgartner Naikon 2015)
Duqu	Duqu examines running system processes for tokens that have specific system privileges. If it finds one, it will copy the token and store it for later use. Eventually it will start new processes with the stored token attached. It can also steal tokens to acquire administrative privileges.(Citation: Kaspersky Duqu 2.0)
Empire	Empire can use PowerSploit's `Invoke-TokenManipulation` to manipulate access tokens.(Citation: Github PowerShell Empire)
Gelsemium	Gelsemium can use token manipulation to bypass UAC on Windows7 systems.(Citation: ESET Gelsemium June 2021)
Cuba	Cuba has used `SeDebugPrivilege` and `AdjustTokenPrivileges` to elevate privileges.(Citation: McAfee Cuba April 2021)
PoshC2	PoshC2 can use Invoke-TokenManipulation for manipulating tokens.(Citation: GitHub PoshC2)
Hydraq	Hydraq creates a backdoor through which remote attackers can adjust token privileges.(Citation: Symantec Hydraq Jan 2010)
KillDisk	KillDisk has attempted to get the access token of a process by calling `OpenProcessToken`. If KillDisk gets the access token, then it attempt to modify the token privileges with `AdjustTokenPrivileges`.(Citation: Trend Micro KillDisk 2)
Ryuk	Ryuk has attempted to adjust its token privileges to have the `SeDebugPrivilege`.(Citation: CrowdStrike Ryuk January 2019)
MegaCortex	MegaCortex can enable `SeDebugPrivilege` and adjust token privileges.(Citation: IBM MegaCortex)

Mitigation	Description
Mitigations
User Account Management	Manage the creation, modification, use, and permissions associated to user accounts.
Privileged Account Management	Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
Access Token Manipulation Mitigation	Access tokens are an integral part of the security system within Windows and cannot be turned off. However, an attacker must already have administrator level access on the local system to make full use of this technique; be sure to restrict users and accounts to the least privileges they require to do their job. Any user can also spoof access tokens if they have legitimate credentials. Follow mitigation guidelines for preventing adversary use of Valid Accounts. Limit permissions so that users and user groups cannot create tokens. This setting should be defined for the local system account only. GPO: Computer Configuration > [Policies] > Windows Settings > Security Settings > Local Policies > User Rights Assignment: Create a token object. (Citation: Microsoft Create Token) Also define who can create a process level token to only the local and network service through GPO: Computer Configuration > [Policies] > Windows Settings > Security Settings > Local Policies > User Rights Assignment: Replace a process level token. (Citation: Microsoft Replace Process Token) Also limit opportunities for adversaries to increase privileges by limiting Privilege Escalation opportunities.

Detection

If an adversary is using a standard command-line shell, analysts can detect token manipulation by auditing command-line activity. Specifically, analysts should look for use of the runas command. Detailed command-line logging is not enabled by default in Windows.(Citation: Microsoft Command-line Logging) If an adversary is using a payload that calls the Windows token APIs directly, analysts can detect token manipulation only through careful analysis of user network activity, examination of running processes, and correlation with other endpoint and network behavior. There are many Windows API calls a payload can take advantage of to manipulate access tokens (e.g., LogonUser (Citation: Microsoft LogonUser), DuplicateTokenEx(Citation: Microsoft DuplicateTokenEx), and ImpersonateLoggedOnUser(Citation: Microsoft ImpersonateLoggedOnUser)). Please see the referenced Windows API pages for more information. Query systems for process and thread token information and look for inconsistencies such as user owns processes impersonating the local SYSTEM account.(Citation: BlackHat Atkinson Winchester Token Manipulation) Look for inconsistencies between the various fields that store PPID information, such as the EventHeader ProcessId from data collected via Event Tracing for Windows (ETW), Creator Process ID/Name from Windows event logs, and the ProcessID and ParentProcessID (which are also produced from ETW and other utilities such as Task Manager and Process Explorer). The ETW provided EventHeader ProcessId identifies the actual parent process.

References

Связанные риски

Ничего не найдено

Каталоги

Мы используем cookie-файлы, чтобы получить статистику, которая помогает нам улучшить сервис для вас с целью персонализации сервисов и предложений. Вы может прочитать подробнее о cookie-файлах или изменить настройки браузера. Продолжая пользоваться сайтом, вы даёте согласие на использование ваших cookie-файлов и соглашаетесь с Политикой обработки персональных данных.