Activation du rejet d’alerte délégué pour l’analyse du code

Vous pouvez utiliser le rejet d’alerte délégué pour contrôler qui peut rejeter une alerte trouvée par code scanning.

Qui peut utiliser cette fonctionnalité ?

Les propriétaires d’organisation, les gestionnaires de sécurité et les administrateurs de référentiel peuvent activer les rejets d’alertes délégués. Une fois activés, les propriétaires d’organisation et les gestionnaires de sécurité peuvent rejeter les alertes.

Dans cet article

About enabling delegated alert dismissal

Note

Delegated alert dismissal is currently in public preview and subject to change.

Delegated alert dismissal lets you restrict which users can directly dismiss an alert. When the feature is enabled, users attempting to dismiss an alert will instead create a request for dismissal.

Enabling the feature automatically assigns organization owners and security managers with the permission to approve or deny dismissal requests for alerts. This permission is:

  • "Review and manage code scanning alert dismissal requests" permission for code scanning.

  • "Review and manage secret scanning alert dismissal requests" permission for secret scanning'

For more information about these permissions, see Roles in an organization.

To learn more about the security manager role, see Managing security managers in your organization.

Note

The implementation of this approval process can potentially cause some friction, so it's important to ensure that the team of security managers has adequate coverage before proceeding.

Reviewers (security managers and organization owners):

  • Get an email notification for requests. These users need to ensure that they can review these lists periodically, so that there is no backlog and that the process is smooth.
  • Can process requests in a dedicated view in the "Security" tab of the organization. An alert will only be dismissed if the dismissal request is approved; otherwise, the alert will remain open.

Requesters will get an email notification with the decision as to whether the alert can be dismissed or not.

Configuring delegated dismissal for a repository

Note

If an organization owner configures delegated alert dismissal via an enforced security configuration, the settings can't be changed at the repository level.

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.

  3. In the "Security" section of the sidebar, click Advanced Security.

  4. Under "Code Security", click Enable for "Prevent direct alert dismissals".

Configuring delegated dismissal for an organization

You must configure delegated dismissal for your organization using a custom security configuration. You can then apply the security configuration to all (or selected) repositories in your organization.

  1. Create a new custom security configuration, or edit an existing one. See Creating a custom security configuration.
  2. When creating the custom security configuration, under "Code scanning", set "Prevent direct alert dismissals" to Enabled.
  3. Click Save configuration.
  4. Apply the security configuration to all (or selected) repositories in your organization. See Applying a custom security configuration.

To learn more about security configurations, see About enabling security features at scale.