This version of GitHub Enterprise was discontinued on 2020-11-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Enabling alerts for vulnerable dependencies on GitHub Enterprise Server

You can connect your GitHub Enterprise Server instance to GitHub Enterprise Cloud and enable security alerts for vulnerable dependencies in repositories in your instance.

Site administrators for GitHub Enterprise Server who are also owners of the connected GitHub Enterprise Cloud organization or enterprise account can enable security alerts for vulnerable dependencies on GitHub Enterprise Server.

In this article

About alerts for vulnerable dependencies on GitHub Enterprise Server

We add vulnerabilities to the GitHub Advisory Database from the following sources:

You can connect your GitHub Enterprise Server instance to GitHub.com, then sync vulnerability data to your instance and generate security alerts in repositories with a vulnerable dependency.

After connecting your GitHub Enterprise Server instance to GitHub.com and enabling security alerts for vulnerable dependencies, vulnerability data is synced from GitHub.com to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from your GitHub Enterprise Server instance is uploaded to GitHub.com.

When your GitHub Enterprise Server instance receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate security alerts. You can customize how you receive security alerts. For more information, see "Choosing the delivery method for your notifications."

Enabling security alerts for vulnerable dependencies on GitHub Enterprise Server

Before enabling security alerts for vulnerable dependencies on your GitHub Enterprise Server instance, you must connect your GitHub Enterprise Server instance to GitHub.com. For more information, see "Connecting GitHub Enterprise Server to GitHub Enterprise Cloud."

  1. Sign in to your GitHub Enterprise Server instance at http(s)://HOSTNAME/login.

  2. In the administrative shell, enable the security alerts for vulnerable dependencies on your GitHub Enterprise Server instance:

    $ ghe-dep-graph-enable

    Note: For more information about enabling access to the administrative shell via SSH, see "Accessing the administrative shell (SSH)."

  3. Return to GitHub Enterprise Server.

  4. Navigate to your enterprise account by visiting https://HOSTNAME/enterprises/ENTERPRISE-NAME, replacing HOSTNAME with your instance's hostname and ENTERPRISE-NAME with your enterprise account's name.

  5. In the enterprise account sidebar, click Settings.

    Settings tab in the enterprise account sidebar

  6. In the left sidebar, click GitHub Connect.

    GitHub Connect tab in the business account settings sidebar

  7. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select Enabled.

    Drop-down menu to enable scanning repositories for vulnerabilities

Viewing vulnerable dependencies on GitHub Enterprise Server

You can view all vulnerabilities in your GitHub Enterprise Server instance and manually sync vulnerability data from GitHub.com to update the list.

  1. From an administrative account on GitHub Enterprise Server, click in the upper-right corner of any page.
    Rocketship icon for accessing site admin settings
  2. In the left sidebar, click Vulnerabilities.
    Vulnerabilities tab in the site admin sidebar
  3. To sync vulnerability data, click Sync Vulnerabilities now.
    Sync vulnerabilities now button