Skip to content Skip to footer

GitHub’s New Security Controls and Developer Tools: What Engineering Teams Should Adopt Now

What Happened

GitHub made security advisory permissions generally available in custom repository roles. Owners can delegate advisory and private vulnerability report work for specific repositories without granting repository administrator or organization-wide security manager access. Merging changes from a temporary private fork still requires an administrator or security manager. [1]

GitHub Enterprise Server 3.23 is a release candidate, not a general-availability release. It adds a public-preview, CPU-based detector for unstructured secrets that can run in air-gapped environments, broader malicious-package coverage, more expressive Projects filters, and an option for OAuth apps to use eight-hour access tokens with refresh tokens. Dependabot version-update pull requests will wait at least three days. [2]

Other changes are closer to daily developer workflows: GitHub Desktop 3.7.0 supports multiple accounts per host and associates each repository with an account; the pull request Overview public preview makes merge blockers easier to distinguish from failed optional checks; and dashboard favorites can be pinned across web and mobile, up to 25 repositories. [3][4][5]

Why It Matters to Businesses

The advisory-role change offers a narrower way to staff vulnerability response across product teams. Clearer pull request status can reduce time spent determining whether a change is actually blocked, while Desktop’s per-repository account selection can help developers working across company and client organizations use the intended credentials. These are workflow improvements, not substitutes for access reviews or branch protections. [1][4][5]

For self-hosted GitHub, the 3.23 candidate is worth testing where air-gapped secret detection or malicious-package intelligence matters. Its three-day wait for version-update pull requests also changes dependency maintenance timing and should be assessed against teams’ update policies. [2]

Kimbodo Engineering Perspective

We would prioritize permission boundaries and merge controls over interface changes. An advisory manager needs enough authority to coordinate disclosure, but the separate requirement for an administrator or security manager to merge a private-fork fix remains an important handoff to design into the response process. [1]

The pull request Overview can improve reviewer comprehension, but the authoritative control is still the configured required checks and approvals. Likewise, a preview secret detector should be evaluated for useful findings and operational noise before it becomes part of an incident-response workflow. [2][5]

How We Would Implement It

  • Map vulnerability-response duties to the four advisory permissions, assign custom roles to repository-specific teams, and document who can approve and merge fixes from temporary private forks. [1]
  • Test GHES 3.23 in a non-production appliance before upgrading. Exercise secret detection against representative repositories, review CPU impact, validate dependency-alert coverage, and check OAuth refresh-token handling for integrations that opt in. [2]
  • Pilot the pull request Overview with maintainers. Confirm that required checks, optional failures, approvals, and force-push history are interpreted correctly before recommending it broadly. [5]
  • For developers using multiple accounts on one host, upgrade GitHub Desktop to 3.7.0 and verify each repository’s account association before cloning or publishing sensitive work. [4]

Risks, Costs and Security

Custom roles reduce the need for broad privileges, but incorrect assignments can still expose private vulnerability reports or permit premature publication. Review membership regularly and retain a clear escalation path for merges that require elevated authority. [1]

GHES 3.23 remains a release candidate, and its AI secret detector is a public preview. Budget testing time and appliance CPU capacity rather than assuming production behavior or detection quality. The version-update delay may reduce immediate dependency-change volume, but teams should account for the later arrival of those pull requests. [2]

These notes establish GitHub changes only; they do not substantiate new releases from Cursor, Windsurf, Replit, Sourcegraph, JetBrains, VS Code, or Continue.dev.

Where Kimbodo Comes In

Kimbodo builds and operates this in production for businesses — see our AI Application Development practice, or Estimate My AI Application.

Sources

  1. [1] Security advisory permissions are now generally available
  2. [2] GitHub Enterprise Server 3.23 release candidate
  3. [3] Pin your favorite repositories to your dashboard
  4. [4] GitHub Desktop now supports multiple accounts per host
  5. [5] Improvements on the pull request overview in public preview

Leave a comment

0.0/5

Engineering Founded & Customer Focused

KIMBODO LLC. © 2026. All Rights Reserved.