Secure your GitHub surface
Branch protection that can be bypassed, secrets in git history, and Actions with more access than they need. We don’t connect to GitHub to collect evidence for its own sake — we connect to secure it, and the compliance artefacts follow from that work.
Book a Demo[01] What This Surface Exposes
Where GitHub goes wrong
GitHub goes wrong through exemptions and history: a branch rule your most active engineer can bypass, and secrets that survive the commit that removed them.
- Branch protection rules that administrators can bypass, or that exempt the accounts doing the most merging
- Secrets committed at any point in history, which remain retrievable long after the fixing commit
- GitHub Actions workflows using pull_request_target or unpinned third-party actions
- Deploy keys and personal access tokens with write scope, held by people rather than services
- Outside collaborators and stale team membership retaining repository access
[02] What We Secure
What we watch, catch and fix on GitHub
On GitHub we assess branch protection by who can bypass it, and scan full history rather than the current tree.
- Branch protection assessed for who can bypass it, since a rule with an exemption for your most active engineer is not a control
- Full-history secret scanning, because removing a secret in a later commit does not remove it from the repository
- Third-party action pinning tracked as a supply chain control — an unpinned action is arbitrary code with your token
- Token and deploy key inventory with scope, owner, and last use
- Collaborator access reconciled against your HR record
[03] Where It Lands
Where GitHub lands in your registers
Repositories and pipelines become asset register entries with their own criticality, because a build system that can deploy to production is a production system. Access reviews cover repository and pipeline permissions alongside your other entitlements, and the risk register carries supply chain exposure — the dependencies you pull, the actions you run, and who can push without review.
[04] How We Engage
On GitHub specifically
On GitHub, we revoke stale tokens and collaborator access, pin actions, and tighten branch protection under agreed authority. Rotating whatever a committed secret exposed we run as an incident with your engineers, because the commit is the least of it.
Platform licence
Everything you need to find and fix it yourself, with no ceiling on the depth of the answer.
- Every connected tool monitored for misconfiguration and drift, with findings mapped to the assets and risks they affect
- Remediation guidance that tells you what is wrong and exactly how to fix it — however deep or awkward the issue is. We are engineers running a security company, so the answer is the real one, not a link to vendor documentation
- Assets, access reviews, and risk register populated from the tools themselves rather than from spreadsheets
- Unlimited integrations and unlimited users, with anything missing built within two weeks
Managed service
Every tool you connect through Konfirmity comes under our care, with our team doing the work.
- Continuous misconfiguration and drift monitoring across every connected tool, watched by our analysts rather than by a dashboard waiting for you
- Incident response led by us, with containment coordinated with your team
- Remediation performed directly wherever you have granted us the authority to act — and where we cannot act, we project-manage the fix to completion rather than handing you a ticket
- Decision support on the tools themselves: where something is failing you on capability or costing more than it returns, we will tell you, and help you replace it
[05] GitHub FAQs
What GitHub permissions does Konfirmity need?
Konfirmity needs a GitHub App installed with read access to administration, contents, metadata, actions and secret scanning alerts. App installation is preferred over personal access tokens because permissions are explicit, scoped per repository and not tied to an individual's account.
What do you do about secrets found in git history?
We treat the live credential as the incident and the commit as the evidence. Rewriting history without rotating first leaves the exposure in place, so we identify what the secret grants, drive rotation, and then help you decide whether history rewriting is worth its disruption.
GitLab
Bitbucket
Jenkins
CircleCI
Snyk