T1021.007_cloud-services

T1021.007 Cloud Services

Sub-technique of: T1021

High-Level Description

Adversaries may log into accessible cloud services within a compromised environment using Valid Accounts that are synchronized with or federated to on-premises user identities. The adversary may then perform management actions or access cloud-hosted resources as the logged-on user.

Many enterprises federate centrally managed user identities to cloud services, allowing users to login with their domain credentials in order to access the cloud control plane. Similarly, adversaries may connect to available cloud services through the web console or through the cloud command line interface (CLI) (e.g., Cloud API), using commands such as Connect-AZAccount for Azure PowerShell, Connect-MgGraph for Microsoft Graph PowerShell, and gcloud auth login for the Google Cloud CLI.

In some cases, adversaries may be able to authenticate to these services via Application Access Token instead of a username and password.

Kill Chain Phase

• Lateral Movement (TA0008)

Platforms: IaaS, Identity Provider, Office Suite, SaaS

What to Check

• Identify if Cloud Services technique is applicable to target environment
• Check IaaS systems for indicators of Cloud Services
• Check Identity Provider systems for indicators of Cloud Services
• Check Office Suite systems for indicators of Cloud Services
• Verify mitigations are bypassed or absent (2 known mitigations)
• Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

1. Identify Attack Surface: Determine if the target environment is susceptible to Cloud Services by examining the target platforms (IaaS, Identity Provider, Office Suite).

2. Assess Existing Defenses: Review whether mitigations for T1021.007 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. 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.

Remediation Guide

M1032 Multi-factor Authentication

Use multi-factor authentication on cloud services whenever possible.

M1026 Privileged Account Management

Limit the number of high-privileged domain and cloud accounts, and ensure that these are not used for day-to-day operations. Ensure that on-premises accounts do not have privileged cloud permissions and that isolated, cloud-only accounts are used for managing cloud environments.

Detection

Behavioral Detection of Remote Cloud Logins via Valid Accounts

Risk Assessment

CWE Categories

References

• Atomic Red Team - T1021.007
• MITRE ATT&CK - T1021.007