Data in transit
TLS 1.3 as the intended control for every connection between unit and platform.
Security and assurance
In regulated and critical sectors, security decides whether you can buy at all. We treat it as a design requirement, and we are explicit about what is in place, what is planned and what still needs independent verification.
Controls
TLS 1.3 as the intended control for every connection between unit and platform.
AES-256 or equivalent, with documented key management and any exceptions stated.
Hardware identity per unit, role-based access and multi-factor authentication where appropriate.
Events and administrative actions logged, with agreed retention, export and review.
A controlled update process for firmware and software, backed by vulnerability management.
Data minimisation, a DPIA template and clearly defined processing roles. No patient data unless explicitly contracted.
Threat model, penetration test, gap analysis and independent assessment before broader roll-out.
Sector frameworks
Formal use in regulated settings requires agreed validation and contractual roles. Until that work is done, we say “supports” or “preparing for”, never “compliant”.
We would rather show you the evidence than a badge.
For risk owners
Architecture, controls, current status and the roadmap, in one document for your security, privacy and quality teams.