Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-30643

[Scanner] Determine Date CVE Fixed for RHEL/VEX to support Policy criteria "Days since CVE FIX was published"

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.10.0
    • None
    • None
    • [Scanner] Determine Date CVE Fixed to support Policy criteria "Days since CVE FIX was published"
    • Product / Portfolio Work
    • S
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • In Progress
    • ROX-29708 - Policy Criteria for "Days since CVE Fix was available"
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      Implementation complete

      Show
      Implementation complete

      The scope of this effort for 4.10 for Scanner is:

      • Scanner V4 only
      • Fixed by date for RH vulns only - that date is provided in Advisories/VEX (other vuln sources the fixed date will be inferred in Central / not come from Scanner V4)

      The implementation will be added to ACS only (not ClairCore) - based on prior conversations to add this to ClairCore would be inefficient and require parsing VEX data.

      The existing ACS CSAF Enricher will be used, leveraging the "initial release date" of the Advisory as the fixed available date - which is already available to the CSAF enricher. 

      The Advisories, like VEX, contains multiple "vendor fix" dates that are per product, which were analyzed and every advisory's "initial release date" is identical to the vendor fix dates - which makes sense given the advisories are per product. In VEX the vendor_fix dates will differ per product complicating matching.

              dcaravel David Caravello
              vwilson@redhat.com Van Wilson
              Shubha Badve Shubha Badve
              ACS Scanner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: