MITRE ATT&CK · TA0006 Credential Access

T1528: Steal Application Access Token

Last reviewed:

Detection coverage in DCV across AWS, Azure and GCP for Steal Application Access Token, plus the corresponding Sigma rules in the CloudSigma library. Source data refreshed 2026-05-23.

01 What is T1528?

Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources.

Application access tokens are used to make authorized API requests on behalf of a user or service and are commonly used as a way to access resources in cloud and container-based applications and software-as-a-service (SaaS). Adversaries who steal account API tokens in cloud and containerized environments may be able to access data and perform actions with the permissions of these accounts, which can lead to privilege escalation and further compromise of the environment.

For example, in Kubernetes environments, processes running inside a container may communicate with the Kubernetes API server using service account tokens. If a container is compromised, an adversary may be able to steal the container’s token and thereby gain access to Kubernetes API commands.

Similarly, instances within continuous-development / continuous-integration (CI/CD) pipelines will often use API tokens to authenticate to other services for testing and deployment. If these pipelines are compromised, adversaries may be able to steal these tokens and leverage their privileges.

In Azure, an adversary who compromises a resource with an attached Managed Identity, such as an Azure VM, can request short-lived tokens through the Azure Instance Metadata Service (IMDS). These tokens can then facilitate unauthorized actions or further access to other Azure services, bypassing typical credential-based authentication.

Token theft can also occur through social engineering, in which case user action may be required to grant access. OAuth is one commonly implemented framework that issues tokens to users for access to systems. An application desiring access to cloud-based services or protected APIs can gain entry using OAuth 2.0 through a variety of authorization protocols. An example commonly-used sequence is Microsoft's Authorization Code Grant flow. An OAuth access token enables a third-party application to interact with resources containing user data in the ways requested by the application without obtaining user credentials.

Adversaries can leverage OAuth authorization by constructing a malicious application designed to be granted access to resources with the target user's OAuth token. The adversary will need to complete registration of their application with the authorization server, for example Microsoft Identity Platform using Azure Portal, the Visual Studio IDE, the command-line interface, PowerShell, or REST API calls. Then, they can send a Spearphishing Link to the target user to entice them to grant access to the application. Once the OAuth access token is granted, the application can gain potentially long-term access to features of the user account through Application Access Token.

Application access tokens may function within a limited lifetime, limiting how long an adversary can utilize the stolen token. However, in some cases, adversaries can also steal application refresh tokens, allowing them to obtain new access tokens without prompting the user.

Platforms: Containers, IaaS, Identity Provider, Office Suite, SaaS.

02 Coverage in DCV

DCV maps 10 detections across 3 cloud providers to T1528. Coverage by source:

Source Cloud Findings mapped Avg confidence
Azure Policy Azure 3 0.85
Microsoft Defender for Cloud Azure 3 0.85
AWS Macie AWS 2 0.88
Azure Regulatory Compliance Azure 1 0.90
GCP Chronicle GCP 1 0.90

03 Detect with CloudSigma

CloudSigma has coverage metadata for 10 T1528 rules across 6 platforms. The linked platform page remains the canonical rule surface; this page will embed an example after a rule clears the public embed bar.

CloudSigma has coverage metadata for T1528, but no public example rule clears the embed bar for this page yet. Generate a fresh starting-point rule in CloudSigma from the relevant advisory or threat-research input, then validate it against your local telemetry before enabling it in production.

05 Related techniques

06 FAQ

What is T1528 (Steal Application Access Token)?

Detection coverage in DCV across AWS, Azure and GCP for Steal Application Access Token, plus the corresponding Sigma rules in the CloudSigma library. Source data refreshed 2026-05-23.

Where does T1528 appear in cloud detection sources?

DCV maps 10 cloud-native detections to T1528 across 3 cloud providers, drawn from AWS Macie, Azure Policy, Azure Regulatory Compliance, GCP Chronicle and Microsoft Defender for Cloud.

What MITRE ATT&CK tactic does T1528 belong to?

T1528 is part of MITRE ATT&CK TA0006 Credential Access: How adversaries steal credentials, account names and passwords.

How does CloudSigma fit for T1528?

CloudSigma ships 6 validated Sigma rules for T1528 across AWS CloudTrail, Azure Activity, Entra ID Audit, Entra ID Sign-in, GCP Audit Logs and Okta System Log. Each rule is validated against its source SIEM dialect before publication.

Sources
  • MITRE ATT&CK, https://attack.mitre.org/techniques/T1528/
  • MITRE Tactic TA0006 Credential Access, https://attack.mitre.org/tactics/TA0006/
  • MITRE Center for Threat-Informed Defense, Security Stack Mappings (https://center-for-threat-informed-defense.github.io/security-stack-mappings/)
Last verified: 2026-05-23