Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 2 · Lesson 5 of 5
Cloud indicators: stolen keys and disabled audit trails
1 min read
In the cloud, attacks show up as a sequence of API calls in the provider's audit trail, and the sequence is what convicts. A single call such as launching instances can be innocent.
A stolen access key typically follows a recognizable path: discovery of available regions, creation of a new identity with administrator rights, and then costly compute in a region the organization never uses.
The new user is persistence, because it survives rotation of the original key. A misconfigured pipeline or autoscaling policy may build instances, but it has no reason to create an administrator.
Defense evasion comes first in many cloud intrusions. Example: a deployment role stops the organization's audit trail, two minutes later changes a storage bucket policy so anyone can read objects, and an external address then downloads thousands of files, seen only because object-level logging, such as a separate data-event trail or bucket access logs, was still running.
Turning off logging just before exposing data is a decision about being watched, which no template drift, lifecycle rule or replication job makes. Contain the role that made the calls and treat the downloads as exfiltration.
On the exam, when cloud calls are listed with timestamps, read them in order and ask which step only makes sense if someone wanted to avoid being seen.
Check yourself
1. Cloud audit logs (the organization trail plus a separate data-event trail that stayed on) record StopLogging on the organization trail by the role ci-deploy at 02:14, PutBucketPolicy granting s3:GetObject to principal "*" on a customer data bucket at 02:15, and 41,000 GetObject calls from one external address between 02:16 and 03:40. What does the ordering indicate?
2. Cloud audit records show an access key belonging to a build pipeline used from a region the organization never deploys to. Within four minutes the same key calls DescribeRegions, CreateUser, AttachUserPolicy with administrator rights, and RunInstances for twenty GPU instances. What does this indicate?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, AWS CloudTrail User Guide: Logging data events
CompTIA CySA+ cheat sheet: every key fact on one page →