Install
openclaw skills install cloudguardCloud infrastructure & IaC security scanner -- detects insecure Terraform, open S3 buckets, permissive IAM, missing encryption, exposed ports, and cloud misconfigurations
openclaw skills install cloudguardCloudGuard scans codebases for insecure cloud infrastructure patterns including Terraform misconfigurations, open S3 buckets, overly permissive IAM policies, missing encryption at rest, exposed ports, absent logging and monitoring, and general cloud compliance gaps. It uses 90 regex-based patterns across 6 security categories, produces severity-graded reports with actionable remediation, and integrates with git hooks via lefthook. 100% local. Zero telemetry.
cloudguard scan [file|directory]One-shot cloud security scan of infrastructure-as-code files or directories.
How to execute:
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target]
What it does:
Example usage scenarios:
cloudguard scan .cloudguard scan infra/cloudguard scan terraform/cloudguard scan .cloudguard scan [file|directory] (Pro -- 60 patterns)Full scan with 60 of 90 patterns unlocked covering all 6 categories in depth.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target] --tier pro
cloudguard hooks installInstall git pre-commit hooks that scan staged IaC files for cloud security issues before every commit.
How to execute:
bash "<SKILL_DIR>/scripts/dispatcher.sh" hooks install
What it does:
cloudguard hooks uninstallRemove CloudGuard git hooks.
bash "<SKILL_DIR>/scripts/dispatcher.sh" hooks uninstall
cloudguard report [directory]Generate a markdown cloud security report with findings, severity breakdown, category analysis, and remediation steps.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format text report
What it does:
cloudguard audit [directory]Deep cloud security audit across all categories.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] audit
What it does:
cloudguard scan [file|directory] (Team -- all 90 patterns)Full scan with all 90 patterns unlocked.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target] --tier team
cloudguard scan --format json [directory]JSON output for CI/CD pipeline integration.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format json
What it does:
cloudguard scan --format html [directory]HTML report output for stakeholder sharing.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format html
cloudguard scan --category [category] [directory]Category-filtered scan for focused audits.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --category S3
What it does:
cloudguard statusShow license and configuration information.
bash "<SKILL_DIR>/scripts/dispatcher.sh" status
CloudGuard detects 90 cloud security patterns across 6 categories:
| Category | Code | Patterns | Examples | Severity Range |
|---|---|---|---|---|
| Storage Security | S3 | 15 | Public S3 buckets, missing encryption, no versioning, overly permissive bucket policies, missing access logging, no lifecycle rules | Critical/High/Medium |
| IAM & Permissions | IM | 15 | Wildcard IAM policies, AdministratorAccess, overly broad assume role, missing MFA, root account usage, no least privilege | Critical/High/Medium |
| Network Security | NW | 15 | Open security groups (0.0.0.0/0), exposed ports (22, 3389, 3306), missing VPC, no network ACLs, public subnets without NAT, SSH open to world | Critical/High/Medium |
| Encryption | EN | 15 | Missing encryption at rest, no KMS key rotation, unencrypted EBS volumes, missing SSL/TLS, no transit encryption, weak cipher suites | Critical/High/Medium/Low |
| Logging & Monitoring | LG | 15 | Missing CloudTrail, no VPC flow logs, disabled GuardDuty, missing alarm configurations, no SNS notifications, absent audit logs | High/Medium/Low |
| Configuration & Compliance | CF | 15 | Missing tags, no resource naming convention, hardcoded regions, missing backups, no disaster recovery, drift detection gaps | Medium/Low |
| Level | Points Deducted | Meaning | Action Required |
|---|---|---|---|
| Critical | 25 | Immediate infrastructure compromise risk (open to internet, no auth, wildcard admin) | Fix immediately; block deployment |
| High | 15 | Significant security gap that could be exploited (missing encryption, overly permissive policies) | Fix within current sprint |
| Medium | 8 | Security best practice violation that increases attack surface | Plan remediation within 30 days |
| Low | 3 | Informational finding, minor hygiene issue, or hardening recommendation | Address when convenient |
CloudGuard uses a 0-100 scoring system:
| Grade | Score Range | Meaning |
|---|---|---|
| A | 90-100 | Excellent -- minimal or no cloud security issues |
| B | 80-89 | Good -- minor issues that should be addressed |
| C | 70-79 | Acceptable -- passing but needs improvement |
| D | 60-69 | Poor -- significant security gaps requiring attention |
| F | Below 60 | Failing -- critical misconfigurations must be fixed immediately |
| Tier | Patterns Available | Categories |
|---|---|---|
| Free | 30 patterns | First 5 patterns per category |
| Pro | 60 patterns | First 10 patterns per category |
| Team | 90 patterns (all) | All 15 patterns per category |
| Enterprise | 90 patterns (all) | All 15 patterns per category + priority support |
Users can configure CloudGuard in ~/.openclaw/openclaw.json:
{
"skills": {
"entries": {
"cloudguard": {
"enabled": true,
"apiKey": "YOUR_LICENSE_KEY_HERE",
"config": {
"severityThreshold": "high",
"ignorePatterns": ["**/test/**", "**/examples/**", "**/fixtures/**"],
"ignoreChecks": [],
"reportFormat": "text",
"categories": ["S3", "IM", "NW", "EN", "LG", "CF"]
}
}
}
}
}
CloudGuard scans the following file types for cloud security patterns:
| File Type | Extensions | Use Case |
|---|---|---|
| Terraform | .tf, .tfvars | HashiCorp Terraform IaC definitions |
| CloudFormation | .yml, .yaml, .json, .template | AWS CloudFormation templates |
| Kubernetes | .yml, .yaml | Kubernetes manifests and Helm charts |
| Docker | Dockerfile, docker-compose.yml | Container configurations |
| Ansible | .yml, .yaml | Ansible playbooks and roles |
| General Config | .conf, .cfg, .ini, .toml, .hcl | Infrastructure configuration files |
| Scripts | .sh, .bash, .ps1, .py | Deployment and provisioning scripts |
| Policy | .json, .rego | IAM policies, OPA Rego rules |
hooks install, prompt to install itThe user might say things like: