-
Legal Safe Harbor:
- Add a Safe Harbor Clause: Include a statement that protects researchers from legal action when they report vulnerabilities in good faith and follow the policy guidelines.
- Example: "We will not take legal action against individuals who discover and report security vulnerabilities responsibly, in accordance with this policy."
- Add a Safe Harbor Clause: Include a statement that protects researchers from legal action when they report vulnerabilities in good faith and follow the policy guidelines.
-
Confidentiality Assurance:
- Protect Reporter Privacy: Assure reporters that their personal information and report details will be kept confidential and used only for remediation purposes.
- Example: "All reports will be handled confidentially, and we will not share your information without your consent."
- Protect Reporter Privacy: Assure reporters that their personal information and report details will be kept confidential and used only for remediation purposes.
-
Secure Communication Channels:
- Provide Encryption Options: Offer a method for securely sending sensitive information, such as a PGP key or secure submission form.
- Example: "For secure communication, please use our PGP key available at [link] when sending emails."
- Provide Encryption Options: Offer a method for securely sending sensitive information, such as a PGP key or secure submission form.
-
Bug Bounty Information (if applicable):
- Incentivize Reporting: If you have a reward program, mention it to encourage more researchers to report vulnerabilities.
- Example: "We offer rewards for valid vulnerability reports as part of our bug bounty program. Details can be found at [link]."
- Incentivize Reporting: If you have a reward program, mention it to encourage more researchers to report vulnerabilities.
-
Clarify Scope:
- Define In-Scope and Out-of-Scope Vulnerabilities: Specify which types of vulnerabilities are covered and which are not, to focus efforts on significant security issues.
- Example: "The following areas are in scope: [list]. The following are out of scope: [list]."
- Define In-Scope and Out-of-Scope Vulnerabilities: Specify which types of vulnerabilities are covered and which are not, to focus efforts on significant security issues.
-
Versioning Details:
- Include Release Dates: Adding release dates for each version can help users identify if they're on a supported version more easily.
-
Example:
Version Release Date Supported 5.1.x 2023-08-15 ✅ 5.0.x 2022-12-10 ❌ 4.0.x 2021-06-05 ✅ < 4.0 Before 2021 ❌
-
- Include Release Dates: Adding release dates for each version can help users identify if they're on a supported version more easily.
-
Response Commitment:
- Set Clear Expectations: While you've outlined response times, reiterate your commitment to resolving issues promptly.
- Example: "We are committed to resolving all verified vulnerabilities promptly and will keep you informed throughout the process."
- Set Clear Expectations: While you've outlined response times, reiterate your commitment to resolving issues promptly.
-
Acknowledgment Preference:
- Respect Anonymity Requests: Clearly state that you respect the reporter's preference regarding public acknowledgment.
- Example: "We appreciate your contribution and, with your consent, would like to acknowledge your efforts publicly. If you prefer to remain anonymous, please let us know."
- Respect Anonymity Requests: Clearly state that you respect the reporter's preference regarding public acknowledgment.
-
Update Notification:
- Inform Users of Fixes: Explain how and when users will be notified about security fixes.
- Example: "Security fixes will be announced in our release notes and through our official communication channels."
- Inform Users of Fixes: Explain how and when users will be notified about security fixes.
-
Contact Verification:
- Ensure Contact Information is Accurate: Make sure that the provided email address is monitored and that emails are responded to promptly.
- Example: "Our security team is available at [email protected], and we ensure prompt attention to all reports."
- Ensure Contact Information is Accurate: Make sure that the provided email address is monitored and that emails are responded to promptly.
-
Notifications
You must be signed in to change notification settings - Fork 0
dislovemartin/AI-snyk-fix-21cfee235f025aca7c6335a21d76ccfb
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Security policy
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published