ben.carrasco/prowler
1
0
Fork 0
mirror of https://github.com/prowler-cloud/prowler.git synced 2026-07-04 19:21:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(compliance): expand developer guide for new compliance frameworks (#10870)

Browse Source 
Co-authored-by: Pedro Martín <pedromarting3@gmail.com>
This commit is contained in:
Hugo Pereira Brito
2026-05-12 09:04:35 +01:00
committed by GitHub
parent 8f041f6f52
commit adbfc0bcd1
15 changed files with 650 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/tutorials/v2_to_v3_checks_mapping.mdx
+1 -1
View File
@@ -2,7 +2,7 @@
Prowler v3 and v4 introduce distinct identifiers while preserving the checks originally implemented in v2. This change was made because, in previous versions, check names were primarily derived from the CIS Benchmark for AWS. Starting with v3 and v4, all checks are independent of any security framework and have unique names and IDs.
For more details on the updated compliance implementation in Prowler v4 and v3, refer to the [Compliance](/user-guide/cli/tutorials/compliance) section.
For more details on the updated compliance implementation in Prowler v4 and v3, refer to the [Compliance](/user-guide/compliance/tutorials/compliance) section.
```
checks_v4_v3_to_v2_mapping = {