1. You are here:
2. Handbook
3. Security at GitLab
4. Security Assurance
5. Field Security Team
6. Customer Assurance Package Internal Request Process

On this page

• GitLab's Customer Assurance Package
  • GitLab offers and actively maintains two Customer Assurance Packages:
  • CAP request process
    • New or updated CAP collateral
      • SME owned collateral
    • Additional support

GitLab's Customer Assurance Package

Are you looking for GitLab's Customer Assurance Package? We've moved! Please click below to be redirected:

GitLab offers and actively maintains two Customer Assurance Packages:

• Community Package: The first step on the trust journey, this package is a compilation of publicly available documentation designed to introduce GitLab’s approach to security.
• Customer Package: This package provides detailed security information to prospective and existing customers for completing vendor security assessments.

CAP request process

Due to the nature of some of GitLab's security reports, the Customer Package is available under a Non Disclosure Agreement or contractual confidentiality clauses only.

Note: Customers who have registered for services via GitLab.com and paid via credit card will be required to sign a purpose specific NDA before the CAP can be distributed.

These resources can be requested by a GitLab team member on behalf of a customer/prospect using the Customer Assurance workflow in the #sec-fieldsecurity slack channel or opening an issue directly in the Customer Assurance Service Desk.

Customers or prospects can request a copy using the Request by Email option on our Customer Assurance Package webpage.

New or updated CAP collateral

To request new or updated CAP collateral, click the button below:

SME owned collateral

For collateral owned by SMEs outside of Field Security, we perform an annual review and maintenance session. SMEs are notified via a GitLab issue and assigned relevant collateral pieces for review and maintenance. Upon completion, the updated collateral pieces are added to the appropriate CAP and prepared for publishing.

Additional support

If you have any further questions, please follow the below steps:

• Prospective Customers: Please fill out a request and a representative will reach out to you.
• Current Customers: Please contact your Account Owner at GitLab. If you don't know who that is, please reach out to sales and ask to be connected to your Account Owner.
• GitLab Team Members: Contact the Field Security team using the Customer Assurance workflow in the #sec-fieldsecurity slack channel.