FedRAMP Execution Working Group
|Date Created||November 25, 2021|
|Slack||#wg_fedramp (only accessible from within the company)|
|Google Doc||Working Group Agenda (only accessible from within the company)|
|Epic||Main Project Epic (only accessible from within the company)|
|Public Handbook Page||GitLab’s FedRAMP Authorization Program|
|Internal Handbook Page||[FedRAMP Compliance]https://internal.gitlab.com/handbook/engineering/fedramp-compliance/|
|Epic||Top Initiative Epic (limited access)|
GitLab achieves FedRAMP Moderate Authorization (Authority to Operate - ATO) for a new SaaS offering.
Roles and Responsibilities
|Working Group Role||Team Member||Functional Title|
|Executive Sponsor||David DeSanto||Chief Product Officer|
|Functional Lead: PM||Chris Balane||Sr. Product Manager, US Public Sector Services|
|Functional Lead: Pub Sec||Bob Stevens||Area Vice President, Public Sector Sales|
|Functional Lead: Infrastructure||Stephen Dumesnil||Engineering Manager, US Public Sector Services|
|Functional Lead: Compliance||Corey Oas||Manager, Security Compliance, Dedicated Markets|
|Executive Stakeholder||David DeSanto||Chief Product Officer|
|Member||Chris Maurer||Public Sector Manager, Customer Success|
|Member||Vincy Wilson||Quality Engineering Manager, Fulfillment, Growth, Sec, Enablement|
|Member||Joanna Shih||Quality Engineering Manager, Ops|
GitLab is pursuing FedRAMP authorization at the Moderate Impact Level. We will evaluate demand for High once we attain Moderate.
Further details of the FedRAMP plan, including anticipated or actual dates, cannot be shared publicly at this time. Team members can view details in the internal handbook. This public handbook page contains information about the FedRAMP Authorization process as it pertains to GitLab.