Home > Store

GitHub Advanced Security Cert Prep (Video)

GitHub Advanced Security Cert Prep (Video)

Your browser doesn't support playback of this video. Please download the file to view it.

Online Video

Register your product to gain access to bonus material or receive a coupon.


  • Copyright 2024
  • Edition: 1st
  • Online Video
  • ISBN-10: 0-13-532653-2
  • ISBN-13: 978-0-13-532653-4

Master GitHub Advanced Security and learn all you need to know to ace the new certification.


GitHub Actions is a game-changing automation platform that revolutionizes DevOps and CI/CD pipelines by allowing seamless automation of code builds, tests, and deployments right within your GitHub repository. With its event-driven architecture, you can trigger workflows on almost any GitHub event, streamlining the development process and fostering a culture of collaboration. Its versatility extends from a marketplace of pre-built actions to the ability to write custom actions, making it an indispensable tool for modern DevOps teams. As organizations shift towards microservices and cloud-native architectures, GitHub Actions emerges as a pivotal technology for automating, customizing, and scaling workflows, thereby accelerating development cycles and achieving operational excellence.

In a world where cyber threats are escalating, mastering the advanced security features of GitHuba platform integral to modern development workflowsis non-negotiable. This course covers everything from secret scanning and dependency management to CodeQL and GitHub Enterprise configurations, ensuring you're well-prepared to pass the GHAS certification exam and implement top-notch security measures in your projects. No fluff, just the skills you need for real-world impact.


Skill Level:

  • Intermediate to Advanced

Learn How To:

  • Understand GitHub security features and functionality
  • Configure and use secret scanning
  • Configure and use dependency management
  • Configure and use code scanning
  • Use code scanning with CodeQL
  • GitHub Advanced Security best practices, results, and how to take corrective measures
  • Configure GitHub Advanced Security tools in GitHub Enterprise

Course requirement:

  • Prerequisites: Likely familiar with basic GitHub features like repositories, pull requests, and issues. Additionally, they've probably had some exposure to security best practices.

Who Should Take This Course:

Depending on the organization, the target audience could also include:

  • DevOps engineers
  • Security teams

About Pearson Video Training:   

Pearson publishes expert-led video tutorials covering a wide selection of technology topics designed to teach you the skills you need to succeed. These professional and personal technology videos feature world-leading author instructors published by your trusted technology brands: Addison-Wesley, Cisco Press, Pearson IT Certification, Prentice Hall, Sams, and Que. Topics include: IT Certification, Network Security, Cisco Technology, Programming, Web Development, Mobile Development, and more. Learn more about Pearson Video training at  http://www.informit.com/video.

Video Lessons are available for download for offline viewing within the streaming format. Look for the green arrow in each lesson.

Sample Content

Table of Contents


Lesson 1: Unveil GHAS Security Features

1.1 Differentiate security features with open-source projects and the features available when GHAS pairs with GHEC or GHES

1.2 Describe the features and benefits of Security Overview

1.3 Describe the differences between secret scanning and code scanning

1.4 Describe how secret scanning, code scanning, and Dependabot create a more secure software development life cycle

1.5 Contrast a security scenario with isolated security review and an advanced scenario

Lesson 2: Harness GHAS Features          

2.1 Describe how vulnerable dependencies are identified

2.2 Explain how to act on alerts from GHAS

2.3 Explain the implications of ignoring an alert

2.4 Explain the role of a developer when they discover a security alert

2.5 Describe the differences in access management to view alerts for different security features          

2.6 Describe a security policy in a GitHub repository

2.7 Identify where to use Dependabot alerts in the software development lifecycle

Lesson 3: Implement Secret Scanning

3.1 Describe secret scanning

3.2 Choose when secret scanning occurs

3.3 Contrast secret scanning availability for public and private repositories

3.4 Enable secret scanning for private repositories

3.5 Enable secret scanning for an organization

3.6 Explain how to pick an appropriate response to a secret scanning alert

3.7 Determine if an alert is generated for a given secret, pattern, or service provider

3.8 Determine if a given user role will see secret scanning alerts

Lesson 4: Tailor Secret Scanning

4.1 Configure the recipients of a secret scanning alert

4.2 Describe how to exclude certain files from being scanned for secrets

4.3 Explain how to enable custom secret scanning for a repository

4.4 Explain how to enable custom secret scanning for an organization

Lesson 5: Explore Dependency Vulnerability Tools         

5.1 Define a vulnerability

5.2 Describe Dependabot alerts

5.3 Describe Dependabot security updates

5.4 Define the dependency graph

5.5 Describe how the dependency graph is generated

5.6 Describe how alerts are generated for vulnerable dependencies

Lesson 6: Set Up Vulnerability Management Tools

6.1 Identify the default settings for Dependabot alerts in public and private repositories

6.2 Identify the permissions and roles required to enable Dependabot alerts

6.3 Identify the permissions and roles required to view Dependabot alerts

6.4 Enable Dependabot alerts for private repositories

6.5 Enable Dependabot alerts for organizations

6.6 Create a valid Dependabot configuration file

6.7 Configure notifications for vulnerable dependencies

Lesson 7: Resolve Vulnerable Dependencies

7.1 Identify a vulnerable dependency from a Dependabot alert

7.2 Identify vulnerable dependencies from a pull request

7.3 Enable Dependabot security updates

7.4 Remedy a vulnerability from a Dependabot alert in the Security tab

7.5 Remedy a vulnerability from a Dependabot alert in the context of a pull request

7.6 Act on any Dependabot alerts by testing and merging pull requests

Lesson 8: Initiate Code Scanning            

8.1 Describe code scanning

8.2 List the steps for enabling code scanning in a repository using GitHub Actions

8.3 Enable code scanning for use with a CodeQL analysis workflow

8.4 Describe how code scanning relates to GitHub Actions consumption

Lesson 9: Integrate Third-Party Code Scanning

9.1 Enable code scanning for use with a third-party analysis

9.2 Contrast the steps for using CodeQL versus third-party analysis when enabling code scanning

9.3 Contrast how to implement CodeQL analysis in a GitHub Actions workflow versus a third-party CI tool

Lesson 10: Configure Code Scanning

10.1 Describe how code scanning fits in the software development life cycle

10.2 Contrast the frequency of code scanning workflows

10.3 Choose a triggering event for a given development pattern

10.4 Edit the default template for Actions workflow to fit an active, open source, production repository

Lesson 11: Discover CodeQL Scanning Capabilities

11.1 Describe CodeQL

11.2 Define a QL pack, code query, code suite

11.3 Describe the default CodeQL query suites

11.4 Describe how CodeQL analyzes code and produces results

Lesson 12: Apply CodeQL Scanning

12.1 Introduce a CodeQL analysis workflow to a repository

12.2 List the locations in which CodeQL queries can be specified for use with code scanning

12.3 Configure the language matrix in a CodeQL workflow

12.4 Reference a CodeQL query from a public repository within a code scanning workflow

12.5 Reference a CodeQL query from a private repository within a code scanning workflow

12.6 Reference a CodeQL query from a local directory within a code scanning workflow

12.7 Reference a configuration file within the same repository

12.8 Reference a configuration file in a remote public repository

12.9 Execute code scanning with the CodeQL CLI

12.10 Contrast the steps to execute code scanning in GitHub Actions vs the CodeQL CLI

Lesson 13: Triage CodeQL Analysis Results

13.1 Describe how to view code scanning results from CodeQL analysis

13.2 Troubleshoot a failing code scanning workflow using CodeQL

13.3 Follow the data flow through code using the show paths experience

13.4 Explain the reason for a code scanning alert given documentation linked from the alert

13.5 Determine if and why a code scanning alert needs to be dismissed

13.6 Describe potential shortfalls in CodeQL via model of compilation and language support

13.7 Optimize CodeQL analysis runtimes

Lesson 14: Incorporate External Scanning Tools

14.1 Explain how to upload 3rd party SARIF results via the SARIF endpoint

14.2 Explain the purpose of defining a SARIF category

Lesson 15: Implement GHAS Best Practices

15.1 Use a CVE and CWE to describe a GitHub Advanced Security alert and list potential remediation

15.2 Advanced Security alert and list potential remediation

15.3 Describe the decision-making process for closing and dismissing security alerts

15.4 Determine the roles and responsibilities of development and security teams on a software development workflow

15.5 Explain how to set a review cadence with security teams, when appropriate

15.6 Use security policies to instruct all contributors to better secure their repositories

15.7 Compare the code scanning alert against the repositorys security policy

15.8 Align repository branch protection configuration with written security policies

Lesson 16: Administer GitHub Advanced Security

16.1 Explain how GitHub Advanced Security features are enabled on GitHub Enterprise Server

16.2 Explain how GitHub Advanced Security features are enabled for an organization

16.3 Set security policies for a repository

16.4 Set security policies for an organization

16.5 Describe how permissions are interpreted throughout security workflow

16.6 Locate API endpoints for GHAS features, like secret scanning, code scanning, and dependabot

16.7 List stakeholders that need to be involved in the security workflows enabled by GHAS

16.8 Configure code scanning within a repository or organization using the default CodeQL workflow

16.9 Identify the custom build steps necessary in a CodeQL workflow



Submit Errata

More Information

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Pearson IT Certification products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.pearsonitcertification.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020