Security
How your data is kept separate
Test evidence and defect records describe how an organization actually works. The isolation below is enforced by PostgreSQL itself, not only by application code.
- Tenant isolation enforced by the database
- Every customer-owned table carries an organization id and has PostgreSQL row-level security enabled and forced. The application connects as a role that cannot bypass it, and each request runs inside a transaction pinned to one organization. A query that forgets its tenant filter returns nothing rather than someone else’s data.
- Isolation is tested adversarially
- The test suite builds two organizations and has the second attack the first with its identifiers, reading records by stolen primary key, planting rows, cancelling jobs, resolving object keys and fetching files. Knowing another tenant’s identifier is worth nothing.
- Passwords and sessions
- Passwords are hashed with scrypt. Session cookies are opaque and random; only their digest is stored, so a database copy does not yield a usable session. Sign-in is rate limited and accounts lock after repeated failures.
- An audit trail the application cannot rewrite
- Audit events and defect history are append-only: the application role holds INSERT and SELECT and nothing else, enforced by database privileges rather than by convention.
- Credentials are referenced, never stored
- SAP tenant credentials are held in a secret provider. SaviQora stores only a reference and resolves it at the moment of use. Credentials never enter the database, a log line, a test case, a screenshot or a report.
- Security controls are respected, not worked around
- Automation does not bypass single sign-on, multi-factor authentication or CAPTCHA. If one is presented, the run fails and says so.
- Production is protected by default
- Automation refuses to run against a tenant flagged as production unless an authorised override is configured, and write actions are refused unless the execution profile permits them.
- Evidence is served, not exposed
- Screenshots and attachments have no public URL. They are served only to an authenticated member of the owning organization, and the object store is asked for them under that organization’s own prefix.
What we do not claim
Stated here rather than left for you to discover during procurement.
- Formal certification
- SaviQora holds no SOC 2, ISO 27001 or comparable certification. If you need one, say so. It is a roadmap question, not something we will imply we have.
- Independent penetration test
- None has been commissioned yet. The security properties above are implemented and tested by us.
- Single sign-on
- SSO is designed and included in the Business tier, but is not yet implemented. It is not available today at any price.
- Published uptime commitment
- No service level agreement is offered, because nothing has been measured over a meaningful period.
Questions from your security team?
Send them to contact@saviqora.com. Specific questions get specific answers, including where the answer is “not yet”.