Trust · Security
Understand security before deployment
Review security information and discuss requirements for a Kurasa deployment.
What a security review usually covers
- Sign-in and authentication.
- Role permissions: who can see and change what.
- Where data is stored and who can access it.
- Backups and recovery.
- Monitoring and incident response.
- What happens to data when an agreement ends.
What this site does and does not claim
Kurasa does not list a security certification on this site. Ask for the documents available for your proposed deployment and confirm what each one covers, rather than assuming a particular certification or control.
How to ask
Describe the users, data types and workflows involved, and include your organisation’s review requirements. Public and multi-site customers can request documentation, and the team will confirm what is available for that scope.
Ask for the details that inform your decision
Discuss authentication, role permissions, backup arrangements, monitoring and incident-response requirements with the team. Confirm the documentation available for the proposed deployment rather than assuming a particular certification or control. Read privacy and governance information alongside the technical discussion, and use the procurement page for an institutional review conversation.