Tenant boundary
Row-Level Security
PostgreSQL row-level security with check conditions supports tenant-data separation at the database layer.
Security and trust
Security is the foundation, not the fine print.
CentaurNexus combines role-based access, tenant isolation, encrypted data paths, audit context and read-back. Production operation for EU customers runs entirely on STACKIT in the EU.
Controlled actions
Audit and Read-back
Keep actor, time, tenant, target, status and the confirmed target-system result together for supported workflows.
Access protection
Zero Trust Self-Protection
Protect access to the administration layer using tenant Zero Trust signals and a check separated from the login identity.
Regional operation
Data Control
State region, data paths, tenant isolation and operating responsibility in the agreed service scope.
Defense in depth
Independent controls protect identity, application and data.
Security controls are designed to limit impact and keep operational responsibility explicit.
Protect privileged sessions
Use hardened sessions, CSRF protection, refresh-token rotation and optional MFA for privileged access.
Treat every input as untrusted
Apply server-side validation, authenticated routes, security headers, rate limits and structured logging.
Keep tenants separated
Use database-enforced row-level security and encryption for sensitive fields.
Confirm supported writes
Show a write as successful only after actual target-system effect and read-back.
Technical evidence
Make operational boundaries and results inspectable.
CentaurNexus provides technical operating and change evidence. Suitability for a specific regulatory or contractual purpose must be assessed in that context.
Identify access and responsibility
Connect roles, permissions and configured approvals to a tenant and responsible actor.
Execute under the tenant policy
Apply the concrete approval and authorization path for the selected workflow.
Verify the outcome
Record status, target-system effect, read-back, source, data age and coverage where applicable.
Zero Trust Self-Protection
The administration layer protects itself with tenant signals.
The patent-pending CentaurNexus method uses Zero Trust signals from the customer tenant and a check separated from the login identity to protect privileged access. NexusAgent adds endpoint signals required for supported CentaurNexus workflows to the ZDX context.
- Access checks remain separate from the login identity.
- The configured risk state can restrict privileged access.
- An indeterminate state fails closed for the protected path.
Security principles
Controls support the daily workflow.
Role-based access and explicit operating boundaries make safer actions practical.
Security is a process
Controls remain useful when they are visible in the workflow.
Role limits, tenant boundaries, source context and verified outcomes support decisions without hiding responsibility.
Next step
Discuss security requirements
Bring one recurring operating situation. We will map the roles, required context and appropriate demo path.
Frequently asked questions
Security and data control questions.
How are customer tenants separated?
CentaurNexus uses role-based access and PostgreSQL row-level security with check conditions to support tenant-data separation.
What does read-back establish?
Read-back confirms the observed target-system state after a supported write. The action is not shown as successful before that confirmation.
Does CentaurNexus claim regulatory conformity?
No blanket conformity or certification claim is made. Technical evidence must be assessed against the concrete regulatory and contractual context.
Where does EU production operation run?
For EU customers, production operation runs entirely on STACKIT in the EU. Further data paths are described in the applicable contractual and privacy documents.
Further reading