Platform OverviewOne evidence trail, from intake to Jira.See how it fits together
See it on your documentsA 30-minute call. Bring a vendor you are reviewing now.Book a demo
GitHub Enterprise Cloud logo

GitHub Enterprise Cloud security and compliance

Source code hosting and DevOps platform · GitHub, Inc. (Microsoft Corporation) · United States

Cloud platform for Git repositories, code review, CI/CD (Actions), package hosting and Copilot, so it typically holds a customer's source code, issues, pipeline secrets and developer account data.

  • SOC 2 report
  • ISO/IEC 27001
  • Public DPA
  • Subprocessor list
  • Data residency option
  • AI data statement
  • –HIPAA BAA
  • Vulnerability disclosure

Checked · 7 certifications and reports · 4 incidents on record since 2020 ·

GitHub Enterprise Cloud states that it holds a SOC 2 Type II report and ISO/IEC 27001 certification, along with SOC 1 Type II, CSA STAR Level 2, PCI DSS, FedRAMP Tailored and others. A data processing agreement is published, and so is its subprocessor list.

Certifications and reports

As GitHub Enterprise Cloud lists them. Scope varies by product, so check each report or certificate against the service you buy.

Certification or reportScopeSource
Audit reports 2
SOC 1 Type II–docs.github.com
SOC 2 Type II–docs.github.com
ISO standards 2
ISO/IEC 27001:2022–docs.github.com
ISO/IEC 42001GitHub Copilot, via Microsoft's certificationlearn.microsoft.com
Government and regional 1
FedRAMP TailoredAuthority to Operate listed for the Enterprise plangithub.com
Industry and privacy 2
CSA STAR Level 2CSA CAIQ Level 1 self-assessment also availabledocs.github.com
PCI DSSAttestation of Compliance; level not stateddocs.github.com

How to get the SOC 2 report

Enterprise owners download SOC 1 and SOC 2 Type II reports, the ISO certificate, CSA documents and the PCI AOC from the Compliance tab of their enterprise account.

Source: docs.github.com

How to get the SOC 2 report from every vendor

Data and contracts

DPA and transfers

The DPA forms part of the GitHub Customer Agreement. Transfers may rely on GitHub's EU-US DPF, UK Extension and Swiss-US DPF self-certification and/or the EU SCCs, with the UK Addendum for UK transfers.

Read the DPA

Subprocessors

GitHub updates the list and notifies subscribers (via gh.io/subscribe) 30 days before a new subprocessor gets access to Customer Personal Data; customers who object may terminate the affected subscription without penalty.

Subprocessor list

Subprocessor lists: compare all vendors

Data residency

GitHub Enterprise Cloud with data residency runs on a dedicated GHE.com subdomain with regions in the EU (including Norway and Switzerland), Australia, the US and Japan.

Source: docs.github.com

EU data residency: compare all vendors

AI and your data

GitHub states it does not use Copilot Business or Copilot Enterprise customer data to train AI models. Since April 2026 it uses interaction data from individual Copilot Free, Pro and Pro+ users for training unless they opt out.

Source: docs.github.com

AI and your data: compare all vendors

HIPAA BAA

Not stated. No BAA was found; the DPA bars customers from providing HIPAA-covered PHI without GitHub's prior, written and specific consent.

Source: github.com

HIPAA BAA: compare all vendors

Service status

githubstatus.com

Security incidents since 2020

Publicly confirmed incidents, as the vendor or its investigators described them.

  1. Stolen OAuth tokens issued to Heroku and Travis CI were used to download private repositories from dozens of organisations, including npm; GitHub said the tokens were not obtained by compromising GitHub's systems.

    Source: github.blog

  2. A compromised personal access token was used to clone GitHub Desktop and Atom repositories and take encrypted code-signing certificates; GitHub said none of the repositories held customer data.

    Source: github.blog

  3. GitHub.com's RSA SSH private host key was briefly exposed in a public repository and replaced; GitHub said it had no reason to believe the key was abused.

    Source: github.blog

  4. After an employee device was compromised through a poisoned third-party VS Code extension, an attacker exfiltrated GitHub-internal repositories, some containing excerpts of customer support interactions; GitHub said it had no evidence of impact to customer enterprises, organisations or repositories.

    Source: github.blog

What to ask GitHub Enterprise Cloud

What the public record leaves open, written to paste into your request.

  1. Does the SOC 2 report cover the product and plan you buy?

    GitHub Enterprise Cloud offers several products. Compare the system description in section 3 of the report with your order form, and ask for a bridge letter if the period ended more than three months ago.

  2. Which complementary user entity controls fall on you?

    Cloud services assume the customer configures access, retention and sharing. List the controls the report expects you to run and give each an owner.

  3. Which subprocessors touch your data?

    The public list covers every product. Ask which entries apply to your plan, region and features, and subscribe to change notices.

  4. How are AI features governed in your tenant?

    Confirm in writing whether your content is used to train models, which AI features are on by default, and which model providers process prompts.

  5. Where will your data be stored and processed?

    Residency options often depend on plan and region. Record the region in the contract and ask where support and backups are handled.

  6. What changed after the incidents on record?

    Ask for the remediation evidence and whether any of it touched the product or region you use.

When the documents arrive, ProcureCortex reads them clause by clause and keeps the page behind every finding.

Sources

  1. GitHub Enterprise Cloud trust centerghec.github.trust.page
  2. GitHub Enterprise Cloud: certifications and attestationsdocs.github.com/en/enterprise-cloud@latest/admin/overview/accessing-compliance-reports-for-your-enterprise
  3. GitHub Enterprise Cloud: FedRAMP Tailoredgithub.com/pricing
  4. GitHub Enterprise Cloud: ISO/IEC 42001learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001
  5. GitHub Enterprise Cloud: data processing agreementgithub.com/customer-terms/github-data-protection-agreement
  6. GitHub Enterprise Cloud: data residencydocs.github.com/en/enterprise-cloud@latest/admin/data-residency/about-github-enterprise-cloud-with-data-residency
  7. GitHub Enterprise Cloud: AI and customer datadocs.github.com/en/copilot/reference/ai-models/model-hosting
  8. GitHub Enterprise Cloud: subprocessor listdocs.github.com/en/site-policy/privacy-policies/github-subprocessors
  9. Incident, Apr 2022github.blog/news-insights/company-news/security-alert-stolen-oauth-user-tokens
  10. Incident, Dec 2022github.blog/news-insights/product-news/action-needed-for-github-desktop-and-atom-users
  11. Incident, Mar 2023github.blog/news-insights/company-news/we-updated-our-rsa-ssh-host-key
  12. Incident, May 2026github.blog/security/investigating-unauthorized-access-to-githubs-internal-repositories
  13. GitHub Enterprise Cloud service statusgithubstatus.com

Compiled from GitHub Enterprise Cloud’s public pages on 17 Nov 2026. Not affiliated with or endorsed by GitHub, Inc. (Microsoft Corporation). Certifications, terms and lists change; check the source before relying on any line here.

Work at GitHub Enterprise Cloud?

Claim this profile for free to add your trust center, a link where buyers request documents and a short statement, shown as provided by GitHub Enterprise Cloud. The public record above stays as compiled from public sources.

Show this profile on your site

Vendors add it to their trust page; reviewers add it to their vendor lists. It links here and updates when the profile does.

GitHub Enterprise Cloud security profile badge
<a href="https://procurecortex.com/vendors/github"><img src="https://procurecortex.com/vendors/badge/github.svg" alt="GitHub Enterprise Cloud security profile on Vendor profiles" width="381" height="52"></a>

GitHub Enterprise Cloud: common questions

Does GitHub Enterprise Cloud have a SOC 2 report?

Yes. GitHub Enterprise Cloud lists a SOC 2 Type II report. Enterprise owners download SOC 1 and SOC 2 Type II reports, the ISO certificate, CSA documents and the PCI AOC from the Compliance tab of their enterprise account.

Is GitHub Enterprise Cloud ISO 27001 certified?

Yes. GitHub Enterprise Cloud lists ISO/IEC 27001 certification. Ask for the certificate and the statement of applicability to check the scope.

Does GitHub Enterprise Cloud sign a DPA?

The DPA forms part of the GitHub Customer Agreement. Transfers may rely on GitHub's EU-US DPF, UK Extension and Swiss-US DPF self-certification and/or the EU SCCs, with the UK Addendum for UK transfers.

Where is GitHub Enterprise Cloud’s subprocessor list?

GitHub Enterprise Cloud publishes it at docs.github.com/en/site-policy/privacy-policies/github-subprocessors. GitHub updates the list and notifies subscribers (via gh.io/subscribe) 30 days before a new subprocessor gets access to Customer Personal Data; customers who object may terminate the affected subscription without penalty.

Does GitHub Enterprise Cloud use customer data to train AI?

GitHub states it does not use Copilot Business or Copilot Enterprise customer data to train AI models. Since April 2026 it uses interaction data from individual Copilot Free, Pro and Pro+ users for training unless they opt out.

Suggest a vendor

Tell us which vendor you review. We will read its public security record, add a profile and email you when it is live.

We use these details to reply about your request. See our Privacy Policy.

Claim the GitHub Enterprise Cloud profile

Claiming is free. Once we confirm you work at GitHub, Inc. (Microsoft Corporation), you can add a vendor statement to this page: your trust center, a link where buyers request documents, a security contact and a short summary. It is shown as provided by GitHub Enterprise Cloud. The public record stays as compiled from public sources, and corrections to it need a public source.

We use these details to verify your claim and reply. See our Privacy Policy.