Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/54 ▾
  1. 1.Architecture & Log Sources0/5
    1. What each log source can and cannot prove
    2. Time synchronization and log normalization
    3. Sensor placement, logging levels and retention
    4. Cloud, containers, serverless and virtual machines
    5. Identity, directory and federation logs
  2. 2.Indicators of Malicious Activity0/5
    1. Network indicators: DNS abuse, odd protocols and unusual volume
    2. Host indicators: process lineage, masquerading and built-in tools
    3. Persistence and anti-forensics on hosts
    4. Identity and application indicators
    5. Cloud indicators: stolen keys and disabled audit trails
  3. 3.Investigation Tools & Threat Hunting0/5
    1. Packet capture, flow data and network monitoring sensors
    2. Endpoint telemetry, file reputation and sandboxes
    3. SIEM correlation rules and email header analysis
    4. Judging and sharing threat intelligence
    5. Running a threat hunt from hypothesis to detection
  4. 4.Process Improvement, Automation & AI0/5
    1. Choosing what to automate in the SOC
    2. Standard processes: playbooks, runbooks and the case record
    3. Integrations, alert tuning and measuring improvement
    4. AI in security operations: good uses and main risks
    5. AI governance: accountability, audit trails and validation
  5. 5.Vulnerability Scanning Methods0/5
    1. Asset inventory, discovery scans and scan scope
    2. Credentialed, non-credentialed and agent-based scanning
    3. Scanner placement: internal, external and what sits in between
    4. Passive scanning, fragile devices and scan scheduling
    5. Web applications, containers, infrastructure-as-code and baselines
  6. 6.Analyzing Scan Output0/5
    1. Validating findings and spotting false positives
    2. False negatives, failed credentials and stale plugin feeds
    3. Present, reachable, mitigated or already compromised
    4. Reading the kind of finding: patch, configuration, end of life or shared source
    5. Consolidating and deduplicating findings
  7. 7.Prioritization, Mitigation & Controls0/5
    1. Severity scores versus risk, and how CVSS v4.0 is organized
    2. Risk-based prioritization: exploitation, exposure and business context
    3. Remediation paths, change control and verifying the fix
    4. Compensating controls, exceptions, acceptance and transfer
    5. Classifying controls by type and by function
  8. 8.Attack Frameworks & the Response Process0/5
    1. Three attack frameworks, three different questions
    2. Using MITRE ATT&CK: tactics, techniques and procedures
    3. The Cyber Kill Chain: stages and where to break them
    4. The incident response lifecycle, old and new framing
    5. Containment, eradication, recovery and post-incident activity
  9. 9.Incident Response Techniques0/5
    1. Triage and scoping an incident
    2. Collecting evidence: order of volatility and safe access
    3. Integrity, chain of custody and legal hold
    4. Containment techniques that keep the evidence
    5. Eradication, recovery and root cause
  10. 10.Vulnerability Reporting & Communication0/5
    1. From raw scan export to an actionable finding
    2. Matching the report to the audience
    3. Metrics that show direction: trends, aging, recurrence and coverage
    4. Risk acceptance, exceptions, action plans and escalation
    5. Credibility: honest severity, controlled disclosure and AI-drafted reports
  11. 11.Incident Reporting & Metrics0/4
    1. Writing a defensible incident record
    2. Communicating while the incident is live
    3. After-action reports, root cause and lessons learned
    4. Response metrics and how they mislead
Saved in this browser. Move it to another device →
← Indicators of Malicious Activity

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 →