AZ-400 ยท Security and compliance scanning
GitHub Advanced Security and Defender for Cloud DevOps Security
GitHub Advanced Security for GitHub and for Azure DevOps (code scanning, secret scanning with push protection, dependency scanning), connecting GitHub/Azure DevOps to Defender for Cloud DevOps Security, findings and attack paths.
Key points
- GitHub Advanced Security (also for Azure DevOps):
- Code scanning with CodeQL, dependency scanning: Code Security.
- Secret scanning with push protection: Secret Protection.
- Defender for Cloud DevOps security: one console for Azure DevOps, GitHub and GitLab.
- It shows code, secret, dependency and IaC findings by severity, posture recommendations, pull request annotations, code-to-cloud context.
Source: https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-devops-introduction
Practice questions
Which Defender for Cloud capability gives security teams one console for code, secret, dependency and IaC findings across Azure DevOps, GitHub and GitLab?
- Defender for Containers
- DevOps security
- Azure Key Vault
- Azure Policy guest configuration
Show answer
Answer: B. DevOps security
DevOps security is the capability for pre-production code and pipeline posture. Defender for Containers covers images and clusters, and Key Vault is a secret store, not a scanner console.
Which capabilities belong to GitHub Secret Protection for Azure DevOps?
- Push protection that blocks new pushes containing secrets
- Repository scanning that finds secrets in earlier commits
- Dependency scanning for vulnerable packages
- CodeQL code scanning
- Container image rescans in a registry
Show answer
Answer: A. Push protection that blocks new pushes containing secrets, B. Repository scanning that finds secrets in earlier commits
Secret Protection covers push protection and scanning of existing content including history. Dependency and code scanning belong to Code Security.
True or false: turning on push protection also removes secrets that were already committed before it was enabled.
Show answer
Answer: False
False. Push protection only evaluates pushes made after it is enabled. Existing secrets are found by repository scanning, and exposed ones must still be revoked.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
