You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cncf/self-assessment.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,8 +202,7 @@ This document provides the CNCF TAG-Security with an initial understanding of Po
202
202
203
203
***Outbound**:
204
204
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
207
206
- Documentation updates and blog posts
208
207
- Conference presentations and talks
209
208
- 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:
226
225
227
226
***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.
228
227
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).
230
229
231
230
***Credit**: Security researchers who responsibly disclose vulnerabilities are credited in security advisories and release notes.
232
231
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.
234
233
235
234
### Vulnerability Response Process
236
235
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.
238
237
239
238
***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.
240
239
241
240
***Fix Development**: Security fixes for embargoed CVEs are developed in private repositories to prevent premature disclosure.
242
241
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.
244
243
245
244
### Incident Response
246
245
@@ -250,6 +249,11 @@ Podman is a critical component of the cloud-native ecosystem:
250
249
251
250
## Appendix
252
251
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
+
253
257
### OpenSSF Best Practices
254
258
255
259
***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:
266
270
267
271
* 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)
268
272
269
-
* Details TBD
270
-
271
273
### Related Projects / Vendors
272
274
273
275
***Buildah**: A tool that facitiliates building OCI container images.
0 commit comments