> For AI agents: the complete documentation index is available at https://nhanbe.id.vn/llms.txt, the full documentation bundle is available at https://nhanbe.id.vn/llms-full.txt.

# Config GitHub Advanced Security for Azure DevOps

## Enable GitHub Advanced Security

You can enable Secret Protection or Code Security at the organization, project, or repository level.

### Repository-level onboarding

1. go to Project Settings
2. Repos > Security
3. Select repo you want to enable GHAS
4. Toggle either Secret Protection or Code Security
5. Select Begin billing. A shild icon now appears in the repository view for any repository with either product enabled.
6. To ontionally enable dependency scanning default setup, selecct Options and enable the Dependency scanning default checkbox.

![project setting ghas](/static/image/image-2.e5f9de1e8b.png)
### Project Level onboarding

1. go to Project Settings
2. Security
3. Select project you want to enable GHAS
4. Toggle either Secret Protection or Code Security
5. Select Begin billing. A shild icon now appears in the repository view for any repository with either product enabled.
6. To ontionally enable dependency scanning default setup, selecct Options and enable the Dependency scanning default checkbox.

![project setting ghas](/static/image/image-2.e5f9de1e8b.png)
### Project Level onboarding

1. Go to your Project settings for your Azure DevOps project.
2. Select Repos.
3. Select the Settings tab.
4. Select Enable all and see an estimate for the number of active committers per product for your project appear. This action only enables the selected product for existing repositories.
5. Toggle your desired products of Secret Protection or Code Security and all associated subfeatures.
6. Select Begin billing to activate Secret Protection and/or Code Security for every existing repository in your project.
7. Optionally, toggle Automatically enable Advanced Security for new repositories so that any newly created repositories in the future have Secret Protection or Code Security enabled upon creation. This setting is separate from the Enable all action and must be selected independently.

![project level](/static/image/image-3.3cf53bc0f8.png)
## Setup

### Set up secret scanning

Push protection and repository scanning are automatically enabled with Secret Protection. Configure push protection from repository settings.

![secret scanning](/static/image/image-4.400b83533d.png)
Push protection only scans commits after enabling. Repository scanning detects existing secrets, including historical commits.

### Set up dependency scanning

Requires Code Security enabled. Dependency scanning runs via pipelines with results aggregated per repository.

For default branch scanning, enable "Scan for vulnerable dependencies" in repository settings. This automatically adds the scanning task to pipelines targeting your default branch or PR builds.

![alt text](/static/image/image-5.2daf9d2002.png)
For all-branch scanning, add the dependency scanning task to your pipelines directly.

### Set up code scanning

Requires Code Security enabled. Code scanning runs via pipelines with results aggregated per repository.

**Default setup** - Quick, scheduled scanning via Azure Pipelines. Auto-detects supported languages (C#, C/C++, Java, JS/TS, Python, Ruby, Rust) and configures scanning. Go and Swift require advanced setup.

![alt text](/static/image/image-6.2daf9d2002.png)
Configure agent pool and schedule from Organization settings > Repositories > CodeQL default setup options.

**Advanced setup** - Full control by adding CodeQL pipeline tasks directly to your pipelines. Use for custom agent pools, build steps, or multi-branch scanning.

**Recommendation:** Start with default setup. Combine with advanced setup if you need more control.

Default setup runs weekly. Initial scan queues immediately upon enabling—no wait for scheduled run. Vulnerabilities appear in the Advanced Security tab.

## Dependency Scanning Explain

### Maven

Detection requires the maven CLI to be installed on the agent.

Development dependencies are identified when they use the test dependency scope.

### npm

Dependency scanning detects any root package.json files but doesn't resolve specific package versions without a package restore at build time even if dependencies in the package.json aren't semantically versioned.

Development dependencies are identified by the devDependencies property in package.json and the dev flag in package-lock.json.

## References

[GHAS Billing](https://learn.microsoft.com/vi-vn/azure/devops/repos/security/github-advanced-security-billing?view=azure-devops\&pivots=standalone-ghazdo)