|
| 1 | +<!-- |
| 2 | +Copyright (c) 2025 Erick Bourgeois, firestoned |
| 3 | +SPDX-License-Identifier: Apache-2.0 |
| 4 | +--> |
| 5 | + |
| 6 | +# Security Policy |
| 7 | + |
| 8 | +5-Spot is a FINOS-incubating project. Its security posture is described |
| 9 | +in detail under [`docs/src/security/`](./docs/src/security/); this |
| 10 | +document gives the short version: how to report a vulnerability and what |
| 11 | +to expect back. |
| 12 | + |
| 13 | +## Reporting a vulnerability |
| 14 | + |
| 15 | +**Do not open a public GitHub issue for security problems.** Please use |
| 16 | +one of the private channels below so we can triage and coordinate |
| 17 | +disclosure: |
| 18 | + |
| 19 | +1. **GitHub private vulnerability report** (preferred): |
| 20 | + <https://github.com/finos/5-spot/security/advisories/new> |
| 21 | +2. **Email**: `security@finos.org` — for general FINOS-coordinated |
| 22 | + disclosure. Include `5-spot` in the subject line. |
| 23 | +3. **Direct maintainer**: `erick.bourgeois@gmail.com` — PGP-signed |
| 24 | + messages welcome. |
| 25 | + |
| 26 | +Please include, where possible: |
| 27 | + |
| 28 | +- A description of the vulnerability and its impact. |
| 29 | +- The version / commit SHA / container image digest you tested against. |
| 30 | +- Steps to reproduce or a minimal proof-of-concept. |
| 31 | +- Any suggested mitigation or patch. |
| 32 | + |
| 33 | +## What to expect |
| 34 | + |
| 35 | +| Phase | Target | |
| 36 | +| ---------------------- | ------------------------------------------------------------------- | |
| 37 | +| Acknowledgement | 3 business days | |
| 38 | +| Initial triage | 7 business days | |
| 39 | +| Fix / mitigation ETA | Shared after triage; depends on severity (CVSS) and blast radius | |
| 40 | +| Public disclosure | After a fix is released, coordinated with the reporter | |
| 41 | + |
| 42 | +We follow standard coordinated-disclosure practice: the reporter is |
| 43 | +credited in the resulting advisory unless they prefer to remain |
| 44 | +anonymous. |
| 45 | + |
| 46 | +## Supported versions |
| 47 | + |
| 48 | +5-Spot follows a rolling-release model until `v1.0.0`. Only the latest |
| 49 | +release on `main` receives security fixes during the incubation phase. |
| 50 | + |
| 51 | +## Scope |
| 52 | + |
| 53 | +In scope: |
| 54 | + |
| 55 | +- The 5-Spot controller binary and its container images |
| 56 | + (`ghcr.io/finos/5-spot`, `ghcr.io/finos/5-spot-distroless`). |
| 57 | +- The Custom Resource Definitions and admission policies shipped under |
| 58 | + [`deploy/`](./deploy). |
| 59 | +- The build and release pipeline |
| 60 | + ([`.github/workflows/`](./.github/workflows)) insofar as a compromise |
| 61 | + would affect published artifacts. |
| 62 | + |
| 63 | +Out of scope: |
| 64 | + |
| 65 | +- Vulnerabilities in upstream dependencies that are already addressed |
| 66 | + in our [`.vex/`](./.vex) directory as `not_affected` — these have a |
| 67 | + documented, reviewed justification. If you disagree with one, please |
| 68 | + still report it so we can re-evaluate. |
| 69 | +- Findings that require the reporter to already have cluster-admin or |
| 70 | + equivalent privileges. |
| 71 | +- Denial-of-service against a single 5-Spot replica (the operator is |
| 72 | + designed to be run with leader election and horizontal replicas; see |
| 73 | + [`docs/src/operations/multi-instance.md`](./docs/src/operations/multi-instance.md)). |
| 74 | + |
| 75 | +## Related documents |
| 76 | + |
| 77 | +- [Threat model](./docs/src/security/threat-model.md) |
| 78 | +- [VEX publication process](./docs/src/security/vex.md) |
| 79 | +- [Admission policies & validation](./docs/src/security/admission-validation.md) |
| 80 | +- [FINOS security policy](https://www.finos.org/hubfs/finos/FINOS%20Vulnerability%20Disclosure%20Policy.pdf) |
0 commit comments