Overview

In this interactive session, GitHub’s experts guide participants through practical labs and exercises, enabling engineers to immediately apply GitHub Secret Protection within their repositories.

Participants gain hands-on experience on how to integrate secret protection seamlessly into developer workflows, block secret leaks with push protection, and streamline remediation processes—ultimately enhancing both security and developer productivity.

This training is largely targeted towards roles that directly configure the tool, like security teams and security champions, rather than the roles that are mainly responsible for responding to alerts.

Topics

• GitHub Advanced Security and GitHub Secret Protection features and benefits overview
• Integrating GitHub Secret Protection into developer workflows
• Real-time secret detection and prevention
• Automating secret remediation processes
• Custom patterns to cover internal or specific-to-you secret providers
• Reducing false positives
• Best practices for Secret Protection

Customer benefits

This offering will help customers:

• Proactively prevent secret leaks and secret compromises
• Enhance developer productivity through seamless integration of Secret Protection into workflows
• Empower developers to independently manage secret scanning alerts and custom patterns effectively

Learning objectives

After completing this training, learners will be able to:

• Set up and manage custom security configurations for secret scanning across repositories
• Create and deploy custom secret scanning patterns
• Enable and utilize push protection to block secret exposure at the source
• Remediate secret scanning alerts efficiently

Audience

Required:

• Application security teams
• Security champions

Optional:

• Influential senior developers and leaders

Delivery details

• Level: Intermediate [200]
• Offering type: Training
• Format: Remote
• Class size: 16 participants maximum

Customer prerequisites

Before this training, the customer needs to have in place:

• GitHub Secret Protection licenses
• Each attendee should have an active GitHub.com account (NOT their EMU or GHES account)