Sign-in through your identity provider
People sign in with your organisation's single sign-on (OpenID Connect). Sessions are kept on the server, end after 30 minutes idle by default, and can be ended by an administrator at once.
Security
How we protect your data
Your data centres' records say a lot about your business. Divjyot ONE is built to keep them separate, to control who sees them, and to record every change.
In the application, wherever it runs
Roles, per environment, enforced by the database
Roles come from your identity provider's groups and can be limited to one environment. The database's row-level security enforces them, so a fault in a screen can't show someone records they may not see.
An audit trail nobody can change
Every change is recorded with who made it and when. The database refuses to change or delete those records, for administrators too.
Access reviews and blocking
Administrators see everyone's access, sessions and API tokens on one page, download it for review, and block someone at once, with a reason recorded.
Secrets stay secret
Integration credentials can be set but never read back, and are stored encrypted. Costs are hidden from roles without cost access. Request forgery is blocked on every change.
Privacy tools
An inventory of the personal data the application holds, retention limits for email, and a way to erase a person's name and email address when they ask.
When we host it: Divjyot ONE Cloud
Every hosted customer gets an instance of their own. Nothing in one customer's instance can reach another's.
Separate, from the application down
Each customer has their own application, database, storage, encryption key, secrets and web address. On Standard, the database server is shared, but each customer's database can be opened only with that customer's own logins. On Dedicated, the database server and machines are the customer's alone.
Encrypted in transit and at rest
Connections are encrypted with TLS, including to the database, whose certificate is checked. Databases, files and backups are encrypted at rest. Attachments and Dedicated databases use a key of the customer's own.
Sign-in with an authenticator app
Customers without their own identity provider get accounts we host, with an authenticator app required by default, a password policy, and protection against guessing. They can move to their own provider later, keeping their accounts.
Backups that can't be deleted early
Each customer's database is backed up nightly and kept for 35 days, locked against deletion for that time. One customer's data can be restored without touching anyone else's.
Two people for risky actions
Deleting a customer, or restoring their data from a backup, needs a second administrator's approval, and the system refuses the requester's own. Every action our staff take is logged.
A locked-down platform
Customers' pods run under Kubernetes' strictest pod security standard, with network policies that deny by default. The service that manages instances can change customers' namespaces and nothing else.
How we build it
- Every change runs thousands of automated tests, including access-control and isolation tests, and browser tests with accessibility checks.
- Container images are scanned for vulnerabilities, and a critical finding stops a release.
- The tools our builds use are pinned to exact versions.
What we don't claim
Divjyot ONE isn't certified to SOC 2 or ISO 27001. When we host it, we run it on Amazon Web Services, which holds those certifications for its own infrastructure; ask us for the details you need for your own assessment.
Found a problem?
If you think you've found a security issue in Divjyot ONE or this website, please tell us or email support@statistyxsit.com. Please don't test against other customers' instances.