GH-500 domain - 18% of the exam

Describe GitHub Security suites, features, and ecosystem

Describe GitHub Security suites, features, and ecosystem is 18% of the GH-500 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

53
Practice questions
5
Objectives
42
Medium
11
Hard

Where people go wrong

  • Treating detection as prevention

    The wrong answers offer secret scanning alerts, faster detection or a shorter detection cycle as the prevention-first choice. A credential found by an alert is already exposed in history and must be revoked and rotated, so that is clean-up after the fact. Push protection refuses the push, so a recognised secret is never committed. Applied through a security configuration across organisations, it gives that prevention consistently at scale.

    See it in a sample question
  • Misplacing the free-versus-paid licensing line

    The wrong answers draw the licence boundary in the wrong place: requiring a seat on public repositories, billing for Dependabot alerts, or assuming a repository keeps its free features after turning private. On public repositories, code scanning, secret scanning with push protection and Dependabot alerts cost nothing. On private repositories, code scanning and secret scanning need GitHub Advanced Security, billed by unique committer, while Dependabot alerts stay free.

    See it in a sample question
  • Merging Secret Protection and Code Security

    The wrong answers fold the two standalone products into one licence, or hand a feature to the wrong product. Secret Protection holds secret scanning, push protection and custom patterns for credentials. Code Security holds code scanning with CodeQL, which analyses first-party source rather than looking for committed tokens. Buying only Secret Protection leaves CodeQL unlicensed. The dependency graph and Dependabot belong to Supply Chain Security.

    See it in a sample question
  • Picking the wrong Security Overview view

    The wrong answers choose a view or surface that answers a neighbouring question. The Coverage view reports which security features are enabled per repository, so it answers an adoption question. The Risk view shows where open alerts concentrate now. The Overview view charts detection, remediation and prevention trends over time. A repository Security tab covers one repository, and the audit log is an event stream, so neither is a cross-repository alert dashboard.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleDescribe GitHub Security suites, features, and ecosystemhard

An enterprise security architect must choose between two postures for credential safety across many organisations. Posture one detects credentials that have already been committed and raises alerts for triage. Posture two refuses pushes that contain recognised credentials so they are never committed in the first place. The architect wants to lead with the posture that keeps secrets out rather than cleaning up after the fact, applied consistently across organisations. Which choice reflects a prevention-first strategy applied at scale?

  • ARely on secret scanning alerts alone and route them to an incident queue, because detecting committed secrets quickly is equivalent to preventing their exposure.
  • BEnable Dependency Review as a required check across organisations, because blocking risky changes at merge keeps credentials out of the codebase.
  • CEnable push protection through a security configuration applied across the organisations, so pushes containing recognised secrets are blocked before the credential is ever committed. Correct
  • DSchedule a daily secret scanning sweep across all repositories so any committed credential is found within twenty-four hours and rotated, because shorter exposure windows are prevention-first.
Recognise push protection delivered via a security configuration as the prevention-first credential strategy enforced consistently across organisations. Prevention-first keeps the insecure artefact from ever existing, so blocking the push means the secret is never committed and no rotation or history clean-up is needed. Secret scanning detection, faster sweeps, and dependency gating all act after a secret is committed or address a different risk, whereas push protection rolled out through a security configuration prevents the commit at scale.

Why A is wrong: Fast detection is valuable, but a committed secret has already been exposed in history and must be revoked and rotated, so this is clean-up after the fact rather than prevention. Equating detection with prevention is the precise mistake the question is probing.

Why B is wrong: Dependency Review gates dependency changes for vulnerabilities and licences, not committed credentials, so it does not address secrets at all. It is a plausible-sounding gate but solves a different problem from keeping tokens out of the repository.

Why C is correct: Push protection stops the secret at the push, so it never enters the repository, which is the prevention-first posture the architect wants. Delivering it through a security configuration applied across organisations is how that posture is enforced consistently at scale. This satisfies both the strategy and the scope requirements.

Why D is wrong: Shrinking the exposure window reduces risk, but the credential is still committed and must be rotated, so this remains a detect-and-remediate posture. Calling a shorter detection cycle prevention-first conflates faster clean-up with stopping the secret from entering at all.

Free sampleDescribe GitHub Security suites, features, and ecosystemmedium

A startup hosts an open-source project in a public repository on GitHub Enterprise Cloud and has not purchased any GitHub Advanced Security seats. The maintainers want code scanning to run on pull requests, secret scanning to flag exposed tokens, and Dependabot alerts on vulnerable dependencies. What can they enable without buying a GitHub Advanced Security licence?

  • AOnly Dependabot alerts, because dependency features are free everywhere while code scanning and secret scanning always require a licence regardless of repository visibility.
  • BAll three, because code scanning, secret scanning with push protection, and Dependabot alerts are available at no cost on public repositories. Correct
  • COnly secret scanning with push protection, because credential detection is free on any repository while code scanning and Dependabot are gated behind GitHub Advanced Security seats.
  • DNone of them until at least one GitHub Advanced Security seat is assigned, because every scanning feature is part of the paid product on GitHub Enterprise Cloud.
Recognise that code scanning, secret scanning with push protection, and Dependabot alerts are free on public repositories. GitHub makes its core security scanning available without charge on public repositories to support open-source projects, so code scanning, secret scanning with push protection, and Dependabot alerts all run there without a GitHub Advanced Security licence. The paywall applies to private and internal repositories, not to public ones.

Why A is wrong: Dependabot alerts are indeed free, which makes this partly right, but it wrongly claims code scanning and secret scanning always need a licence. On public repositories both run at no cost, so restricting the answer to Dependabot understates what is available.

Why B is correct: On public repositories GitHub provides code scanning, secret scanning with push protection, and Dependabot alerts free of charge, so a GitHub Advanced Security licence is unnecessary. All three of the maintainers' goals can therefore be met without buying seats.

Why C is wrong: Secret scanning is free on public repositories, so naming it is tempting, but Dependabot alerts are also free and code scanning is free on public repositories too. Singling out secret scanning misrepresents the rest of the suite as licensed.

Why D is wrong: This treats the whole suite as paid everywhere, which is the visibility distinction the objective tests. On public repositories these features are free, so requiring a seat before any of them runs is incorrect.

Free sampleDescribe GitHub Security suites, features, and ecosystemmedium

A platform team is mapping out which GitHub Advanced Security capabilities belong to which licensable product so they can budget seats correctly. They need to place CodeQL-based code scanning and the alerts it raises under the correct product line. Which product does code scanning with CodeQL belong to?

  • ACode Security, because code scanning with CodeQL performs static analysis to find vulnerabilities in the codebase. Correct
  • BSecret Protection, because CodeQL inspects source files for sensitive strings before they are committed.
  • CSupply Chain Security, because CodeQL evaluates the security of third-party dependencies pulled into the build.
  • DSecurity Overview, because code scanning alerts are surfaced there for the whole organisation.
Place code scanning with CodeQL under the Code Security product within GitHub Advanced Security. GitHub Advanced Security is divided into product lines by the type of risk each addresses. Code scanning with CodeQL is static analysis of first-party source for vulnerabilities, which is the defining function of Code Security, distinct from credential detection (Secret Protection) and dependency risk (Supply Chain Security).

Why A is correct: Code scanning with CodeQL is the static application security testing capability, and GitHub packages it under the Code Security product. It analyses code paths for vulnerabilities such as injection flaws, which is exactly the Code Security remit.

Why B is wrong: This is tempting because both features analyse source code, but Secret Protection covers secret scanning and push protection for credentials, not static analysis of code logic. CodeQL does not look for committed credentials, so it is not part of Secret Protection.

Why C is wrong: Supply Chain Security covers the dependency graph, Dependabot, and Dependency Review, which assess third-party components. CodeQL analyses first-party source code rather than declared dependencies, so this product placement is wrong.

Why D is wrong: Security Overview is a reporting and navigation surface that aggregates alerts from multiple features; it is not a licensable product that owns code scanning. Seeing CodeQL alerts in Security Overview does not make code scanning part of it.

Free sampleDescribe GitHub Security suites, features, and ecosystemmedium

A security lead has rolled out secret scanning across an organisation over the past quarter and now wants to answer one specific question for a board update: which repositories still have secret scanning switched off, so the remaining rollout can be planned. They open "Security Overview" and must pick the view that answers an adoption question rather than an alert-burden question. Which view should they use?

  • AThe Risk view, filtered to secret scanning, because it ranks repositories by the number of open secret scanning alerts and the repositories with zero alerts are the ones where the feature is off.
  • BThe Overview view, because its detection, remediation, and prevention trend lines show enablement gaps as dips in the secret scanning alert volume over time.
  • CThe Coverage view, because it reports the enablement status of each security feature per repository, so repositories where secret scanning is not enabled can be listed directly. Correct
  • DThe organisation audit log, because it records every change to security feature settings and can be filtered to show repositories where secret scanning was never switched on.
Choose the Coverage view in Security Overview to assess which repositories have each security feature enabled, distinct from alert-risk views. Security Overview separates adoption questions from risk questions: the Coverage view reports per-repository enablement of each feature, while the Risk and Overview views describe open alerts and trends. Only the Coverage view directly enumerates repositories where a feature such as secret scanning is still disabled.

Why A is wrong: This is tempting because the Risk view does focus on secret scanning, but it ranks by open alert risk, and a repository with zero secret scanning alerts may simply be clean rather than unenabled. It cannot reliably distinguish a disabled feature from a feature that found nothing, so it does not answer the adoption question.

Why B is wrong: The Overview view charts trends in detection, remediation, and prevention of alerts over time, which is useful for tracking progress but not for enumerating unenabled repositories. A dip in alert volume does not identify which repositories lack the feature, so it answers the wrong question.

Why C is correct: The Coverage view in Security Overview is built to show which security features are enabled or disabled across repositories, which is exactly an adoption question. It lists each repository's enablement state for secret scanning, letting the lead see precisely where the feature is still off.

Why D is wrong: The audit log records discrete configuration events, so it can show where secret scanning was turned on, but proving a feature was never enabled by the absence of an event is unreliable and laborious. It is an event stream, not a current enablement inventory, so it is the wrong tool for this question.

Other domains in this exam

See also the GH-500 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.