GitHub compliance, automated for SOC 2, ISO 27001 & Cyber Essentials
OneClickComply connects to GitHub through a least-privilege API connection and checks how it is configured against SOC 2, ISO 27001, Cyber Essentials and NIST CSF. Checks include: default branch requires pull-request review, MFA required for all organisation members and secret scanning enabled on all repositories. Every result is stored as audit evidence, so there are no screenshots to collect.
SOC 2 · ISO 27001 · Cyber Essentials · NIST CSF
- Set up in minutes
- Least-privilege access
- Evidence collected continuously
- Built for UK teams
Continuous control checks
What OneClickComply checks in GitHub
Source control is where change management lives. Branch protection, code review and secret scanning are standard SOC 2 and ISO 27001 asks.
Default branch requires pull-request review
MFA required for all organisation members
Secret scanning enabled on all repositories
See it work
Watch OneClickComply check GitHub
A read-only API connection pulls GitHub's settings, tests each one against your controls and files the result as evidence.
GitHub admin
Security settings
- Default branch requires pull-request review
- MFA required for all organisation members
- Secret scanning enabled on all repositories
OneClickComply
- Connected to the GitHub API (read-only)
- Reading repositories, branch protection, members
- Default branch requires pull-request review
- MFA required for all organisation membersGap found, fix it in one click with OneClickFix
- Secret scanning enabled on all repositories
Evidence saved and mapped
GitHub evidence, collected automatically
The GitHub evidence auditors ask for, captured on a schedule and stored against the right requirement. No more screenshots the week before the audit.
- Repositories
- Branch protection
- Members
- MFA status
- Secret scanning
- Audit log
Mapped to your frameworks
Every GitHub check is mapped to the controls it satisfies, so one piece of evidence counts everywhere it applies.
Set up in minutes
How to connect GitHub to OneClickComply
- 1
Connect GitHub
Authorise a read-only, least-privilege connection to GitHub from your OneClickComply dashboard. It takes a couple of minutes.
- 2
We check every control
OneClickComply pulls GitHub's settings, tests them against your frameworks and flags anything that fails.
- 3
Fix it in one click
OneClickFix can correct supported misconfigurations in GitHub for you, with the change logged as evidence.
See GitHub checked live against your controls.
GitHub security & compliance FAQs
How does OneClickComply connect to GitHub?
Through a direct, least-privilege API connection that you authorise from your OneClickComply dashboard. You can revoke it at any time.
What does OneClickComply check in GitHub?
Its checks for GitHub include: default branch requires pull-request review, MFA required for all organisation members and secret scanning enabled on all repositories. Each result is stored as evidence against the requirement it satisfies.
What GitHub evidence do auditors ask for?
For developer tools and code tools, auditors usually want repositories, branch protection, members and MFA status. OneClickComply captures it on a schedule, so it's ready before they ask.
Which frameworks does the GitHub integration cover?
GitHub evidence is mapped to SOC 2, ISO 27001, Cyber Essentials and NIST CSF.
Further reading on GitHub
All articlesAlso connects with
Other developer tools and code tools we connect to
Using more than one developer tools and code tool? OneClickComply connects to these too, so your evidence stays in one place.
Get GitHub audit-ready this week
OneClickComply connects to GitHub and the rest of your stack, collects the evidence and tells you exactly what to fix. If it has a web admin console, we can work with it.
All product names and logos are trademarks of their respective owners.