Clarify SECURITY.md with base image scanning policy (#674)

This commit is contained in:
Geoff Bourne authored and GitHub committed 2026-09-16 20:59:37 -05:00
1 parent e2b5c995b7
commit 43e5ef3607
2 files changed
+7 -2

No files matched your search

+2 -2
View File
@@ -8,7 +8,7 @@ on:
tags: tags:
- "[0-9]+.[0-9]+.[0-9]+" - "[0-9]+.[0-9]+.[0-9]+"
paths-ignore: paths-ignore:
- README.md - "*.md"
- "examples/**" - "examples/**"
- "docs/**" - "docs/**"
- "renovate.json5" - "renovate.json5"
@@ -16,7 +16,7 @@ on:
branches: branches:
- master - master
paths-ignore: paths-ignore:
- README.md - "*.md"
- "examples/**" - "examples/**"
- "docs/**" - "docs/**"
- "renovate.json5" - "renovate.json5"
+5
View File
@@ -15,6 +15,11 @@ To report a vulnerability privately:
This allows us to review, reproduce, and resolve the issue in a private environment before public disclosure. This allows us to review, reproduce, and resolve the issue in a private environment before public disclosure.
### Base Image & Non-Runtime Package Scans
- **Unused & Non-Runtime Base OS Packages:** Automated scanner reports (e.g., Trivy, Grype) flagging vulnerabilities in base OS packages that are **neither executed during container startup nor involved in running the Bedrock server process** (e.g., `perl` or unused system utilities) are considered non-actionable.
- **Base Image Lifecycle:** We do not manually patch or update individual OS packages inside the container build (e.g., running `apt-get upgrade`), nor do we accept PRs to do so. Base OS packages are updated automatically whenever upstream base image updates are pulled during routine builds.
- **Actionable Reports:** Security advisories must demonstrate a plausible attack vector or exploit path that directly impacts the Bedrock server execution environment.
--- ---
## Important Expectations & Bug Bounties ## Important Expectations & Bug Bounties