mcpField
P
performing-cloud-forensics-with-aws-cloudtrail

performing-cloud-forensics-with-aws-cloudtrail

github.com/mukul975Security35.2k55 installsUpdated 8w ago
Repository

About performing-cloud-forensics-with-aws-cloudtrail

A forensic guide to investigating cloud security incidents with AWS CloudTrail, intended for incident response teams analyzing suspicious API activity and credential exposure. It describes querying logs, filtering anomalous activity, reconstructing timelines, and compiling findings.

Key features

  1. 01Query CloudTrail events with boto3
  2. 02Analyze historical S3 logs with Athena
  3. 03Filter by user agent, IP, and event
  4. 04Reconstruct attacker timelines
  5. 05Review data access and IAM changes
  6. 06Compile forensic reports

Use cases

  1. 01Investigate suspected AWS account compromise
  2. 02Trace unauthorized API calls or exposed credentials
  3. 03Analyze S3 data exfiltration and IAM privilege escalation
  4. 04Reconstruct incident timelines from API activity

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill performing-cloud-forensics-with-aws-cloudtrail

After installing, type/performing-cloud-forensics-with-aws-cloudtrailin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE
references/
api-reference.md
scripts/
agent.py

Details

From the project README

Performing Cloud Forensics with AWS CloudTrail

When to Use

  • When investigating suspected AWS account compromise
  • After detecting unauthorized API calls or credential exposure
  • During incident response involving cloud infrastructure
  • When analyzing S3 data exfiltration or IAM privilege escalation
  • For post-incident forensic timeline reconstruction

Prerequisites

  • AWS account with CloudTrail enabled (management and data events)
  • IAM permissions for cloudtrail:LookupEvents, s3:GetObject, athena:StartQueryExecution
  • boto3 Python SDK installed
  • CloudTrail logs delivered to S3 with optional Athena table configured
  • AWS CLI configured with appropriate credentials

Workflow

  1. Scope Investigation: Identify timeframe, affected accounts, and compromised credentials.
  2. Query CloudTrail: Use boto3 lookup_events or Athena to retrieve relevant API events.
  3. Filter by Indicators: Search for suspicious user agents, source IPs, and event names.
  4. Reconstruct Timeline: Build chronological sequence of attacker actions from API calls.
  5. Analyze Access Patterns: Identify data access, IAM changes, and resource modifications.
  6. Identify Persistence: Check for new IAM users, access keys, roles, or Lambda functions.
  7. Generate Report: Produce forensic timeline with findings and remediation steps.

Key Concepts

ConceptDescription
LookupEventsCloudTrail API to query management events (last 90 days)
Athena QueriesSQL queries against CloudTrail logs in S3 for historical analysis
User Agent AnalysisIdentify tool signatures (AWS CLI, SDK, console, custom)
AccessKeyIdTrack activity by specific IAM access key
EventNameAWS API action name (e.g., GetObject, CreateUser, AssumeRole)
sourceIPAddressOrigin IP of API call for geolocation analysis

Tools & Systems

ToolPurpose
boto3 CloudTrail clientProgrammatic CloudTrail event lookup
AWS AthenaSQL-based analysis of CloudTrail S3 logs
AWS CLICommand-line CloudTrail queries
jqJSON processing for CloudTrail event parsing
CloudTrail LakeAdvanced event data store with SQL query support

Output Format

Forensic Report: AWS-IR-[DATE]-[SEQ]
Account: [AWS Account ID]
Timeframe: [Start] to [End]
Compromised Credentials: [Access Key IDs]
Suspicious Events: [Count]
Source IPs: [List of attacker IPs]
Actions Taken: [API calls by attacker]
Data Accessed: [S3 objects, secrets, etc.]
Persistence Mechanisms: [New users, keys, roles]

Comments

Markdown supported