Security
Built for data you cannot afford to leak
Qry runs in an installation of its own, signs its users in through your identity provider and checks every query against your permissions. This page says how — and where the limits are.
The path of a question
Five steps between a question and an answer
01
Who asks
Signed in through your identity provider. Identity comes from the session, never from the prompt.
02
The query
Qry writes the SQL for the engine, with the definitions your team set as skills.
03
The grants
Every table the query names is checked against this person's grants, datasource to table.
04
The rules
Row filters from attribute policies are applied before anything runs.
05
The answer
The engine runs it with a read-only account. The answer shows the SQL — and flags any figure the data does not back.
Your installation
- Each organisation has its own installation and its own database — run by IXEN or inside your Google Cloud, Microsoft Azure or Kubernetes.
- Models are reached through your own Anthropic, Azure AI Foundry, Google Vertex AI or OpenAI account, or an endpoint you host.
- Database credentials are stored encrypted, and the key that protects them must be set by whoever installs Qry — there is no default.
Identity
- Single sign-on with Microsoft Entra ID (secret or certificate) or Google.
- Directory groups mapped to Qry groups, refreshed at every sign-in.
- Personal tokens for messaging and the command line, each tied to exactly one person.
Permissions
- Access is granted, never assumed: per datasource, catalog, schema and table, to users and groups.
- Attribute-based policies add row filters, applied to every query that touches a tagged table.
- SAP HANA can be granted per module.
- Search, the catalog and metadata fail closed: what cannot be verified is not shown.
The query path
- Every query a person starts — in a conversation, a notebook, a dashboard or an API call — is checked before it runs.
- The model never chooses whose permissions it uses: identity comes from the session, not the prompt.
- Scheduled work runs with the scheduling person's current permissions, and stops when they lose access.
Software supply chain
- Containers run as an unprivileged user with every Linux capability dropped.
- Every release is scanned, and a critical vulnerability with a fix blocks it.
- Images are signed with Sigstore Cosign and ship with an SPDX software bill of materials.
The company
IXEN, the company that builds and runs Qry, is certified at the HIGH category of Spain's National Security Framework (Esquema Nacional de Seguridad, ENS).
What we ask of you
- Connect Qry with read-only database accounts. Qry checks the tables a query names against your grants; the account's own rights are the ceiling.
- Keep your installation current — upgrades carry security fixes, and the operator CLI checks one before it starts.
Questions for your security review? Write to us and we will answer them in writing.
See it on your own data
We'll set up Qry against a dataset you choose and walk you through it — one hour, no slides.