Menu

Individual skill

hardening-cloud-posture

0upvotes

Proactively harden a cloud account or organization before an incident — prioritizing IAM and identity risk over checkbox findings, closing the exposures that become attack paths (public storage, over-broad roles, missing audit logging, unencrypted data), reading CSPM output critically, and enforcing guardrails at the org level. Use when reviewing a cloud environment's security posture, triaging a Prowler/ScoutSuite/Security Hub report, deciding which misconfigurations actually matter, or setting preventive controls across AWS, Azure, or GCP.

secskills-defense/skills/hardening-cloud-posture/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
188
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Hardening Cloud Posture

A CSPM scan returns a thousand findings. Almost none of them are the way in.
The job is not to close a thousand findings; it is to find the handful that
form an attack path and close those, then set guardrails so they cannot recur.
Posture work that treats every finding as equal drowns the real one.

The organizing principle: **identity is the perimeter.** In cloud, the attack
path is almost always a chain of IAM permissions, not a network hop. Rank by
"what does this let a principal reach?", not by a scanner's severity label.

## When to Use

- Reviewing an AWS/Azure/GCP account or organization's security posture
Back to top