NIST SSDF Mapping - Githubissues

owaspsamm / samm-suite

This is an issues-only repository.

0 stars 1 forks source link

NIST SSDF Mapping #10

Closed johnellingsworth closed 7 months ago

johnellingsworth commented 2 years ago

Goals

Leverage SAMM’s capabilities to create a roadmap towards SSDF compliance
Starting point for further mapping initiatives

johnellingsworth commented 2 years ago

[x] Generate first draft of NIST mapping
[x] Follow up with NIST on process
[x] Apply recommendations from NIST to mapping
[ ] Review with stakeholders for feedback on quality of mapping and update accordingly
[ ] Share final version with NIST and publish on SAMM website

aramhovsepyan commented 2 years ago

I went through it again end-to-end with a fresh head. I now have a mapping that I can rationalize. Let me know when you guys are ready with a sweep and we can sync the results and finalize it. It seems to me that we should refine the relationship in both directions. So for some mappings SAMM is the generic end while NIST is the specific end as SAMM is much broader. Anyway - happy to discuss whenever you are ready.

johnellingsworth commented 2 years ago

@aramhovsepyan I invited you to a meeting we have scheduled for Tuesday where we can discuss. I also heard back from NIST and the news is good.

aramhovsepyan commented 2 years ago

Awesome. I hope I can reply here to thisSent from a smartphoneAram Hovsepyan, @. 13 Nov 2022, at 19:28, John Ellingsworth @.> wrote: @aramhovsepyan I invited you to a meeting we have scheduled for Tuesday where we can discuss. I also heard back from NIST and the news is good.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

johnellingsworth commented 7 months ago

Housekeeping. Closing issues that have been marked as 'Done'