1 Rookie
•
2 Posts
•
8 Points
0
158
April 3rd, 2026 01:54
Data Refresh Latency in Open Vulnerability API: Is there a 30-day lag?
Hi ,
I am currently evaluating the Dell Security Vulnerability API to automate our internal vulnerability management workflow. Our goal is to fetch the latest Dell Security Advisories (DSA) as soon as they are published.
However, I've come across some discussions suggesting that there might be a significant delay—potentially up to 30 days (one month)—between the time a DSA is posted on the official Dell Support website and when it becomes available via the /all or /advisory-list API endpoints.
I would like to ask the following to the experts or anyone using this API in production:
Sync Frequency: Has anyone measured the actual latency for new DSAs to appear in the API? Is the "one-month lag" a known limitation or just an occasional synchronization issue?
Use Case Suitability: Is this API intended for real-time security monitoring, or is it designed more for historical auditing/reporting?
Best Practices: If the API does have a delay, what is the recommended way to programmatically fetch "day-zero" or "day-one" advisory data? (Since RSS feeds seem to be deprecated/limited).
Any insights or official documentation regarding the data refresh cycle would be greatly appreciated.
Best regards,
FORCIA
1 Rookie
•
2 Posts
•
8 Points
0
May 13th, 2026 07:42
After further testing, we were unable to consistently reproduce the issue where the API appeared to return advisories only up to approximately 30 days prior to the latest reports. In subsequent verification, we were also able to successfully retrieve reports from within the past 30 days via the API.
Based on the additional investigation, we believe the behavior may have been influenced by the specific test conditions or parameters used during our earlier verification.
However, we also confirmed that there are still some cases where advisory information cannot be retrieved as expected via the API. For example, some recently updated advisories could not be retrieved even when specifying the DSA number directly.
We would therefore like to continue our internal investigation regarding advisory retrieval behavior through the API. That said, since the originally reported issue could not be definitively reproduced, please consider this forum thread closed.
Thank you for your support and assistance.
(edited)