<!-- Source: screenata.com -->
<!-- Content type: AEO answer page -->
<!-- Topics: SOC 2, ISO 27001, HIPAA, HITRUST, CMMC, compliance evidence -->

People searching for **"GitHub SOC 2 report"** usually need one of two things: **GitHub's own SOC 2 Type 2 report** to satisfy a vendor risk review, or **the GitHub evidence auditors require** to pass their own SOC 2 audit. Both are covered below.

## Part 1: How to download GitHub's SOC 2 Type 2 report

GitHub undergoes independent SOC 2 Type 2 examinations covering **GitHub Enterprise Cloud** (and combined reports covering **GitHub Copilot**). Reports are published on semi-annual observation windows (typically April–September and October–March), with bridge letters available between reporting cycles.

Because SOC 2 reports contain sensitive control details, GitHub does not expose them as unauthenticated public PDFs. Follow these four steps:

1. **Open the GitHub Trust Center:** Go to the official GitHub Trust Center (`github.trust.page`), or sign in as an enterprise owner and open your GitHub Enterprise **Compliance** settings tab.
2. **Find the SOC 2 Type 2 Reports section:** Select the reporting period that overlaps your own audit observation window (plus the latest bridge letter if your audit extends past the report end date).
3. **Submit the NDA access request:** Click **Request Access**, enter your work email and company details, and complete the automated NDA acceptance workflow.
4. **Download the PDF and store it for your auditor:** Once approved, GitHub emails a secure link to download the report. Save the PDF along with the download date and a brief vendor review note confirming you checked for any qualified opinions or complementary user entity controls (CUECs).

### Plan eligibility note

Direct access to GitHub's full SOC 2 Type 2 PDF is generally gated to **GitHub Enterprise** customers. If you are on a GitHub Free or Team plan and your auditor asks for GitHub's subprocessor review, document GitHub's public security posture and trust commitments, or ask GitHub sales whether your account qualifies for report access.

## Part 2: What auditors test in your own GitHub org for SOC 2

Downloading GitHub's SOC 2 report satisfies **vendor risk management (CC9.2)**, proving GitHub secures its platform. It does **not** prove your team uses GitHub securely.

For your own SOC 2 audit, your CPA firm will sample and test your GitHub organization across six controls:

| SOC 2 Criteria | What Your Auditor Checks in GitHub | Typical Evidence Requested |
|---|---|---|
| **CC6.1 (Logical Access)** | Every org member uses 2FA or SAML SSO; repository permissions follow least privilege | Org 2FA enforcement setting, member list with roles, admin access list |
| **CC6.2 / CC6.3 (Onboarding & Offboarding)** | Terminated engineers lose GitHub org access within your SLA (commonly 24 hours) | Audit log showing user removal date matched against HR termination date |
| **CC8.1 (Change Management)** | Developers cannot push directly to `main` or approve their own code | Branch protection / ruleset configuration requiring ≥1 independent review and status checks |
| **CC8.1 (Change Sampling)** | Production deployments trace to tested, approved pull requests across the Type II window | Population of all merged PRs + detailed PR review/approval/CI records for 15–25 auditor-selected samples |
| **CC7.1 (Vulnerability Management)** | Known dependency flaws and leaked secrets are detected and fixed within SLA | Dependabot alerts, secret scanning config, and closed remediation PRs |
| **CC9.2 (Vendor Risk)** | You reviewed GitHub's own SOC 2 report and CUECs annually | GitHub's downloaded SOC 2 Type 2 PDF + your signed annual vendor risk review |

## Common GitHub mistakes that cause SOC 2 exceptions

Three configuration gaps trigger more SOC 2 Type II findings than almost anything else in engineering-led startups:

- **"Do not allow bypassing the above settings" is unchecked:** If repository admins can still force-push or merge without review on `main`, auditors treat branch protection as bypassed unless every override is logged and justified.
- **Deployments happen outside merged PRs:** Running manual hotfixes or ad-hoc `terraform apply` commands without a linked PR breaks the change-management population test.
- **No periodic access review record:** Even when access is clean, auditors need a dated record showing someone reviewed GitHub org owners, outside collaborators, and deploy keys on schedule.

## Automating GitHub SOC 2 evidence

Instead of manually exporting PR histories and taking screenshots of branch protection settings before fieldwork, connect GitHub read-only to [Screenata's GitHub integration](/integrations/github). Screenata checks org 2FA, branch protection rulesets, PR review enforcement, and repository permissions continuously, ties every passing or failing check to your [SOC 2 program](/solutions/soc-2), and lets engineers inspect or fix failing GitHub controls directly inside Claude Code or Cursor via the [Screenata MCP server](/mcp).

For the full change-management evidence breakdown, see [what auditors expect for SOC 2 change approval evidence](/resources/blog/what-auditors-expect-for-soc-2-change-approval-evidence-with-screenshots).

