omnidesk
  • Ticket
    • Message
    • Using forms
    • Contact forms
  • Customers
    • General
    • API sync on contact
    • CSV import
    • API sync before contact
    • Customer lookup
  • Telephone
    • Callflow
    • Numbers
  • E-mail
  • Users
  • Live chat
    • Livechat chatbot and app integration (backend)
  • Facebook
  • Twitter
  • Survey
    • Push data
  • Statistics
    • Statistics API
  • Raw data - BI
  • Security policy
  • Hosting
  • API docs
    • General
    • Authentication
    • REST
  • API specification
    • Documentation for the Omnidesk API endpoints
    • Chat
    • Customer
    • Email
    • Form
    • Formfield
    • Message
    • Notification
    • Raw
    • Statisticsv2
    • Ticket
    • User
    • View
Powered by GitBook
On this page

Security policy

The security of our platform is of the utmost importance to us. We created a set of rules for our users and ourselves (the security policy) to make sure our platform is well protected.

Overall:

  • Omnidesk is ISO27001 certified

  • Our datacenter is ISO27001 certified

  • Pentested

  • OWASP proof

Security measures for end-users (agents, supervisors and administrators):

  • Login through two factor authentication (email or sms)

  • Password requirements

  • Strong hashing of passwords

  • HTTPS encryption on all endpoints

  • Input validation on all endpoints

  • Permission whitelist per group

  • IP whitelisting

Among security measures for Omnidesk staff are:

  • Lock computer/terminal after use

  • VOG declaration (Dutch certificate of good behaviour)

  • Only EU staff can access EU prod environment (GDPR)

  • Admin always works trough VPN

  • VPN login based on certificate

  • VPN login IP whitelisted

  • Physical locks for spaces with computers

  • Named accounts for server access

  • Centrally managed accounts through LDAP

  • Activity logs of users on servers

  • Always use password manager

  • Only administrator staff have access to application servers

  • Internal communication servers through private network

  • OS always within support terms (preferably LTS)

  • Auto install of important security updates

  • Strict firewall whitelisting

  • Explain-requirement when software runs as root

  • Code-review of new code

  • Servers provisioned through scripts which are also code-reviewed

PreviousRaw data - BINextHosting

Last updated 1 year ago