Split safety impact into supplier / deployer safety impacts #1

Activity

1. ahouseholder

   added

   enhancementNew feature or requestNew feature or request

   on Sep 9, 2020
2. ahouseholder

   assigned

   ahouseholder

   and

   j---

   on Sep 25, 2020
3. ahouseholder

   added this to the SSVC v2 milestone on Oct 2, 2020
4. j--- commented on Oct 8, 2020

   

   j---

   on Oct 8, 2020

   Collaborator

   More actions

   This is also related to feedback from https://blog.secursive.com/posts/critical-look-stakeholder-specific-vulnerability-categorization-ssvc/
   Basically that "safety impact" as written in v1 is too complicated / fine grained for the supplier to provide accurately.
5. ahouseholder

   changed the title [-]Split safety impact into vendor / applier safety impacts[/-] [+]Split safety impact into supplier / deployer safety impacts[/+] on Oct 16, 2020
6. ahouseholder commented on Oct 16, 2020

   

   ahouseholder

   on Oct 16, 2020

   Last edited by ahouseholder

   ContributorAuthor

   More actions

   Updated plan based on recent discussions:

   • Combine none/minor categories into one, leaving 4 levels
   • Split safety into separate decisions for supplier / deployer
   • Supplier is focused on public_safety
   • Supplier maps those 4 levels to 2 (maybe 3) public_safety_impact categories (L/H or L/M/H)
   • Deployer is focused on situated_safety
   • Deployer version integrated with Mission Impact Merge situated safety impact and mission impact into a unified factor #7 in a ~4x4 table that maps both dimensions impact into a combined 3 safety&mission_impact categories (L/M/H)

   End result for Deployers will be that safety & mission will go from 5x5=25 possibilities to 4x4 -> 3 categories which should reduce the complexity of the deployer tree considerably.
7. ahouseholder

   added a commit that references this issue on Oct 26, 2020

   Compress safety and mission impacts fix for #1(+11 squashed commits)

   ...

   4c76ef9
8. zmanion

   closed this as completedin #51on Oct 29, 2020
9. zmanion

   added a commit that references this issue on Oct 29, 2020

   Merge pull request #51 from ahouseholder/feature/fix_1

   ...

   aa55a3c
10. laurie-tyz

    added a commit that references this issue on Oct 30, 2020

    Merge pull request #1 from CERTCC/main

    ...

    dbc0341
11. j---

    added a commit that references this issue on Nov 24, 2020

    Merge pull request #1 from CERTCC/main

    ...

    1cfe69b