copyright | lastupdated | subcollection | ||
---|---|---|---|---|
|
2021-03-01 |
assistant |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:external: target="_blank" .external} {:deprecated: .deprecated} {:important: .important} {:note: .note} {:tip: .tip} {:pre: .pre} {:codeblock: .codeblock} {:screen: .screen} {:javascript: .ph data-hd-programlang='javascript'} {:java: .ph data-hd-programlang='java'} {:python: .ph data-hd-programlang='python'} {:swift: .ph data-hd-programlang='swift'}
{: #security}
Learn more about strategies that are available for you to use to ensure that your {{site.data.keyword.conversationshort}} data remains secure and protected in the cloud. {: shortdesc}
For more information about {{site.data.keyword.Bluemix_notm}} security, see Security architecture{: external}.
{: #security-byok}
This feature is available with Enterprise with Data Isolation plans that are hosted in Dallas or Washington, DC only. {: note}
When you integrate with {{site.data.keyword.keymanagementservicefull}}, you can encrypt {{site.data.keyword.conversationshort}} data in Enterprise with Data Isolation plan instances with encryption keys that you create or import.
For implementation details, see Protecting sensitive information in your {{site.data.keyword.watson}} service{: external}.
{: #security-byok-notes}
- Do not delete your key or your {{site.data.keyword.keymanagementserviceshort}} instance. The key is required to access your data and only you manage it. IBM cannot help you retrieve your data if you accidentally delete your key.
- You cannot delete the first {{site.data.keyword.conversationshort}} service instance that you create with your Enterprise with Data Isolation plan. The access policies for your Enterprise with Data Isolation instances are derived from the first instance that you add. In fact, each time you create an instance in this Enterprise with Data Isolation plan, you must set the Encrypted with a Key Protect root key option to Yes, and then specify the key protect instance details for this plan.
For existing customers, a new Enterprise with Data Isolation slot must be provisioned for you before you can use {{site.data.keyword.keymanagementserviceshort}}. (A Enterprise with Data Isolation slot is a collection of Kubernetes deployments of a {{site.data.keyword.conversationshort}} service.) Your data must be migrated to the newly provisioned slot. You also must create a new resource group and use it with your new Enterprise with Data Isolation instances.
{: #security-private-endpoints}
You can set up a private network for {{site.data.keyword.conversationshort}} instances that are part of a Plus or Enterprise service plan. Using a private network prevents data from being transferred over the public internet, and ensures greater data isolation.
This feature is available only to users of paid plans.
Private network endpoints support routing services over the {{site.data.keyword.cloud_notm}} private network instead of the public network. A private network endpoint provides a unique IP address that is accessible to you without a VPN connection.
For implementation details, see Public and private network endpoints{: external}.
{: #security-private-endpoint-notes}
- The integrations that are provided with the product require endpoints that are available on the public internet. Therefore, any built-in integrations you add to your assistant will have public endpoints. If you only want to connect to a client application or messaging channel over the private network, then you must build your own custom client application or channel integration.
- Before you can create a search skill, you must create a {{site.data.keyword.discoveryshort}} instance with a private network endpoint. The list of {{site.data.keyword.discoveryshort}} instances that are displayed for you to connect to includes only instances with private network endpoints. Normally, when you create a search skill and do not have any {{site.data.keyword.discoveryshort}} instances, a Lite plan instance is provisioned for you automatically. No instance is provisioned for you when you are using a private network. You must create a {{site.data.keyword.discoveryshort}} instance with a private network endpoint first.
{: #security-related}
- Information security: Describes strategies for complying with data protection regulations, such as GDPR and HIPAA.
- Security architecture{: external}: Describes the security components that are needed for secure cloud development, deployment, and operations.
- IBM Cloud compliance programs{: external}: Describes how to manage regulatory compliance and internal governance requirements with IBM Cloud services.