Know what changed. Keep the review context.
Compare analysed releases of the same product. Follow identified components, review dependency changes and decide which earlier vulnerability assessments can carry forward.
Last updated September 16, 2026
FDIE's cross-version analysis layer.
It connects identified components, findings and assessment history across analysed firmware versions. Review what changed alongside the context and coverage of the earlier analysis.
Quick definition
Delta Intelligence combines release comparisons, component lineage, dependency-impact analysis and triage suggestions using recorded evidence and deterministic rules.
A release review needs more than an inventory. Your team needs to understand changed components, newly relevant vulnerability candidates and the reasoning behind earlier decisions.
Start with two releases of one product. Use the comparison to decide what needs fresh investigation and which previous records remain useful. Changed component versions, analysis coverage or vulnerability intelligence may require reassessment.
Follow component history across analysed releases.
Review identified version and licence changes alongside vulnerability matches at each step. A finding that stops matching needs review: removal, changed identification or updated intelligence can affect the result without proving a fix.
- Identify the component and its recorded aliases.
- Inspect established import and dependency relationships.
- Review known consumers and unresolved mappings separately.
A missing mapping does not establish zero impact.
Review where a shared component is used.
Use known component and binary relationships to investigate the impact of a version, licence or vulnerability change across analysed images. The result depends on available dependency evidence; it is not a complete inventory of deployed devices or proof of exploitability.
Carry forward decisions with their reasoning.
When a matching CVE appears in a later analysed release of the same product, FDIE offers the earlier triage status and note as a suggestion. Review the prior release, current component version and available evidence before applying it. Nothing is re-applied automatically; a matching identifier does not establish that the earlier decision still holds.
Inspect function changes during patch review.
FunctionDiff compares two releases function by function and highlights changes for patch review. It helps distinguish a version-string change from a change inside the binary.
Changed bytes identify a patch candidate. Confirming a fix requires evidence tied to the vulnerability and review; a rebuilt function alone does not prove remediation.
Review the evidence behind the result.
Component lineage, blast-radius mappings and triage carry-forward use rules and recorded evidence; report narratives are assembled from fixed templates over that evidence, never from a language model. Compare engine versions, vulnerability-feed freshness and analysis coverage alongside the firmware bytes when reviewing changes between assessments.
Reports separate observed evidence, inferred relationships and unassessed controls so reviewers can judge the support for each result.
See Delta Intelligence on your own firmware.
Review a sample comparison with us. Then scope a supported image pair, hosting requirements and the evidence your team needs to evaluate.
21-day free trial on the full platform. No card, no automatic conversion.