Access control for data and agents

An agent sees what the person who runs it can see. Nothing more.

Row- and column-level Cedar policies, applied in real time on every query. Agents inherit the permissions of the user who starts them. Every access is logged with the reason it was allowed or denied.

The controls

Six answers for the security review.

01

Row and column policies

Access is written as Cedar policies at row and column level and applied in real time, on every query, for every caller.

02

Agents inherit the person

An agent runs with the permissions of the user who starts it. It cannot see a row that person could not see, whatever the prompt says.

03

Every access, with its reason

Each read is logged with the policy that allowed or denied it. A reviewer reads why, not just what.

04

Isolated per tenant

Customer data is physically separated per tenant. Only schemas and settings are gated in the application.

05

Models under policy

You choose the model providers. A policy decides who is allowed to change them.

06

Where it runs

Your cloud, ours, or on-prem, including air-gapped with scheduled updates. SSO through OpenID Connect.

One request

How a request is decided.

  1. Who is asking

    The person signs in through your OpenID Connect provider. An agent carries the identity of the user who started it.

  2. Which rows and columns

    Cedar policies decide which rows that identity can see and which columns it can read, at query time, below the model.

  3. The query runs

    Only within what the policy allows. No instruction in a prompt can widen it, because the model never holds the permission.

  4. The decision is logged

    Allow or deny, with the policy that made the call, for people and agents in one log.

Access logsample
06:47:12 shrink-watch for m.kim inventory_adjustments allow region = North, as m.kim
06:47:12 shrink-watch for m.kim payroll.hourly_rate deny column outside store-ops policy
06:48:03 availability for j.osei stock_levels (SAP) allow supply-chain role, all stores
06:52:40 r.patel models.provider deny only platform admins change models

The last line is a person, not an agent: changing the model provider is itself a policy decision.

Where data lives

Physically isolated per tenant, or never leaving your network.

In Ward’s cloud, customer data is physically separated per tenant; only schemas and settings are gated in the application. Or run Ward in your own cloud, or on-prem, including air-gapped with scheduled updates. Live databases are queried in place through the proxy on a read-only replica, so they are not copied at all.

For compliance status, sub-processors and the documents a reviewer will ask for, see the trust center and the evaluation packet.

Questions

What a security reviewer asks first.

With Cedar policies at row and column level, applied in real time on every query for every caller. A policy decides which rows a person can see and which columns they can read, and the same rule applies whether they ask in the console or through an agent.

Exactly what the person who started it can see. Agents run with that user's permissions, and policy is applied below the model, so no instruction in a prompt can widen it.

Yes. Each access is logged with the policy that allowed or denied it, so a reviewer can read why a request was allowed, not only that it was.

Yes. Customer data is physically isolated per tenant. Only schemas and settings are separated at the application layer.

You choose the model providers, and a policy controls who is allowed to change them. A user without that permission cannot switch models.

SSO through OpenID Connect providers. Keycloak is in use today, and adding another OpenID Connect provider is a short configuration task.

Your security review starts with a short list of questions.

Architecture, policy model, access log, isolation. On the table before you sign.

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3
What are your goals?
Step 2 of 3
About your operation
Step 3 of 3
Your contact info