GH-100 practice question 2 of 15

Why would someone choose to configure a security policy?

Full set: 65 questions
Answer options
A: To communicate corporate security and compliance policies for end users on a private repository.
B: To provide information on an open source repository for open source collaborators and researchers that may need to report and disclose sensitive security findings to maintainers securely. Correct answer
C: To prevent anyone from pushing to the repository without approval.
D: To define which open source packages are permitted for use as part of that repository.
Correct Answer:
B. To provide information on an open source repository for open source collaborators and researchers that may need to report and disclose sensitive security findings to maintainers securely.
Explanation

A security policy, implemented as a SECURITY.md file in a GitHub repository, serves as a public-facing set of instructions for security researchers and users. Its primary purpose is to define a clear and secure process for them to report potential security vulnerabilities they have discovered in the project. This allows maintainers to receive and address sensitive security information privately, preventing premature public disclosure that could be exploited. This practice is a cornerstone of responsible disclosure and is crucial for maintaining the security and integrity of both open-source and private projects.

Why Incorrect

A. A SECURITY.md file is for vulnerability disclosure procedures, not for communicating general corporate security and compliance policies to end-users.
C. Preventing pushes without approval is managed through repository permissions and branch protection rules, not a security policy file.
D. Defining permitted open-source packages is a function of dependency management and supply chain security policies, often enforced with other tools.

References

1. GitHub Docs. (n.d.). Adding a security policy to your repository. GitHub. Retrieved from https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository.

Reference Details: The first paragraph under the "About security policies" section explicitly states

"You can provide instructions for how to report a security vulnerability in your project by adding a SECURITY.md file... When someone creates an issue in your repository

they will see a link to your project's security policy." This directly supports the purpose described in option B.

2. The Open Source Security Foundation (OpenSSF). (n.d.). A guide to coordinated vulnerability disclosure for open source projects. Retrieved from https://github.com/ossf/oss-vulnerability-guide/blob/main/maintainer-guide.md#readme.

Reference Details: In the section "Have a vulnerability disclosure policy

" the guide recommends creating a SECURITY.md file and states its purpose is to "tell people how to report potential vulnerabilities in your project." This aligns with providing a secure reporting channel for collaborators and researchers.

3. Stanford University Information Security Office. (n.d.). Secure Software Development. Retrieved from https://uit.stanford.edu/guide/secure-software/development.

Reference Details: Under the "Vulnerability Management" section

the guide advises to "Establish a vulnerability disclosure policy (VDP) that provides a clear path for external security researchers to report vulnerabilities." While not mentioning SECURITY.md by name

it describes its exact function

which is the standard implementation of a VDP on GitHub.

Scroll to Top