Continuous monitoring

Keep released firmware under review.

Vulnerability intelligence keeps changing after a release ships. FDIE refreshes its CVE, EPSS and KEV data daily and re-matches the components it has already identified, so a newly published vulnerability surfaces against the firmware you analysed earlier without uploading it again.

Continuous monitoring

Refresh the intelligence

NVD, EPSS and CISA KEV data are refreshed on a schedule, separately from firmware analysis, so a long refresh never delays an analysis.

  • Pick up newly published and newly modified CVEs.
  • Reflect changes in exploit probability and known-exploited status.
  • Separate a change in the data from a change in the firmware.

Continuous monitoring

Re-match analysed firmware

Components identified in earlier analyses are checked against the refreshed data, across the firmware library.

  • See which analysed releases contain a newly affected component.
  • Prioritise releases where a known-exploited vulnerability appears.
  • Keep relationships FDIE has not recorded visible as unknown rather than unaffected.

Continuous monitoring

Act on what changed

Bring the change into your vulnerability handling and the next release review.

  • Revisit earlier decisions that a new advisory could affect.
  • Schedule re-analysis of supported images when the evidence warrants it.
  • Record awareness times and decisions for disclosure obligations.

FDIE · next step

Keep released firmware under review.

Re-check analysed firmware against new CVE, EPSS and KEV data every day, and see which releases a new advisory reaches.

Paid at checkout. 14-day money-back guarantee on the first payment if three or fewer new images have been analysed.