-
Notifications
You must be signed in to change notification settings - Fork 518
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
document annual review process to update security assessment #152
Comments
It would be great if someone were to draft some text about this and suggest which of our docs it shoul go into, since this keeps coming up as a question |
Happy to take a stab at it.
…On Mon, Jul 1, 2019 at 6:51 PM Sarah Allen ***@***.***> wrote:
It would be great if someone were to draft some text about this and
suggest which of our docs it shoul go into, since this keeps coming up as a
question
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGENIQJWOO6DMAGVOLA5WLP5K7DPANCNFSM4HHMQGKQ>
.
|
WIP outline... 4fee281 |
This issue has been automatically marked as inactive because it has not had recent activity. |
There is some text in https://github.com/cncf/tag-security/blob/main/assessments/intake-process.md for this, is this sufficient for now? |
Needs additional definition of scope. |
revisit again when staleness hits. |
This issue has been automatically marked as inactive because it has not had recent activity. |
While we recognize this is something we need to get to due to the evolving nature of software projects, it currently exceeds our capacity due to the increased number of projects in the CNCF which correlates to the increased number of projects in the assessments backlog that we need to get to. Should the TOC request a review of projects previously assessed or a new subproject under the same project umbrella, we will prioritize those. In the meantime, we will continue to follow the intake process to prioritize ordering and sequencing of assessments. |
this has been discussed in meetings
well-articulated in PR comment by @rficcaglia
"I think the notion that a single point in time review ignores the reality that threats change over time. someone using this review process as evidence of "trustworthiness" can be lulled into thinking something is "safe" since it was reviewed N years ago."
The text was updated successfully, but these errors were encountered: