Security
Security at Elevated Context
Elevated Context is a product of Cognispace, LLC, and is designed to a production, multi-tenant security bar. This page summarizes how we protect data. For the company-wide program, see the Cognispace Security & Trust Center, which governs where the two differ.
Confidentiality, integrity, availability
The service is built so that data is seen only by those authorized to see it, decisions are recorded faithfully, and the plane stays available to make those decisions. Elevated Context is itself an access-control layer, so these principles are the product, not an afterthought.
Tenant isolation
Every query is bound, on the server, to the tenant it belongs to. A caller never selects their own tenant, and a null or ambiguous tenant fails closed. One customer’s data is never returned in another customer’s context.
Identity & access
- Verified identity. Identity is established through Google and verified by the service. A service account authenticates a workload, never a person.
- Least privilege. Each action and each result release is authorized independently. Being allowed to read data does not authorize an action over it.
- Role-based access. Permissions follow the roles your organization assigns, enforced on every request.
Data protection
Connections are encrypted in transit. Secrets are held in a managed secret store, never in code or logs. Session and credential material is referenced by shape, never exposed in audit artifacts.
Monitoring & auditability
Governed decisions trace to persisted records: who requested what, and whether context was released, withheld, transformed, denied, or failed closed. A stored record is evidence and provenance — it is never a standing grant for a future request.
Responsible disclosure
If you believe you’ve found a security issue, email [email protected]. Please give us a reasonable window to investigate and respond before any public disclosure.