Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surface value of performing (self|joint) security assessments better #1378

Open
mrbobbytables opened this issue Jul 12, 2024 · 2 comments
Open
Labels
process-documentation Doc changes for process and procedures

Comments

@mrbobbytables
Copy link
Member

The security assessments were originally thought of as a "package" with each assessment building on the previous one with the idea that they make the following assessments easier/faster to complete. This is MUCH more important for the eventual security audit and speeding up that process.

The fact that they are intended to speed up the later processes isn't surfaced well, and more projects might be more inclined to do them / think about them further if they knew that it'd make things easier for them to get through the later processes.

cc @TheFoxAtWork

@mrbobbytables mrbobbytables added the process-documentation Doc changes for process and procedures label Jul 12, 2024
@TheFoxAtWork
Copy link
Contributor

Thanks @mrbobbytables for creating this.

As we've been exploring the #1277 Security DTR, we talked a little about the differences between Self-Assessment, Joint-assessment, and Security Audit. Its not the first time these questions have come up, so we're not doing a good job surfacing these to projects.

With the recent criteria changes for moving levels, Self-assessments are required for Incubation level. Joint -assessments are not because we did not want to impose a moving levels requirement that was contingent upon the availability and expertise of community members to participate. However in the years since the Security Assessments were created by TAG Security, we've found projects that complete a self-assessment and joint-assessment have more robust security considerations that directly benefit them during the audit. Feedback we've received from organizations conducting security audits on projects with a self-assessment and joint-assessment allow the Audit to be conducted faster, reducing the volume of information discovery required to get started, as much of the background detail was presented in both of those documents.

What suggestions do people have for making this more clear or at least increasing the awareness of these benefits?

@angellk
Copy link
Contributor

angellk commented Nov 2, 2024

Suggestions:

  • In the due diligence for projects moving to Incubation - the TOC reviewer(s) include a recommendation for the project to begin a joint security assessment with TAG Security upon moving to Incubation.
  • Update the documentation for Incubation and Graduation to clarify that the Joint assessments help prepare for the security audits and the due diligence for projects moving levels
  • A CNCF blog on why security assessments matter - and what differentiates them from a security and/or fuzzing audit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process-documentation Doc changes for process and procedures
Projects
Status: New
Development

No branches or pull requests

3 participants