Synqly Adds GitHub Identity Integration for Access Visibility

We are announcing a new GitHub identity integration now live within the Synqly ecosystem. Security vendors building on Synqly can connect directly to GitHub as an identity provider and give their OEM customers visibility into a customer’s GitHub users, teams, and organization level activity, without carrying the engineering cost of building and maintaining that connector on their own.

GitHub is the platform where most software organizations already manage who can access their code, and that access model, organizations, teams, and roles, is itself a form of identity data that security teams increasingly need to account for. A developer’s GitHub permissions determine what source code, secrets, and deployment pipelines that person can reach, which makes GitHub organization membership a meaningful input for identity governance and insider risk programs, not just a developer productivity concern. Readers who want more background on the platform itself can visit GitHub.

With the GitHub identity integration live, OEM customers building their product on Synqly can query users and groups from a customer’s GitHub organization through one consistent API, rather than writing a separate connector for GitHub’s own identity endpoints. The get user and query users capabilities return user objects that include a person’s current groups and roles where GitHub exposes that data, while the get group and query groups capabilities return group objects along with the roles assigned to them. A get group members capability lists the users who belong to a specific group, which lets a product answer a direct question, such as who currently has access through a given team, without assembling that answer from several separate calls. A query audit log capability rounds this out by returning events from the organization’s audit log, though this capability requires a GitHub Enterprise plan or a GitHub Enterprise Server instance, since GitHub does not expose organization audit log data on lower plan tiers.

Together, these capabilities let a security product fold GitHub organization access into the same identity picture it already builds from providers like an identity provider or a directory service, rather than treating developer access to source code as a blind spot separate from the rest of a customer’s identity posture. Full configuration and setup instructions for this integration live in the GitHub Identity Configuration Guide on the Synqly documentation site at docs.synqly.com/guides/provider-configuration/github-identity-setup, and we are not restating capabilities beyond what is documented there.

This integration extends GitHub’s presence inside the Synqly ecosystem rather than introducing GitHub to it for the first time. Synqly customers already connect to GitHub through a ticketing integration built on GitHub Issues and an application security integration that surfaces findings from GitHub’s own application security tooling. This new GitHub identity integration adds a third category of GitHub coverage to that list. We are linking to those pages rather than repeating their use cases here, since each integration is documented in full on its own page.

Full details on the GitHub identity integration, including supported capabilities and schema mappings, live on the GitHub Identity integration partner page. For hands on setup instructions, the GitHub Identity Configuration Guide at docs.synqly.com/guides/provider-configuration/github-identity-setup walks through generating a fine grained personal access token and configuring the organization slug Synqly needs to connect.

This GitHub identity integration is part of Synqly’s Identity Unified API, which already connects OEM products to identity providers including Microsoft Entra ID and Google Workspace, among others. Source code access rarely appears in the same identity review as an employee’s email or single sign-on account, even though a compromised or overprivileged GitHub account can expose far more than either. Instead of standing up and maintaining a separate connection to GitHub’s identity endpoints alongside every other identity provider a customer already runs, product teams can integrate with Synqly once and pick up new identity sources, including this GitHub identity integration, as Synqly adds them to the ecosystem.