PR

prowler-compliance

Automates the creation, syncing, and auditing of cloud compliance frameworks within Prowler.

Install

mkdir -p .claude/skills/prowler-compliance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6537" && unzip -o skill.zip -d .claude/skills/prowler-compliance && rm skill.zip

Installs to .claude/skills/prowler-compliance

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Creates and manages Prowler compliance frameworks. Trigger: When working with compliance frameworks (CIS, NIST, PCI-DSS, SOC2, GDPR, ISO27001, ENS, MITRE ATT&CK).
162 chars · catalog description✓ has a “when” trigger
Intermediate

Key capabilities

  • →Auto-generate output formatters for new compliance providers
  • →Validate JSON schemas against Prowler-specific requirements
  • →Fix common configuration bugs like duplicate check IDs
  • →Map security controls to specific Prowler compliance checks
  • →Sync framework files with upstream catalogs like NIST or CIS

How it works

It parses compliance framework JSON files and compares them against the internal Prowler SDK architecture models.

Inputs & outputs

You give it
Compliance framework specification or JSON catalog file
You get back
Validated JSON structure or framework dispatcher code

When to use prowler-compliance

  • →Mapping security checks to compliance controls
  • →Syncing frameworks with upstream sources
  • →Auditing check-to-requirement mappings
  • →Fixing compliance JSON configuration bugs

About this skill

When to Use

  • Creating a framework (decide universal vs legacy first), adding requirements or providers to one
  • Mapping checks, adding ConfigRequirements guardrails, auditing existing mappings
  • Syncing with an upstream catalog, adding a legacy output formatter, fixing JSON bugs
  • Explaining why a finding does not show under a framework (CLI, API or UI)

For reviewing a compliance PR use prowler-compliance-review. Contributor doc: docs/developer-guide/security-compliance-framework.mdx.

Universal vs Legacy: decide first

Both formats load into the universal ComplianceFramework model (legacy via adapt_legacy_to_universal()). The difference is authoring cost.

Universal (default for new frameworks)Legacy per-provider
Locationprowler/compliance/<framework>_<version>.jsonprowler/compliance/<provider>/<framework>_<version>_<provider>.json
ProvidersAny, in one file (checks: {provider: [...]})One per file
Keyslowercase (framework, requirements, checks)Capitalized (Framework, Requirements, Checks)
Attribute schemaDeclared in-file (attributes_metadata), validated at loadPydantic class in compliance_models.py
CLI table/CSV/OCSFData driven from outputs.table_config, no PythonFormatter package + registrations
Guardrailsconfig_requirements (+ Provider on each)ConfigRequirements
Shipped (5.48)cis_controls_8.1, cmmc_2.0, csa_ccm_4.0, cyber_essentials_3.3, dora_2022_2554, fedramp_20x_frr_class_c_2026, fedramp_20x_ksi_2026Everything under provider dirs

Use legacy only to extend an existing legacy family (new CIS version for a provider that already has CIS, ENS for a new provider). Everything else, including single-provider frameworks, is universal.

Files a new framework needs

PieceUniversalLegacy (new family member)
JSONprowler/compliance/<key>.jsonprowler/compliance/<provider>/<key>.json
Attribute modelnone (attributes_metadata)existing class, or new class before Generic in the Union
CLI table / CSV / OCSFnone (needs outputs.table_config)reuse family package; new provider = {framework}_{provider}.py + models.py row + branch in prowler/__main__.py
API compliance CSVnone (auto via process_universal_compliance_frameworks)COMPLIANCE_CLASS_MAP entry in api/src/backend/tasks/jobs/export.py (else GenericCompliance)
API PDFonly if required: generator + FRAMEWORK_REGISTRY + report.py wiringsame
UIoptional: mapper + getComplianceMappers() entry keyed by framework, detail panel, type, iconsame; unknown frameworks use the generic mapper
Dashboardoptional (dashboard/compliance/generic.py fallback)optional
Changelogprowler/changelog.d/<slug>.added.md (towncrier fragment, not CHANGELOG.md)same

Critical Rules

  1. Universal files need outputs.table_config (group_by = a declared attribute key). Without it the framework loads and lists but produces no compliance CSV, OCSF or table.
  2. Declare attributes_metadata with required/enum where possible. If it is missing nothing is validated; when present, unknown keys are rejected.
  3. Set version/Version for any versioned framework. get_check_compliance() keys legacy findings "{Framework}-{Version}", or just "{Framework}" when Version is empty (31 unversioned legacy files ship that way, e.g. hipaa_aws, soc2_aws, mitre_attack_aws). Changing Version on an existing file changes that key. Keep the filename version equal to Version (the CIS table matches compliance_framework.split("_")[1] against Version).
  4. Provider keys in universal checks are lowercase directory names under prowler/providers/. Extending to a provider = adding a key. Every config_requirements entry carries Provider.
  5. Generic stays LAST in Compliance_Requirement.Attributes (Pydantic v1 tries members in order). compliance_models.py uses pydantic.v1 only.
  6. Loaders differ. Compliance.get_bulk() sees only provider dirs and exits on a broken built-in file; the universal loader also reads top-level files and logs-and-skips broken ones. A framework that "disappears" was usually skipped: check the log.
  7. Universal-only frameworks are not in CheckMetadata.Compliance, so they do not appear in the per-finding compliance field of regular outputs; they get their own compliance CSV + OCSF files.
  8. Include every requirement of the source catalog. Empty checks = manual. Do not pad with tangential checks: honest MANUAL beats fake coverage.
  9. Legacy table modules must not import Finding (circular import through get_check_compliance); use TYPE_CHECKING or function-local imports. CSV row field names in models.py are public API.
  10. pdf_config is not consumed by the API; PDFs come from the hardcoded FRAMEWORK_REGISTRY (prowler_threatscore, ens, nis2, csa_ccm, cis).
  11. UI groups on attributes[0] values (Section/SubSection, Category, FamilyName depending on the mapper). Normalize spelling or the tree splits.
  12. Icons: COMPLIANCE_LOGOS in IconCompliance.tsx is an ordered substring match (essentials before essential, cisa before cis, nist before nis2).

Schemas, field tables and guardrail operators: references/schema-reference.md. Loaders, dispatch, API/UI internals: references/compliance-docs.md.

Minimal universal framework

{
  "framework": "My-Framework",
  "name": "My Framework 1.0",
  "version": "1.0",
  "description": "...",
  "attributes_metadata": [
    {"key": "Section", "type": "str", "required": true},
    {"key": "Service", "type": "str"}
  ],
  "outputs": {"table_config": {"group_by": "Section"}},
  "requirements": [
    {
      "id": "MF-1.1",
      "name": "Root MFA",
      "description": "Root account must have MFA enabled.",
      "attributes": {"Section": "IAM", "Service": "iam"},
      "checks": {"aws": ["iam_root_mfa_enabled"], "azure": []}
    }
  ]
}

Real templates: prowler/compliance/dora_2022_2554.json, csa_ccm_4.0.json, cmmc_2.0.json. Legacy templates: assets/ (cis_framework.json, ens_framework.json, iso27001_framework.json, mitre_attack_framework.json, prowler_threatscore_framework.json, generic_framework.json).

Workflows

New universal framework

  1. Write prowler/compliance/<framework>_<version>.json (key = basename).
  2. attributes_metadata + outputs.table_config.group_by.
  3. Map checks per provider (verify ids, see Validation); config_requirements with Provider for configurable checks; empty lists for manual requirements.
  4. Validate. No Python is needed for CLI table/CSV/OCSF or the API CSV export.
  5. Optional UI mapper/detail panel/type/icon, optional PDF generator.
  6. Changelog fragment; user guide under docs/user-guide/compliance/ for high-profile frameworks.

New legacy formatter (existing legacy family, new framework package)

  1. prowler/lib/outputs/compliance/{framework}/ with __init__.py, {framework}.py (copy c5/c5.py, rename function and framework string), models.py (one row model per provider), {framework}_{provider}.py (ComplianceOutput subclass with transform()).
  2. Register: display_compliance_table() branch in compliance.py, per-provider branch in prowler/__main__.py, COMPLIANCE_CLASS_MAP in api/src/backend/tasks/jobs/export.py (startswith for anything versionable).
  3. Tests in tests/lib/outputs/compliance/{framework}/ with fixtures in tests/lib/outputs/compliance/fixtures.py (one evaluated + one manual requirement).

Sync with upstream

Config-driven runner in assets/ (writes legacy JSON): references/upstream-sync.md.

Audit check mappings (cloud auditor)

Golden rule: a check's title/risk must literally verify what the requirement text says; otherwise MANUAL.

python skills/prowler-compliance/assets/build_inventory.py aws          # /tmp/checks_aws.json
python skills/prowler-compliance/assets/query_checks.py aws encryption transit
python skills/prowler-compliance/assets/query_checks.py aws --service iam
python skills/prowler-compliance/assets/dump_section.py cis_5.0_aws "1."   # legacy files only

Encode decisions as full REPLACE lists in a copy of assets/audit_framework_template.py (missing provider key = untouched, [] = explicitly manual), abort on unknown check ids, then validate. Curated mappings and controls Prowler cannot verify: references/check-mapping-reference.md (entries with * are patterns, expand them before use).

Validation (run before every commit)

# 1. Load (both formats). The universal loader returns None on error instead of raising.
uv run python -c "from prowler.lib.check.compliance_models import load_compliance_framework_universal as l; \
fw=l('prowler/compliance/<file>.json'); assert fw, 'see log'; print(fw.framework, len(fw.requirements), fw.get_providers())"

# 2. Catalog integrity for every JSON: unique ids, no repeated checks, every check exists for its provider
uv run pytest tests/lib/check/compliance_catalog_integrity_test.py -k "<file_basename>" -q

# 3. Model/output suites (test_loads_as_universal is parametrized over every shipped JSON)
uv run pytest -n auto tests/lib/check/ tests/lib/outputs/compliance/ -q

# 4. CLI smoke test (listing needs no credentials)
uv run python prowler-cli.py <provider> --list-compliance | grep <key>
uv run python prowler-cli.py <provider> --list-compliance-requirements <key>
uv run python prowler-cli.py <provider> --compliance <key>    # real scan: check output/compliance/

CI and hooks: prek runs check-json and


Content truncated.

When not to use it

  • →General security policy drafting unrelated to Prowler JSON schemas
  • →Manual remediation of cloud infrastructure findings

Prerequisites

Prowler CLI environmentLocal clone of Prowler repository

Limitations

  • →Requires manual verification of domain-specific mapping accuracy
  • →Dependent on Prowler SDK versions and internal framework APIs

How it compares

Unlike generic linting, it enforces compliance-specific architectural constraints required for Prowler's internal check-mapping.

Compared to similar skills

prowler-compliance side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
prowler-compliance (this skill)15moReviewIntermediate
1password276moReviewIntermediate
senior-security3111moReviewAdvanced
fix-dependabot-alerts189moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

1password

openclaw

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

2799

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

3191

fix-dependabot-alerts

microsoft

Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.

1872

red-team-tools-and-methodology

davila7

This skill should be used when the user asks to "follow red team methodology", "perform bug bounty hunting", "automate reconnaissance", "hunt for XSS vulnerabilities", "enumerate subdomains", or needs security researcher techniques and tool configurations from top bug bounty hunters.

759

wsdiscovery

BrownFineSecurity

WS-Discovery protocol scanner for discovering and enumerating ONVIF cameras and IoT devices on the network. Use when you need to discover ONVIF devices, cameras, or WS-Discovery enabled equipment on a network.

16

trivy-offline-vulnerability-scanning

benchflow-ai

Use Trivy vulnerability scanner in offline mode to discover security vulnerabilities in dependency files. This skill covers setting up offline scanning, executing Trivy against package lock files, and generating JSON vulnerability reports without requiring internet access.

14

Search skills

Search the agent skills registry