cloud-security-automation
Skill4 starsChanged 5 months agoMITView on GitHub
Cloud security posture skill for AWS, Azure, GCP, and multi-cloud. Covers IAM least-privilege, key and secret hygiene, network exposure, data protection, logging coverage, IaC scanning (Terraform, CloudFormation, Bicep, Pulumi), CSPM remediation, and landing-zone hardening. Use for misconfig discovery, IaC review, and automated drift-and-fix workflows on cloud accounts you own.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Default to read-only APIs and --dry-run/plan mode for any change.
- Distinctive: line 12
Do not exfiltrate customer data.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cloud Security Automation
Authorization Boundary
- Require account IDs, role ARNs/principals, and read-only credentials in scope before any live query.
- Default to read-only APIs and
--dry-run/plan mode for any change. - Do not exfiltrate customer data; redact resource names if shared outside the engagement.
Posture Workflow
- Inventory: accounts, subscriptions, projects, regions, services in use, owners, tags.
- Baseline: pull config via
aws configservice,az resource graph,gcloud asset, plusprowler,scout-suite,cloudsploit,steampipe. - Score: map findings to CIS, NIST 800-53, Well-Architected, and CSA CCM.
- IaC pre-flight:
checkov,tfsec,kics,terrascan,cfn-nagon PRs; block on critical. - Remediate: produce least-privilege IAM diffs, network restrictions, encryption defaults, and logging fixes as code, not console clicks.
- Drift watch: compare desired state to live; alert on out-of-band changes.
Focus Areas
- IAM: wildcard actions, cross-account trust, unused roles, long-lived keys, OIDC federation.
- Network: public S3/Blob/GCS, 0.0.0.0/0 ingress, exposed databases, lateral paths.
- Data: encryption at rest, KMS key policies, backup posture, PII tagging.
- Logging: CloudTrail/Activity Logs/Audit Logs coverage, retention, SIEM ingestion.
- Identity: MFA, conditional access, SCP/Org Policy guardrails, break-glass accounts.
Output Contract
inventory.json,findings.csv(with severity, control, evidence, fix).iac-patches/: ready-to-PR diffs.runbooks/: incident-grade response for each top finding.posture-trend.md: weekly delta with regressions called out.
Other versions1 project uses a version of this.
Word for word · 1
- Garyson26/Trident-SecOps-Skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- prompt-enhancementSkill
- python-programmingSkill
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.