title

How GitLab went about choosing the right compliance framework

charset

utf-8

viewport

width=device-width, initial-scale=1

Content-Security-Policy

default-src 'self' https: http:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https: http: *.googletagmanager.com *.mutinycdn.com; style-src 'self' 'unsafe-inline' https: http:; object-src https: http:; base-uri 'self'; connect-src 'self' https: http: wss: ws: *.google-analytics.com *.analytics.google.com *.googletagmanager.com *.mutinyhq.com *.mutinyhq.io *.mutinycdn.com; frame-src 'self' https: http:; img-src 'self' https: http: data: *.google-analytics.com *.googletagmanager.com *.mutinycdn.com; manifest-src 'self'; media-src 'self' https: http:; child-src 'self' blob: https: http:; font-src 'self' https: http: data:;

format-detection

telephone=no

og:type

website

og:title

How GitLab went about choosing the right compliance framework

og:description

Independent vs aggregate? Determining the most effective security controls approach for any organization has many considerations.

og:image

https://about.gitlab.com/images/blog/hero-images/compliance-frameworks.jpeg

og:url

https://about.gitlab.com/blog/choosing-a-compliance-framework

twitter:card

summary_large_image

twitter:site

@GitLab

twitter:title

How GitLab went about choosing the right compliance framework

twitter:image

https://about.gitlab.com/images/blog/hero-images/compliance-frameworks.jpeg

twitter:description

Independent vs aggregate? Determining the most effective security controls approach for any organization has many considerations.

alternate

/atom.xml

alternate

/all-releases.xml

alternate

/security-releases.xml

alternate

/releases.xml

apple-touch-icon

/images/ico/apple-touch-icon.png

x-default

https://about.gitlab.com/blog/choosing-a-compliance-framework/