Versions Compared

Old Version 19

changes.mady.by.user Unknown User (mjc)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (mjc)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Require a minimum of 3 PPMC members to have attended a (yet to be written) training course on Vulnerability handling at the ASF before the podling is allowed to graduate
  • Require projects to maintain a security team of at least 3 people all of whom have undertaken the training described in the previous point
  • Is OpenSSF training something we should promote to committers
  • Educate projects on the selection of dependencies, and their upkeep (see also "Help users pick secure projects") (This could possibly be OpenSSF Scorecards)
  • Write up how the ASF acts as a Curator of OSS (in terms of the curation discussions happening) and what curation functions are performed

Theme: Improving our process and policy

WH Theme: Preventing Defects

...

  • Make sure our projects are keeping track of their dependencies, especially things that are EOL, especially things that are other Apache projects and EOL (example log4j v1)
    • Track the dependencies across our projects so we can see the combined-graph for the latest version of each ASF project. Work centrally to encourage that dependencies are not insecure, or excessively dated.
  • Facilitate direct funding efforts such as TideLift which provide direct financial support for developers to focus on matters such as security
  • How does OpenSSF Alpha and/or Omega fit with ASF
  • Look at the sponsored SOS rewards program
  • Think about which ASF projects would benefit from being covered by IBB (they reached out to us to expand our current set)
  • Looks at OpenSSF OSS Fuzz (high false positive rate - would benefit from manual triage by OSS Fuzz team before notifications are sent to maintainers). See also mail from GOSST. 

WH Theme: Identify Critical projects / Help users pick secure projects

...

WH Theme: SBOMS /  Notifications

  • See SBOM page
  • Look at OpenSSF SLSA/SBOM work (SLSA)Consider adopting providing vulnerability data in a format that can be combined with SBOM such as VEX (CSAF) and/or OSV  https://osv.dev/ (instead of CVE/CVSS). (These are not mutually exclusive)/
  • Look at EOL notifications CSAF as an example https://access.redhat.com/security/data/csaf/beta/2019/rhsa-2019_1862.json
  • We have no way to know who is using our projects, nor do we want to capture that data (so is the current vulnerability notification system sufficient?)

Unsorted / Not Security

Completed

  • Look again into SCR:CLR as a service to projects. Done. Rejected for various reasons.
  • Sometimes communication with vulnerability reporters breaks down, is it time to have a more structured tool for handling reports which forces the process? or is it more people engagement? or can we just require checkboxes before allocating CVE names in our existing tool?
    • From September 2022 we have a dedicated person paid by ASF to perform vulnerability handling functions
  • In July 2022 we implemented automated checks (INFRA-23459) to ensure packages contained the right signatures and met policy
  • Minimize situations in which PMCs refuse contributions for anything other than strong technical reasons
    • Forking increases the attack area and complexity of fixes - projects should be governed such that the need to fork when using the code is minimized
    • Stop accepting forks as a necessary and acceptable outcome of PMC control of ASF projects - users cannot be expected to invest in a community if the gates to the PMC are closed
    • Focus on education such that PMCs can enable "constructive forking" in a controlled manner such that the forking community are supported in improving a projects architecture to minimize the need to fork
    • Educate ASF projects that the way to a healthy community is through the production of reusable components that enable contributions designed to enhance reuse in broader contexts so as to allow the pool of contributors to grow (covered in a different bullet)
    • Re-Affirm that ASF Projects are successful when the broadest possible community is engaged leading to more maintainers and more eyeballs on the shared code
  • Consider annual re-affirmation by PMCs towards Apache Way, with reminders of What It Is.
  • Creating messaging for community members, e.g.
    • Popularizing, re-affirming The Apache Way
    • Presentations for community members to share with Colleagues on how to give back, how to handle Open Source contributions  (covered in a different bullet)
    • Language for corporate lawyers to facilitate contributions by developers in their organization, what it means when a developer signs an ICLA (or is hired already having one on file), etc. 
  • One of the big Elephants-In-The-Room in terms of security is that we have no idea who is using our products. Increasingly, finding good information on the Web requires some sort of log-in requiring an email address.  If we had a registry of everyone that downloaded our code by project, we would be able to notify them of updates and security fixes.  It would be best if this was implemented ASF-wide, at least as a policy, or as a shared registry.  I realize there are privacy issues here, but I believe these can be addressed.  (summarised under notiifcations)