The Zendesk Shared Responsibility Model outlines the division of security and privacy responsibilities between Zendesk and its subscribers. In essence, Zendesk is responsible for the security of the service itself, while subscribers are responsible…
Subscribers are responsible for managing access controls within their instances of Zendesk, including user provisioning, authentication methods, and session handling. Zendesk, on the other hand, manages access controls for the systems that underpin…
Zendesk is responsible for vetting and integrating reputable third parties into the service, ensuring proper security considerations are in place. Subscribers, however, must consider the security implications of any third-party integrations they…
Subscribers are responsible for the proper treatment of data within their instances, ensuring compliance with relevant laws and regulations. Zendesk protects service data at the infrastructure level, encrypts data in transit and at rest, and…
Subscribers are responsible for monitoring user activity within their instances, while Zendesk monitors the service itself, including privileged access, incoming traffic, and service uptime. This division ensures comprehensive oversight of security…
Subscribers are responsible for maintaining and patching their own systems and any custom code used with Zendesk services. Zendesk handles maintenance and patching within its architectural boundaries, including its infrastructure and proprietary…
Subscribers are responsible for managing security incidents within their instances, including breaches caused by insufficient access control or third-party integrations. Zendesk manages incidents related to the service itself, including…