Skip to main content

Diese Version von GitHub Enterprise Server wird eingestellt am 2024-06-29. Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für bessere Leistung, verbesserte Sicherheit und neue Features aktualisiere auf die neueste Version von GitHub Enterprise Server. Wende dich an den GitHub Enterprise-Support, um Hilfe zum Upgrade zu erhalten.

Bewerten der Einführung von Codesicherheitsfeatures

Du kannst die Sicherheitsübersicht verwenden, um zu sehen, welche Teams und Repositorys bereits Codesicherheitsfeatures aktiviert haben, und um alle zu identifizieren, die noch nicht geschützt sind.

Wer kann dieses Feature verwenden?

Die Sicherheitsübersicht für eine Organisation steht allen Mitgliedern der Organisation zur Verfügung. Welche Ansichten und Daten angezeigt werden, wird von deiner Rolle in der Organisation und deinen Berechtigungen für einzelne Repositorys innerhalb der Organisation bestimmt. Weitere Informationen findest du unter Informationen zur Sicherheitsübersicht.

Die Sicherheitsübersicht für ein Unternehmen zeigt Organisationsbesitzerinnen und Sicherheits-Managerinnen Daten für die Organisationen an, auf die sie Zugriff haben. Unternehmensbesitzerinnen können nur Daten für Organisationen anzeigen, denen sie als Organisationsbesitzerin oder Sicherheits-Manager*in hinzugefügt wurden. Weitere Informationen findest du unter Verwalten deiner Rolle in einer Organisation, die deinem Unternehmen gehört.

Alle Unternehmen und ihre Organisationen verfügen über eine Sicherheitsübersicht. Wenn Sie GitHub Advanced Security features werden Sie zusätzliche Informationen sehen. Weitere Informationen findest du unter Informationen zu GitHub Advanced Security.

Note: The "Security risk" and "Security coverage" views are currently in beta and subject to change.

About adoption of code security features

You can use security overview to see which repositories and teams have already enabled each code security feature, and where people need more encouragement to adopt these features. The "Security coverage" view shows a summary and detailed information on feature enablement for an organization. You can filter the view to show a subset of repositories using the "enabled" and "not enabled" links, the "Teams" dropdown menu, and a search field in the page header.

Screenshot of the header section of the "Security coverage" view on the "Security" tab for an organization. The options for filtering are outlined in dark orange, including "enabled" and "not enabled" links, "Teams" selector, and search field.

Note: "Pull request alerts" are reported as enabled only when code scanning has analyzed at least one pull request since alerts were enabled for the repository.

Viewing the enablement of code security features for an organization

You can view data to assess the enablement of code security features across organizations in an enterprise. The information shown by security overview varies according to your access to repositories, and according to whether GitHub Advanced Security is used by those repositories . For more information, see "About security overview."

  1. On your GitHub Enterprise Server instance, navigate to the main page of the organization.

  2. Under your organization name, click Security.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a shield icon and "Security," is outlined in dark orange.

  3. To display the "Security coverage" view, in the sidebar, click Coverage.

  4. Use options in the page summary to filter results to show the repositories you want to assess. The list of repositories and metrics displayed on the page automatically update to match your current selection. For more information on filtering, see "Filtering alerts in security overview."

    • Use the Teams dropdown to show information only for the repositories owned by one or more teams. For more information, see "Managing team access to an organization repository."
    • 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.
    • At the top of the list of repositories, click NUMBER Archived to show only repositories that are archived.
    • Click in the search box to add further filters to the repositories displayed.

    Screenshot of the header section of the "Security coverage" view on the "Security" tab for an organization. The options for filtering are outlined in dark orange, including "enabled" and "not enabled" links, "Teams" selector, archived repositories, and search field.

  5. Optionally, click Security settings to enable code security features for a repository and click Save security settings to confirm the changes. If a feature is not shown, it has more complex configuration requirements and you need to use the repository settings dialog. For more information, see "Quickstart for securing your repository."

Interpreting and acting on the enablement data

Some code security features can and should be enabled on all repositories. For example, secret scanning alerts and push protection reduce the risk of a security leak no matter what information is stored in the repository. If you see repositories that don't already use these features, you should either enable them or discuss an enablement plan with the team who owns the repository. For information on enabling features for a whole organization, see "Managing security and analysis settings for your organization." For information on enabling features across your entire enterprise, see "Managing GitHub Advanced Security features for your enterprise."

Other features are not available for use in all repositories. For example, there would be no point in enabling Dependabot or code scanning for repositories that only use ecosystems or languages that are unsupported. As such, it's normal to have some repositories where these features are not enabled.

Your enterprise may also have configured policies to limit the use of some code security features. For more information, see "Enforcing policies for code security and analysis for your enterprise."