Maps attacker post-compromise stages to detection signals and preventive security controls for major cloud providers.

Install

mkdir -p .claude/skills/cloud-defense && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19505" && unzip -o skill.zip -d .claude/skills/cloud-defense && rm skill.zip

Installs to .claude/skills/cloud-defense

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Detect and break the cloud post-compromise attack chain (AWS / Azure / GCP) — per-stage CloudTrail / Activity-Log / Audit-Log detection signals and the preventive controls that close each step. Use for cloud detection engineering, hardening, remediation write-ups, or blue-team posture review of the lateral-movement -> privilege-escalation -> exfiltration -> evasion chain.
374 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Map cloud attack stages to detection signals
  • Identify preventive controls for cloud hardening
  • Draft remediation steps for security reports
  • Review cloud account posture against attack chains

How it works

It maps specific attacker stages like lateral movement or privilege escalation to corresponding cloud audit log events and provides the specific preventive control required to break that stage.

Inputs & outputs

You give it
Cloud attack technique or security finding
You get back
Detection signal and preventive hardening control

When to use cloud-defense

  • Review cloud account security posture
  • Identify audit log signals for lateral movement
  • Apply hardening controls to AWS/Azure/GCP
  • Draft remediation reports for pentests

About this skill

Cloud Defense

The blue-team counterpart to cloud-containers. For each attacker move — lateral movement, privilege escalation, data exfiltration, defense evasion — this skill gives the log event to alert on and the single control that removes the technique. Use it to turn an offensive cloud finding into a concrete detection and remediation.

When to use

  • Writing the remediation / hardening section of a cloud pentest report.
  • Cloud detection engineering: deciding which control-plane events to alert on.
  • Reviewing an AWS / Azure / GCP account's posture against the post-compromise chain.

Workflow

  1. Confirm the logging prerequisites are in place (org-wide trail, data events, threat detection on) — without them the signals below are invisible.
  2. Map each attacker stage to its detection signal — see reference/detection-signals.md.
  3. Apply the preventive control that breaks each stage — see reference/hardening-controls.md.
  4. Re-run the matching offensive technique from cloud-containers to confirm the control holds or the alert fires.

References

When not to use it

  • When logging prerequisites like org-wide trails are missing
  • When the environment is not AWS, Azure, or GCP

Prerequisites

Org-wide trailData eventsThreat detection enabled

Limitations

  • Signals are invisible without logging prerequisites
  • Limited to AWS, Azure, and GCP

How it compares

This skill provides a direct mapping between offensive cloud techniques and specific defensive controls, rather than generic security advice.

Compared to similar skills

cloud-defense side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
cloud-defense (this skill)021dNo flagsIntermediate
cloud-penetration-testing36moReviewAdvanced
building-cloud-siem-with-sentinel01moReviewAdvanced
azure-cloud-security-review03moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry