You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
match(product_tree, asset_database_connection, matching_threshold)
- resp. -
match(product_tree, sbom_database_connection, matching_threshold)
Output
for each product_id in product_tree:
a list of tuples (asset_id, probability, matching_reason)
- resp -
for each product_id in product_tree:
a list of tuples (sbom_component_id, probability, matching_reason)
Matching
Algorithm - priorities:
Match based on product_identification_helper. Different ones might imply a different confidence: An sbom_url or serial_number might be stronger than a cpe.
Match based on the categorized strings (value of name) in the branches (e. g. vendor, product_name, product_version).
Match on the human-readable full_product_name_t/name.
The algorithm may end after it created a sufficient result - it can, but does not have to go through all steps.
Edit: The experience shows, we also want to provide a matching_threshold that allows us to fine tune what the lowest probability is that we get results for (a matching_threshold of 0 would give for each asset/SBOM component the probability that it matched with (which might be 0 if those are completely different)) and the matching_reason which provides insights into the confidence and helps debugging (a direct match on a serial number would potentially better than a match on the human-readable string).
The text was updated successfully, but these errors were encountered:
We need to document the matching algorithm interface for CSAF asset matching systems and CSAF SBOM matching systems. Both work similar:
Input
Output
Matching
Algorithm - priorities:
product_identification_helper
. Different ones might imply a different confidence: Ansbom_url
orserial_number
might be stronger than acpe
.name
) in thebranches
(e. g.vendor
,product_name
,product_version
).full_product_name_t/name
.The algorithm may end after it created a sufficient result - it can, but does not have to go through all steps.
Edit: The experience shows, we also want to provide a
matching_threshold
that allows us to fine tune what the lowest probability is that we get results for (amatching_threshold
of0
would give for each asset/SBOM component the probability that it matched with (which might be 0 if those are completely different)) and thematching_reason
which provides insights into the confidence and helps debugging (a direct match on a serial number would potentially better than a match on the human-readable string).The text was updated successfully, but these errors were encountered: