Cloud Forensics (AWS GuardDuty / CloudTrail / S3)

Analyze AWS GuardDuty and CloudTrail logs to reconstruct incident timelines.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rjonhaas/SIFTics --skill cloud-forensics-aws-guardduty-cloudtrail-s3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Cloud Forensics (AWS GuardDuty / CloudTrail / S3)
Source: https://github.com/rjonhaas/SIFTics/tree/main/skills/cloud-forensics
Command: npx skills add https://github.com/rjonhaas/SIFTics --skill cloud-forensics-aws-guardduty-cloudtrail-s3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and guesswork needed to triage AWS cloud incidents by transforming GuardDuty and CloudTrail evidence into prioritized findings, timelines, and exfiltration/persistence indicators.

Core Features & Use Cases

  • GuardDuty finding triage: Decompress GuardDuty .jsonl.gz and generate high-severity exports, principal pivots, and network IOC-focused extracts.
  • CloudTrail timeline reconstruction: Decompress CloudTrail .json.gz, flatten Records into JSONL, and produce event frequency summaries, error/denied-event lists, and CSV timelines for investigation.
  • Threat pattern detection: Identify AWS IMDS credential theft signals, IAM persistence (new keys/policy changes), and S3 exfiltration patterns (GetObject/Deletes) from log artifacts.

Use case: You receive a customer’s S3-copied GuardDuty and CloudTrail archives and need to quickly determine whether an attacker attempted credential theft, established IAM persistence, and accessed or deleted S3 objects—without touching originals.

Quick Start

Use the cloud-forensics skill to parse GuardDuty and CloudTrail logs from your case root and produce CSV exports under exports/cloud and analysis/cloud for prioritized triage.

Frequently Asked Questions about Cloud Forensics (AWS GuardDuty / CloudTrail / S3)

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage GuardDuty findings from local JSON log archives?

Triage GuardDuty findings by decompressing .jsonl.gz archives and extracting high-severity exports, principal pivots, and network IOC-focused extracts. This process surfaces high-signal incident indicators from local copies without touching original evidence.

Can I reconstruct an incident timeline from CloudTrail logs?

Reconstruct a CloudTrail timeline by decompressing .json.gz files, flattening Records into JSONL, and generating event frequency summaries, error lists, and CSV investigation timelines to track AWS IAM compromise activity.

What is IMDS credential theft and how do I detect it in AWS logs?

IMDS credential theft detection involves analyzing AWS CloudTrail and GuardDuty evidence for specific threat patterns indicating stolen instance metadata service credentials. The analysis identifies these signals alongside IAM persistence and S3 exfiltration patterns.

How do I identify IAM persistence mechanisms like new keys or policy changes?

Identify IAM persistence by parsing CloudTrail logs for threat patterns like new access keys and policy changes. The extraction process flags these indicators alongside IMDS credential theft signals and suspicious S3 object access.

Do I need jq or Python to analyze AWS CloudTrail and GuardDuty evidence?

You need jq or Python to perform extraction of prioritized findings, timelines, and principal pivots. These tools process the decompressed and flattened JSONL data to generate CSV exports under analysis and export directories.

What's the best way to detect S3 exfiltration from read-only log artifacts?

Detect S3 exfiltration from read-only log artifacts by analyzing GuardDuty and CloudTrail evidence for suspicious GetObject and Delete event patterns. This avoids modifying originals while extracting prioritized findings into investigation timelines.