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.

  1. Sign-in

    Is two-factor authentication available?

    Yes

    Authenticator-app codes, with one-time recovery codes.

  2. Sign-in

    Can admins make it mandatory?

    Yes

    One workspace setting requires two-factor sign-in for everyone.

  3. Sign-in

    Single sign-on?

    Yes

    Sign in with Google. Password and email magic link can each be switched off.

  4. Sign-in

    SAML single sign-on or SCIM provisioning?

    Not yet

    Users are invited or imported from CSV today.

  5. Sign-in

    Can sign-ins be limited to our email domain?

    Yes

    Only addresses at the trusted domain can sign in.

  6. Sessions

    Are sessions kept out of reach of page scripts?

    Yes

    Sessions live in httpOnly cookies, and admins set the timeout.

  7. Sessions

    Can a user sign out other devices?

    Yes

    Each person sees their active sessions and can end any of them.

  8. Sessions

    IP allowlisting?

    Not yet

    Access is controlled by sign-in method, domain and two-factor.

  9. Access

    Is access role-based?

    Yes

    229 permissions in 23 groups, combined into the roles you define.

  10. Access

    Is access enforced on the server?

    Yes

    Lists, reports and search filter records before they are sent.

  11. Data

    Is data encrypted in transit?

    Yes

    All traffic runs over HTTPS.

  12. Data

    Are sensitive fields encrypted at rest?

    Yes

    Private employee fields and integration tokens use AES-256-GCM.

  13. Data

    Is customer data kept separate?

    Yes

    Every record carries its organisation's ID, and queries filter by it.

  14. Data

    Can we export our data?

    Yes

    Core records export to CSV at any time.

  15. Audit

    Is there an audit log?

    Yes

    Every create, update and delete, with who, their role and when. It exports to CSV.

  16. Compliance

    SOC 2 or ISO 27001?

    Not yet

    We'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.

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.