To ensure compliance with HIPAA, Zendesk requires specific security configurations for HIPAA-enabled accounts. These include secure agent authentication, SSL encryption, IP address restrictions, and API security measures.
For agent authentication, you can use either Zendesk's native support with high-security password settings and two-factor authentication (2FA) or an external Single Sign-On (SSO) solution with similar security standards. SSL encryption must be enabled at all times, and agent access should be restricted to specific IP addresses unless multi-factor authentication is used. Additionally, API access should follow best practices like using OAuth 2.0 for granular security and ensuring API tokens are managed securely. For more details, visit theoriginal Zendesk help article.
For HIPAA compliance, Zendesk Guide and Gather services must be configured to prevent the inclusion of PHI in public articles or comments. Subscribers should ensure that no PHI is included in articles or attachments. It's recommended to disable…
When using Zendesk messaging with HIPAA accounts, certain security measures must be implemented to protect ePHI. Subscribers should avoid enabling social media messaging integrations unless they ensure no ePHI is present or have a BAA with the…
For HIPAA compliance, Zendesk Sunshine Conversations should be configured to manage ePHI securely and restrict third-party integrations. Subscribers should avoid enabling third-party channel integrations unless they ensure no ePHI is present or…
To use Zendesk Chat with HIPAA accounts, specific security configurations must be followed to protect ePHI. Agents' access to Zendesk Chat should be limited and authenticated via Zendesk Support. Email piping and chat transcript emails should be…