Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a Security Policy with safe consuming instructions #6353

Closed
joycebrum opened this issue Mar 27, 2024 · 0 comments · Fixed by #6354
Closed

Create a Security Policy with safe consuming instructions #6353

joycebrum opened this issue Mar 27, 2024 · 0 comments · Fixed by #6354
Labels
enhancement New feature or request

Comments

@joycebrum
Copy link
Contributor

Feature Description

Hi, I'm Joyce and I'd like to suggest the adoption of a security policy that not only allows security researchers to privately report security vulnerabilities in LLaMA C++, but also informs users of common security practices they should consider when using it.

A Security Policy is a GitHub standard document (SECURITY.md) that can be found in the "Security Tab" to instruct users how to report vulnerabilities in a safe and efficient way. It appears in both the About section on the right and as a tab option together with README and LICENSE.

image

Motivation

This information will benefit:

  1. the user, that will have guidelines on how to safely run a model for their application
  2. the project, that can avoid receiving false positive vulnerability reports while allowing security researches to disclose newly found vulnerabilities

Possible Implementation

I'll send a PR along with this issue with some suggestions such as data privacy, untrusted models, untrusted inputs, etc.

Disclosure: I work for Google at Google’s Open Source Security Upstream Team to suggest security improvements to open sources.

@joycebrum joycebrum added the enhancement New feature or request label Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant