Your responsibilities when using Key Protect
Learn about the management responsibilities and terms and conditions that you have when you use IBM® Key Protect for IBM Cloud®.
For a high-level view of the service types in IBM Cloud and the breakdown of responsibilities between the customer and IBM for each type, see Shared responsibilities for IBM Cloud offerings.
Review the following sections for the specific responsibilities for you and for IBM when you use IBM Key Protect. For the overall terms of use, see IBM Cloud Terms and Notices.
This document also includes comparative information about Key Protect Standard and Key Protect Dedicated to help you understand the differences in shared responsibilities between the two service tiers.
Incident and operations management
You and IBM share responsibilities for the set up and maintenance of your IBM Key Protect instance for your application workloads.
You are responsible for incident and operations management of your application data.
Key Protect Standard responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Availability | Provide high availability capabilities, such as IBM-owned infrastructure in multizone regions, to meet local access and low latency requirements for each supported region. | Use the list of available regions to plan for and create new instances of the service. |
| Monitoring | Provide integration with select third-party partnership technologies, such as IBM Cloud Logs. | Use the provided tools to review instance logs and activities. |
| Incidents | Provide notifications for planned maintenance, security bulletins, or unplanned outages. | Set preferences to receive emails about platform notifications, and monitor the IBM Cloud status page for general announcements. |
Key Protect Dedicated responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Monitoring | Provide integration with select third-party partnership technologies, such as IBM Cloud Activity Tracker. | Use the provided tools to review instance logs and activities. |
| Incidents | Provide notifications for planned maintenance, security bulletins, or unplanned outages. | Set preferences to receive emails about platform notifications, and monitor the IBM Cloud status page for general announcements. |
| Firmware updates | Provide firmware updates for multiple crypto units in a sequential manner with no impact to running workloads. | Perform tasks as usual. |
| Connecting to third-party cloud | Provide error messages when access to the third-party keystores does not work. | Contact affected third-party cloud service provider to resolve access or connection issues. |
Change management
You and IBM share responsibilities for keeping IBM Key Protect service components at the latest version.
You are responsible for change management of your application data.
Key Protect Standard responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Provide major, minor, and patch version updates for Key Protect interfaces. | Use the API, CLI, or console tools to apply the provided updates, including version updates, new features, and security patches. |
Key Protect Dedicated responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Provide major, minor, and patch version updates for Key Protect Dedicated interfaces. | Use the API, CLI, or console tools to perform updated functions. |
Identity and access management
You and IBM share responsibilities for controlling access to your IBM Key Protect instances and resources.
You are responsible for identity and access management to your application data.
Key Protect Standard responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Provide the ability to restrict access to resources. | Depending on your needs, restrict access to resources and service functionality by using Cloud IAM access policies. For more information, see Managing user access. |
Key Protect Dedicated responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| User management | IBM does not have access to your resources but provides you with the ability to restrict user access to resources. | Depending on your needs, restrict access to resources and service functionality by using Cloud IAM access policies. For more information, see Managing user access. |
| Service and key policies | IBM does not have access to your resources but provides you with the ability to set service and key policies. | Depending on your needs, set service and key policies to control access to your Key Protect Dedicated instance and keys. For more information, see Managing user access. |
| Connecting to third-party cloud | Provide error messages when access to the third-party keystores does not work. | Make sure the connection information and access credentials for the third-party cloud service provider are always up to date in your Key Protect Dedicated instance. |
Security and regulation compliance
IBM is responsible for the security and compliance of IBM Key Protect.
You are responsible for the security and compliance of your application data.
Key Protect Standard responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Maintain controls that are commensurate to various industry compliance standards, such as SOC and ISO. | Set up and maintain security and regulation compliance for your apps and data. For example, you can enable extra security settings to meet your compliance needs by choosing how and when to import, wrap, rotate, rewrap, and delete keys. |
Key Protect Dedicated responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Maintain controls that are commensurate to various industry compliance standards, such as SOC and ISO. | Set up and maintain security and regulation compliance for your apps and data. For example, you can enable extra security settings to meet your compliance needs by choosing how and when to import, wrap, rotate, rewrap, and delete keys. |
| Cryptographic operations | IBM never touches your master key. | Keep your master key secure. Perform cryptographic operations by using your workstation or smart cards. |
| Master key backups | IBM never touches your master key. | Back up your master key in a regular basis to your smart card or workstation. |
| Smart cards and smart card readers | IBM never touches your smart cards and smart card readers. | Store smart cards, the associated PINs, and the smart card readers in secure vaults to prevent unauthorized access. |
| Key part files | IBM never touches your key part files. | Secure key part files in the directory associated with CLOUDTKEFILES in an approved file storage vault and securely store the respective passwords. |
Disaster recovery
IBM is responsible for the recovery of IBM Key Protect components in case of disaster.
You are responsible for the recovery of the workloads that run Key Protect and your application data.
Key Protect Standard responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Applications | Continuously back up keys in the region that the service operates in, and automatically recover and restart service components after any disaster event. | None. IBM and Key Protect are fully responsible for managing disaster recovery. |
| Virtual Private Endpoints (VPE) | VPE does not support automatically switching to backup during failover at this time. | VPE settings, specifically the Internet Protocol (IP) address, need to be manually updated during disaster recovery procedures. |
| Private Endpoint (PE) | PE will not support allowed IP settings during disaster recovery at this time, but an announcement on this topic will be made soon. | PE settings, specifically the Internet Protocol (IP) address, need to be manually updated during disaster recovery procedures. |
Key Protect Dedicated responsibilities
| Task | IBM Responsibilities | Your Responsibilities |
|---|---|---|
| Instance backups | Continuously perform in-region and cross-region backups of key resources and perform continuous testing of backups. | Back up your master key; validate the backups and restore data when needed. |
| Disaster recovery | When an in-region disaster occurs, automatically recover and restart service components. When a regional disaster that affects all available zones occurs, ensure that all data except the master key is replicated to another region. IBM will also make additional crypto units available in a different region and manage routing requests to the new crypto units. | When a regional disaster that affects all available zones occurs, load your master key to the new crypto units that IBM provisions in a different region for restoring data. You can also enable and initialize failover crypto units before a disaster occurs, which reduces the downtime. |
| Availability | Provide high availability capabilities, such as IBM-owned infrastructure in multizone regions, to meet local access and low latency requirements for each supported region. | Use the list of available regions to plan for and create new instances of the service. |