- Home
- Skills
- DevOps & Cloud
- Cloud Infrastructure Security Readiness Auditor
Works with the AI Agents you already use
Cloud Infrastructure Security Readiness Auditor
Assess cloud architecture and IaC artifacts to determine production security readiness and audit maturity.
$29.99
Cloud Infrastructure Security Readiness Auditor
Example session with this skill installed
Review this Terraform snippet for an AWS production environment. We have a public ALB, private RDS, and S3 for logs. MFA is required for console users. Is this ready for a production launch?
- Read your context and instructions
- Compiled the cloud infrastructure security
I have reviewed the Terraform configuration and security policies provided for the AWS production environment. The assessment focuses on the ALB, RDS, and S3 logging architecture.
Executive Readiness Decision: Conditionally Ready
The architecture follows standard tier-segmentation, but critical gaps in data lifecycle and workload identity evidence remain before a full production launch.
Security Readiness Assessment
| Control Domain | Status | Evidence Quality | Findings |
|---|---|---|---|
| Identity & Access | Partially Implemented | Medium (IaC) | MFA is active for console, but workload roles lack 'Permission Boundaries'. |
| Network Security | Implemented | High (IaC) | ALB is public; RDS is correctly placed in private subnets with no 0.0.0.0/0 ingress. |
| Data Protection | Not Implemented | Low (Missing) | S3 buckets lack Versioning and Object Lock; RDS encryption is not explicitly defined. |
| Logging & Mon. | Implemented & Evidenced | High (IaC) | S3 Access Logging is enabled for the ALB; Flow Logs are present. |
| Resilience | Unknown | None | Backup schedules and Multi-AZ configuration were not provided in the snippet. |
Priority Findings & Blockers
- Critical: RDS Instance lacks
storage_encrypted = true. Risk of data exposure at rest.
High: S3 log bucket lacks a LifecycleConfiguration to transition logs to Glacier, risking uncapped costs and storage bloat.
Medium: IAM roles for EC2/Lambda do not use specific ManagedPolicyArns, increasing the risk of privilege escalation.
Positive Controls Observed
- Network segmentation strictly separates the data layer from the internet-facing ingress.
- Access logging is centralized to a dedicated S3 bucket.
Next steps
- Add
storage_encrypted = trueandkms_key_idto the RDS Terraform resource. - Provide the
aws_iam_policydefinitions to verify the "Least Privilege" implementation for application roles. - Define an
aws_s3_bucket_versioningresource for the logging and data buckets.
Connects securely to your tools. The creator never sees your data.
About this skill
Securing a cloud environment before launch requires more than a passing scan. Misconfigured IAM roles, exposed network boundaries, and unverified backup procedures often slip through automated tools. This skill evaluates your architecture, IaC, and security policies to determine if your environment is truly ready for production or audit.
What it does
- Architectural review maps internet-facing entry points, trust boundaries, and privileged administration paths.
- Control maturity assessment categorizes controls from 'Implemented and evidenced' to 'Unknown' based on provided artifacts.
- Risk prioritization flags critical blockers and high-impact gaps using data sensitivity and blast radius.
- Remediation roadmapping organizes security tasks into pre-launch, 30-day, and 90-day windows.
- Evidence validation distinguishes between design intent, configured controls, and operationally evidenced safeguards.
How it works
- Scope definition where you provide cloud providers, regions, and data classification.
- Artifact ingestion using your redacted IaC (Terraform, Bicep, K8s), policy documents, and configuration exports.
- Domain analysis across identity, network, data protection, logging, and operational readiness.
- Readiness determination resulting in a formal status of Ready, Conditionally ready, or Not ready.
Frameworks & tools
Works with AWS, Azure, and GCP environments. Analyzes Terraform, CloudFormation, Bicep, ARM, and Kubernetes manifests.
Why this beats prompting it yourself
Generic prompts often miss the distinction between a policy existing on paper and a control being effectively evidenced in configuration. This skill uses a structured maturity model to ensure you don't mistake a checklist item for a functional safeguard.
Use cases
- Pre-launch audit to identify critical security blockers before going live.
- Compliance preparation to gather and verify evidence for SOC2 or ISO 27001 assessments.
- Acquisition due diligence to evaluate the security posture of a new cloud environment.
- Architecture refresh to find drift between design intent and actual infrastructure state.
Known limitations
Does not perform live scanning or exploit testing. Requires manually supplied, redacted evidence for analysis. Cannot verify implementation without specific configuration or policy exports.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Requires manual provision of redacted IaC or config exports. Cannot access live cloud environments or execute active scans. Decisions are limited by the quality and recency of provided evidence.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago