Ability to detect custom patterns: Organizations can define custom patterns for detecting secrets unique to their environment. This customization ensures that push Protection can effectively identify and block even non-standard secrets [Not C].
Customizing push protection
Once push protection is enabled, you can customize it further [Not A]:
Configure push protected patterns
Customize which secret patterns are included in push protection at the enterprise or organization level.
Define custom patterns
Define custom patterns that push protection can use to identify secrets and block pushes containing these secrets Note: You can enable push protection:
At repository/organization level, if you are a repository administrator or an organization owner.
You will see alerts in the Security tab of your repository when a contributor to the repository bypasses push protection.
For your account on GitHub, as a user. This type of push protection is referred to as "push protection for users." It protects you from pushing secrets to any public repository on GitHub, but no alerts are generated.

Access to Dependabot alerts
You can see all of the alerts that affect a particular project on the repository's Security tab or in the repository's dependency graph.
By default, we notify people with write, maintain, or admin permissions in the affected repositories about new Dependabot alerts.
Write permissionis the minimum levelneeded to be automatically notified.

Where a dependency has a known vulnerability, the warning message includes:
A brief description of the vulnerability.
A Common Vulnerabilities and Exposures (CVE) or GitHub Security Advisories (GHSA) identification number. You can click this ID to find out more about the vulnerability.
The severity of the vulnerability.
The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release.

Reviewing dependency changes in a pull request
If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.
Reviewing and fixing alerts
It's important to ensure that all of your dependencies are clean of any security weaknesses.
When Dependabot discovers vulnerabilities in your dependencies, you should assess your project's level of exposure and determine what remediation steps to take to secure your application.
If a patched version of the dependency is available, you can generate a Dependabot pull request to update this dependency directly from a Dependabot alert. If you have Dependabot security updates enabled, the pull request may be linked in the Dependabot alert.