csaf-poc / csaf_webview

Web app (module) to display a CSAF 2 document and to browse CSAF 2 ROLIE feeds. ⚠️ The web demo is often not allowed to access servers:
https://csaf-poc.github.io/csaf_webview/
1 stars 3 forks source link

Add table to simplify result #8

Closed tschmidtb51 closed 8 months ago

tschmidtb51 commented 11 months ago

CSAF files can be quite complex. We should introduce as much help to the reader as we can. A table should be created to show the results:

Example given for 6 products and 3 vulnerabilities:

Product Total result CVE-2021-44228 CVE-2021-45046 CVE-2021-45105
Product A :heavy_check_mark: :heavy_check_mark: :heavy_check_mark: :heavy_check_mark:
Product B :warning: :heavy_check_mark: :warning: :warning:
Product C :heavy_multiplication_x: :heavy_multiplication_x: :heavy_multiplication_x: :heavy_multiplication_x:
Product D :heavy_multiplication_x: :heavy_check_mark: :heavy_multiplication_x: :warning:
Product E :heavy_minus_sign: :heavy_minus_sign: :heavy_minus_sign: :heavy_minus_sign:
Product F :heavy_minus_sign: :heavy_minus_sign: :green_heart: :heavy_minus_sign: :heavy_minus_sign: :green_heart:

Symbols could be: :heavy_check_mark: fixed :warning: under_investigation :heavy_multiplication_x: known affected :heavy_minus_sign: not affected :green_heart: recommended

ThomasJunk commented 10 months ago

A rough draft in the development branch is in this component.

The parser has to be made more robust and there are several questions we should adress.

The result looks like this: overview

More at a later point in time.

ThomasJunk commented 10 months ago

We talked (in our status meeting ) about having the functionality of clickable links for CVEs and Products which link to the detailed view related parts of the document tree.

tschmidtb51 commented 10 months ago

We talked (in our status meeting ) about having the functionality of clickable links for CVEs and Products which link to the detailed view related parts of the document tree.

Just to clarify: "document tree" => "CSAF document"

tschmidtb51 commented 10 months ago

The total result is computed as a kind of maximum function where:

not affected < fixed < under_investigation < affected
tschmidtb51 commented 10 months ago

The recommended computation needs to be discussed:

  1. Min function: If it is set anywhere => set in total (this might be counter-intuitive)
  2. Sum function: The number of times it is set => number of times it apprears in total
  3. Max function: Only set if status applies for all vulnerabilities (might never be set)

Thoughts?

ThomasJunk commented 10 months ago

From a naive point of view I would expect solution (3) max - reading "fully recommended".

ThomasJunk commented 8 months ago

I close here because the general requiremet is met. Speficis should be part of specific issues.