Bitzu

AZ-400 ยท Security and compliance scanning

Scanning strategy: dependency, code, secret, license

SCA, SAST, DAST, secret scanning and licensing/compliance scanning, where in the pipeline each runs, shift-left, blocking vs informing, tools such as CodeQL, Dependabot, Defender for Cloud.

Key points

  • SAST: reads source code without running it (CodeQL).
  • SCA: open-source dependencies, known vulnerabilities and licenses (Dependabot, dependency review).
  • DAST: probes a running app from outside.
  • Secret scanning: credentials in code and history.
  • Shift left: cheap scans early (commit, pull request), heavier later.
  • Start informing, then block merges on high severity once noise is tuned.

Source: https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning

Practice questions

Single choice

Which kind of scan analyzes source code for flaws without executing the application?

  1. DAST
  2. SAST
  3. Penetration testing of production
  4. Load testing
Show answer

Answer: B. SAST

SAST is static analysis of code. DAST needs a running app, SCA inspects third-party packages, and secret scanning looks for credentials.

Select all that apply

Which measures are examples of shifting security left?

  1. Running code scanning on every pull request
  2. Checking for secrets before a commit is pushed
  3. Running DAST only against production once a week
  4. Reviewing dependency changes in the pull request
  5. Scheduling one external audit per year
Show answer

Answer: A. Running code scanning on every pull request, B. Checking for secrets before a commit is pushed, D. Reviewing dependency changes in the pull request

Shift left means catching issues at commit and pull request time. Weekly production-only tests and yearly audits happen too late to be cheap to fix.

True or false

True or false: secret scanning alerts and push protection do the same thing, because both stop a secret from reaching the repository.

Show answer

Answer: False

False. Alerts report a secret after it has been pushed. Push protection acts before the push completes, so the secret never enters history.

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.

Download on the App StoreGet it on Google Play

More AZ-400 topics in this module