prowler-compliance-review

You validate Prowler compliance framework JSON by running the local validator script against the framework file, which checks syntax correctness, enforces unique requirement IDs, and verifies cross-checks against existing code. This ensures the compliance definitions meet repository standards before merging.

Adding a new compliance framework to Prowler requires JSON validity checks, duplicate ID detection, required field validation, cross-checks against existing checks, and dashboard and CHANGELOG governance verification to maintain consistency across the codebase.

Yes, the Prowler compliance review process includes duplicate ID detection to ensure all requirement IDs within the framework definitions are unique, alongside validating required fields and verifying proper metadata like dashboard conformity and changelog entries.

You run the validator script by executing the Python validation file directly against your target compliance JSON, for example passing the framework file path as an argument to check JSON validity, unique requirement IDs, complete checks, and proper metadata.

Automating PR reviews for Prowler compliance updates is best handled by running a local validation script that enforces JSON validity, unique requirement IDs, complete checks, and proper metadata such as dashboard conformity and changelog entries, reducing human error and accelerating merges.

Your Prowler compliance framework PR may fail validation due to invalid JSON syntax, duplicate requirement IDs, incomplete checks, or missing metadata such as dashboard conformity and changelog entries, all of which the validator script enforces against repository definitions.