Skip to content

Commit 41ff61a

Browse files
committed
vendor neutral language, NIST database for known issues
Signed-off-by: Lokesh Mandvekar <[email protected]>
1 parent 57c7a02 commit 41ff61a

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

docs/cncf/self-assessment.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -202,8 +202,7 @@ This document provides the CNCF TAG-Security with an initial understanding of Po
202202

203203
* **Outbound**:
204204

205-
- Release announcements via GitHub releases and the Podman mailing list
206-
- Security advisories through [https://access.redhat.com](https://access.redhat.com) and Bugzilla trackers for Fedora and RHEL on [bugzilla.redhat.com](http://bugzilla.redhat.com)
205+
- Release announcements via the [official Podman website](https://podman.io), GitHub releases, and the Podman mailing list
207206
- Documentation updates and blog posts
208207
- Conference presentations and talks
209208
- Project website at [podman.io](https://podman.io) with comprehensive documentation
@@ -226,21 +225,21 @@ Podman is a critical component of the cloud-native ecosystem:
226225

227226
* **Response Time**: The team commits to responding to vulnerability reports within 48 hours. All medium and higher severity exploitable vulnerabilities are prioritized as a matter of general practice.
228227

229-
* **Coordination**: For critical vulnerabilities, Red Hat’s Product Security team coordinates with downstream projects to file bug trackers for downstreams (Fedora / RHEL).
228+
* **Coordination**: For critical vulnerabilities, ct Security team coordinates with downstream projects to file bug trackers for downstreams (Fedora / RHEL).
230229

231230
* **Credit**: Security researchers who responsibly disclose vulnerabilities are credited in security advisories and release notes.
232231

233-
* **Public Disclosure**: Vulnerabilities are disclosed by Red Hat’s Product Security team with appropriate embargo periods for critical issues, following industry best practices for responsible disclosure.
232+
* **Public Disclosure**: Vulnerabilities are disclosed by the project maintainers with appropriate embargo periods for critical issues, following industry best practices for responsible disclosure.
234233

235234
### Vulnerability Response Process
236235

237-
* **Triage**: Security reports are triaged by the Red Hat’s Product security team and assigned severity levels (Critical, High, Medium, Low) using CVSS scoring where applicable.
236+
* **Triage**: Security reports are triaged by the project maintainers and assigned severity levels (Critical, High, Medium, Low) using CVSS scoring where applicable.
238237

239238
* **Investigation**: The team investigates the vulnerability, determines impact, and develops fixes. All medium and higher severity exploitable vulnerabilities discovered through static or dynamic analysis are fixed in a timely way after they are confirmed.
240239

241240
* **Fix Development**: Security fixes for embargoed CVEs are developed in private repositories to prevent premature disclosure.
242241

243-
* **Disclosure**: Vulnerabilities are disclosed by the Red Hat Product Security team with appropriate embargo periods for critical issues. The project follows industry best practices for coordinated vulnerability disclosure.
242+
* **Disclosure**: Vulnerabilities are disclosed by the project maintainers with appropriate embargo periods for critical issues. The project follows industry best practices for coordinated vulnerability disclosure.
244243

245244
### Incident Response
246245

@@ -250,6 +249,11 @@ Podman is a critical component of the cloud-native ecosystem:
250249

251250
## Appendix
252251

252+
### Known Issues Over Time
253+
254+
* See [this NIST Vulnerability Database list](https://nvd.nist.gov/vuln/search#/nvd/home?vulnRevisionStatusList=published&offset=0&rowCount=50&keyword=podman&resultType=records) for CVEs to date. This includes issues in the Go toolchain and dependencies used by Podman.
255+
(Four of the entries as of the date of this writing aren't directly related to Podman but contain Podman in the search terms.)
256+
253257
### OpenSSF Best Practices
254258

255259
* **Current Status**: Podman has achieved a [passing OpenSSF Best Practices badge](https://www.bestpractices.dev/projects/10499) (100% compliance), demonstrating adherence to security best practices.
@@ -266,8 +270,6 @@ Podman is a critical component of the cloud-native ecosystem:
266270

267271
* List of companies and organizations using / shipping Podman [https://github.com/containers/podman/blob/main/ADOPTERS.md](https://github.com/containers/podman/blob/main/ADOPTERS.md)
268272

269-
* Details TBD
270-
271273
### Related Projects / Vendors
272274

273275
* **Buildah**: A tool that facitiliates building OCI container images.

0 commit comments

Comments
 (0)