IBM Hyper Protect Virtual Servers for Virtual Private Cloud (VPC) Is An Excellent Choice For Securely Processing Sensitive Data
Rating: 10 out of 10
Use Cases and Deployment Scope
Sensitive patient data is defined as protected health information (PHI) under HIPAA which is a United States patient privacy law. Processing PHI within a very secure enclave is incredibly important for us, as a fintech, healthcare AI company, and our customers. Our first choice was IBM Hyper Protect Virtual Servers for Virtual Private Cloud (VPC) (i.e., the “Fort Knox of data security”).
Pros
- Process sensitive data within a secure enclave
- Support for common Infrastructure As Code containerized solutions
- Healthy marketplace for cybersecurity analytics solutions
Cons
- Support for S390X and x86 architectures in managed Kubernetes
- Some common frameworks don’t support big-endian architectures. We had to migrate from Apache Parquet to MessagePack because S390X doesn’t support Apache Parquet. Although MessagePack or Protobufs works fine on S390X, it would be nice to have a page of common databases, serialization formats, etc. that have S390X support.
- Improve the non-native S390X development tools and guides. Most development machines aren’t built on the S390X architecture.
Likelihood to Recommend
IBM Hyper Protect Virtual Servers for Virtual Private Cloud (VPC) works great in scenarios where there is a need to process sensitive data within a secure enclave. IBM Hyper Protect Virtual Servers for Virtual Private Cloud (VPC) isn’t suitable as a commodity solution for general purpose compute. The IBM Hyper Protect Virtual Servers For Virtual Private Cloud have less CPUs and available RAM than some x86 virtual machines on IBM Cloud. In other words, using IBM Hyper Protect Virtual Servers for Virtual Private Cloud (VPC) to process generic data doesn’t make much sense. You may be able to get more compute for your money by processing generic data using an x86 architecture server on IBM Cloud or another public cloud provider.
