Your workspace, your database
Each organization on Orisynx gets its own workspace, and each workspace is backed by its own database. Your audits, findings and evidence are never stored alongside another organization’s records.
Audit data,kept apart
Audit records hold the weak points of your organization. This is how Orisynx is built to protect them.
Activity logToday
- CLOSEA. Mensah closed REM-0087Effectiveness: Effective · 14:02
- ROLEK. Lewis changed R. Patel’s role to AuditorUsers · 11:47
- FILEJ. Okafor attached supplier-evaluations-2026.xlsxFND-0142 · 09:15
Access checked on the server
People get access through roles, and roles carry permissions. The interface hides what someone cannot do, but the server checks the permission again on every request, so hiding a button is never the only control.
Passwords and sessions
Passwords are stored as bcrypt hashes, never in plain text. New users join through an emailed invitation and set their own password. Sessions use signed tokens that expire.
Hardened at the edge
Every request is rate limited and every input is validated before it reaches the database. Errors are logged in full for us and returned in general terms to the browser, so internal details are not exposed. Schema introspection is switched off in production.
A record of every change
The activity log records who created, changed or closed what, and when. It is the same trail an auditor would ask for, kept for your own system.
Files kept in object storage
Documents and evidence are uploaded to dedicated object storage, kept apart from the application database, and linked to the record they support.
Have a security questionnaire?
Send it to support@orisynx.com and we will answer it as part of your evaluation.
See it with your own audits
Bring an audit you have already run. We will walk it through Orisynx with you, from the plan to the last closed corrective action.