Skip to content

Hardware Roles and Implementation Status

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

Cyberdeck Home ยท Portable Wireless Field Workflow ยท Device & Platform References ยท Architecture ยท Workflow

The roles below are derived from the documented design of a separate PNWC private prototype. A listed device does not mean that a physical unit was verified, flashed, integrated or tested.

Hardware Design Matrix

Component Reference Role Publication/Validation State
Windows 11 mini PC (exact model unspecified) or supported Linux host Local operator UI and guided steps Private prototype feature; no UI code in this public edition
GL.iNet travel router Upstream connectivity/repeater/WISP Manual design; model/firmware/site mode must be established
MikroTik RouterOS router Routed policy and segmented interfaces Manual design; verify hardware, RouterOS features and port maps
ZimaBoard and attached storage Proposed encrypted local evidence vault Vault encryption, backup and restore not proven by this edition
ZimaBlade and Raspberry Pi Optional local or offline sensors Manual export/collector roadmap; no autonomous field agents shipped here
Kismet, Snort, Wazuh, nzyme (software) Monitoring and independent detection evidence External products; no guaranteed packet visibility or integrated deployment
Flipper Zero, WiFi Pineapple, M5StickC Plus2 with Bruce, and ESP32 Marauder Optional supervised wireless/field inventory; setup, exports and evidence procedure Manual operation and reviewed exports only; no automatic device control, firmware interchangeability or completed hardware tests
Separate office/VPS sensor Real outside-in origin Planned, not integrated here

Hardware identification: Confirm the specific board, interface and firmware before applying instructions from a linked manufacturer. The ZimaBlade-to-ZimaBoard SE product update concerns newer configurations; earlier ZimaBlade owners should use their original specifications. These hyperlinks do not imply functional integrations.

Portable Wireless Device Qualification

The new wireless field-device runbook documents Flipper/Marauder companion roles, standalone Marauder, Bruce on M5StickC Plus2, and Pineapple Mark VII/Pager. Every device has its own firmware, controller, collection mode, export location and stop action. See Q15โ€“Q18 before any real deployment; nothing in the public release asserts those tests passed.

Capability Boundaries

Capability Private Prototype Documentation Public Edition
Local operator dashboard Implemented as localhost prototype Not included
Case records, guided questions, bounded one-IP Nmap Implemented privately with safety restrictions Not included
Device export ingestion and draft reports Manual/partial private implementation Documentation and example schema only
Device firmware/approval previews Planning UI, not device drivers Conceptual reference only
Offsite runner, automatic live hardware collection Planned / partially prototyped Not included
Signature provider validation and production evidence vault Not yet qualified end-to-end Not included
Read-only offline SHA-256 manifest of preexisting files Public helper implemented here Included

Public Expansion Status

The public edition also supplies offline manifest verification, a build runbook, an acceptance matrix, qualification/report templates and a private implementation roadmap. These additions qualify no physical equipment and do not update independently unverified private prototype status.

No Implicit Claims

Passing Python tests verifies only that the local manifest helper behaves as tested. It does not qualify a Wi-Fi chipset, hardware adapter, RouterOS configuration, customer scope, e-signature, IDS deployment, offsite runner or production security assessment.

Release Checklist ยท Lab Monitoring Visibility.


๐Ÿ“„ Source: Cyberdeck/docs/HARDWARE_AND_STATUS.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to PNWC Cyberdeck

Clone this wiki locally