Security teams should maintain a single inventory of every GitHub App and PAT, including owner, scope, permissions, creation date, last use, and installation context. That visibility makes it easier to spot over-permissioned integrations, unused credentials, and inconsistent access policies before they become an exposure path. Continuous review is better than periodic spreadsheet tracking.
How to govern GitHub Apps and PATs across multiple organisations
The right governance model is centralised visibility with local ownership. Treat every GitHub App and personal access token as a managed access object, not a convenience artifact, and make sure each one has a clear owner, scoped permissions, a documented business purpose, and a review cadence that is shorter than its practical blast radius.
The strongest control is not just knowing what exists, but understanding where it is installed, what it can reach, and whether it still needs that access. That is especially important when a single app or token can span several organisations, repositories, or environments, because the governance failure is usually inconsistent scope rather than outright absence of control.
GitHub and GitHub Actions Security Guide is the best starting point when you need the broader governance context around GitHub Apps, token permissions, workflow exposure, and installation scope.
What inventory data actually matters for control decisions?
An effective inventory should let you answer four questions quickly: who owns it, what permissions it has, where it is installed, and whether it is still used. Creation date and last use are not administrative extras, they are the signals that help you separate active integrations from stale ones and identify credentials that have outlived their intended purpose.
For GitHub Apps, include the app identity, installation targets, granted permissions, and whether the app is organisation-wide or repository-specific. For PATs, include the issuing user, scope, whether it is fine-grained or classic, expiry settings, and any repositories or organisations it can access. Without this level of detail, teams tend to overestimate how much control they have because the inventory exists, but the decision data does not.
Human vs Non-Human Identity helps frame why governance breaks down when people, apps, and delegated access are tracked differently across the same organisations.
How do teams prevent scope creep and stale access?
Governance should be event-driven as well as periodic. New installations, permission changes, token creation, long periods of inactivity, and cross-organisation reuse should all trigger review. The practical test is whether the current scope still matches the current task, not whether the original request was once justified.
Where teams operate across several organisations, they should normalise policy at the top level and enforce it consistently at the edge. That means standard permission baselines, approved exception paths, and a clear process for revoking or rotating credentials when the owning team changes, the app moves function, or the integration is no longer used. When permissions are allowed to accrete over time, a small convenience choice becomes a standing access path.
Token and Session Security Guide is useful when your governance process needs a firmer rule set for token lifetime, rotation, revocation, and replay-resistant handling.
Risk and Threat Considerations
GitHub Apps and PATs become a material exposure path when they are over-scoped, long-lived, or reused across organisations. In practice, the risk is not only theft, but also quiet abuse of valid access, because attackers often prefer credentials that already look legitimate and operate within normal workflow noise.
Failure mechanism: permissions expand beyond the original business need, unused credentials remain active, and cross-organisation access is not reviewed with enough frequency to catch drift, orphaned installations, or stale tokens before they are abused.
Impact: one compromised app or token can create lateral access across repositories, organisations, and automation workflows, increasing the chance of source-code exposure, secret theft, malicious commits, or deeper supply-chain compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack surface, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-5 — Account Management | Covers inventory and review of identities and access paths across organisations. |
| Recommendation — Inventory, review, and remove stale GitHub Apps and PAT access paths on a defined cadence. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Applies to lifecycle, rotation, and revocation of PATs and app credentials. |
| AC-6 — Least Privilege | Directly addresses over-scoped app and token permissions. | |
| Recommendation — Set rotation and revocation rules for GitHub App credentials and PATs. Restrict each GitHub App and PAT to the minimum permissions required. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Supports organisation-wide governance of who can access repositories and automation. |
| Recommendation — Define and enforce a consistent access-control policy for GitHub Apps and PATs. | ||
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | GitHub Apps and PATs are non-human access objects that often accumulate excess permission. |
| Recommendation — Audit app and token scopes for privilege creep and remove unnecessary permissions. | ||
Practitioner Guidance
What to prioritise: Build one authoritative inventory and use it as the source of truth for review, revocation, and exception handling. If the team cannot identify the owner, installation context, and current use of a credential within minutes, the control is already too weak for multi-organisation governance.
Decision rule: If an app or PAT has cross-organisation reach, treat it as higher risk than a repository-local integration and review it on a shorter cycle. If it has no recent use and no documented dependency, revoke it rather than carrying it forward as a harmless leftover.
Practitioner takeaway: The key governance mistake is treating GitHub App and PAT management as inventory maintenance instead of access governance, because the real objective is to keep scope current, attributable, and removable.
Related resources from NHI Mgmt Group
- Govern
- How should security teams monitor personal access tokens across inventory and audit logs in GitHub environments?
- How should security teams govern access tokens used to automate cloud operations across multiple AWS accounts?
- How should security teams govern non-human identities that have persistent access?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org