Conducting Cloud Incident Response
Overview
Cybersecurity skill for conducting cloud incident response. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"conducting cloud incident response"
"Responds to security incidents in cloud environments (AWS, Azure, GCP) by perfor"
Cloud security posture management (CSPM) alerts on unauthorized resource changes
CloudTrail, Azure Activity Logs, or GCP Audit Logs show suspicious API calls
Cloud access keys or service principal credentials are suspected compromised
Unauthorized compute instances, storage buckets, or IAM changes are detected
A cloud-hosted application is breached and attacker activity spans cloud services
Do not use for on-premises-only incidents with no cloud component; use standard enterprise IR procedures.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Cloud-native logging enabled and centralized: AWS CloudTrail (all regions), Azure Activity/Sign-in Logs, GCP Cloud Audit Logs
- IR-specific cloud IAM roles pre-provisioned with read-only forensic access
- Isolated forensic account/subscription/project for evidence preservation
- Cloud incident response runbooks specific to each cloud provider
- Cloud-native security tools: AWS GuardDuty, Azure Defender for Cloud, GCP Security Command Center
- Network traffic logging: VPC Flow Logs (AWS/GCP), NSG Flow Logs (Azure)
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Scope the Analysis — Define what cloud incident response artifacts or data sources to examine and the investigation timeline.
- Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
- Extract Key Indicators — Parse and extract relevant cloud incident response data points from collected artifacts.
- Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
- Build Timeline — Construct a chronological sequence of events related to cloud incident response.
- Document Analysis — Write findings report with evidence, conclusions, and recommendations.
Tools
- Forensic Toolkit — Evidence collection and analysis
- Timeline Tools — Chronological event reconstruction
- Log Analysis Platform — Centralized log parsing and search
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: conducting-cloud-incident-response3description: Use when responds to security incidents in cloud environments (AWS, Azure,4 GCP) by performing identity-based containment, cloud-native log analysis, resource5 isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure.6 Activates for requests involving cloud incident response, AWS security incident,7 Azure compromise, GCP breach, cloud forensics, or cloud identity compromise. . Use8 when working with conducting cloud incident response.9domain: cybersecurity10tags:11- cloud-IR12- AWS-forensics13- Azure-incident-response14- GCP-security15- identity-containment16subdomain: incident-response17mitre_attack:18- T107819- T153720- T158021- T152522version: 1.0.023author: oyi7724license: Apache-2.025nist_csf:26- RS.MA-0127- RS.MA-0228- RS.AN-0329- RC.RP-0130category: cybersecurity31metadata:32 source: https://skillmd.com/skills/oyi77/conducting-cloud-incident-response33---3435# Conducting Cloud Incident Response3637## Overview3839Cybersecurity skill for conducting cloud incident response. Follows industry best practices and security standards.4041## When to Use42**Trigger phrases:**43- "conducting cloud incident response"44- "Responds to security incidents in cloud environments (AWS, Azure, GCP) by perfor"454647- Cloud security posture management (CSPM) alerts on unauthorized resource changes48- CloudTrail, Azure Activity Logs, or GCP Audit Logs show suspicious API calls49- Cloud access keys or service principal credentials are suspected compromised50- Unauthorized compute instances, storage buckets, or IAM changes are detected51- A cloud-hosted application is breached and attacker activity spans cloud services5253**Do not use** for on-premises-only incidents with no cloud component; use standard enterprise IR procedures.545556## When NOT to Use5758- When you lack proper authorization for testing59- For production systems without change management60- When the task requires legal or compliance expertise beyond technical scope616263## Prerequisites6465- Cloud-native logging enabled and centralized: AWS CloudTrail (all regions), Azure Activity/Sign-in Logs, GCP Cloud Audit Logs66- IR-specific cloud IAM roles pre-provisioned with read-only forensic access67- Isolated forensic account/subscription/project for evidence preservation68- Cloud incident response runbooks specific to each cloud provider69- Cloud-native security tools: AWS GuardDuty, Azure Defender for Cloud, GCP Security Command Center70- Network traffic logging: VPC Flow Logs (AWS/GCP), NSG Flow Logs (Azure)7172## Workflow7374```python75# Example: IOC detection76import re7778IOC_PATTERNS = {79 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",80 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",81 "hash_md5": r"\b[a-f0-9]{32}\b",82 "hash_sha256": r"\b[a-f0-9]{64}\b",83}8485def extract_iocs(text: str) -> dict:86 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}87```88891. **Scope the Analysis** — Define what cloud incident response artifacts or data sources to examine and the investigation timeline.902. **Preserve Evidence** — Create forensic copies of relevant data. Maintain chain of custody documentation.913. **Extract Key Indicators** — Parse and extract relevant cloud incident response data points from collected artifacts.924. **Correlate Findings** — Cross-reference extracted data with other sources (threat intel, logs, timelines).935. **Build Timeline** — Construct a chronological sequence of events related to cloud incident response.946. **Document Analysis** — Write findings report with evidence, conclusions, and recommendations.9596## Tools9798- **Forensic Toolkit** — Evidence collection and analysis99- **Timeline Tools** — Chronological event reconstruction100- **Log Analysis Platform** — Centralized log parsing and search101102103## Process1041051. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1061. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1071. **Reporting** — Document IOCs, write findings, provide remediation recommendations108109## Verification110111- [ ] All cloud incident response procedures executed completely and documented112- [ ] Findings validated against multiple data sources113- [ ] False positives identified and filtered114- [ ] Results documented with evidence and timestamps115- [ ] Recommendations provided with risk-based prioritization116117## Anti-Rationalization Table118119| Rationalization | Reality |120|---|---|121| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |122| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |123| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |