Security for data actions


Note: This article applies to the Adobe, Microsoft Dynamics 365, Salesforce, web services, and Zendesk data actions integrations.
Feature deprecation: For more information, see Deprecation: TLS 1.1 protocol.

The data actions service sends an SSL certificate to your web service to prove the identity of the data actions service. You can increase the security between the two services in increasingly granular ways.

Note: These methods to increase security might not apply to all types of data actions integrations.
  • IP address filtering allows only PureCloud to access your web service.

    Whitelist IP addresses that are used for outbound data action traffic to your web service. For more information, see Domains and IP Addresses > IP addresses in Ports and services to configure on your company firewall.

  • mTLS authentication verifies that only the data actions service is connecting with your web service.

    Configure your web service to trust client certificates from the PureCloud data actions certificate authority (CA). For more information, see mTLS support for data actions.

  • OrgId headers ensures that other PureCloud customers cannot access your web service.

    Verify that the inin-organization-id header matches your PureCloud organization ID. For more information, see View organization settings.

  • Authentication confirms your identity.

    Use an authentication system to allow PureCloud to access to your system without exposing your credentials. For more information, see Credential types for the web services data actions integration.

For more information about the integrations, see About the Adobe data actions integration, About the Microsoft Dynamics 365 data actions integration, About the Salesforce data actions integration, About the web services data actions integration, and About the Zendesk data actions integration.