GitHub · GH-500
Enabling Secret Protection
GH-500 · Lesson 4 of 16 · 25:01
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Prepare for the GH-500 exam (GitHub Advanced Security). In this lesson: where secret scanning looks and its three alert types, enabling it on a repository, an organization, or an enterprise with security configurations, generic patterns, AI-detected secrets, validity checks, and extended metadata checks, and the differences between public and private repositories. Includes three original practice questions.
Preview the topics
- Contoso wants secret scanning on all 400 private repositories of the retail organization, and on every repository created later, without anyone being able to switch it off. What should the security managers do?
- Contoso wants to know which leaked cloud keys are still usable, to fix those first, and who owns each one. Which settings provide this?
- A Contoso developer pushes a working token to her personal public repository, which has no repository-level settings. What happens by default?