Security, privacy and tenant isolation
Protect encrypted SIP secrets, one-time routes, guest tokens, origins, rate limits, event signatures, private switch services and tenant boundaries.
xConnect
Open guide →GuideUnderstand tenant isolation
Route calls and directory data only within the authorised platform/customer context.
Open guide →GuideUnderstand deny-by-default routing
Reject targets that cannot be resolved and authorised.
Open guide →GuideProtect encrypted SIP secrets
Keep stored SIP passwords encrypted and never display them in management tables.
Open guide →GuideProtect browser session credentials
Return short-lived credentials only to the authenticated active browser session.
Open guide →GuideProtect website access tokens
Store guest access tokens as SHA-256 hashes and compare them in constant time.
Open guide →GuideExpire guest sessions
Disable expired guest extensions and record expiry audit evidence.
Open guide →GuideValidate exact widget origins
Normalise and compare each origin against the current account allow-list.
Open guide →GuideRequire HTTPS origins
Allow secure origins in production and limit HTTP to localhost development addresses.
Open guide →GuideApply website rate limits
Restrict repeated widget requests per IP/account window.
Open guide →GuideApply website concurrency limits
Restrict the number of active guest sessions/calls.
Open guide →GuideProtect switch events
Use timestamp, nonce, HMAC signature and replay records.
Open guide →GuideProtect the event secret file
Store it outside public web roots with restricted permissions.
Open guide →GuideProtect one-time call routes
Consume the route token at the voice switch and reject reuse.
Open guide →GuideReview xConnect audit logs
Use audit records for allocation, widget sessions, event/configuration and security-relevant actions.
Open guide →GuideUnderstand API security headers
Use no-store, nosniff and referrer restrictions on JSON/public responses.
Open guide →GuideProtect call and presence metadata
Apply retention/minimisation to participant IDs, IP, user-agent, timing, failure and presence evidence.
Open guide →GuideProtect private voice services
Expose only approved WSS/RTP paths and keep SIP/event-control interfaces private.
Open guide →GuideKeep external calling disabled
Maintain the server-side external_calling_enabled lock at 0.
Open guide →