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.
For more information, see "About Dependabot alerts," "About secret scanning" 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
Note: The "Security Risk" and "Security Coverage" views are currently in beta and subject to change.
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, the team can use the "Security Coverage" page to monitor the adoption of features across your organization or by a specific team as you rollout GitHub Advanced Security, or use the "Security Risk" page to identify repositories with more than five open secret scanning alerts.
Organization owners and security managers for organizations have access to the security overview for their organizations. Organization members can also access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "Managing security and analysis settings for your repository."
Security Risk view
This view shows data about the repositories affected by different types of security alert.
- Use the Teams dropdown menu to show information only for the repositories owned by one or more teams.
- Click NUMBER affected or NUMBER unaffected in the header for any type of alert to show only the repositories with or without alerts of that type.
- Click any of the descriptions of "Open alerts" in the header to show only repositories with alerts of that type and category. For example, 1 critical to show the repository with a critical alert for Dependabot.
- Click NUMBER Archived to show only repositories that are archived.
- Click in the search box to show a list of the full set of available filters.
Security Coverage view
This view shows data about which security features are used by repositories in the organization. You can filter the view to show the repositories of interest using links, a dropdown menu, and a search field.
- Use the Teams dropdown to show information only for the repositories owned by one or more teams.
- Click NUMBER enabled or NUMBER not enabled in the header for any feature to show only the repositories with that feature enabled or not enabled.
- Click NUMBER Archived to show only repositories that are archived.
- Click in the search box to show a list of the full set of available filters.
In addition, you can click Security settings for any repository to enable the security features that have a one-click setup.
Note: The ability to enable and disable default set up for code scanning for eligible repositories in an organization is currently in beta and subject to change. During the beta release, if you disable CodeQL code scanning for all repositories this change will not be reflected in the coverage information shown in security overview for the organization. The repositories will still appear to have code scanning enabled in this view.
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.