feat(prowler): chunk15 add the NIS2/ISO27001 compliance contract (#422) - #445
Draft
Christophe Melchior (Kakudou) wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #422.
Chunk 15 of the Prowler injector stack: add the NIS2 / ISO 27001 compliance contract — the CHK.015 NIS2 and ISO 27001 assessments: the BDD suite (behaviour, lifecycle / verbose diagnostics recorded through the conftest recording logger, OCSF record fixtures), the new
contracts/nis2_iso27001.pydefining the seven canonical routesnis2/aws,nis2/azure,nis2/gcp,iso27001/aws,iso27001/azure,iso27001/gcp,iso27001/kubernetesagainst the Prowler 5.36 NIS2 / ISO 27001:2022 frameworks (nis2_aws,nis2_azure,nis2_gcp,iso27001_2022_aws,iso27001_2022_azure,iso27001_2022_gcp,iso27001_2022_kubernetes), the seven selectors added to theComplianceSelectortype and the client's compliance → provider-type mapping, unsupported and cross-provider compliance selectors rejected before the adapter / engine, their registration in the registry /__init__(15 → 22 canonical contracts), and the cross-chunk registry-alignment BDD updates (chk001, chk007, chk008, chk009, chk010, chk011, chk012, chk013, chk014) plus the chk006 unit registry expectations. Existing check and service selection channels are untouched, and framework routing is not exposed as form input.Re-landed from
feat/422-prowler-chk015-compliance-nis2-iso27001(c75f7a9..89bcb8e): 10 source commits folded into 4 (Q1:227551c; Q2:96ee856+0df461c+859639f+caa65bf+89bcb8e; Q3:0007bf8+92e5f69+5f93042; Q4:f7d4102). Q2 landed at the source-final post-images of the CHK.015 BDD suite (including the source's own missing__init__.pyfix from859639f) and the chk006 registry unit test, so the four later suite commits fold in as content with zero conflicts; Q3 carries the five implementation files (the new contract at its5f93042post-image, unchanged through the tip) and the nine prior-chunk BDDs at their final post-images, with the CHK.014 BDD at its0007bf8post-image; Q4 is the re-flow of that CHK.014 BDD (1+/3−). Gate V (whole-branch tree vs source tip89bcb8e): byte-identical except (a) the 14pyproject.tomlversion differences of the other injectors (source base3.260805.0vs re-land base3.260821.0;prowler/subtree otherwise untouched), (b) the 12trap-analysis.mdfiles (chk004–chk015) excluded by standing call, and (c) one approved deviation — the pinnedpyoaevversion assert removed fromprowler/tests/unit/chk006_executable_base/test_outputs_registry_runtime.py.