Implement security through a pipeline using Azure DevOps (AZ-2001)

Course Outline

1) Configure a project and repository structure to support secure pipelines
• Separate a project into team projects and repositories
• Separate secure files between projects
• Move the security repository away from a project
• Assign project and repository permissions
• Organize a project and repository structure
• Lab: Configure a project and repository structure to support secure pipelines

2) Configure secure access to pipeline resources
• Identify and mitigate common security threats
• Configure pipeline access to specific agent pools
• Manage secret variables and variable groups
• Secure files and storage
• Configure service connections
• Manage environments
• Secure repositories
• Lab: Configure agents and agent pools for secure pipelines

3) Manage identity for projects pipelines and agents
• Configure a Microsoft-hosted pool
• Configure agents for projects
• Configure agent identities
• Configure the scope of a service connection
• Convert to a managed identity in Azure DevOps
• Lab: Manage identity for projects and pipelines

4) Configure and validate permissions
• Configure and validate user permissions
• Configure and validate pipeline permissions
• Configure and validate approval and branch checks
• Manage and audit permissions in Azure DevOps
• Lab: Configure and validate permissions

5) Extend a pipeline to use multiple templates
• Create nested templates
• Rewrite the main deployment pipeline
• Configure the pipeline and the application to use tokenization
• Remove plain text secrets
• Restrict agent logging
• Identify and conditionally remove script tasks in Azure DevOps
• Lab: Extend a pipeline to use multiple templates

6) Configure secure access to Azure Repos from pipelines
• Configure pipeline access to packages
• Configure credential secrets, and secrets for services
• Ensure that the secrets are in the Azure Key Vault
• Ensure that secrets aren't in the logs
• Lab: Integrate Azure Key Vault with Azure Pipelines

7) Configure pipelines to securely use variables and parameters
• Ensure that parameters and variables retain their type
• Identify and restrict insecure use of parameters and variables
• Move parameters into a YAML file that protects their type
• Limit variables that can be set at queue time
• Validate that mandatory variables are present and set correctly in Azure DevOps
• Lab: Configure pipelines to securely use variables and parameters