cloud-exposure-review
Skill0 starsChanged 12 days agoMITView on GitHub
Identify internet exposure across cloud estates — public IPs and load balancers, open security groups/NSGs/firewall rules, public storage and snapshots, exposed databases and managed services, serverless URLs, public container registries — and validate what is actually reachable. Use when mapping the cloud attack surface, after a misconfiguration incident, or before a pen test.
In this repository273 other files it gives its agents.
- ad-attack-path-analysisSkill
- adcs-security-reviewSkill
- ad-privileged-access-reviewSkill
- dcsync-detectionSkill
- gpo-security-reviewSkill
- kerberos-attack-detectionSkill
- agent-tool-permission-reviewSkill
- ai-incident-responseSkill
- llm-gateway-controlsSkill
- llm-security-evaluationSkill
- mcp-server-security-reviewSkill
- model-artifact-securitySkill
- prompt-injection-reviewSkill
- rag-security-reviewSkill
- api-abuse-detectionSkill
- api-authorization-testingSkill
- api-inventorySkill
- api-schema-securitySkill
- dast-baselineSkill
- sast-triageSkill
- sca-dependency-riskSkill
- secure-code-reviewSkill
- security-requirementsSkill
- threat-modelingSkill
- asset-criticality-tieringSkill
- asset-inventory-reconciliationSkill
- external-attack-surface-reviewSkill
- shadow-it-discoverySkill
- aws-credential-compromiseSkill
- aws-iam-reviewSkill
- aws-org-guardrailsSkill
- cloudtrail-investigationSkill
- guardduty-triageSkill
- s3-exposure-reviewSkill
- azure-activity-investigationSkill
- azure-rbac-reviewSkill
- conditional-access-reviewSkill
- entra-audit-investigationSkill
- entra-signin-investigationSkill
- backup-assuranceSkill
- critical-service-mappingSkill
- ransomware-recoverySkill
- recovery-exerciseSkill
- cloud-incident-responseSkill
- cloud-logging-baselineSkill
- cloud-posture-assessmentSkill
- audit-evidence-packageSkill
- continuous-control-monitoringSkill
- control-mappingSkill
- control-testing-samplingSkill
- container-incidentSkill
- dockerfile-hardeningSkill
- image-scanningSkill
- runtime-detection-falcoSkill
- db-audit-loggingSkill
- db-exfiltration-investigationSkill
- db-hardeningSkill
- db-privilege-reviewSkill
- data-classificationSkill
- data-discoverySkill
- The first 60 shown.
The file
Files
Cloud Exposure Review
Inventory queries
AWS:
aws ec2 describe-instances --query 'Reservations[].Instances[?PublicIpAddress].[InstanceId,PublicIpAddress,MetadataOptions.HttpTokens]' --output text
aws elbv2 describe-load-balancers --query 'LoadBalancers[?Scheme==`internet-facing`].[LoadBalancerName,DNSName]'
aws rds describe-db-instances --query 'DBInstances[?PubliclyAccessible].[DBInstanceIdentifier,Endpoint.Address]'
aws ec2 describe-snapshots --owner-ids self --query 'Snapshots[].SnapshotId' --output text | xargs -n1 -I{} aws ec2 describe-snapshot-attribute --snapshot-id {} --attribute createVolumePermission --query 'CreateVolumePermissions'
aws lambda list-function-url-configs --function-name F # per function; AuthType NONE = publicAzure (Resource Graph):
az graph query -q "Resources | where type =~ 'microsoft.network/publicipaddresses' | project name, properties.ipAddress, properties.ipConfiguration.id"
az graph query -q "Resources | where type =~ 'microsoft.storage/storageaccounts' | where properties.allowBlobPublicAccess == true | project name, resourceGroup"GCP (Cloud Asset Inventory):
gcloud asset search-all-resources --scope=organizations/ORG --asset-types=compute.googleapis.com/Address --query="addressType:EXTERNAL"
gcloud asset search-all-iam-policies --scope=organizations/ORG --query="policy:allUsers OR policy:allAuthenticatedUsers"Validate reachability
Rules can be shadowed by other layers (NACLs, WAF, private endpoints). Confirm with an external scan of your own IPs (authorized, external-attack-surface-review) or provider reachability analyzers (AWS Network Access Analyzer / Reachability Analyzer, Azure Network Watcher, GCP Connectivity Tests).
Prioritize
Data stores and admin interfaces reachable from the internet first; then compute with privileged identities; then everything else. For each exposed resource record: owner, purpose, data, auth, intended (y/n).
Related skills
cloud-posture-assessment, s3-exposure-review, firewall-rule-review, external-attack-surface-review, cloud-firewall-build
References
- AWS Network Access Analyzer: https://docs.aws.amazon.com/vpc/latest/network-access-analyzer/what-is-network-access-analyzer.html
- Azure Resource Graph: https://learn.microsoft.com/en-us/azure/governance/resource-graph/overview
- GCP Cloud Asset Inventory: https://cloud.google.com/asset-inventory/docs/overview
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.

