You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ISO 27001:2022 didn't just add controls, but they came up with completely new controls. It can be seen as a backwards-incompatible change of ISO 27001. Let's map it.
Prerequisites
The following acceptance criteria assumes knowledge with the following concepts and tools:
Said page maps all applicable (as determined by the author) ISO 27001:2022 controls to Compliant Kubernetes features using the mkdocs-ciso-plugin. The tag prefix should be ISO 27001:2022.
Controls which are not applicable to Compliant Kubernetes are listed in a table at the end, which includes "justification for exclusion", similar to this page. For example, Compliant Kubernetes does not provide any story to A 6.4 Disciplinary Process. Please look at each control and write a good justification for exclusion along the lines of "This control requires a disciplinary process, which is outside the scope of Compliant Kubernetes." Please group controls which have a similar justification for exclusion.
The German TSO's information security policy is based on ISO 27001:2022. Also, we passed our ISO 27001:2022 recertification and no finding was related to the documentation of Compliant Kubernetes. Hence, the current value of "4" is correct.
ISO 27001:2022 didn't just add controls, but they came up with completely new controls. It can be seen as a backwards-incompatible change of ISO 27001. Let's map it.
Prerequisites
The following acceptance criteria assumes knowledge with the following concepts and tools:
Acceptance criteria
ISO 27001:2022
.Additional context
Ask @cristiklein , @HansOlofEdblom or @OlleLarsson
Downstream tasks
The text was updated successfully, but these errors were encountered: