Security
The answers to your security review, before you send it.
Below are the questions security teams ask us most, answered plainly. Where the answer is not yet, we say so.
Sixteen questions, answered.
13 of the 16 are a yes today. The rest are marked Not yet, with what we do instead.
- Sign-in
Is two-factor authentication available?
YesAuthenticator-app codes, with one-time recovery codes.
- Sign-in
Can admins make it mandatory?
YesOne workspace setting requires two-factor sign-in for everyone.
- Sign-in
Single sign-on?
YesSign in with Google. Password and email magic link can each be switched off.
- Sign-in
SAML single sign-on or SCIM provisioning?
Not yetUsers are invited or imported from CSV today.
- Sign-in
Can sign-ins be limited to our email domain?
YesOnly addresses at the trusted domain can sign in.
- Sessions
Are sessions kept out of reach of page scripts?
YesSessions live in httpOnly cookies, and admins set the timeout.
- Sessions
Can a user sign out other devices?
YesEach person sees their active sessions and can end any of them.
- Sessions
IP allowlisting?
Not yetAccess is controlled by sign-in method, domain and two-factor.
- Access
Is access role-based?
Yes229 permissions in 23 groups, combined into the roles you define.
- Access
Is access enforced on the server?
YesLists, reports and search filter records before they are sent.
- Data
Is data encrypted in transit?
YesAll traffic runs over HTTPS.
- Data
Are sensitive fields encrypted at rest?
YesPrivate employee fields and integration tokens use AES-256-GCM.
- Data
Is customer data kept separate?
YesEvery record carries its organisation's ID, and queries filter by it.
- Data
Can we export our data?
YesCore records export to CSV at any time.
- Audit
Is there an audit log?
YesEvery create, update and delete, with who, their role and when. It exports to CSV.
- Compliance
SOC 2 or ISO 27001?
Not yetWe'll name a certification here, with its report date, once we hold one.
In more detail.
Sensitive employee data
Pay and private details have a second lock. Seeing another person's pay or private documents takes a permission and a PIN check, even for Super Admins.
- Short-lived access
- A correct PIN opens access for a short time, then it closes again.
- Lockout
- Wrong PINs are logged like wrong passwords, and repeated failures lock the PIN.
Integrations
Connections go through each provider's consent screen. Kora never sees Microsoft, Google, Slack or Zoom passwords.
- Tokens encrypted
- Access tokens are stored with AES-256-GCM.
- Disconnect deletes them
- Kora deletes stored tokens on disconnect, and also revokes Slack and Zoom access with the provider.
Contract terms are in the Data Processing Agreement and the Service Level Agreement.
Have a security review coming up?
Send us your questionnaire. We'll answer it against how Kora is built, and say where the answer is not yet.
