Screenata

SOC 2 Controls and Evidence

How do I get GitHub's SOC 2 report, and what GitHub controls do auditors test for my own SOC 2?

Quick answer

To download GitHub's own SOC 2 Type 2 report for vendor risk management, visit the GitHub Trust Center (github.trust.page) or your GitHub Enterprise Compliance tab, select the audit period (covering GitHub Enterprise Cloud and GitHub Copilot), complete the NDA request form with your work email, and download the PDF from the verification email. Direct report downloads generally require an eligible GitHub Enterprise account. If you are preparing your own company for SOC 2, auditors also test six core controls inside your GitHub organization: SSO/MFA, org role reviews, branch protection, PR approvals, CI checks, and Dependabot or secret scanning.

4 min read

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 CriteriaWhat Your Auditor Checks in GitHubTypical Evidence Requested
CC6.1 (Logical Access)Every org member uses 2FA or SAML SSO; repository permissions follow least privilegeOrg 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 codeBranch 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 windowPopulation 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 SLADependabot alerts, secret scanning config, and closed remediation PRs
CC9.2 (Vendor Risk)You reviewed GitHub's own SOC 2 report and CUECs annuallyGitHub'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. 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, and lets engineers inspect or fix failing GitHub controls directly inside Claude Code or Cursor via the Screenata MCP server.

For the full change-management evidence breakdown, see what auditors expect for SOC 2 change approval evidence.

Frequently asked questions

Where do I download GitHub's SOC 2 Type 2 report?
Request it through the official GitHub Trust Center (github.trust.page) under the SOC 2 Type 2 Reports section, or from the Compliance tab inside your GitHub Enterprise settings. You submit your work email and accept GitHub's NDA flow, then receive a secure download link by email.
Can I get GitHub's SOC 2 report on a Free or Team plan?
Generally no. GitHub restricts downloadable SOC 2 Type 2 reports to eligible paid accounts, primarily GitHub Enterprise customers. Teams on Free or Team plans can reference GitHub's public security documentation or contact GitHub sales if an enterprise customer requires the full report during vendor review.
Does GitHub's SOC 2 report make my repositories SOC 2 compliant?
No. Under the shared responsibility model, GitHub's SOC 2 report only covers GitHub's own platform security and availability. Your auditor still tests how your engineering team configures GitHub: who has admin access, whether branch protection enforces code review, and whether production changes trace back to approved pull requests.
What GitHub evidence do SOC 2 auditors ask for?
Auditors typically request proof of org-wide 2FA or SAML SSO, quarterly member and admin access reviews (CC6.1/CC6.2), branch protection rules on default branches, a sample of merged pull requests showing independent peer approval and passing CI checks (CC8.1), and vulnerability or secret scanning alerts with remediation trails (CC7.1).

Related questions

AI for Compliance Audit Prep

Can AI actually write SOC 2 policies that pass an audit?

Yes, if the AI reads your actual codebase and infrastructure instead of generating from training data. AI-written policies that reference your specific tools and configurations pass audits because they describe what the auditor will observe. Generic AI output (like ChatGPT responses) fails for the same reason templates fail.

AI for Compliance Audit Prep

Can AI agents replace the need for a compliance consultant?

AI agents that read your codebase and infrastructure can handle the repeatable operational work in a consultant engagement, system analysis, policy drafting, evidence collection, and gap assessment. You still need a CPA auditor for the report, and a consultant's judgment still matters for complex scope. Increasingly, consultants themselves run AI to do the grunt work and take on more clients.

SOC 2 Tools and Platforms

Can I switch compliance platforms during a SOC 2 observation period?

Yes. A SOC 2 Type II report covers how your controls operated across the observation period, and the platform that stored the evidence is not part of that test, so switching mid-window does not restart it. Agree a cutover date with your auditor first. Before your access ends, export what exists only inside the old platform: policy approvals, employee acknowledgments, access reviews, uploaded evidence with its original dates, and test history. Keep evidence continuous across the cutover, and pick a platform that leaves the audit to the firm you already use.

Connect and see

See your SOC 2 with your real systems.

Connect GitHub and cloud read-only. Vera shows your control matrix, policy gaps, and prioritized next actions before you commit to anything.