Skip to content

docs: add vulnerability response policy to support page #7423

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

Open
adamvialpando wants to merge 1 commit into
base: main
Choose a base branch
from
+14 −0
Open

docs: add vulnerability response policy to support page #7423

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions docs/docs/support/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,20 @@ Beyond that, many issues have already been solved. A quick search can save you t
- [Rust](https://github.com/Flagsmith/flagsmith-rust-client)
- [Elixir](https://github.com/Flagsmith/flagsmith-elixir-client)

## CVEs and Vulnerability Reports

### Remediation SLAs

Severity is assigned using CVSS together with the exploitability of the component as Flagsmith uses it.

| Severity | Remediation SLA |
| ------------- | --------------- |
| Critical/High | 30 days |
| Medium | 60 days |
| Low | 90 days |

Flagsmith evaluates exploitability for each reported finding.

## What We Need From You

When you do reach out, including the right information from the start makes a big difference. Here's what helps us
Expand Down
Loading