-
Notifications
You must be signed in to change notification settings - Fork 526
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
Intoto summary #208
Intoto summary #208
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks for all the hard work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few logistical notes + nits. Else, lgtm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please address the comment for details on common supply chain threat reference
Needs a rebase... |
In-toto security assessment summary
Content taken from here: https://docs.google.com/document/d/1dcDu8XWHlJ47FsIh3M1NwihmgfO3iqjH_Dn5tkevdqg/edit
I moved around the sections a bit for readability and thinking a little about how this might have looked over time, if we had started with this process.
Note: this is both the in-toto assessment and a template. We're planning to follow the same process for first 5 assessment (see #167) -- we're not going to get too caught up in sticking to the format if we find unexpected differences, but trying to avoid revisiting process until we have done the first set.