agentleFS
mondoohqmondoohq/secure-stack/skills/secure-cloud/SKILL.md

secure-cloud

Skill2 starsChanged 33 days agoApache-2.0View on GitHub

Audit cloud account security posture — scan AWS, Azure, GCP (and Alibaba, Oracle, Cloudflare, Kubernetes) against CIS foundations and Mondoo cloud policies with cnspec, finding IAM, network, storage, encryption, and service misconfigurations mapped to compliance. Use to check a cloud account, subscription, project, or cluster's posture.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether a cloud account is configured securely, by running cnspec against it.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Secure Cloud

Check whether a cloud account is configured securely, by running cnspec against it. You ask the outcome — "is this AWS account / Azure subscription / GCP project hardened?" — and this skill picks the right scan and reads the result; cnspec carries the policies.

When to use

  • Auditing an AWS account, Azure subscription, GCP project, or Kubernetes cluster against CIS foundations / Mondoo cloud security policies.
  • Finding IAM, network (security groups / firewall), public-storage, encryption, and logging misconfigurations across a cloud environment.

This is live posture (an account you can connect to). For the Terraform/CloudFormation an agent writes before deploy, use secure-pipeline (it policy-checks the IaC with cnspec).

What cnspec checks

  • AWS — mondoo-aws-security · Azure — mondoo-azure-security · GCP — mondoo-gcp-security
  • Kubernetes — mondoo-kubernetes-security, mondoo-kubernetes-best-practices
  • Also — mondoo-alibaba-security, mondoo-cloudflare-security, mondoo-clickhousecloud-security

Run a scan

cnspec scan aws    -o sarif    # uses your AWS credentials / profile
cnspec scan azure  -o sarif    # uses your Azure login
cnspec scan gcp    -o sarif    # uses your gcloud credentials
cnspec scan k8s    -o sarif    # current kube context
  • Logged in to Mondoo Platform, cnspec runs the assigned policies automatically; otherwise add --incognito and -f <bundle> to run a specific bundle locally.
  • Each provider authenticates with that cloud's standard credentials — see the cnspec docs for per-provider connection options.
  • -o sarif emits findings for a CI gate; cnspec exits non-zero on failures.

Reference, don't duplicate

cnspec owns the policies and their authoring (see the cnspec repo for the mql / policy-graph skills). This skill invokes cnspec and interprets results.

Compliance

Cloud policies map to CIS benchmarks, SOC 2, ISO 27001, PCI-DSS, NIST, HIPAA, and more — a scan doubles as a compliance report; filter or report by the framework you need.

Part of the secure-your-stack toolkit

secure-cloud is the cloud account pillar of posture, alongside secure-os (hosts & devices), secure-saas (SaaS & identity), and secure-ai-services (AI). The secure development skills secure the code and IaC you deploy into these accounts. Needs cnspec (install) plus credentials for the target cloud.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.