Sanket.Chat
The Problem

Strengthen Cyber Resilience: NIS2, DORA and CER

NIS2, DORA and CER expect critical entities and financial institutions to keep communicating securely through a cyber incident. SANKET provides a pre-deployed, end-to-end encrypted out-of-band channel, independent of primary systems and built for high availability, designed to support these resilience obligations.

The SANKET Answer

Independent out-of-band encrypted channel

High availability with second-site recovery

Hash-chained audit with SIEM export

Pre-deployed and exercised before incidents

See It In Action

The shift

Before SANKET vs. After SANKET

Before - current state risks

Regulators expect tested alternative communication arrangements, not plans made mid-crisis

Primary email, identity and collaboration systems are often the first to fail

Incident discussions can be visible to an attacker inside primary systems

Designed to support DORA Articles 11 and 12 and NIS2 Article 21 with an independent encrypted channel

After - with SANKET

High-availability profile with an asynchronous second site for disaster recovery

Hash-chained audit log, exportable to your SIEM over TLS-protected syslog

Calls and messaging that keep working over HTTPS port 443 on restrictive networks

Built for this

The architecture behind the solution

Resilience is evidenced, not asserted. SANKET's hash-chained audit log records security and administrative events by Sanket ID, never message content, and exports to your SIEM to support your supervisory evidence.

Server-Blind Architecture

A resilience channel must not share infrastructure, identity or dependency with what it backs up. SANKET runs as its own installation with end-to-end encryption, its own identities and certificate authority, and signed releases with automatic rollback.

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

Sanket.Work provides a dedicated hosted channel in any region on any cloud. Sanket.Enterprise provides maximum isolation on-premise or air-gapped, with a high-availability profile and a second site.

The result

What organisations achieve

Support DORA and NIS2 alternative communication expectations with an encrypted, tested channel

Evidence resilience with audit records exported to your SIEM

Keep incident communication out of reach of attackers in primary systems

Evaluation guide

Questions every buyer should ask

Is the channel independent of primary email, identity and SaaS?

Is it deployed and exercised before incidents?

Does it offer high availability with second-site recovery?

Can audit evidence be exported to our SIEM?

Is incident communication end-to-end encrypted?

Does it support our DORA, NIS2 and CER obligations?

FAQ

Frequently asked questions

How does SANKET support DORA Articles 11 and 12?

DORA expects alternative communication arrangements for ICT disruptions and regular testing of continuity plans. SANKET provides a pre-deployed, encrypted out-of-band channel that can be exercised as part of that testing.

How does SANKET support NIS2 Article 21?

NIS2 expects incident handling capabilities, including secure communication. SANKET provides an end-to-end encrypted channel independent of primary infrastructure for incident coordination.

Is SANKET highly available?

SANKET offers a multi-host high-availability profile with an asynchronous second site, designed for a recovery point of five minutes and a recovery time of one hour, and each disaster-recovery drill records its measured figures.

How often should the out-of-band channel be exercised?

We recommend regular communication exercises so that every key person is enrolled and confident before an incident, with the results recorded for your continuity evidence.

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.