Apache Spark meets FIPS standard
summary
Explains how to run Apache Spark on an OpenShift/Kubernetes cluster with Cloud HSM and bring your own key using envelope encryption so cloud providers cannot read data; shows configuring Java/JDK security policy and using a PKCS#11 provider, and compiling OpenSSL in FIPS mode. Demonstrates AES-256-GCM and approved cipher subsets, describes wrapping/unwrapping DEKs, and lists practical steps to make OS, libraries and Spark use only FIPS-approved algorithms to meet enterprise compliance.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:16Apache Spark meets FIPS Federal Information Processing Standards
- 0:52Center for Open Source Data & AI Technologies
- 1:32Why do we need encryption for bigdata processing engines like Apache Spark.
- 2:19Why do certain enterprises build their own solution, rather than license from others?
- 2:59A general solution.
- 3:35Can we still use the convenience of a cloud platform while we handle sensitive data?
- 3:46FIPS - Federal Information Processing Standards
- 4:20Bring Your Own Key
- 7:46Envelope encryption in action in a Hybrid Cloud
- 9:47A library/system/application is FIPS compliant means
- 10:29OpenSSL FIPS compliant v/s default version
- 12:13FIPS compliant JAVA
- 13:36Make Spark FIPS Complaint
- 15:17Making the Operating System - FIPS compliant
- 16:48Set up Mozilla NSS PKCS library.
- 17:53Configure spark security
related talks
37mScaling and Securing Spark on Kubernetes at Bloomberg
10mUnconference Session: From RFP to Fips
38mChallenges of and Solutions for Migrating Spark From Legacy Hadoop Clusters To Kubernetes
50mEnabling FIPS for Tomcat
26mRe-architecting the Data Platform with Spark on Kubernetes
43mSpark Over a Mesos Secured Productive Environment
42mApache Spark on planet scale
29mCloud-Native Apache Spark - Spark on Kubernetes Is Now Generally Available