Skip to content

Latest commit

 

History

History
58 lines (40 loc) · 2.88 KB

File metadata and controls

58 lines (40 loc) · 2.88 KB
title Permissions for GitHub Advanced Security for Azure DevOps
titleSuffix Azure Repos
description Configure permissions for GitHub Advanced Security for Azure DevOps
ms.service azure-devops
ms.subservice azure-devops-integration
ms.topic how-to
ms.custom cross-service
ms.author laurajiang
author laurajjiang
monikerRange azure-devops
ms.date 09/20/2023

Advanced Security permissions

GitHub Advanced Security for Azure DevOps includes extra permissions for more levels of control around Advanced Security results and management. There are three new permissions added through Advanced Security: read alerts, dismiss and manage alerts, and manage settings.

[!INCLUDE GitHub Advanced Security for Azure DevOps is different from GitHub Advanced Security.]

Default permissions and access levels

  • Advanced Security: read alerts grants permission to view security alerts for the repository.
  • Advanced Security: manage and dismiss alerts grants permission to dismiss alerts for the repository.
  • Advanced Security: manage settings grants permission to enable Advanced Security, which is a billable action.
Azure DevOps group  Default permissions
Contributors Advanced Security: read alerts
Project administrator Advanced Security: read alerts, manage and dismiss alerts
Project collection administrator Advanced Security: read alerts, manage and dismiss alerts, manage settings

Manage Advanced Security permissions

If you're a project collection admin for your organization or otherwise have the Advanced Security: manage settings permission, you can manage all other Advanced Security permissions.

If you're running into an error when viewing Advanced Security alerts, you can adjust individual permissions for your repository.

If the dropdowns are disabled, contact your administrator for the necessary permissions.

To adjust permissions for a specific repository:

  1. Go to Project Settings > Repositories.
  2. Select the specific repository you wish to adjust permissions for.
  3. Select Security.
  4. Select the security group you wish to adjust permissions for.
  5. Select the permission bit to change. If successful, a green checkmark appears next to the selected permission.

Screenshot of adjusting permissions for a specific repository

Use personal access tokens (PATs)

You can use a personal access token to use the Advanced Security APIs. For more information about PATs on Azure DevOps and how to create them, refer to About PATs.

Advanced Security offers three extra scopes for a PAT: read, read and write, and read, write, and manage.

Screenshot of Advanced Security PAT scopes