Skip to main content

Security and deployment

What your security teamasks first.

Who signs in, which models are called, where the record lives, what an agent may reach, and what you receive before anything runs at scale.

  1. 01

    Sign in through your identity provider, and no other

    People sign in with the identity you already run; seats and roles follow from it.

  2. 02

    Every model call through one gateway, including the model provider your enterprise already contracts

    Which models each seat may use, and with what data, is a rule like any other; the gateway applies it.

  3. 03

    Hosted in your cloud region; the record stays in your tenancy

    Who asked, which rule applied, who decided and what was done: an audit trail you can ask, kept for as long as your policy says.

  4. 04

    What an agent may reach is granted per seat, with an end date, and one switch stops every agent

    Access is a request, decided by the person who holds it; an agent reaches nothing its seat does not allow.

  5. 05

    What your security team receives in a pilot

    The seat definitions, the access profile, the decision record and the gateway log.

Hosting model, retention default, subprocessors, the app’s permissions and certification status: answered in writing in the pilot’s first week.

A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.

The person who prepares a decision is never the person who takes it: the agent prepares, the owner decides, and the record shows both.

An access request, as it runs

Access is a request,decided by the person who holds it.

At Corvane, a fictional company, a new coding agent asked for production access. The CISO declined it for the first quarter, and the record says why and when it is reviewed.

Access request

Production read access for an agent

rulesSEC-R03: production access for agents needs the CISO

Declined · decision record DEC-2214

No production access for the first quarter; review date set

Sign in through

  • Google Workspace
  • Keycloak
  • Microsoft Entra ID
  • Okta

Model providers, through one gateway

  • Anthropic
  • Amazon Bedrock
  • Azure OpenAI
  • Google Gemini
  • OpenAI
  • Models you host

Start with howyou run today.

Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.