Performing Cloud Forensics Investigation
Overview
Cybersecurity skill for performing cloud forensics investigation. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing cloud forensics investigation"
"Conduct forensic investigations in cloud environments by collecting and analyzin"
When investigating a security breach in AWS, Azure, or GCP cloud environments
For collecting volatile and non-volatile evidence from cloud infrastructure
When tracing unauthorized access through cloud service API logs
During incident response requiring preservation of cloud-based evidence
For analyzing compromised virtual machines, containers, or serverless functions
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
- Administrative access to the cloud account under investigation
- AWS CLI, Azure CLI, or gcloud CLI configured with appropriate permissions
- Understanding of cloud-native logging (CloudTrail, Activity Log, Audit Log)
- Forensic workstation with cloud SDKs installed
- Knowledge of IAM, networking, and compute services in target cloud
- Evidence preservation procedures for cloud environments
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()}
- Plan Operations — Define objectives, scope, and success criteria for cloud forensics investigation operations.
- Prepare Environment — Set up tools, access, and data sources required for cloud forensics investigation.
- Execute Core Workflow — Perform the cloud forensics investigation operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
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: performing-cloud-forensics-investigation3description: Use when conduct forensic investigations in cloud environments by collecting and analyzing logs, snapshots, and metadata from AWS, Azure, and GCP services. Use when conducting forensic investigations in cloud environments by collecting and analyzing.4license: Apache-2.05---67# Performing Cloud Forensics Investigation89## Overview1011Cybersecurity skill for performing cloud forensics investigation. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing cloud forensics investigation"16- "Conduct forensic investigations in cloud environments by collecting and analyzin"1718- When investigating a security breach in AWS, Azure, or GCP cloud environments19- For collecting volatile and non-volatile evidence from cloud infrastructure20- When tracing unauthorized access through cloud service API logs21- During incident response requiring preservation of cloud-based evidence22- For analyzing compromised virtual machines, containers, or serverless functions232425## When NOT to Use2627- When you lack proper authorization for testing28- For production systems without change management29- When the task requires legal or compliance expertise beyond technical scope303132## Prerequisites33- Administrative access to the cloud account under investigation34- AWS CLI, Azure CLI, or gcloud CLI configured with appropriate permissions35- Understanding of cloud-native logging (CloudTrail, Activity Log, Audit Log)36- Forensic workstation with cloud SDKs installed37- Knowledge of IAM, networking, and compute services in target cloud38- Evidence preservation procedures for cloud environments3940## Workflow4142```python43# Example: IOC detection44import re4546IOC_PATTERNS = {47 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",48 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",49 "hash_md5": r"\b[a-f0-9]{32}\b",50 "hash_sha256": r"\b[a-f0-9]{64}\b",51}5253def extract_iocs(text: str) -> dict:54 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}55```56571. **Plan Operations** — Define objectives, scope, and success criteria for cloud forensics investigation operations.582. **Prepare Environment** — Set up tools, access, and data sources required for cloud forensics investigation.593. **Execute Core Workflow** — Perform the cloud forensics investigation operations following established procedures.604. **Validate Results** — Verify that results meet quality standards and objectives.615. **Report Findings** — Document results, observations, and recommendations.626. **Follow Up** — Track remediation actions and verify fixes where applicable.6364## Tools6566- **Analysis Platform** — Data processing and visualization67- **Collaboration Tools** — Team coordination and knowledge sharing686970## Process71721. **Reconnaissance** — Gather target information, identify attack surface, enumerate services731. **Analysis/Exploitation** — Execute the technique, analyze results, document findings741. **Reporting** — Document IOCs, write findings, provide remediation recommendations7576## Verification7778- [ ] All cloud forensics investigation procedures executed completely and documented79- [ ] Findings validated against multiple data sources80- [ ] False positives identified and filtered81- [ ] Results documented with evidence and timestamps82- [ ] Recommendations provided with risk-based prioritization8384## Anti-Rationalization Table8586| Rationalization | Reality |87|---|---|88| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |89| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |90| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |