Inspect the evidence in context.

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.

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 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 DAP2360 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 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 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.

Historical fleet assessment view of older firmware, showing six framework cards. Scores, grades and “Mandatory” labels 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.

ETSI EN 303 645 checklist for an older DAP2360 release. The header and selected-firmware scores have unresolved scope and scoring labels and are not directly comparable. Recorded pass/fail outcomes need supporting evidence and review; they do not establish product conformity.