Скачать или смотреть Adhering to compliance requirements with built-in compliance controls

In GitLab 17.11, we are introducing a new way for compliance managers to get more in-depth compliance monitoring in GitLab through ‘requirements’. With requirements, as part of a custom compliance framework, you can define specific requirements from a number of different compliance standards, laws, and regulations that must be followed as an organization.

We are also expanding the number of compliance controls (previously known as compliance checks) that we offer from five to over 50! These 50 out-of-the-box (OOTB) controls can be mapped to the compliance framework requirements.cThese controls check particular project, security, and merge request settings across your GitLab instance to help you meet requirements under a number of different compliance standards, laws, and regulations such as SOC2, NIST, ISO 27001, and the GitLab CIS Benchmark.

Adherence to these controls is reflected in standard adherence report, which is redesigned to take into account requirements and the mapping of controls to those requirements. In addition to expanding our OOTB controls, we now allow users to map requirements to external controls, which can be for items, programs, or systems that exist outside the GitLab platform. These mappings allow you to use the GitLab compliance centre as the single source of truth when it comes to your compliance monitoring and audit evidence needs.

OUTLINE
0:00 - Introduction
0:25 - Creating a Custom Compliance Framework
1:50 - Adding requirements with built-in controls
3:50 - Applying compliance frameworks to projects
4:39 - Viewing compliance adherence status
5:17 - Conclusion

USEFUL LINKS
Release Post: https://about.gitlab.com/releases/202...
Documentation: https://docs.gitlab.com/user/complian...