Secure Communication for Mobile and Field Workforces
SANKET gives field officers, inspectors, responders and mobile teams encrypted communication built for the field: hardware-backed keys on every phone, an encrypted outbox for poor coverage, calls tuned for 3G and 4G links, and administrator controls that contain a lost or seized device in minutes.
Encrypted outbox for poor coverage
Lost mode and remote wipe for field devices
Hardware-backed keys on every phone
Calls tuned for constrained networks
The shift
Before SANKET vs. After SANKET
Before - current state risks
Phones lost, seized or replaced in the field, with no way to cut them off
Unpredictable networks, from strong 4G to intermittent coverage
Personal devices and consumer apps carrying operational information
Encrypted outbox for text, attachments and voice notes when coverage drops
After - with SANKET
Voice and video calls tuned for 3G, 4G and constrained links, including over HTTPS port 443
Device approval, lost mode, locate and server-confirmed remote wipe
MDM managed configuration for app passcode, lock timeout and biometrics on iOS and Android
Built for this
The architecture behind the solution
On the device, SANKET keeps its database in SQLCipher and its file cache under AES-256-GCM, with keys protected by the phone's secure hardware, so a lost phone does not become a lost conversation history.
Server-Blind Architecture
Field security is device security. Each approved device holds hardware-backed keys and its own client certificate, administrators can revoke it instantly, and root and jailbreak indicators are detected and reported, with enforcement configurable by policy.
Signal Protocol via libsignal
Built on Signal's independently audited libsignal, with post-quantum PQXDH key agreement and the Double Ratchet with SPQR, so every message has a fresh key.
Administrator Control
Administrators control identities, groups, devices, policies and retention, with FIDO2 security keys protecting the console itself.
Sovereign Deployment
Field teams typically run on Sanket.Work with iOS and Android apps. Classified field operations use Sanket.Enterprise for the same capabilities on an isolated installation.
The result
What organisations achieve
Contain lost or stolen field devices before they expose communication
Keep field teams connected across unpredictable networks
Enforce device policy across a distributed mobile fleet
Evaluation guide
Questions every buyer should ask
Can administrators lock, locate and wipe lost field devices?
Are keys on the phone protected by secure hardware?
Does the app hold messages safely when coverage drops?
Do calls work on constrained and restrictive networks?
Does the platform support our MDM?
Is local data encrypted at rest?
FAQ
Frequently asked questions
What happens if a field device is lost?
Administrators can revoke the device, place it in lost mode, locate it or wipe it remotely with server confirmation. Local data is encrypted and the keys are protected by the phone's secure hardware.
How does SANKET handle poor coverage?
Messages composed offline are held in an encrypted outbox and sent when the connection returns, and calls adapt automatically to constrained 3G and 4G links.
Does SANKET work with our MDM?
Yes. SANKET supports managed app configuration on iOS and Android, which can require an app passcode, shorten the lock timeout, control biometrics and pin the expected installation.
Is SANKET safe on public Wi-Fi?
Yes. Content is end-to-end encrypted, transport uses AES-256-GCM-only TLS, and the apps pin the installation's certificate, so an attacker on the network sees only encrypted traffic.
Ready to solve this with SANKET?
Talk to the Tosh Defence team. We start with your threat model and deployment constraints - not a product pitch.