Security
Security at QOREN
Security is not a page on this site — it is a set of controls the platform enforces on every request. Here is what each one does, and how you can check it.
Controls that are enforced, not promised
Every control below is implemented in the request path, not described in a policy document.
The security posture, in numbers
Questions a security reviewer asks first
Where are credentials stored?
Server-side, in an encrypted vault, scoped per tenant and per connector. They are never sent to the browser and never appear in an API response.
Can one tenant see another tenant’s data?
No. Tenant isolation is enforced on every request, before the query runs. A request without the right tenant context is rejected rather than filtered.
Can an agent change my systems without approval?
No. A write is prepared, queued and shown to a named person with the risk level attached. Nothing is executed until it is approved, and the approval is audited.
What happens to the data you send to a model?
Prompts are screened for injection attempts before they are sent, and responses are screened before they are returned. The public copilot on this website uses public product facts only and never sees visitor or tenant data.
How do I verify the audit trail is complete?
Every action writes one entry with the actor, the tenant, the timestamp and the outcome. The log is append-only, and entries can be exported for an external review.
Get the security pack
The architecture note, the control list and the audit format — sent as one document you can hand to your reviewer.