To repeat, SSC improves on the traditional method of deploying applications. Most  importantly, it prevents tampering with the appliance image and prevents load of the  appliance at arbitrary times. Furthermore, the appliance code and data is  protected/confidential while in transit and while at rest. In addition, memory access is disabled and disk access is encrypted by default and these  configurations cannot be disabled. The debugging data that system memory dumps provide  is also encrypted. So, support groups can view only the application instructions in the dump,  not any data that is included in the dump. Finally, SSC makes your cloud infrastructure more secure and efficient for your blockchain  deployments. This publication will consider use cases and implementations in the next  sections. Figure 2-3 IBM Secure Service Container for IBM Cloud Private - Full-stack solution 2.2 Persistent Storage providers For deployment of IBM Blockchain Platform (IBP), you must have mechanisms to persistently  store data. This requirement applies to both an IBM Secure Service Container (SSC) and a  non-SSC environment. IBM Cloud Private offers many options for managing persistent storage within the cluster. IBM  Cloud Private includes the following features: GLYPH<SM590000> GlusterFS enterprise grade of storage to Kubernetes (K8s) pods. They offer ease of  configuration, scaling, encryption support, replication, striping, and dynamic provisioning. Chapter 2. Planning for installation  23