Compliance
Contributing to the measures, without promising compliance
Software does not make an organisation compliant: compliance depends on governance, procedures, people and suppliers. Kayzen can contribute to some of the technical measures and provide evidence for them.
General information, not legal advice. Your situation and obligations are to be validated by a professional. Kayzen contributes to certain measures; it does not make any organisation compliant.
Kayzen Security is under development: no module is on sale yet. The contributions described here are based on K-Comply's technical mapping and on the actual status of each module as of 31 October 2026.
Compliance
- NIS2The ten measures of article 21 of directive (UE) 2022/2555, and Kayzen's possible contribution to each.Read the page
- GDPRKayzen as a processor, and its contribution to the security measures of article 32.Read the page
- ISO/IEC 27001The Annex A measures Kayzen can contribute to, by module.Read the page
Our principle
- We write “contributes to the measures of”, never “compliant with”.
- Each contribution refers to a module and its actual status.
- What remains your organisation's responsibility is stated in black and white.
- No compliance percentage is calculated or displayed.