TA0011Tactic 13 of 15

Command and Controlin cloud and AI environments

How do attackers control compromised cloud workloads?

ATT&CK v20.1Updated Official tactic page
Command and Control technique map18 techniques in Command and Control, 0 of them apply to cloud platforms. Highlighted: T1071, T1102, T1105, T1090.T1071T1090T1102T1105TA001118 TECHNIQUES
Key for cloud (this guide)Applies to cloud platformsOther platforms
18
Techniques
27
Sub-techniques
0
Apply to cloud platforms
4
Defensive controls
2
Detection signals

What the tactic means

Command and Control covers how adversaries communicate with systems they control inside your environment — sending instructions and receiving results. Adversaries usually disguise this traffic as normal web or DNS activity, and choose channels the victim’s network already allows.

The adversary is trying to communicate with compromised systems to control them.

Command and Control consists of techniques that adversaries may use to communicate with systems under their control within a victim network. Adversaries commonly attempt to mimic normal, expected traffic to avoid detection. There are many ways an adversary can establish command and control with various levels of stealth depending on the victim’s network structure and defenses.

MITRE ATT&CK TA0011 description

Why it matters: cloud, AWS and AI

Cloud environments

Compromised instances and containers need to reach the adversary. Cloud workloads often have unrestricted outbound internet access, and adversaries hide traffic in common web services.

AWS specifics

Outbound HTTPS from instances or containers, DNS queries, and use of legitimate cloud services (object storage, serverless endpoints) as relays are common. Route 53 Resolver query logs, VPC flow logs and GuardDuty provide visibility.

AI & workloads

Agents with web-fetch tools or plugins can be steered to contact adversary infrastructure; ATLAS tracks the use of AI service APIs for command and control.

What the attacker is trying to achieve

  1. 01Maintain interactive control
  2. 02Receive instructions and send results
  3. 03Blend with normal web traffic

Techniques that matter most in cloud

What it needs, and what breaks it

Attacker needs

  • Outbound network access from compromised workload

Defenders control

  • Default-deny egress for workloads that do not need the internet
  • VPC endpoints for AWS services
  • DNS firewalling and query logging
  • Restricted agent egress

Detection signals and telemetry

Signal
  • Connections to known-bad or newly seen domains

    GuardDutyRoute 53 Resolver query logs
  • Unusual outbound volume from workloads

    VPC flow logs

For leadership

What this means for the business

Many production workloads have unrestricted internet access by default. Restricting it is a design decision that limits both command-and-control and exfiltration.

Common misconceptions

Myth

“HTTPS to popular services is safe.”

Reality

Adversaries routinely use well-known services to hide control traffic.

Practical security checklist

0 of 3 done

Saved only in this browser. Nothing is sent to Securitain.

Related attack scenarios

Where Securitain fits

  • Outside Securitain’s current scopeReal-time detection of attacker activity in CloudTrail is not part of Securitain’s current assessment — use GuardDuty, a SIEM or your SOC for that.

Official sources and references

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain