Separate identity boundaries
Customer users and Nebverse platform operators use different principals, sessions and cookies.
Security and governance
Sensitive people operations need visible boundaries.
Nebverse security begins with tenant and identity separation, then carries through sessions, mutations, audit evidence, deployment health and recovery.
Implemented today
Specific product controls, described without inflated certification claims.
This page distinguishes implemented behaviour from customer configuration and future assurance work.
Tenant-scoped data
Customer identities derive company and role scope on the server rather than accepting it from the browser.
Credential protection
Passwords use bounded scrypt hashing, failed-attempt lockout and forced change for initial platform access.
Session controls
Secure HttpOnly cookies, idle and absolute expiry, version invalidation and revocation protect active access.
Audited platform changes
Company lifecycle, plans, modules and enquiry updates require reasons and idempotency keys.
Production readiness
Web readiness checks both the API and the database dependency used by login and sessions.
Three operating boundaries
Every actor enters through the right door.
Customer workspace
Employees, managers and administrators operate only inside their authenticated tenant and assigned permissions.
- Tenant and role from session
- Location and reporting scope
- Tenant-specific branding and modules
Platform control plane
Nebverse superadmins use separate credentials to manage company lifecycle, entitlements, enquiries and audit.
- Distinct cookie and session table
- Forced initial password change
- No silent tenant impersonation
Operator workflows
Deployment, migration and maintenance run through protected VM and CLI workflows outside browser permissions.
- Environment-gated operations
- Backups before release
- Isolated Docker project
Control catalogue
From request to retained evidence.
AreaNebverse controlCustomer responsibility
AuthenticationHashed credentials, lockout, protected cookies and session expiryMaintain authorised users and secure endpoints
AuthorisationServer-derived tenant, role and relationship scopeDesign least-privilege roles and review access
Sensitive mutationsOrigin protection, validation, idempotency and auditApprove policies and provide meaningful reasons
Data qualityBounded imports, validation and tenant-safe keysClean source data and sign off control totals
Business continuityDocker health checks, database backups and restore rehearsalAgree retention, recovery targets and escalation
ComplianceConfigurable India-first workflows and evidenceValidate laws, filings and professional advice
Shared responsibility
Software controls support governance; they do not replace it.
Each organisation remains responsible for policy accuracy, lawful processing, administrator access, statutory interpretation and approved integrations. Nebverse implementation makes those decisions explicit and testable.
Read the multi-tenant security guideSecurity questions
Clear answers, no invented proof.
Does Nebverse claim a security certification?
No certification is claimed on this page. Any future assurance will be published with its verified scope and date.
Can a customer administrator become platform superadmin?
No. Platform identities are separate from customer users and tenant role assignments.
Can platform operators silently impersonate employees?
No silent impersonation is provided. Any future support access must be explicit, time-bound and audited.
What happens when a company is suspended?
The tenant lifecycle is changed, its session version is incremented and active tenant sessions are revoked.
Are backups enough on their own?
No. Backup jobs must be accompanied by artifact checks and restore rehearsal evidence.
Bring your control requirements
Review security in the context of your real roles and data.
Use the walkthrough to examine tenant separation, approval ownership, sensitive reports and release responsibilities.