Security you can check, not just trust
Here is every control in the platform today, and, just as plainly, what your own team should add before a regulated rollout.
Sign-in and accounts
Separation and oversight
Network and calls
Integrations and internals
What your team adds for a regulated rollout
The platform gives you the controls above. Banks, hospitals and universities usually need these too. We can help with each of them.
Have a third party test your installation before go-live, and again after major changes.
Put recordings, voicemail, transcripts and the database on encrypted disks (for example an encrypted cloud volume).
TLS is available; for regulated sites, turn off plain UDP registration and require encrypted audio for desk phones and trunks.
If callers read out card numbers, plan for PCI DSS: pause recording during card details, or keep card entry out of the call.
Run a second server, take tested backups and agree recovery-time targets. Scaling out is supported; failover is your design.
If you need sign-in through your own directory, or roles beyond Admin and user, plan it as part of the rollout.
Decide how long recordings and transcripts are kept, and schedule their deletion to match your policy.
Check your regulator's rules on where call data may be stored and who may host it. Self-hosting makes this your choice.
Forward server and audit logs to your SIEM, and include the platform in your patching and incident response.
Put your security team's questions to us
We'll walk them through every control, and the rollout checklist, on a call.