Inside FDIE

Inspect the evidence in context.

Real product captures from example analyses of older firmware. They show the review workflow and its limitations; they are not independent validation of a vulnerability or an endorsement by the device manufacturer.

See the workspace behind FDIE

FDIE security overview dashboard with fleet summary cards, an assessment-history chart by framework and a finding-severity breakdown. — Historical demo workspace with older firmware samples. Displayed totals mix finding types and may include repeated occurrences; they are not a validated count of unique vulnerabilities. Count definitions, severity and grade labels still need reconciliation. This capture illustrates the workspace, not a verified security outcome.

Historical demo workspace with older firmware samples. Displayed totals mix finding types and may include repeated occurrences; they are not a validated count of unique vulnerabilities. Count definitions, severity and grade labels still need reconciliation. This capture illustrates the workspace, not a verified security outcome.

View the original capture for context ↗

Keep firmware and coverage in view

FDIE firmware library showing six older firmware samples with partial and unassessed binary-analysis coverage. — Example library of older firmware releases. “Complete” refers to processing, while partial and unassessed coverage warnings remain visible. Grades and count semantics await reconciliation; zero recovered binaries or missing findings do not establish that a device is secure.

Example library of older firmware releases. “Complete” refers to processing, while partial and unassessed coverage warnings remain visible. Grades and count semantics await reconciliation; zero recovered binaries or missing findings do not establish that a device is secure.

View the original capture for context ↗

Follow a finding back to the file

BusyBox selected in the FDIE filesystem browser for an older DAP2360 release, with source location and associated findings. — Example analysis of an older firmware release. BusyBox is selected with its source location and associated findings. This capture illustrates the evidence browser; displayed findings are not independent vulnerability validation or a statement about current vendor products.

Example analysis of an older firmware release. BusyBox is selected with its source location and associated findings. This capture illustrates the evidence browser; displayed findings are not independent vulnerability validation or a statement about current vendor products.

Inspect a recorded runtime run

FDIE binary emulation run for an older DAP2330 firmware release, showing artifact and execution counts, per-artifact coverage and recorded runtime observations. — Example analysis of an older DAP2330 firmware release using per-binary emulation, not a full-device boot. Displayed execution counts and severity labels await reconciliation. Process and shell observations do not establish command injection or device exploitability; unobserved paths remain unassessed.

Example analysis of an older DAP2330 firmware release using per-binary emulation, not a full-device boot. Displayed execution counts and severity labels await reconciliation. Process and shell observations do not establish command injection or device exploitability; unobserved paths remain unassessed.

View the original capture for context ↗

Keep processing and coverage in view

FDIE analysis queue lists older firmware samples with partial and unassessed binary coverage warnings. — Example analyses of older firmware releases. Processing completion is separate from assessment coverage: partial and unassessed warnings remain visible. A completed job or zero findings does not establish that a product is secure.

Example analyses of older firmware releases. Processing completion is separate from assessment coverage: partial and unassessed warnings remain visible. A completed job or zero findings does not establish that a product is secure.

Inspect function comparisons and uncertainty

FDIE FunctionDiff for aparraymsg shows modified, renamed and provisional function matches with missing decompilation warnings. — Example comparison of older DAP2360 releases. Function comparisons include confirmed and provisional matches for analyst review. The capture includes 187 comparisons without decompiled code on one side; additions and removals marked unconfirmed are not established changes. Changed functions do not prove a vulnerability was fixed.

Example comparison of older DAP2360 releases. Function comparisons include confirmed and provisional matches for analyst review. The capture includes 187 comparisons without decompiled code on one side; additions and removals marked unconfirmed are not established changes. Changed functions do not prove a vulnerability was fixed.

Review coverage across frameworks

FDIE compliance overview with a fleet pass summary and six framework cards showing assessed coverage, pass, fail and manual-review counts and recorded grades. — Historical fleet assessment view of older firmware, showing six framework cards. Scores and grades await reconciliation; applicability depends on the product and jurisdiction. Coverage and manual-review counts remain visible. These are assessment outputs, not certification or a CRA conformity grade.

Historical fleet assessment view of older firmware, showing six framework cards. Scores and grades await reconciliation; applicability depends on the product and jurisdiction. Coverage and manual-review counts remain visible. These are assessment outputs, not certification or a CRA conformity grade.

View the original capture for context ↗

Follow a framework into its checks

FDIE ETSI EN 303 645 checklist for an OpenWrt 23.05.5 firmware image, with fleet score, firmware selection, coverage limits and credential-check outcomes. — ETSI EN 303 645 checklist for an OpenWrt 23.05.5 firmware image. The fleet-average header score and the selected firmware's raw pass rate use different scopes and are not directly comparable. Recorded pass/fail outcomes need supporting evidence and review; they do not establish product conformity.

ETSI EN 303 645 checklist for an OpenWrt 23.05.5 firmware image. The fleet-average header score and the selected firmware's raw pass rate use different scopes and are not directly comparable. Recorded pass/fail outcomes need supporting evidence and review; they do not establish product conformity.

Next step

Start with one product and two releases.

Review a sample comparison with us. Then scope a supported image pair, hosting requirements and the evidence your team needs to evaluate.

or explore pricing

21-day free trial on the full platform. No card, no automatic conversion.