Skip to main content
GitHub AE is currently under limited release.

About the security overview

You can view, filter, and sort security alerts for repositories owned by your organization or team in the security overview pages.

Who can use this feature

Organization owners and security managers can access the organization-level security overview and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager. Members of a team can see the security overview for repositories that the team has admin privileges for.

A security overview for your enterprise and for organizations is available if you use GitHub Advanced Security, which is free during the beta release. For more information, see "About GitHub Advanced Security."

Note: The security overview is currently in beta and subject to change.

About the security overview

The security overview provides high-level summaries of the security status of an organization or enterprise and make it easy to identify problematic repositories that require intervention. You can also use the security overview to see which repositories have enabled specific security features and to configure any available security features that are not currently in use.

The security overview shows which security features are enabled for repositories and consolidate alerts for each feature.

  • Risk and coverage information about Dependabot features and alerts is shown for all repositories.
  • Risk and coverage information for GitHub Advanced Security features, such as code scanning and secret scanning, is shown for enterprises that use GitHub Advanced Security and for public repositories.

For more information, see "About Dependabot alerts" and "About GitHub Advanced Security."

About filtering and sorting alerts

The security overview provides a powerful way to understand the security of a group of repositories. The views are interactive with filters that allow you to drill into the aggregated data and identify sources of high risk or low feature coverage. As you apply multiple filters to focus on narrower areas of interest, the data across the view changes to reflect your selection. For more information, see "Filtering alerts in the security overview."

There are also dedicated views for each type of security alert that you can use to limit your analysis to a specific set of alerts, and then narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the Secret type filter to view only secret scanning alerts for a specific secret, like a GitHub personal access token.

Note: The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.

About the organization-level security overview

You can find the security overview on the Security tab for any organization that's owned by an enterprise. Each view shows aggregated data that you can drill down into, as you add each filter, the data is updated to reflect the repositories or alerts that you've selected.

The application security team at your company can use the different views for both broad and specific analyses of your organization's security status. For example, they can use the overview page to monitor adoption of features by your organization or by a specific team as you rollout GitHub Advanced Security to your enterprise, or to review all alerts of a specific type and severity level across all repositories in your organization.

Organization owners and security managers for organizations have access to the security overview for their organizations.

Understanding the main security overview

Screenshot of the security overview for an organization

Each repository in the security overview includes an indicator for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the indicator for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its code scanning, Dependabot and secret scanning alerts. This score is in beta and should be used with caution. Its algorithm and approach is subject to change.

Code scanning alerts. For more information, see "About code scanning."
Secret scanning alerts. For more information, see "About secret scanning."
Dependabot alerts. For more information, see "About Dependabot alerts."
The security feature is enabled, but does not raise alerts in this repository.
The security feature is not supported in this repository.

About the enterprise-level security overview

You can find the security overview on the Code Security tab for your enterprise. Each overview displays aggregated and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.

Enterprise owners can view alerts for organizations that they are an owner or a security manager of. Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "Managing your role in an organization owned by your enterprise."

Organization owners and security managers for organizations in an enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.

About the team-level security overview

You can find the security overview on the Security tab for any team in an organization that's owned by an enterprise.

At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "Managing team access to an organization repository."

Further reading