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 report | Scope | Source |
|---|---|---|
| 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 42001 | GitHub Copilot, via Microsoft's certification | learn.microsoft.com |
| Government and regional 1 | ||
| FedRAMP Tailored | Authority to Operate listed for the Enterprise plan | github.com |
| Industry and privacy 2 | ||
| CSA STAR Level 2 | CSA CAIQ Level 1 self-assessment also available | docs.github.com |
| PCI DSS | Attestation of Compliance; level not stated | docs.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
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.
- 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.
- 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
- 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
- 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
- Vulnerability disclosure
docs.github.com/en/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities
- Service status
Security incidents since 2020
Publicly confirmed incidents, as the vendor or its investigators described them.
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
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
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
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- GitHub Enterprise Cloud trust centerghec.github.trust.page
- GitHub Enterprise Cloud: certifications and attestationsdocs.github.com/en/enterprise-cloud@latest/admin/overview/accessing-compliance-reports-for-your-enterprise
- GitHub Enterprise Cloud: FedRAMP Tailoredgithub.com/pricing
- GitHub Enterprise Cloud: ISO/IEC 42001learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001
- GitHub Enterprise Cloud: data processing agreementgithub.com/customer-terms/github-data-protection-agreement
- GitHub Enterprise Cloud: data residencydocs.github.com/en/enterprise-cloud@latest/admin/data-residency/about-github-enterprise-cloud-with-data-residency
- GitHub Enterprise Cloud: AI and customer datadocs.github.com/en/copilot/reference/ai-models/model-hosting
- GitHub Enterprise Cloud: subprocessor listdocs.github.com/en/site-policy/privacy-policies/github-subprocessors
- Incident, Apr 2022github.blog/news-insights/company-news/security-alert-stolen-oauth-user-tokens
- Incident, Dec 2022github.blog/news-insights/product-news/action-needed-for-github-desktop-and-atom-users
- Incident, Mar 2023github.blog/news-insights/company-news/we-updated-our-rsa-ssh-host-key
- Incident, May 2026github.blog/security/investigating-unauthorized-access-to-githubs-internal-repositories
- 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.
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.