Security

Security

Vertical AI checks every request to agent data against workspace membership, on the web app and the MCP server. Secret variable values are stored encrypted.

Workspace membership decides every read and write of agent data, on the web application and on the MCP server. Secret variable values are stored encrypted, and API keys are stored as hashes. Where each part of a call runs is covered on Data residency.

Platform boundaries

Vertical AI is multi-tenant. The tenancy unit is the workspace, and every agent belongs to exactly one workspace.

How isolation is enforced

Every request to agent data is checked against the same two questions:

  • Is the requesting user a member of the workspace that owns this agent?
  • If their membership is limited to chosen agents, is this agent one of them?

Writes also need a role that can edit: owner, admin, editor or member. The same check applies on every access path: the web application, the MCP server, and any service that acts as a user.

Our platform staff are the one exception: they can reach a workspace they are not a member of.

Continuous verification

Automated tests of the isolation rules run on every pull request, and a pull request that changes the database also runs them against a fresh copy of it. Every pull request is scanned for leaked secrets. Code and dependency security scans run every night.

Authentication

MethodStatus
Email and passwordAvailable
Google sign-inAvailable
Time-based one-time password, second factorAvailable, per user
Recovery codes for second-factor lossAvailable, stored hashed

Access control

Workspace membership carries a role. Roles govern what the application permits (inviting members, managing billing, changing workspace settings). To limit someone to particular agents, limit their membership to those agents.

See Access control for roles, agent-limited members and the audit log.

Credentials

Secret variable values are stored encrypted. API keys and publishable keys are stored as hashes.

See Credential handling for the dialog that stores a secret without the AI model reading it.

Call recordings

Recordings are held in private storage. Only someone who can open the call can play it, and a workspace setting decides which roles can download it.

Operators get a recording through a signed link made at the moment of the request. In the app the link lasts an hour or less; through the API or the MCP server it lasts up to a day.

While a call is running

The AI model is told to treat what a caller says as information, not instructions, and outbound requests are constrained to prevent agents reaching internal infrastructure.

See Runtime safeguards.

Reporting a vulnerability

Send details to security@verticalai.com.au. We will acknowledge receipt and keep you informed while we investigate.

On this page