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.

Sign up for GitHub

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

Jump to bottom

Set a security policy #2142

Merged
merged 2 commits into from
Nov 14, 2023
Merged

Set a security policy #2142

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bb8bac8
Add security policy
pnacht Nov 13, 2023
342ce4b
Only use private vuln report
pnacht Nov 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Security Policy

If you have discovered a security vulnerability in this project, please report it
privately. **Do not disclose it as a public issue.** This gives us time to work with you
to fix the issue before public exposure, reducing the chance that the exploit will be
used before a patch is released.

You may submit the report in the following ways:

- send a [private vulnerability report](https://github.com/keras-team/keras-cv/security/advisories/new)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would actually just vote for just this latter option here. Seems simpler, and that we don't have to maintain a separate email address for this.

Is there a downside?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pnacht as to the question about the right mental model for keras-cv and keras-nlp, they can be thought of as equivalent to keras-team/keras at least from this perspective. Maintained by the Keras team directly, supporting TF but not under the TF umbrella for maintenance/contribution.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would actually just vote for just this latter option here. Seems simpler, and that we don't have to maintain a separate email address for this.

Is there a downside?

Done. And nope, no downside. Just remember to actually enable the advisories in the repo Settings > "Code security & analysis"!

@pnacht as to the question about the right mental model for keras-cv and keras-nlp, they can be thought of as equivalent to keras-team/keras at least from this perspective. Maintained by the Keras team directly, supporting TF but not under the TF umbrella for maintenance/contribution.

Gotcha. Thanks for the info.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enabled the reporting now. Thanks!


Please provide the following information in your report:

- A description of the vulnerability and its impact
- How to reproduce the issue

This project is maintained by volunteers on a reasonable-effort basis. As such,
please give us 90 days to work on a fix before public exposure.
Loading