conducting-cloud-incident-response

Featured

Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.

DevOps & Infrastructure 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Conducting Cloud Incident Response ## When to Use - 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. ## 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 ### Step 1: Detect and Confirm the Cloud Incident Identify the scope and nature of the compromise: **AWS Indicators:** ``` CloudTrail suspicious events to investigate: - ConsoleLogin from unexpected geolocation or IP - CreateAccessKey for existing IAM user (persistence) - RunInstances for crypto-mining (large instance types) - PutBucketPolicy making S3 bucket public - Assu...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

conducting-cloud-incident-response

Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.

100 Updated 2 weeks ago
adriannoes
DevOps & Infrastructure Listed

cloud-incident-investigation

Investigate suspected compromise in AWS, Azure, or GCP: find the right logs (CloudTrail, AzureActivity, Entra audit, GCP Cloud Audit Logs), reconstruct what an identity or access key did, spot the high-signal control-plane events (access key creation, role assumption chains, StopLogging, PutBucketPolicy, role assignments, Key Vault reads, setIamPolicy, service account key creation), size the blast radius, and contain safely (rotate, deny, SCP, revoke) while preserving evidence. Use it whenever someone mentions a leaked or exposed access key, a GuardDuty / Defender for Cloud / Security Command Center finding, an unexpected cloud bill, a public bucket, an unknown IAM user or role, "someone logged into the console", "who created this resource", or pastes CloudTrail, Activity Log, or audit log JSON, even if they do not say "incident". Also use it for post-hoc "what did this credential touch" reviews.

0 Updated 2 months ago
ftrout
DevOps & Infrastructure Featured

performing-cloud-incident-containment-procedures

Execute cloud-native incident containment across AWS, Azure, and GCP by isolating compromised resources, revoking credentials, preserving forensic evidence, and applying security group restrictions to prevent lateral movement.

36,355 Updated 2 months ago
mukul975