Skip to content

Ideas for creating Compound Decision Tables when a Decision Table is too big or complex #1244

Description

@sei-vsarvepalli

Is your feature request related to a problem? Please describe.
No. Complex SSVC decision tables can become difficult to understand and explain, particularly when they use more than ~6 decision points. This creates a human-scale bottleneck when designing and communicating SSVC decisions.

Describe the solution you'd like

Build tooling to help evaluate and optimize SSVC decision tables. The tooling should identify opportunities to combine or decompose decisions into Compound Decision Tables, keeping individual tables simple enough for humans to understand while preserving the decision logic.

For examples, our partners VulDB has a decision table https://vuldb.com/kb/ssvc that uses 13 decision points (Features or Attributes as mentioned there). These type of decision tables beyond (say with more than 6 or less decision points) makes them too complex and too difficult to explain. It is recommended that when such decision tables are built, there are tools to evaluate if some decisions can be combined to create "Compound Decision Tables" - basically the more complex decision table can be broken down and is kept to be not confusing for the Human Scale problem https://certcc.github.io/SSVC/topics/ssvc-human-scale-bottleneck/

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions