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.
5 sample questions with correct answers and explanations. Start a practice session to test yourself across all 299 questions.
1. FinanceSecure Inc. wants to combine their existing compliance queries defined in a configuration file with additional security queries specified directly in their GitHub Actions workflow. Their compliance team maintains queries in a YAML configuration file, while their security team wants to add supplementary queries through the workflow. What configuration approach ensures both query sets are executed together?
Explanation
To run the combined set of queries from both a configuration file and workflow specifications, FinanceSecure Inc. must use the + symbol prefix before the workflow query values. This ensures that the additional queries specified in the workflow are used together with any queries specified in the referenced configuration file. Without the + symbol, any queries specified in the workflow would replace those in the configuration file rather than combining them. This approach allows the compliance team to maintain their queries in a configuration file for better organization and version control, while enabling the security team to supplement these with additional queries through the workflow file, ensuring both teams' requirements are met in a single analysis run.
2. StartupCloud needs to enable Dependabot alerts for their private repositories. Their security engineer wants to understand the default behavior for different repository types. What are the default settings for Dependabot alerts in public versus private repositories?
Explanation
Dependabot alerts are enabled by default for public repositories but must be manually enabled for private repositories. This is because private repositories require a GitHub Advanced Security license to access security features like Dependabot alerts. Public repositories receive these security features automatically as part of GitHub's commitment to open source security. Organizations with private repositories need to enable Dependabot alerts explicitly and ensure they have appropriate GHAS licensing.
3. CloudSecure Corp has implemented GitHub secret scanning across their organization and wants to integrate the security data with their broader security information and event management (SIEM) system for centralized monitoring and compliance reporting. They need to export secret scanning data for analysis and correlation with other security events. Which approach enables them to integrate secret scanning data with external security systems?
Explanation
CloudSecure should use GitHub's REST API and webhooks to retrieve secret scanning alerts and events for integration with external security systems. GitHub provides comprehensive API access to secret scanning data including alert details, resolution status, and alert metadata that can be programmatically retrieved for SIEM integration. Webhooks can provide real-time notification of new secret scanning events, enabling immediate correlation with other security data. The API access includes alert creation timestamps, resolution information, secret types, and repository details that support comprehensive security analysis and compliance reporting. This integration approach enables centralized security monitoring while maintaining GitHub as the primary interface for alert management and remediation, providing the best of both specialized GitHub security features and enterprise-wide security correlation capabilities.
4. A security team at Digital Horizons is rolling out a new application security program. Their previous attempt with another tool failed because developers quickly grew tired of investigating a high volume of alerts that turned out to be incorrect. To ensure success this time, the team chose GitHub Advanced Security. What key principle, particularly for partner token and non-provider pattern scanning, is crucial for gaining developer trust and adoption?
Explanation
Maintaining a low false positive rate is essential for the success of any application security program. If developers are constantly flooded with alerts that are not real issues, they will begin to distrust and ignore the tool, a phenomenon known as alert fatigue. GitHub Advanced Security tools are designed to be highly accurate to ensure that when an alert is raised, it is a real issue worth investigating. This builds trust and encourages developers to actively engage with the security findings.
5. GlobalSecure Ltd has implemented code scanning across multiple geographic regions with development teams in different time zones. They need to coordinate security response capabilities while accommodating regional differences in working hours and expertise. How should they structure their global code scanning operations?
Explanation
GlobalSecure should implement follow-the-sun security coverage with regional teams responsible for code scanning response during their business hours, supported by escalation procedures for critical issues. This approach ensures continuous security monitoring and response capabilities while leveraging regional expertise and accommodating local working schedules. Each regional team can be configured to receive notifications for repositories in their sphere of responsibility during their business hours, with clear escalation procedures for critical security alerts that require immediate response regardless of time zone. The global coordination should include shared knowledge bases, consistent response procedures, and communication protocols that ensure security issues are handled promptly by the appropriate regional teams. This model provides comprehensive security coverage while maintaining sustainable operations across all regions.
One-time access to this exam