Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/checking-infrastructure-compliance

@820dfc8
Run it yourself

Execute use when you need to work with compliance checking. This skill provides compliance monitoring and validation with comprehensive guidance and automation. Trigger with phrases like "check compliance", "validate policies", or "audit compliance".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/checking-infrastructure-compliance

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈926 when used: this file. ≈4.6k more on demand in 6 files.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈287 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Checking Infrastructure Compliance

Overview

Audit infrastructure configurations against compliance frameworks (CIS Benchmarks, SOC 2, HIPAA, PCI-DSS, GDPR) using policy-as-code tools like Open Policy Agent (OPA), Checkov, and tfsec. Generate compliance reports, identify violations, and produce remediation plans for Terraform, Kubernetes, and cloud provider configurations.

Prerequisites

  • Policy-as-code tool installed: checkov, tfsec, opa, or kube-bench
  • Infrastructure-as-code files (Terraform, CloudFormation, Kubernetes manifests) in the project
  • Cloud provider CLI authenticated with read access to resources
  • Compliance framework requirements documented (CIS, SOC 2, HIPAA, PCI-DSS)
  • jq for parsing JSON policy outputs

Instructions

  1. Identify the applicable compliance framework(s) based on industry and data classification
  2. Scan Terraform files with checkov -d . or tfsec . to detect misconfigurations
  3. Scan Kubernetes manifests for security issues: missing resource limits, privileged containers, missing network policies
  4. Validate IAM policies for least-privilege violations using cloud-native tools (aws iam access-analyzer)
  5. Check encryption at rest and in transit: verify S3 bucket encryption, database TLS, and EBS volume encryption
  6. Audit logging configurations: confirm CloudTrail/Cloud Audit Logs are enabled and sent to immutable storage
  7. Generate a compliance report mapping each finding to the relevant control (e.g., CIS AWS 2.1.1)
  8. Produce remediation Terraform/YAML patches for each violation with severity ranking (Critical, High, Medium, Low)
  9. Set up CI/CD integration so compliance checks block merges on Critical/High violations

Output

  • Compliance scan results in JSON/SARIF format for CI integration
  • Markdown compliance report with control mappings and pass/fail status
  • Remediation code patches (Terraform diffs, Kubernetes manifest updates)
  • OPA/Rego policy files for custom organizational rules
  • CI/CD pipeline step configuration for automated compliance gating

Error Handling

Error Cause Solution
checkov: no Terraform files found Scanner run from wrong directory Specify path explicitly with -d path/to/terraform/
tfsec: failed to parse HCL Syntax error in Terraform files Run terraform validate first to fix HCL syntax before compliance scan
False positive on compliance check Rule too broad for the specific use case Add inline skip comments (#checkov:skip=CKV_AWS_18:Reason) or create a .checkov.yml skip list
OPA policy evaluation error Rego syntax error or missing input data Test policies with opa eval -d policy.rego -i input.json and validate Rego syntax
Scan timeout on large codebase Too many files or complex module references Use --compact mode, scan directories individually, or increase timeout limits

Examples

  • "Run a CIS Benchmark compliance check against all Terraform files and generate a report with remediation steps for Critical findings."
  • "Create OPA policies that enforce: all S3 buckets must have encryption, all EC2 instances must have IMDSv2, and all security groups must not allow 0.0.0.0/0 ingress."
  • "Scan Kubernetes manifests for PCI-DSS compliance: verify no privileged containers, all pods have resource limits, and network policies exist for every namespace."

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk MEDIUM
  • Gen Agent Trust Hub2mo

    The skill facilitates infrastructure compliance audits using standard security tools. It contains embedded Python code snippets within a JSON configuration file designed for runtime execution, and it processes external configuration data which presents a surface for indirect prompt injection.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.26.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "devops",
  "monitoring",
  "compliance",
  "audit"
]
All 6 allowed tools
ReadWriteEditGrepGlobBash(cmd:*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/checking-infrastructure-compliance