cloud-audit

Audit AWS, GCP, and Azure infrastructure for security misconfigurations and logging gaps.

345|47|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/briiirussell/cybersecurity-skills --skill cloud-audit-briiirussell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-audit
Source: https://github.com/briiirussell/cybersecurity-skills/tree/main/skills/cloud-audit
Command: npx skills add https://github.com/briiirussell/cybersecurity-skills --skill cloud-audit-briiirussell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloud environments accumulate risky misconfigurations over time, including overly permissive identity access, public exposure, weak encryption, and missing monitoring, leaving systems vulnerable to compromise and non-compliance.

Core Features & Use Cases

  • Multi-cloud posture review (AWS/GCP/Azure): Audits core configuration areas including identity/access, network exposure, storage controls, compute hardening, logging/monitoring, and secrets management.
  • Evidence-backed findings with actionable remediation: Produces structured findings with risk descriptions, concrete evidence (CLI outputs and IaC snippets), and specific fixes while accounting for operational impact.
  • Security-program friendly reporting: Uses a severity breakdown and organizes output into an audit-ready report format, aligned to evidence-first workflows.

Use cases: Run a baseline cloud security audit before a release, verify IAM and public exposure controls for a new environment, or validate ongoing hardening for an existing production stack across regions.

Quick Start

Ask the agent to run a Cloud Audit for your AWS/GCP/Azure account by describing the provider, account/project, regions, and whether you’re auditing via CLI or IaC.

Frequently Asked Questions about cloud-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my AWS, GCP, or Azure infrastructure for security misconfigurations?

To audit cloud infrastructure for security misconfigurations, you can run a multi-cloud posture review across identity, network, storage, compute, monitoring, and secrets using either provider CLI tools or Infrastructure-as-Code evidence.

What is the best way to check for excessive IAM permissions and public exposure in my cloud environment?

Checking for excessive IAM permissions and public exposure involves reviewing identity access and network controls to identify risky misconfigurations, producing evidence-backed findings with specific remediation steps while accounting for operational impact.

Can I generate compliance reporting for cloud security using Infrastructure-as-Code?

Yes, compliance reporting can be generated using Infrastructure-as-Code evidence to audit configuration areas like storage controls, compute hardening, and logging gaps, producing an audit-ready report with severity breakdowns and categorized findings.

Does this cloud security review work across multiple cloud providers like AWS, GCP, and Azure?

Yes, this cloud security review works across AWS, GCP, and Azure, auditing core configuration areas including identity, network, storage, compute, logging, and secrets management to identify risks and enforce defined audit boundaries.

How do I remediate weak encryption and missing monitoring gaps found during a cloud audit?

To remediate weak encryption and missing monitoring gaps, the audit produces structured findings that include risk descriptions, concrete evidence from CLI outputs or IaC snippets, and specific fixes to resolve the identified security vulnerabilities.

What do I need to provide to run a baseline cloud security audit before a release?

To run a baseline cloud security audit, you need to describe your cloud provider, account or project, target regions, and whether you are auditing via CLI tools or Infrastructure-as-Code to establish operational risk boundaries.