Skip to content
English
Contact AgileBlue Support Customer portal
AgileBlue Portal
  • There are no suggestions because the search field is empty.

Monitoring Your GitHub Environment

AgileBlue collects audit logs and GitHub Advanced Security alerts from your GitHub organization by leveraging the GitHub REST API. This guide covers the steps you complete inside GitHub.

Supported Platform Versions

  • GitHub integration version 2.25.2
  • GitHub Enterprise Cloud — Organization accounts (and Enterprise accounts for enterprise-wide audit logs)

Note: audit log collection via the GitHub API is not compatible with GitHub Enterprise Server.

Before You Begin

Please confirm the following prerequisites before starting:

  • Organization owner access — You must be an owner of the GitHub organization to create the token and access audit logs. For enterprise-wide audit logs, you must be an enterprise owner.
  • Eligible plan — Your account must be on a GitHub Enterprise Cloud plan that includes audit log access.

Setup in GitHub

A user with organization owner (or enterprise owner) access should complete the steps below.

  1. Sign in to GitHub as an organization owner.
  2. Note your organization name — this is the value shown in your organization URL, e.g. github.com/your-organization.
  3. Click your profile photo (top-right) and select Settings.
  4. In the left sidebar, scroll down and select Developer settings.
  5. Select Personal access tokens → Tokens (classic).
  6. Select Generate new token → Generate new token (classic).
  7. Under Note, enter a descriptive name such as AgileBlue Integration. Set an Expiration that aligns with your organization’s security policy, and make a note of the expiration date.
  8. Under Select scopes, enable the scopes for the data you would like AgileBlue to monitor:
    Scope What it enables AgileBlue to monitor
    read:audit_log Organization and enterprise audit log events (required).
    repo Secret Scanning and Dependabot alerts for private repositories.
    security_events Code Scanning alerts (GitHub Advanced Security).
    admin:enterprise Enterprise-wide audit logs. Enterprise owners only — include only if AgileBlue will monitor at the enterprise level.
  9. Scroll to the bottom and click Generate token.
  10. Copy the token immediately and store it in a secure location.
Important: GitHub displays your personal access token only once. If you navigate away before copying it, you will need to generate a new token. Store it somewhere safe right away, and never share it over an unencrypted channel.
  1. Securely send the values listed in the next section back to AgileBlue Support.

Values to Provide to AgileBlue

Collect the following values and send them to AgileBlue using a secure method:

Value Details
Personal Access Token The classic token you generated in Step 8. GitHub displays this only once.
Organization Name Your GitHub organization slug, taken from github.com/<organization>.
Enterprise Account Name Only if AgileBlue will collect enterprise-wide audit logs.
Token Expiration Date So AgileBlue can proactively reach out to renew before it lapses.

How to Send Your Values Securely

Email support@agileblue.com via an encrypted communication method. If you prefer, you may request an encrypted email from AgileBlue first, then reply to that message with the values above. Please do not send your personal access token in plain text.

What Happens Next

Once AgileBlue receives your values, our team completes the integration within our platform – no further action is required on your end. We will confirm with you once GitHub data is flowing into your environment, and we will proactively reach out ahead of your token’s expiration date to arrange a renewal.

Need Help?

AgileBlue is always here to support you and ensure you are 100% successful. If there are any issues with the installation or if you have any questions, please reach out to AgileBlue Support.

Email: support@agileblue.com Phone: (216) 606-9400