Microsoft β’ GH-500
Validates expertise in configuring, managing, and operating GitHub Advanced Security tools including code scanning, secret scanning, and dependency management to secure software development workflows.
Questions
299
Duration
100 minutes
Passing Score
Not publicly disclosed
Difficulty
IntermediateLast Updated
Jan 2025
The GitHub Advanced Security (GH-500) certification validates proficiency in configuring, managing, and operationalizing the full suite of GitHub Advanced Security (GHAS) tools to secure modern software development workflows. Candidates demonstrate mastery across three core security pillars: secret scanning (including push protection and custom patterns), dependency management via Dependabot and Dependency Review, and automated code analysis using CodeQL and third-party SARIF-compatible tools. The exam also covers Security Overview, alert management, and enforcement of security policies through Repository Rulesets and GitHub Actions workflows.
The certification is maintained by GitHub and administered through Microsoft's Pearson VUE testing infrastructure. It was updated in 2025 to reflect a revised seven-domain structure, expanding coverage of GitHub Enterprise configuration and sharpening the weight given to best practices and corrective measures. Holding this credential demonstrates the ability to shift security leftβembedding automated vulnerability detection directly into the development lifecycle rather than treating it as a post-deployment concern. The certification is valid for two years from the date of achievement.
The GH-500 exam targets system administrators, software developers, application administrators, and IT professionals who work with GitHub Enterprise Cloud (GHEC) or GitHub Enterprise Server (GHES) and are responsible for securing codebases at scale. Ideal candidates include DevSecOps engineers integrating security gates into CI/CD pipelines, application security specialists managing organizational vulnerability programs, and GitHub administrators enforcing repository and organization-level security policies.
Candidates should have hands-on experience enabling and configuring GHAS features across repositories and organizations, familiarity with GitHub Actions workflows, and an understanding of software supply chain security concepts including dependency graphs, SBOMs, and CVE/CWE classification. The intermediate difficulty level assumes prior GitHub platform experience; this is not an entry-level credential.
Microsoft does not list formal prerequisites for GH-500, but the official audience profile specifies intermediate-level experience with GitHub Enterprise Administration. Candidates are expected to understand GitHub's repository, organization, and enterprise permission model before attempting the exam, as access control questions appear across multiple domains.
Recommended preparation includes practical experience enabling GHAS features on private repositories, working knowledge of GitHub Actions (creating and modifying workflow YAML files), familiarity with CodeQL query suites and SARIF output formats, and experience interpreting Dependabot alerts and dependency graphs. Completing the official Microsoft Learn training course GH-500T00-A: GitHub Advanced Security provides structured coverage of all exam objectives and is the primary recommended prerequisite resource.
The GH-500 exam is delivered through Pearson VUE and includes a 100-minute time limit. The exam is proctored and may include interactive lab components in addition to standard multiple-choice and scenario-based questions. Candidates can experience the question interface in advance via the official exam sandbox at GHCertDemo.starttest.com before scheduling.
The exam is available in English, Spanish, Portuguese (Brazil), Korean, and Japanese. Pricing is approximately $99 USD, varying by country or region of testing. No official passing score is published on the Microsoft Learn certification page; third-party sources cite 700/1000 as a commonly reported threshold, but this should be verified against official communications at time of registration. If a candidate fails, a retake is permitted 24 hours after the first attempt; subsequent retake wait times vary per Microsoft's standard retake policy. A free practice assessment is available on Microsoft Learn (assessment ID 590484996).
Professionals holding the GH-500 certification are positioned for roles such as DevSecOps engineer, application security engineer, GitHub Enterprise administrator, and security-focused software developer. As software supply chain security has become a regulatory and enterprise priority β driven by executive orders, frameworks like SLSA, and incidents targeting dependency ecosystems β the ability to operationalize GHAS tools within existing GitHub workflows is a differentiated and in-demand skill. The certification is relevant across both enterprise cloud environments (GitHub Enterprise Cloud) and self-hosted deployments (GitHub Enterprise Server), broadening its applicability across industries.
Because the credential is issued by GitHub (administered via Microsoft) rather than a generic cloud provider, it signals specific platform expertise to employers already standardized on GitHub for source control and CI/CD. It complements adjacent certifications such as GitHub Actions (GH-200), GitHub Administration (GH-700), and Microsoft's AZ-500 (Azure Security Engineer) for professionals building a security specialization. The two-year validity period requires periodic renewal, keeping certified professionals current with an actively evolving product.
1. CloudSecure Corp wants to understand the difference between Dependabot alerts and Dependency Review in their security workflow. What is the primary distinction between these two features?
2. TechStart Inc. wants to integrate CodeQL into their CI/CD pipeline. They need to understand the structure and contents of a CodeQL database to optimize their analysis workflow. What are the main components that make up a CodeQL database directory?
3. InnovateCode Corporation has multiple development teams working on different projects with varying security requirements. Some projects handle sensitive customer data while others are internal tools. They want to implement code scanning with different configurations based on project risk levels. Which approach should they use to implement risk-appropriate code scanning?
4. SecureBank wants to ensure that only senior developers and security team members can view and resolve secret scanning alerts in their repositories. Currently, all developers with write permissions can see these alerts. What access control configuration should they implement to restrict secret scanning alert visibility?
5. MicroServices Corp has a complex application with multiple package managers including npm, pip, and Maven. Their development team needs to create a comprehensive Dependabot configuration that handles different update strategies for different ecosystems. What elements should they include in their .github/dependabot.yml configuration? (Select two!)
Select all that applyAll exams included β’ Cancel anytime