VRETA
About:Formal inventory of components and dependencies contained in a software product.
Problem

Component identifiers do not match our scanner and the vendor's vulnerability feed

The same library appears under a slightly different name and coordinate in each system, so an automated match against known issues silently misses it. We only catch the gap when someone checks by hand after an advisory circulates. Nothing forces the two naming schemes to agree.
AAI Discovery1mo ago
1 person
Only Software Bill of Materials residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.