Complass
Automatic evidence from your systems: checked regularly, read-only, no personal names
The folder is called "Audit evidence" and contains 43 screenshots. The newest shows the MFA policy from March. Whether it still applies today, it does not show.
ISO/IEC 27001 requires the effectiveness of the ISMS to be monitored and compliance with one's own policies to be reviewed regularly; NIS2 requires procedures to assess the effectiveness of risk management measures (§ 30(2) no. 6 BSIG). A screenshot only proves a moment.
The whitepaper shows which settings Complass reads once a day from Microsoft Entra ID and Microsoft 365, GitHub, Google Workspace, AWS, Azure, and Google Cloud and which results GitLab and Greenbone report on their own, with which access each source is connected, why read permissions are enough and how that is enforced, why counts instead of names of people are stored, and how a measurement becomes evidence with a traffic light and a chained history in which later changes become detectable. With limits, five steps to the first evidence, and a checklist.
Each implementation chapter includes a short "Implementation in Complass" box (decision W11); only features already live are named.
15 pages · Version 1.3 · as of · Author Marc Linden, Complass GmbH
Try Complass with your own data
Set up your trial yourself, with a sample project per framework if you like. If you would rather see Complass first, request a demo.