IBM Cloud Private platform considerations for GDPR readiness

Notice

This document is intended to help you in your preparations for GDPR readiness. It provides information about features of the IBM Cloud Private platform that you can configure, and aspects of the product's use, that you should consider to help your organization with GDPR readiness. This information is not an exhaustive list, due to the many ways that clients can choose and configure features, and the large variety of ways that the product can be used in itself and with third-party applications and systems.

Clients are responsible for ensuring their own compliance with various laws and regulations, including the European Union General Data Protection Regulation. Clients are solely responsible for obtaining advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulations that may affect the clients' business and any actions the clients may need to take to comply with such laws and regulations.

The products, services, and other capabilities described herein are not suitable for all client situations and may have restricted availability. IBM does not provide legal, accounting, or auditing advice or represent or warrant that its services or products will ensure that clients are in compliance with any law or regulation.

Table of Contents

GDPR

General Data Protection Regulation (GDPR) has been adopted by the European Union ("EU") and applies from May 25, 2018.

Why is GDPR important?

GDPR establishes a stronger data protection regulatory framework for processing of personal data of individuals. GDPR brings:

Read more about GDPR

Product Configuration – considerations for GDPR Readiness

The following sections describe aspects of data management within the IBM Cloud Private platform and provide information on capabilities to help clients with GDPR requirements.

Data Life Cycle

IBM Cloud Private is an application platform for developing and managing on-premises, containerized applications. It is an integrated environment for managing containers that includes the container orchestrator Kubernetes, a private image registry, a management console, and monitoring frameworks.

As such, the IBM Cloud Private platform deals primarily with technical data that is related to the configuration and management of the platform, some of which might be subject to GDPR. The IBM Cloud Private platform also deals with information about users who manage the platform. This data will be described throughout this document for the awareness of clients responsible for meeting GDPR requirements.

This data is persisted on the platform on local or remote file systems as configuration files or in databases. Applications that are developed to run on the IBM Cloud Private platform might deal with other forms of personal data subject to GDPR. The mechanisms that are used to protect and manage platform data are also available to applications that run on the platform. Additional mechanisms might be required to manage and protect personal data that is collected by applications run on the IBM Cloud Private platform.

To best understand the IBM Cloud Private platform and its data flows, you must understand how Kubernetes, Docker, and Helm work. These open source components are fundamental to the IBM Cloud Private platform. You use Kubernetes deployments to place instances of applications, which are built into Helm charts that reference Docker images. The Helm charts contain the details about your application, and the Docker images contain all the software packages that your applications need to run.

IBM Cloud Private includes a catalog of containerized software and services from IBM in the default IBM Cloud Private repository list. To view a list of all the IBM Cloud Private charts, see https://github.com/IBM/charts/tree/master/stable Opens in a new tab. For considerations regarding GDPR for the products in the catalog, consult the documentation for those products. Information on the available IBM Cloud Private bundles, which contain the core IBM Cloud Private platform and available entitled software, is available here IBM Cloud Private bundles. Some of the applications available in the catalog are open source software. It is the client’s responsibility to determine and implement any appropriate GDPR controls for open source software. Information on these packages is included in the catalog entry.

Documentation on IBM Cloud Private platform can be found in the IBM Cloud Private collection in IBM Knowledge Center.

What types of data flow through IBM Cloud Private platform

As a platform, IBM Cloud Private deals with several categories of technical data that could be considered as personal data, such as a default admin user ID and password, service user IDs and passwords, IP addresses, and Kubernetes node names. The IBM Cloud Private platform also deals with information about users who manage the platform. Applications that run on the platform might introduce other categories of personal data unknown to the platform.

Information on how this technical data is collected/created, stored, accessed, secured, logged, and deleted is described in later sections of this document.

Personal data used for online contact with IBM

IBM Cloud Private clients can submit online comments/feedback/requests to contact IBM about IBM Cloud Private subjects in a variety of ways, primarily:

Typically, only the client name and email address are used, to enable personal replies for the subject of the contact, and the use of personal data conforms to the IBM Online Privacy Statement Opens in a new tab.

Data Collection

The IBM Cloud Private platform does not collect sensitive personal data. It does create and manage technical data, such as a default admin user ID and password, service user IDs and passwords, IP addresses, and Kubernetes node names, which might be considered personal data. The IBM Cloud Private platform also deals with information about users who manage the platform. All such information is only accessible by the system administrator through a management console with role-based access control or by the system administrator though login to an IBM Cloud Private platform node.

Applications that run on the IBM Cloud Private platform might collect personal data.

When you assess the use of the IBM Cloud Private platform running containerized applications and your need to meet the requirements of GDPR, you must consider the types of personal data that are collected by the application and aspects of how that data is managed, such as:

This is not a definitive list of the types of data that are collected by the IBM Cloud Private platform. It is provided as an example for consideration. If you have any questions about the types of data, contact IBM.

Data storage

The IBM Cloud Private platform persists technical data that is related to configuration and management of the platform in stateful stores on local or remote file systems as configuration files or in databases. Consideration must be given to securing all data at rest. The IBM Cloud Private platform supports encryption of data at rest in stateful stores that use dm-crypt. For more information, see Encrypting volumes by using dm-crypt.

The following items highlight the areas where data is stored, which you might want to consider for GDPR.

Data access

IBM Cloud Private platform data can be accessed through the following defined set of product interfaces.

These interfaces are designed to allow you to make administrative changes to your IBM Cloud Private cluster. Administration access to IBM Cloud Private can be secured and involves three logical, ordered stages when a request is made: authentication, role-mapping, and authorization.

Authentication

The IBM Cloud Private platform authentication manager accepts user credentials from the management console and forwards the credentials to the backend OIDC provider, which validates the user credentials against the enterprise directory. The OIDC provider then returns an authentication cookie (auth-cookie) with the content of a JSON Web Token (JWT) to the authentication manager. The JWT token persists information such as the user ID and email address, in addition to group membership at the time of the authentication request. This authentication cookie is then sent back to the management console. The cookie is refreshed during the session. It is valid for 12 hours after you sign out of the management console or close your web browser.

For all subsequent authentication requests made from the management console, the front-end NGINX server decodes the available authentication cookie in the request and validates the request by calling the authentication manager.

The IBM Cloud Private platform CLI requires the user to provide credentials to log in.

The kubectl CLI also requires credentials to access the cluster. These credentials can be obtained from the management console and expire after 12 hours. Access through service accounts is supported.

Helm CLI access utilizes certificates to access the cluster.

Role Mapping

IBM Cloud Private platform supports role-based access control (RBAC). In the role mapping stage, the user name that is provided in the authentication stage is mapped to a user or group role. The roles are used when authorizing which administrative activities can be carried out by the authenticated user.

Authorization

IBM Cloud Private platform roles control access to cluster configuration actions, to catalog and Helm resources, and to Kubernetes resources. Several IAM (Identity and Access Management) roles are provided, including Cluster Administrator, Administrator, Operator, Editor, Viewer. A role is assigned to users or user groups when you add them to a team. Team access to resources can be controlled by name-space.

Pod Security

Pod security policies are used to set up cluster-level control over what a pod can do or what it can access. For more information, see

Data Processing

Users of IBM Cloud Private can control the way that technical data that is related to configuration and management is processed and secured through system configuration.

Role-based access control (RBAC) controls what data and functions can be accessed by users.

Pod security policies are used to set up cluster-level control over what a pod can do or what it can access.

Data-in-transit is protected by using TLS and IPSEC. HTTPS (TLS underlying) is used for secure data transfer between user client and back end services. Users can specify the root certificate to use during installation. All inter-node data traffic can be encrypted out of the box by using IPSEC without changing any applications.

Data-at-rest protection is supported by using dm-crypt to encrypt data.

Data retention periods for logging (ELK) and monitoring (Prometheus) are configurable and deletion of data is supported through provided APIs.

These same platform mechanisms that are used to manage and secure IBM Cloud Private platform technical data can be used to manage and secure personal data for user-developed or user-provided applications. Clients can develop their own capabilities to implement further controls.

For more information, see

Data Deletion

IBM Cloud Private platform provides commands, application programming interfaces (APIs), and user interface actions to delete data that is created or collected by the product. These functions enable users to delete technical data, such as service user IDs and passwords, IP addresses, Kubernetes node names, or any other platform configuration data, as well as information about users who manage the platform.

Areas of IBM Cloud Private platform to consider for support of data deletion:

Areas of IBM Cloud Private platform to consider for support of account data deletion:

Function to remove user ID and password data that is managed through an enterprise LDAP directory would be provided by the LDAP product used with IBM Cloud Private platform.

Personal data that is persisted by platform logging and monitoring consists of IP addresses of cluster components and some user names and user IDs. User-developed or user-provided applications might include other personal data in their use of logging and monitoring. The same mechanisms that are used for deletion of system logging or monitoring data can be used for application logging and monitoring data. Personal data that is collected by applications outside of these services will require application provided mechanisms to delete data. For more information, see

Data monitoring

Capability for Restricting Use of Personal Data

Using the facilities summarized in this document, IBM Cloud Private platform enables an end user to restrict usage of any technical data within the platform that is considered personal data.

Under GDPR, users have rights to access, modify, and restrict processing. Refer to other sections of this document to control the following:

Appendix - Data logged by IBM Cloud Private platform

As a platform, IBM Cloud Private deals with several categories of technical data that could be considered as personal data, such as a default admin user ID and password, service user IDs and passwords, IP addresses, and Kubernetes node names. IBM Cloud Private platform also deals with information about users who manage the platform. Applications that run on the platform might introduce other categories of personal data that are unknown to the platform.

This appendix includes details on data that is logged by the platform services.

IBM Cloud Private security

For more information, see:

IBM Cloud Private platform API

For more information, see

IBM Cloud Private monitoring

For more information, see:

IBM Cloud Private Kubernetes

Use caution when modifying Kubernetes cluster configuration or deleting cluster data.

For more information, see:

IBM Cloud Private Helm API

For more information, see Elasticsearch API.

IBM Cloud Private Service Broker

For more information, see: