FIPS Support for Ecosystem Components
If used with release 7.0.0 or later, most EEP components support the Federal Information Processing Standard (FIPS) 140-2 Level 1.
FIPS Support Matrix
The following table summarizes component support for FIPS:
| Component | FIPS Support | ||||||
|---|---|---|---|---|---|---|---|
| EEP 9.2.1 | EEP 9.2.0 | EEP 9.1.2 | EEP 9.1.1 | EEP 9.1.0 | EEP 9.0.0 | EEP 8.1.x | |
| Airflow | Yes* | No | No | No | No | No | No |
| Data Access Gateway | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Drill | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| HBase | Yes | Yes | Yes | Yes | Yes | Yes | Yes** |
| Hive | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| HTTPFS | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Hue | No | No | No | No | No | No | No |
| Kafka REST | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Kafka Connect HDFS | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Kafka Connect JDBC | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| KSQL | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Kafka Streams | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Livy | Yes | No | No | No | No | No | Yes*** |
| NiFi | Yes | Yes | Yes | Yes | Yes | Yes | Not included in EEP 8.1.x |
| Oozie | Not included in EEP 9.2.1 | Not included in EEP 9.2.0 | Not included in EEP 9.1.2 | Not included in EEP 9.1.1 | Not included in EEP 9.1.0 | Not included in EEP 9.0.0 | Yes |
| OTel | No | No | Not included in EEP 9.1.2 | Not included in EEP 9.1.1 | Not included in EEP 9.1.0 | Not included in EEP 9.0.0 | Not included in EEP 8.1.x |
| Ranger | Yes**** | Yes**** | Yes**** | Yes**** | Yes**** | Yes**** | Not included in EEP 8.1.x |
| Spark | Yes*** | Yes*** | Yes*** | Yes*** | Yes*** | Yes*** | Yes*** |
| Tez | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| YARN | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Zeppelin | No | No | No | No | No | No | Not included in EEP 8.1.x |
*Installing Airflow in a FIPS environment requires extra steps. For more information, see Installation on a FIPS Node.
**HBase cannot be used in a mixed (FIPS and non-FIPS) configuration. For example, a non-FIPS client node cannot communicate with a FIPS server node.
***In a mixed (FIPS and non-FIPS) configuration, there is a known issue related to Spark and Livy applications if the Spark UI is enabled. See Spark and Livy release notes for more information.
****This version does not support mixed FIPS mode.
For more information about FIPS, see FIPS Compliance for HPE Ezmeral Data Fabric.