AI voice agent security by deployment

What each deployment carries, from encryption and tenancy to sign-in and audit. Single-tenant deployments add their own network, keys and threat detection.

The call plane reads these stores through a grant on a key in your own cloud account.

Controls by deployment

Control
ControlSharedDedicatedHybridYour account
TLS 1.2 or higher on every connectionIncludedIncludedIncludedIncluded
Database encrypted under a customer-managed keyIncludedIncludedIncludedIncluded
Key held in your own cloud accountNot includedOptionIncludedIncluded
One call per single-use processIncludedIncludedIncludedIncluded
A least-privilege role per serviceIncludedIncludedIncludedIncluded
Account-wide audit trail into a locked bucketIncludedIncludedYour trailYour trail
Own VPC, database and model quotaNot includedIncludedIncludedIncluded
Private subnets and an egress allow-listNot includedIncludedIncludedIncluded
Managed threat detectionNot includedIncludedYoursYours
Database failover in under 60 secondsNot includedIncludedIncludedIncluded
Single sign-on over SAML or OIDCNot includedIncludedIncludedIncluded
Telemetry kept in the accountNot includedIncludedIncludedIncluded
No standing access to call dataNot includedIncludedIncludedIncluded
Masking of card, TFN and Medicare numbersIncludedIncludedIncludedIncluded
Retention window with scheduled deletionIncludedIncludedIncludedIncluded
Append-only audit log of changesIncludedIncludedIncludedIncluded

Encryption keys

  • Database

    The database is encrypted at creation under a customer-managed key, and every backup copy carries its own key in Melbourne.

  • Stored secrets

    API keys for your agent tools are stored as ciphertext in the row that owns them. The encryption context names the workspace, table and row, so a ciphertext cannot be moved to another row.

  • Key custody

    In Hybrid and Your account deployments the key lives in your own cloud account, and in Dedicated it can, through a key grant. Revoking it makes the database, recordings and stored secrets unreadable.

Sign-in and access

  • Single sign-on

    Your team signs in through Entra ID, Okta or any identity provider that speaks SAML 2.0 or OIDC.

  • Roles

    Owners, admins and members, and members limited to the agents they work on.

  • Break-glass access

    Our engineers have no standing access to call data. They reach a deployment through a time-limited role logged in its audit trail, which you can disable in Hybrid and Your account deployments.

  • Service roles

    Each service has its own role, limited to the actions and resources it needs. No long-lived cloud access keys are stored anywhere.

Audit trail

  • Cloud audit trail

    Every cloud API call in our accounts is recorded by an organisation-wide trail into a write-locked bucket, in a separate account in Melbourne. In your account the trail is yours.

  • Platform audit log

    Billing, membership and configuration changes are written once to an append-only log, with the person who made each change.

Certifications

  • Cloud infrastructure

    IRAP PROTECTEDSydney and Melbourne

    Assessed services the call plane runs on

    • Containers
    • Database
    • Object storage
    • Key management
    • Queues
    • AI model
    • Load balancing

    This is our cloud provider's assessment of its own services, and it does not cover our platform.

  • Our platform

    • PCI DSS SAQ-ASelf-assessed
    • Privacy Act 1988 (Cth) + 13 APPsSelf-attested
    • Notifiable Data Breaches schemeCompliant
    • GDPR (Art 28 processor)Self-attested
    • SOC 2 Type IIAudit pending
    • ISO/IEC 27001:2022Audit pending
    • Essential Eight (ASD)Mapped
    • HIPAA · IRAP · APRA CPS 234Out of scope
    Detail for each framework

Security questionnaires

We answer security questionnaires in writing and take your team through the architecture on a call. Send yours to hello@verticalai.com.au.