Sub-100KB Images. Zero PHI. No Video Streams. The Lightest Security Footprint on Your Network.
Each sensor transmits a single encrypted sub-100KB JPEG per entry event. No video streams. No watchlist data resident on the device. No biometric templates stored on premises. No PHI created or transmitted. The security system that adds the least risk to your network while providing the most intelligence.
A single encrypted JPEG per entry. Three orders of magnitude less bandwidth than a single 4K camera stream
No video of patients in clinical settings. No identifiable imagery stored. The system does not create data subject to the HIPAA security rule
Intermittent still-image transmission only. No 24/7 streaming. No NVR. No VMS platform. No storage arrays
No watchlist data resident on the sensor. No biometric templates stored on premises. Nothing for a facility-intrusion to exfiltrate
Your Network Carries Enough Risk. Your Security System Should Not Add More.
Healthcare IT teams manage networks that carry PHI, connect medical devices, and support clinical operations. Every new system added to the network increases the attack surface, the data management burden, and the compliance scope. Traditional CCTV systems stream 4K video across the network, store terabytes of footage on local servers, and create PHI that must be secured under HIPAA. Safience was designed for environments where every byte matters and every data element carries compliance implications. Here is how the architecture closes each of the five gaps your security review will surface.
-
The Network Bandwidth Gap
A single 4K camera generates 12-25 Mbps of continuous data. A 100-camera deployment demands 1.2-2.5 Gbps of dedicated bandwidth — often requiring a parallel infrastructure build. Each Safience sensor transmits a single sub-100KB still image per entry event. The bandwidth difference is three orders of magnitude. Sensors run on your existing campus network with negligible impact on clinical traffic, EHR sessions, or medical device communications.
-
The Data Security Gap
CCTV footage is a high-value target — it contains identifiable imagery of patients, staff, and visitors and is increasingly named in healthcare ransomware demands. A breach of CCTV storage exposes thousands of individuals to disclosure and reidentification. Safience retains no footage. Non-match images are deleted at the edge in seconds. There is no data store to breach, no backup tier to encrypt, and no archive to leak.
-
The PHI Exposure Gap
Video of patients entering treatment areas, sitting in clinical waiting rooms, or being transported constitutes PHI under HIPAA. Every hour of CCTV in a clinical setting expands your protected-data footprint and your security rule obligations. Safience captures a single still image per entry event, processes it in under 5 seconds, and deletes non-matches. No video of patients in clinical settings is ever recorded.
-
The Integration Complexity Gap
Traditional VMS platforms require dedicated servers, storage arrays, software licenses, ONVIF integration work, and ongoing maintenance from a specialized team. Safience delivers alerts via REST API integration into your existing SOC, SIEM, or incident management system. No VMS platform. No server infrastructure. No storage management. No additional headcount in IT.
-
The Vendor Risk Gap
CCTV vendors retain and manage massive volumes of footage, often with cloud-based storage and analytics. Each vendor relationship introduces a data processing agreement, a breach notification obligation, and an attack surface. Safience retains nothing — there is no vendor data store to manage or breach, and non-match images never leave the edge.
-
The On-Premises Footprint Gap
Edge sensors deploy on existing PoE infrastructure with encrypted egress to the Safience cloud. There is no on-premises server, no local database, no rack to provision, and no UPS to plan around. When you decommission a sensor, the on-premises footprint goes to zero — there is no residual data store to inventory or destroy.
-
The HIPAA / HITRUST Alignment Gap
HITRUST and the HIPAA security rule reward minimizing the protected-data footprint and maximizing access controls. Safience minimizes the footprint by not creating PHI in the first place. Access controls are enforced by mandatory human verification at the Rapid Action Center — no autonomous machine-generated alerts hit your operations center.
- Single sub-100KB encrypted JPEG per entry event — no continuous video, no audio, no 24/7 streaming
- Encrypted egress over TLS from edge sensor to Safience cloud — no inbound connections to the sensor required
- No on-premises servers, NVRs, VMS platforms, or storage arrays — no rack space, no UPS planning, no capacity expansion
- No watchlist data resident on the sensor — list contents live in compartmented cloud infrastructure under X-LST
- No biometric templates stored on premises — nothing for a facility-intrusion or ransomware actor to exfiltrate
- REST API for alert delivery into existing SOC, SIEM, or incident management tooling — no proprietary VMS integration required
- Aligned with HIPAA security rule and HITRUST objectives by minimizing protected-data creation
- NIST OSAC TGD 0008 compliant — documentation available for security and privacy review
Technical Dimensions: Traditional CCTV vs. Safience Edge
| Technical Dimension | Traditional CCTV Infrastructure | Safience Edge Architecture |
|---|---|---|
| Bandwidth Per Device | 12-25 Mbps continuous (4K) | Sub-100KB per event (intermittent) |
| Data at Rest | Terabytes of stored footage | Zero — no footage stored |
| PHI Creation | Yes — video of patients in clinical areas | No — single still image, non-matches deleted |
| Server Infrastructure | Dedicated NVR/VMS servers | None — cloud-edge architecture |
| Storage Management | Ongoing capacity planning | None — no local storage required |
| Attack Surface | Cameras + NVR + VMS + storage | Sensor + encrypted API endpoint |
| Vendor Data Exposure | Vendor stores and manages footage | Vendor retains nothing; non-match images purged |
| Integration Method | VMS platform, ONVIF, proprietary SDKs | REST API for alert delivery |
| Device Management | Firmware updates, passwords, network segmentation | Managed edge devices; encrypted communications |
| HIPAA / HITRUST Posture | Expands protected-data footprint | Minimizes protected-data footprint by design |
The CISO Product Toolkit
Two products. One sensor. One encrypted egress path. Zero on-premises servers. Zero biometric templates. Zero PHI.
RTIS: Real-Time Threat Identification System
Edge-architected threat detection
Edge sensors capture a single sub-100KB JPEG per entry event. The image is transmitted encrypted to the cloud for matching against UMbRA. Non-matches deleted in seconds. No video stream. No biometric template on device. No PHI created.
Learn MoreRVIS: Real-Time Victim Identification System
Missing person detection on the same sensor
Runs on the same sensor and transmission path as RTIS. Zero additional bandwidth. Zero additional infrastructure. Missing person detection piggybacked on every threat scan — no new attack surface, no new vendor relationship, no new compliance scope.
Learn MoreX-LST: X-List Technology
Compartmented watchlists in the cloud
List contents live in compartmented cloud infrastructure — never on the sensor. Safience has no visibility into list contents during normal operations. Each match generates alerts visible only to authorized personnel via the same REST API pipeline as RTIS.
Learn MoreUMbRA: Law Enforcement Identity Database
Cloud-resident match index
The match index lives in Safience cloud infrastructure — not on your network and not on your sensors. 56M+ identities sourced exclusively from 18,000+ law enforcement agencies. Updated hourly with 50K+ new records daily. Complete chain of custody.
Learn MoreThe full technical architecture, end to end — from edge sensor to encrypted egress to human verification at the Rapid Action Center.
How It Works: Full Technical ArchitectureThe privacy architecture details your General Counsel will validate — no PHI, no biometric storage, NIST OSAC TGD 0008 alignment.
General Counsel: Privacy ComplianceThe operational view of the same deployment — how the CSO uses the alerts your team will route to their SOC.
CSO: Security OperationsThe Lightest Security Footprint. The Deepest Identity Intelligence.
Schedule a Technical Architecture Review. Our team will walk your security architects through the edge sensor design, the encrypted egress model, the cloud match infrastructure, the API integration pattern, and the documentation available for HIPAA, HITRUST, and NIST OSAC review. Come ready with your security questionnaire — we will too.