Add skill: performing-cloud-native-threat-hunting-with-aws-detective

skills/performing-cloud-native-threat-hunting-with-aws-detective/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: performing-cloud-native-threat-hunting-with-aws-detective
+description: Hunt for threats in AWS environments using Detective behavior graphs, entity investigation timelines, GuardDuty finding correlation, and automated entity profiling across IAM users, EC2 instances, and IP addresses.
+domain: cybersecurity
+subdomain: cloud-security
+tags: [aws-detective, threat-hunting, cloud-security, guardduty, behavior-graph, aws, iam, ec2, incident-investigation]
+version: "1.0"
+author: juliosuas
+license: Apache-2.0
+---
+
+# Performing Cloud-Native Threat Hunting with AWS Detective
+
+## Overview
+
+AWS Detective automatically collects and analyzes log data from AWS CloudTrail, VPC Flow Logs, GuardDuty findings, and EKS audit logs to build interactive behavior graphs. These graphs enable security analysts to investigate entities (IAM users, roles, IP addresses, EC2 instances) across time, identify anomalous API calls, detect lateral movement between accounts, and correlate GuardDuty findings into coherent attack narratives — all without manual log parsing.
+
+## Prerequisites
+
+- AWS account with Detective enabled (requires GuardDuty active for 48+ hours)
+- AWS CLI v2 configured with appropriate IAM permissions (`detective:*`, `guardduty:List*`)
+- Python 3.9+ with boto3
+- IAM policy: `AmazonDetectiveFullAccess` or custom policy with `detective:SearchGraph`, `detective:GetInvestigation`, `detective:ListIndicators`
+
+## Key Concepts
+
+| Concept | Description |
+|---------|-------------|
+| **Behavior Graph** | Data structure linking CloudTrail, VPC Flow, GuardDuty, and EKS logs for an account/region |
+| **Entity** | Investigable object: IAM user, IAM role, EC2 instance, IP address, S3 bucket, EKS cluster |
+| **Finding Group** | Correlated set of GuardDuty findings linked to the same attack campaign |
+| **Entity Profile** | Timeline of API calls, network connections, and resource access for a specific entity |
+| **Scope Time** | Investigation window (default 24h, max 1 year) for behavioral analysis |
+
+## Steps
+
+### Step 1: List Available Behavior Graphs
+
+```bash
+aws detective list-graphs --output table
+```
+
+### Step 2: Investigate a Suspicious IAM User
+
+```bash
+# Get entity profile for an IAM user
+aws detective get-investigation \
+  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \
+  --investigation-id 000000000000000000001
+```
+
+### Step 3: Search Entities Programmatically
+
+```python
+#!/usr/bin/env python3
+"""Search AWS Detective for suspicious entities."""
+import boto3
+import json
+from datetime import datetime, timedelta
+
+detective = boto3.client('detective')
+
+def list_behavior_graphs():
+    """List all Detective behavior graphs."""
+    response = detective.list_graphs()
+    return response.get('GraphList', [])
+
+def get_investigation_indicators(graph_arn, investigation_id, max_results=50):
+    """Get indicators for a specific investigation."""
+    response = detective.list_indicators(
+        GraphArn=graph_arn,
+        InvestigationId=investigation_id,
+        MaxResults=max_results
+    )
+    return response.get('Indicators', [])
+
+def investigate_guardduty_findings(graph_arn):
+    """List high-severity investigations correlated by Detective."""
+    response = detective.list_investigations(
+        GraphArn=graph_arn,
+        FilterCriteria={
+            'Severity': {'Value': 'CRITICAL'},
+            'Status': {'Value': 'RUNNING'}
+        },
+        MaxResults=20
+    )
+
+    for investigation in response.get('InvestigationDetails', []):
+        print(f"Investigation: {investigation['InvestigationId']}")
+        print(f"  Entity: {investigation['EntityArn']}")
+        print(f"  Status: {investigation['Status']}")
+        print(f"  Severity: {investigation['Severity']}")
+        print(f"  Created: {investigation['CreatedTime']}")
+        print()
+
+if __name__ == "__main__":
+    graphs = list_behavior_graphs()
+    for graph in graphs:
+        print(f"Graph: {graph['Arn']}")
+        investigate_guardduty_findings(graph['Arn'])
+```
+
+### Step 4: Analyze Finding Groups for Attack Campaigns
+
+```bash
+# List investigations with high severity
+aws detective list-investigations \
+  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \
+  --filter-criteria '{"Severity":{"Value":"HIGH"}}' \
+  --max-results 10
+```
+
+### Step 5: Check Entity Indicators
+
+```bash
+# Get indicators for a specific investigation
+aws detective list-indicators \
+  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \
+  --investigation-id 000000000000000000001 \
+  --max-results 50
+```
+
+## Expected Output
+
+The `list-investigations` command returns investigation metadata:
+
+```json
+{
+  "InvestigationDetails": [
+    {
+      "InvestigationId": "000000000000000000001",
+      "Severity": "CRITICAL",
+      "Status": "RUNNING",
+      "State": "ACTIVE",
+      "EntityArn": "arn:aws:iam::123456789012:user/suspicious-user",
+      "EntityType": "IAM_USER",
+      "CreatedTime": "2026-03-15T14:30:00Z"
+    }
+  ]
+}
+```
+
+Indicators are retrieved separately via `list-indicators` and include types such as `TTP_OBSERVED`, `IMPOSSIBLE_TRAVEL`, `FLAGGED_IP_ADDRESS`, `NEW_GEOLOCATION`, `NEW_ASO`, `NEW_USER_AGENT`, `RELATED_FINDING`, and `RELATED_FINDING_GROUP`.
+
+## Verification
+
+1. Confirm behavior graph has data: `aws detective list-graphs` returns non-empty list
+2. Validate investigation results contain entity timelines with API call sequences
+3. Cross-reference Detective findings with raw CloudTrail logs for accuracy
+4. Verify finding group correlations match manual investigation conclusions
+5. Confirm automated alerts trigger for HIGH/CRITICAL severity investigations

skills/performing-cloud-native-threat-hunting-with-aws-detective/assets/template.md

@@ -0,0 +1,34 @@
+# AWS Detective Investigation Checklist
+
+## Pre-Investigation
+- [ ] Confirm Detective is enabled and receiving data
+- [ ] Identify trigger (GuardDuty finding, alert, manual hunt)
+- [ ] Define scope time window
+- [ ] Document initial IOCs
+
+## Entity Investigation
+- [ ] IAM User/Role profile reviewed
+- [ ] API call timeline analyzed
+- [ ] Geographic anomalies checked (impossible travel)
+- [ ] New API calls identified (never seen before)
+- [ ] Privilege escalation attempts documented
+- [ ] AssumeRole chain traced
+
+## Network Analysis
+- [ ] VPC Flow Logs reviewed for entity
+- [ ] Outbound connections to suspicious IPs identified
+- [ ] Data transfer volumes assessed
+- [ ] DNS query patterns checked
+
+## Finding Correlation
+- [ ] All related GuardDuty findings grouped
+- [ ] MITRE ATT&CK techniques mapped
+- [ ] Attack timeline constructed
+- [ ] Initial access vector identified
+
+## Response Actions
+- [ ] Evidence preserved (or capture rationale if immediate containment required)
+- [ ] Compromised credentials disabled
+- [ ] Active sessions revoked
+- [ ] Affected resources isolated
+- [ ] Stakeholders notified

skills/performing-cloud-native-threat-hunting-with-aws-detective/references/standards.md

@@ -0,0 +1,19 @@
+# Standards & References
+
+## MITRE ATT&CK Cloud Matrix
+- **TA0001** Initial Access: T1078 (Valid Accounts), T1190 (Exploit Public-Facing Application)
+- **TA0003** Persistence: T1098 (Account Manipulation), T1136 (Create Account)
+- **TA0004** Privilege Escalation: T1078, T1484 (Domain Policy Modification)
+- **TA0005** Defense Evasion: T1562 (Impair Defenses), T1070 (Indicator Removal)
+- **TA0006** Credential Access: T1528 (Steal Application Access Token)
+- **TA0007** Discovery: T1580 (Cloud Infrastructure Discovery), T1526 (Cloud Service Discovery)
+- **TA0009** Collection: T1530 (Data from Cloud Storage)
+- **TA0010** Exfiltration: T1537 (Transfer Data to Cloud Account)
+
+## AWS Documentation
+- [AWS Detective User Guide](https://docs.aws.amazon.com/detective/latest/userguide/)
+- [AWS Detective API Reference](https://docs.aws.amazon.com/detective/latest/APIReference/)
+- [GuardDuty Finding Types](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_finding-types-active.html)
+
+## CIS AWS Foundations Benchmark
+- Section 4: Monitoring (relevant to Detective integration)

skills/performing-cloud-native-threat-hunting-with-aws-detective/references/workflows.md

@@ -0,0 +1,31 @@
+# AWS Detective Investigation Workflow
+
+## Phase 1: Triage
+1. Review GuardDuty HIGH/CRITICAL findings
+2. Open Detective console → Finding Groups
+3. Identify clustered findings pointing to same entity
+
+## Phase 2: Entity Investigation
+1. Select entity (IAM user/role, EC2, IP)
+2. Review 24h behavior timeline
+3. Identify unusual API calls, new geolocations, impossible travel
+4. Check for privilege escalation patterns (CreateAccessKey, AttachPolicy)
+
+## Phase 3: Scope Assessment
+1. Trace lateral movement via AssumeRole chains
+2. Check S3 data access patterns
+3. Review VPC Flow Logs for unusual outbound connections
+4. Identify all compromised credentials
+
+## Phase 4: Correlation
+1. Map findings to MITRE ATT&CK techniques
+2. Build attack timeline from entity profiles
+3. Identify initial access vector
+4. Document indicators of compromise (IOCs)
+
+## Phase 5: Response
+1. Preserve evidence (CloudTrail logs, flow logs, snapshots) when safe
+2. Disable compromised credentials
+3. Revoke active sessions
+4. Isolate affected resources
+5. If active impact is ongoing, contain first and document evidence trade-offs