Skip to content

Security

Security & compliance

Voice infrastructure touches every customer conversation. Miuda is built so the secure path is the default — at the network edge, in the call path and in the console.

Transport

Encryption in transit

TLS for SIP and HTTPS/WSS, SRTP for media — DTLS-SRTP on WebRTC legs and automatic SDES on SIP legs. No plaintext media unless a carrier cannot encrypt.

Edge

Edge protection

Deny-by-default ACLs, per-trunk IP allowlists, a built-in scanner User-Agent blacklist and frequency limits that absorb registration floods before authentication.

Access

Access control

Role-based permissions for console users, scoped API tokens for automation and per-customer access scoping on the wholesale side — enforced at the API, not just the UI.

Evidence

Audit & evidence

Call records with leg timelines and per-call media evidence, optional recording, SipFlow signaling capture and access logs.

Resilience

Resilient by design

Memory-safe Rust core, clustered session registry, drain-then-exit upgrades and circuit breakers that isolate bad routes instead of cascading.

Deployment

Deploy your way

On-premise, in your VPC or air-gapped. Recordings, CDRs and signaling stay in storage you control and are never sent to Miuda.

Data & privacy

Your data, your boundary

Data residency
Media, CDRs and captures live in your database and object storage (S3 / Azure / GCS or on-prem). You choose the region.
GDPR posture
Analytics on this website are consent-gated; in-product data is yours to retain or delete under your policy.
Calls to Miuda
Two small requests go to miuda.ai: license verification on commerce builds, and a daily update check that reports the version, uptime, call and extension counts and a fingerprint of the license key. No call content, phone numbers or CDRs.
Retention control
Storage lifecycle rules and archives keep or purge evidence on your schedule.
Backups
Config in Git, database snapshots, recordings mirrored to object storage.
YOUR NETWORKon-prem · VPC · air-gappedSIP trunksTLS · SRTPWebRTCDTLS-SRTPPhonesSIP over TLSPBXcoreDatabaseCDRs · configObject storagerecordingsSipFlowsignaling capturesLicense + update check: no call content or CDRsMiudamiuda.ai✓

Hardening baseline

The first 48 hours

The checklist we recommend for every public deployment. Details in Hardening a public PBX.

01

ACL deny-by-default

Allow internal ranges and carrier egress; deny everything else.

02

Scanner blacklist

The built-in User-Agent blacklist rejects SipVicious-class tools at the door.

03

Frequency limits

Rate-limit registration and INVITE floods; watch the block list for intrusion signals.

04

Per-trunk trust

Pin each carrier to its egress IPs; use challenge-response where registration is needed.

05

Encryption everywhere

TLS on SIP and console, SRTP for media, topology hiding at the border.

06

Least-privilege access

Role-based console accounts, scoped API tokens, registration closed after bootstrap.

Responsible disclosure

Found a vulnerability? Email security@miuda.ai with reproduction steps. We acknowledge reports within two business days and credit researchers who ask.

Security review for your deployment?

We’ll walk your team through the hardening baseline, deployment options and data boundary.