-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Copied from CVEProject/quality-workgroup#17.
As the Program continues to discuss ADP, and more specifically the "supplier CNA as ADP for upstream vulnerabilities" topic, we need to consider where this additional data is stored and how it is retrieved. For example, imagine a future with 10s or 100s of supplier CNA containers associated with a CVE ID (log4j, Heartbleed). We probably don't want a single JSON file or API response with 134 containers in it. Or do we? Today, I think there's a 4MB limit on CVE JSON file size.
Some incomplete ideas:
- Indeed, return the full JSON with all containers via API (or even GitHub file cache).
- Return CVE Record meta/index data, so user can then request specific parts/containers
- Return specified containers from one or more Records
- Could an ADP container instead/also be a pointer/URL to elsewhere? Still have container metadata, but effectively a URL to dereference the container content from somewhere else, perhaps constrained to a location/prefix declared by the supplier-CNA-as-ADP? "Elsewhere" could be the supplier CNA's domain or declared data location, or just an API call into CVE Services.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels