Microsoft GH-500 Questions Answers

Comprehensive and Detailed Explanation:

Dependabot alerts are generated based on data from various sources:​

National Vulnerability Database (NVD): A comprehensive repository of known vulnerabilities, which GitHub integrates into its advisory database.​

GitHub Docs

Security Advisories Reported on GitHub: GitHub allows maintainers and security researchers to report and discuss vulnerabilities, which are then included in the advisory database.​

The dependency graph and manifest/lock files are tools used by GitHub to determine which dependencies are present in a repository but are not sources of vulnerability disclosures themselves.​

CodeQL security queries are associated with Common Weakness Enumeration (CWE) classifications. CWE provides standardized categories for classes of software weaknesses, such as improper input validation, path traversal, or SQL injection. GitHub CodeQL query metadata and alert tags can contain CWE identifiers, and GitHub allows code scanning alerts to be filtered by CWE tags. CVEs identify specific publicly disclosed vulnerabilities rather than general weakness categories in source-code analysis. A GHSA identifies a GitHub Security Advisory, while VEX communicates whether a product is affected by a known vulnerability. For CodeQL findings, CWE is therefore the relevant classification system used to describe the type of weakness represented by an alert. GitHub's code scanning API also exposes CodeQL rules containing external/cwe/... tags.

GitHub secret scanning is designed to identify credentials and other sensitive values that match supported secret patterns. Among the options listed, private keys are the supported secret type. GitHub classifies private keys such as RSA, OpenSSH, EC, and PGP private keys as generic secret patterns. These are distinct from organization-specific custom patterns, which administrators create by defining their own regular expressions. Usernames and general PII are not treated as standard secret-scanning credential patterns, while “sealed boxes” are not a supported secret category. In current GitHub terminology, generic-pattern detection is separately configurable, so it may need to be enabled for the repository. Nevertheless, of the choices presented, private keys are the valid secret-scanning type.

Comprehensive and Detailed Explanation:

To generate a dependency graph for a private repository, GitHub requires:​

Dependency graph enabled: The repository must have the dependency graph feature enabled. This can be configured at the organization level to apply to all new private repositories.​

Access to manifest and lock files: GitHub needs read-only access to the repository's dependency manifest and lock files (e.g., package.json, requirements.txt) to identify and map dependencies.​