Code scanning in GitHub Advanced Security for Azure DevOps lets you analyze the code in an Azure DevOps repository to find security vulnerabilities and coding errors.
CodeQL is the code analysis engine developed by GitHub to automate security checks. You can analyze your code using CodeQL and display the results as code scanning alerts.

Defining a custom pattern for an organization
Before defining a custom pattern, you must ensure that you enable secret scanning for the repositories that you want to scan in your organization. You can use security configurations to enable secret scanning on all repositories in your organization.
1. In the upper-right corner of GitHub, click your profile picture, then click Your organizations.
2. Next to the organization, click Settings.
3. In the "Security" section of the sidebar, select the Advanced Security dropdown menu, then click Global settings.
4. Under "Custom patterns", click New pattern.
*-> 5. Enter the details for your new custom pattern. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
Example:

[B]
A Dependabot direct dependency is a package or library that your project explicitly lists and requires in its manifest file (like package.json or Gemfile). Dependabot specifically focuses on these direct dependencies, creating automated pull requests to update them to newer, more secure, or stable versions, helping to keep your project's dependencies up-to-date and prevent security vulnerabilities.
[D]
Direct dependencies may have their own dependencies, which are referred to as transitive dependencies or indirect dependencies.
Locked Files and Dependencies
A locked file in software development is a file that records the exact versions of all dependencies (both direct and transitive) used in a project at a specific point in time. It acts as a snapshot of the dependency graph, ensuring that the project builds consistently with the same versions across different environments.

About the dependency review action
The "dependency review action" refers to the specific action that can report on differences in a pull request within the GitHub Actions context. You can use the dependency review action in your repository to enforce dependency reviews on your pull requests. [D] The action uses the dependency review REST API to get the diff of dependency changes between the base commit and head commit. You can use the dependency review API to get the diff of dependency changes, including vulnerability data, between any two commits on a repository. [A]
[D] dependency-review-action
The dependency review action scans your pull requests for dependency changes, and will raise an error if any vulnerabilities or invalid licenses are being introduced. The action is supported by an API endpoint that diffs the dependencies between any two revisions on your default branch.
Incorrect:
[Not B] The workflow_dispatch event adds a layer of flexibility and control to your GitHub workflows, enabling manual triggers with custom inputs. Whether integrating with external systems or managing deployments directly from GitHub, workflow_dispatch provides the tools necessary for robust workflow management.