Skip to main content

此版本的 GitHub Enterprise 将停止服务 2023-01-18. 即使针对重大安全问题,也不会发布补丁。 为了获得更好的性能、更高的安全性和新功能,请升级到最新版本的 GitHub Enterprise。 如需升级帮助,请联系 GitHub Enterprise 支持

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. Members of a team can see the security overview for repositories that the team has admin privileges for.

组织安全概览在你拥有 GitHub Advanced Security 许可证时可用。 有关详细信息,请参阅“关于 GitHub Advanced Security”。

注意: 安全概览目前以 beta 版本提供,并且可能会发生更改。

About the security overview

安全概览提供组织或企业的安全状态的概略性摘要,并便于识别需要干预的有问题的存储库。 还可以使用安全概览来查看哪些存储库启用了特定的安全功能,并配置当前未使用的任何可用安全功能。

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 only for enterprises that use GitHub Advanced Security.

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."

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

For each repository in the security overview, you will see icons 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 icon 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.

Icons in the security overview

IconMeaning
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 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