Running Scans
Cloudsploit scans your cloud infrastructure by enumerating resources and running security checks against each one. Learn how to start scans, customize scan scope, and interpret results.
Basic Scan
The simplest scan targets all enabled cloud providers with default settings:
1cloudsploit scan
This will:
- Discover all accessible resources in configured cloud accounts
- Run all enabled security detectors
- Output results to console in table format
- Save full results to
~/.cloudsploit/results/
Scan Specific Cloud Provider
Target specific cloud providers if you only want to scan one environment:
1# Scan AWS only2cloudsploit scan aws34# Scan Azure only5cloudsploit scan azure67# Scan GCP only8cloudsploit scan gcp910# Scan AWS and Azure (skip GCP)11cloudsploit scan aws azure
Limit by Region
Restrict scans to specific regions to reduce scan time or focus on specific deployments:
1# Scan only US regions2cloudsploit scan aws --regions us-east-1,us-west-2,us-west-134# Scan single region5cloudsploit scan aws --region eu-west-167# Exclude regions8cloudsploit scan aws --exclude-regions cn-north-1,us-gov-west-1
Info
Limit by Service
Focus on specific cloud services to speed up scans or target high-risk areas:
1# Scan only storage services2cloudsploit scan aws --services s3,ebs,efs34# Scan IAM and security groups5cloudsploit scan aws --services iam,security-groups67# Exclude specific services8cloudsploit scan aws --exclude-services cloudtrail,config
Warning
cloudsploit detectors --list to see all available service names.Custom Detectors
Run only specific detectors or exclude known false positives:
1# Run only S3 and IAM detectors2cloudsploit scan aws --services s3,iam34# Skip specific detectors by ID5cloudsploit scan aws --suppress S3_BUCKET_PUBLIC_READ,S3_BUCKET_VERSIONING_DISABLED67# Run only critical/high severity detectors8cloudsploit scan aws --severity critical,high910# List all available detectors11cloudsploit detectors --list
Output Formats
Export scan results in various formats for reporting or integration:
1# JSON output (detailed, machine-readable)2cloudsploit scan aws --output json --outfile scan-results.json34# CSV for spreadsheet analysis5cloudsploit scan aws --output csv --outfile findings.csv67# HTML report with interactive filtering8cloudsploit scan aws --output html --outfile report.html910# JUnit format for CI/CD integration11cloudsploit scan aws --output junit --outfile results.xml1213# Table format (default, console-friendly)14cloudsploit scan aws --output table
Info
--outfile, output goes to console (except JSON which writes to ~/.cloudsploit/results/ by default).Scan Modes
Cloudsploit offers different scan modes for various use cases:
Quick Scan
Fast scan with common detectors only. Good for daily checks.
1cloudsploit scan --quick
Comprehensive Scan
All detectors, all regions, thorough enumeration. Takes longer.
1cloudsploit scan --comprehensive
Compliance Mode
Run only CIS benchmark and compliance checks.
1cloudsploit scan --compliance cis
Dry Run
Show what would be scanned without executing. Safe for testing config.
1cloudsploit scan --dry-run
Understanding Output
Scan results show security findings with severity, description, and remediation:
1[CRITICAL] S3 Bucket is publicly accessible2 Resource: arn:aws:s3:::my-bucket3 Region: us-east-14 Description: The S3 bucket has public read/write permissions via bucket policy5 Remediation: Remove public access ACLs and block public access settings6 Reference: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html
Severity levels:
- CRITICAL: Immediate action required, high risk of compromise
- HIGH: Significant security issue, address soon
- MEDIUM: Potential security improvement, schedule remediation
- LOW: Minor issue or informational finding