Chapter 20. Data privacy for Projects OpenStack is designed to support multi-tenancy between projects with different data requirements. A cloud operator will need to consider their applicable data privacy concerns and regulations. This chapter addresses aspects of data residency and disposal for OpenStack deployments. 20.1. Data residency The privacy and isolation of data has consistently been cited as the primary barrier to cloud adoption over the past few years. Concerns over who owns data in the cloud and whether the cloud operator can be ultimately trusted as a custodian of this data have been significant issues in the past. Certain OpenStack services have access to data and metadata belonging to projects or reference project information. For example, project data stored in an OpenStack cloud might include the following items: Object Storage objects. Compute instance ephemeral filesystem storage. Compute instance memory. Block Storage volume data. Public keys for Compute access. Virtual machine images in the Image service. Instance snapshots. Data passed to Compute's configuration-drive extension. Metadata stored by an OpenStack cloud includes the following items (this list is non-exhaustive): Organization name. User's "Real Name". Number or size of running instances, buckets, objects, volumes, and other quota-related items. Number of hours running instances or storing data. IP addresses of users. Internally generated private keys for compute image bundling. 20.2. Data disposal Good practices suggest that the operator must sanitize cloud system media (digital and non-digital) prior to disposal, prior to release out of organization control, or prior to release for reuse. Sanitization methods should implement an appropriate level of strength and integrity given the specific security domain and sensitivity of the information. Note The NIST Special Publication 800-53 Revision 4 takes a particular view on this topic: Cloud operators should consider the following when developing general data disposal and sanitization guidelines (as per the NIST recommended security controls): Track, document and verify media sanitization and disposal actions. Test sanitation equipment and procedures to verify proper performance. Sanitize portable, removable storage devices prior to connecting such devices to the cloud infrastructure. Destroy cloud system media that cannot be sanitized. As a result, an OpenStack deployment will need to address the following practices (among others): Secure data erasure Instance memory scrubbing Block Storage volume data Compute instance ephemeral storage Bare metal server sanitization 20.2.1. Data not securely erased Within OpenStack some data might be deleted, but not securely erased in the context of the NIST standards outlined above. This is generally applicable to most or all of the above-defined metadata and information stored in the database. This might be remediated with database and/or system configuration for auto vacuuming and periodic free-space wiping. 20.2.2. Instance memory scrubbing Specific to various hypervisors is the treatment of instance memory. This behavior is not defined in Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both. 20.3. Encrypting cinder volume data Use of the OpenStack volume encryption feature is highly encouraged. This is discussed below in the Data Encryption section under Volume Encryption. When this feature is used, destruction of data is accomplished by securely deleting the encryption key. The end user can select this feature while creating a volume, but note that an admin must perform a one-time set up of the volume encryption feature first. If the OpenStack volume encryption feature is not used, then other approaches generally would be more difficult to enable. If a back-end plug-in is being used, there might be independent ways of doing encryption or non-standard overwrite solutions. Plug-ins to OpenStack Block Storage store data in a variety of ways. Many plug-ins are specific to a vendor or technology, whereas others are more DIY solutions around file systems (such as LVM or ZFS). Methods for securely destroying data varies between plug-ins, vendors, and file systems. Some back ends (such as ZFS) support copy-on-write to prevent data exposure. In these cases, reads from unwritten blocks always return zero. Other back ends (such as LVM) might not natively support this, so the cinder plug-in takes the responsibility to override previously written blocks before handing them to users. It is important to review what assurances your chosen volume back end provides and to see what remediation might be available for those assurances not provided. 20.4. Image service delay delete features Image Service has a delayed delete feature, which will pend the deletion of an image for a defined time period. Consider disabling this feature if this behavior is a security concern; you can do this by editing glance-api.conf file and setting the delayed_delete option to False . 20.5. Compute soft delete features Compute has a soft-delete feature, which enables an instance that is deleted to be in a soft-delete state for a defined time period. The instance can be restored during this time period. To disable the soft-delete feature, edit the /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf file and leave the reclaim_instance_interval option empty. 20.6. Security hardening for bare metal provisioning For your bare metal provisioning infrastructure, you should consider security hardening the baseboard management controllers (BMC) in general, and IPMI in particular. For example, you might isolate these systems within a provisioning network, configure non-default and strong passwords, and disable unwanted management functions. For more information, you can refer to the vendor's guidance on security hardening these components. Note If possible, consider evaluating Redfish-based BMCs over legacy ones. 20.7. Hardware identification When deploying a server, there might not always have a reliable way to distinguish it from an attacker's server. This capability might be dependent on the hardware/BMC to some extent, but generally it seems that there is no verifiable means of identification built into servers. 20.8. Data encryption The option exists for implementers to encrypt project data wherever it is stored on disk or transported over a network, such as the OpenStack volume encryption feature described below. This is above and beyond the general recommendation that users encrypt their own data before sending it to their provider. The importance of encrypting data on behalf of projects is largely related to the risk assumed by a provider that an attacker could access project data. There might be requirements here in government, as well as requirements per-policy, in private contract, or even in case law in regard to private contracts for public cloud providers. Consider getting a risk assessment and legal advice before choosing project encryption policies. Per-instance or per-object encryption is preferable over, in descending order, per-project, per-host, and per-cloud aggregations. This recommendation is inverse to the complexity and difficulty of implementation. Presently, in some projects it is difficult or impossible to implement encryption as loosely granular as even per-project. Implementers should give serious consideration to encrypting project data. Often, data encryption relates positively to the ability to reliably destroy project and per-instance data, simply by throwing away the keys. It should be noted that in doing so, it becomes of great importance to destroy those keys in a reliable and secure manner. Opportunities to encrypt data for users are present: Object Storage objects Network data 20.8.1. Volume encryption A volume encryption feature in OpenStack supports privacy on a per-project basis. The following features are supported: Creation and usage of encrypted volume types, initiated through the dashboard or a command line interface Enable encryption and select parameters such as encryption algorithm and key size Volume data contained within iSCSI packets is encrypted Supports encrypted backups if the original volume is encrypted Dashboard indication of volume encryption status. Includes indication that a volume is encrypted, and includes the encryption parameters such as algorithm and key size Interface with the Key management service 20.8.2. Object Storage objects Object Storage (swift) supports the optional encryption of object data at rest on storage nodes. The encryption of object data is intended to mitigate the risk of user's data being read if an unauthorized party were to gain physical access to a disk. Encryption of data at rest is implemented by middleware that may be included in the proxy server WSGI pipeline. The feature is internal to a swift cluster and not exposed through the API. Clients are unaware that data is encrypted by this feature internally to the swift service; internally encrypted data should never be returned to clients through the swift API. The following data are encrypted while at rest in swift: Object content, for example, the content of an object PUT request's body. The entity tag ( ETag ) of objects that have non-zero content. All custom user object metadata values. For example, metadata sent using X-Object-Meta- prefixed headers with PUT or POST requests. Any data or metadata not included in the list above is not encrypted, including: Account, container, and object names Account and container custom user metadata values All custom user metadata names Object Content-Type values Object size System metadata 20.8.3. Block Storage performance and back ends When enabling the operating system, you can enhance the OpenStack Volume Encryption performance by using the hardware acceleration features available in both Intel and AMD processors. The OpenStack volume encryption feature uses either dm-crypt on the host or native QEMU encryption support to secure volume data. Red Hat recommends that you use the LUKS volume encryption type when creating encrypted volumes. 20.8.4. Network data Project data for Compute nodes could be encrypted over IPsec or other tunnels. This practice is not common or standard in OpenStack, but is an option available to motivated and interested implementers. Likewise, encrypted data remains encrypted as it is transferred over the network. 20.9. Key management To address the often mentioned concern of project data privacy, there is significant interest within the OpenStack community to make data encryption more ubiquitous. It is relatively easy for an end-user to encrypt their data prior to saving it to the cloud, and this is a viable path for project objects such as media files, database archives among others. In some instances, client-side encryption is used to encrypt data held by the virtualization technologies which requires client interaction, such as presenting keys, to decrypt data for future use. Barbican can help projects more seamlessly encrypt the data and have it accessible without burdening the user with key management. Providing encryption and key management services as part of OpenStack eases data-at-rest security adoption and can help address customer concerns about privacy or misuse of data. The volume encryption feature relies on a key management service, such as the Key Manager service (barbican), for the creation and security-hardened storage of keys.

Commands:
The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal.