GitHub

Guard integrates with GitHub in two distinct ways:

Both integrations are configured through the Integrations Wizard and store credentials per-tenant with no shared credentials across tenants.

---

Source code manager integration

Use this integration to bring GitHub repository assets into Guard for continuous monitoring.

Prerequisites

• A GitHub account with access to the organizations or repositories you want to monitor.
• Sufficient permissions to generate an access token scoped to repository discovery.

Connect

1. In Guard, go to Integrations > Source Code Managers > GitHub.
2. Open the GitHub card in the Integrations Wizard.
3. Enter your credentials and follow the prompts to validate and save.

Once connected, Guard begins discovering repositories and surfacing them as assets on your attack surface.

---

OSINT enrichment integration

Use this integration to enrich Person assets with GitHub identity data. When Guard discovers a new or updated person, it automatically looks up their GitHub login from their email address and links it to the record — giving you a fuller picture of the people associated with your attack surface without manual research.

What gets enriched

When a matching GitHub account is found for a person's email address, Guard adds the following to the Person record:

• GitHub login — the account username.
• GitHub profile URL — a direct link to the public profile.

Enrichment runs automatically whenever a Person asset is created or updated.

Prerequisites

• A GitHub Personal Access Token (PAT) scoped to read:user.
• The token must belong to a GitHub account that can perform user lookups via the GitHub API.

To generate a PAT:

1. In GitHub, go to Settings > Developer settings > Personal access tokens.
2. Create a token with the read:user scope.
3. Copy the token — you will need it during setup in Guard.

Connect

1. In Guard, go to Integrations > OSINT > GitHub.
2. Open the GitHub (PAT) card in the Integrations Wizard.
3. Paste your PAT and follow the prompts to validate and save.

Guard stores the token securely within your tenant's integration credential store. No credentials are shared between tenants.

After connecting

No additional configuration is required. Guard enriches qualifying Person records automatically. To review enriched records, navigate to Assets > Persons and inspect individual records for the GitHub login and profile URL fields.

Removing the integration

To disconnect, return to Integrations > OSINT > GitHub and remove the stored credential from the Integrations Wizard. Enrichment stops immediately; previously enriched data on existing records is retained.