title

The benefits of transparency in a compliance audit

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; 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; frame-src 'self' https: http:; img-src 'self' https: http: data: *.google-analytics.com *.googletagmanager.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:title

The benefits of transparency in a compliance audit

og:description

We’re transparent by default, and just completed our first SOC 2 Type 1 audit! How does our public-first stance affect our compliance efforts and impact an audit?

og:image

https://images.ctfassets.net/r9o86ar0p03f/mvdheuvel-unsplash.jpg/61096f70559a5163fe8f690d7bcd9499/mvdheuvel-unsplash.jpg?fm=webp&w=820&h=500

og:url

https://about.gitlab.com/blog/2020/04/28/benefits-of-transparency-in-compliance/

og:type

article

twitter:card

summary_large_image

twitter:site

@GitLab

alternate

/atom.xml

alternate

/all-releases.xml

alternate

/security-releases.xml

alternate

/releases.xml

apple-touch-icon

/blog/nuxt-images/ico/apple-touch-icon-57x57.png?cache=2022041

x-default

https://about.gitlab.com/blog/2020/04/28/benefits-of-transparency-in-compliance/