One covers architecture and security posture, the other covers what a site needs before installation. Both are written for two different readers, so the sections below split them that way — the owner or operator on one side, the person doing technical review on the other.
You're deciding whether to buy it and where it goes. What matters is ownership, cost over time, what your staff have to do, and what happens to your data. Neither document asks you to understand the networking.
CTO, IT director, managed IT provider, network administrator, or whoever gets asked to sign off. Every control is stated as an implementation rather than a claim, and the egress specification is complete enough to write firewall rules from.
Open either one here, or take the PDF with you. No form and no email gate.
Deployment model, operating environment, network architecture, access control, privilege separation, data custody, maintenance posture and physical resilience. 8 pages.
Site conditions, scope of supply, placement, electrical and network requirements, internet service minimums, firewall and egress rules, ongoing responsibilities and the pre-installation checklist. 7 pages.
The component inventory isn't published. Everything else — architecture, security model, network requirements, egress specification, privilege model and data handling — is documented in full above, and specific questions are answered under a mutual non-disclosure agreement. Tell us the reviewing organisation and the scope of the assessment.