MITRE ATT&CK T1021.007: Cloud Services
When to use this skill
Use this skill when the task involves T1021.007, Cloud Services, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1021.007
- Technique name: Cloud Services
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1021/007
- Tactics: lateral-movement
- Platforms: IaaS, Identity Provider, Office Suite, SaaS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK 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.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.references/known-threat-context.md: ATT&CK relationship context with attribution cautions.templates/detection-brief.md: detection engineering brief template.templates/hunt-plan.md: threat hunt plan template.templates/incident-response-note.md: incident response note template.templates/coverage-assessment.md: ATT&CK coverage assessment template.scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Multi-factor Authentication
- Privileged Account Management
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT29 (intrusion-set)
- C0027 (campaign)
- Scattered Spider (intrusion-set)
- Storm-0501 (intrusion-set)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ent-t1021-007-cloud-services3description: Analyze MITRE ATT&CK T1021.007 Cloud Services in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1021.007, Cloud Services, or enterprise ATT&CK. Adversaries may log into accessible cloud services within a compromised environment using [Valid Accounts](https://attack.mitre.org/techniques/T1078) that are synchronized with or federated to on-premises user identitie…4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h5---67# MITRE ATT&CK T1021.007: Cloud Services89## When to use this skill1011Use this skill when the task involves T1021.007, Cloud Services, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.1213## Technique context1415- ATT&CK domain: enterprise16- ATT&CK ID: T1021.00717- Technique name: Cloud Services18- Type: sub-technique19- ATT&CK URL: https://attack.mitre.org/techniques/T1021/00720- Tactics: lateral-movement21- Platforms: IaaS, Identity Provider, Office Suite, SaaS22- Required permissions: Not specified23- Effective permissions: Not specified24- Defenses bypassed: Not specified2526## ATT&CK description2728Adversaries may log into accessible cloud services within a compromised environment using [Valid Accounts](https://attack.mitre.org/techniques/T1078) 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. 2930Many 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](https://attack.mitre.org/techniques/T1059/009)), using commands such as <code>Connect-AZAccount</code> for Azure PowerShell, <code>Connect-MgGraph</code> for Microsoft Graph PowerShell, and <code>gcloud auth login</code> for the Google Cloud CLI.3132In some cases, adversaries may be able to authenticate to these services via [Application Access Token](https://attack.mitre.org/techniques/T1550/001) instead of a username and password.3334## Agent workflow35361. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.372. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.383. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.394. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.405. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.416. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4243## Bundled resources4445- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.46- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.47- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.48- `templates/detection-brief.md`: detection engineering brief template.49- `templates/hunt-plan.md`: threat hunt plan template.50- `templates/incident-response-note.md`: incident response note template.51- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.52- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.53- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5455To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.5657## Detection guidance5859No ATT&CK detection guidance was present in the source STIX object.6061## Useful telemetry and data sources6263- Not specified in the STIX object.6465## Mitigations to consider6667- Multi-factor Authentication68- Privileged Account Management6970## Known threat context7172Use these examples only as contextual leads, not as proof that an observed event is this technique:7374- APT29 (intrusion-set)75- C0027 (campaign)76- Scattered Spider (intrusion-set)77- Storm-0501 (intrusion-set)7879## Recommended output pattern8081When responding with this skill, structure the answer as:8283- Assessment: whether the evidence supports this ATT&CK mapping and why.84- Evidence: specific indicators, logs, behaviors, and assumptions.85- Detection: telemetry sources, analytic logic, and tuning considerations.86- Response: containment, eradication, recovery, and validation actions.87- Coverage gaps: missing logs, sensors, controls, or environmental details.88- References: include the ATT&CK URL and any user-provided evidence references.
santosomar