--- title: FIPS mode for Ingest tools description: Elastic Agent, Fleet, Filebeat, Metricbeat, and APM Server are FIPS 140-3 capable. They use Go's native FIPS 140-3 module (GOFIPS140=v1.0.0, CMVP Certificate... url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/7818/deploy-manage/security/fips-ingest products: - APM - Beats - Elastic Agent - Fleet applies_to: - Elastic Stack: Preview since 9.1 --- # FIPS mode for Ingest tools Elastic Agent, Fleet, Filebeat, Metricbeat, and APM Server are FIPS 140-3 capable. They use Go's native FIPS 140-3 module (`GOFIPS140=v1.0.0`, CMVP Certificate [#5247](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/5247)) for cryptographic operations. Specific components and configurations that fall outside the certified boundary are documented in the limitations sections below. ## FIPS-compatible binaries and configuration FIPS compatible binaries for Elastic Agent, Fleet, Filebeat, Metricbeat, and APM Server are available for [download](https://www.elastic.co/downloads). Look for the `Linux 64-bit (FIPS)` or `Linux aarch64 (FIPS)` platform option on the product download pages for Elastic Agent and Fleet, Filebeat, and Metricbeat. Look for the `Linux x86_64 (FIPS)` or `Linux aarch64 (FIPS)` platform option on the APM Server download page. The default configurations provided in the binaries are designed for FIPS-capable operation. Review the limitations below to ensure your full deployment stays within the certified boundary. ## Limitations ### TLS Only FIPS 140-3 compliant TLS protocols, ciphers, and curve types are allowed to be used as listed in the following section. - The supported TLS versions are `TLS v1.2` and `TLS v1.3`. - The supported cipher suites are: - `TLS v1.2`: `ECDHE-RSA-AES-128-GCM-SHA256`, `ECDHE-RSA-AES-256-GCM-SHA384`, `ECDHE-ECDSA-AES-128-GCM-SHA256`, `ECDHE-ECDSA-AES-256-GCM-SHA384` - `TLS v1.3`: `TLS-AES-128-GCM-SHA256`, `TLS-AES-256-GCM-SHA384` - The supported curve types are `P-256`, `P-384` and `P-521`. - The minimum key length is 2048 bits for RSA keys. EC key size is determined by the curve in use; see the supported curve types above. Support for encrypted private keys is not available, as the cryptographic modules used for decrypting password protected keys are not FIPS validated. If an output or any other component with an SSL key that is password protected is configured, the components will fail to load the key. When running in FIPS mode, you must provide non-encrypted keys. Be sure to enforce security in your FIPS environments through other means, such as strict file permissions and access controls on the key file itself, for example. These TLS related restrictions apply to all components listed in the preceding section. ### General output and input limitations (Kerberos protocol) The Kerberos protocol is not supported for outputs and inputs in Filebeat, Metricbeat, APM Server, and Fleet Server configurations. This also restricts the available `sasl.mechanism` for the Kafka output, where only `PLAIN` is supported. This impacts [Filebeat](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/configuration-kerberos), [Metricbeat](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/configuration-kerberos) and APM Server, as well as output configurations for Elastic Agent with Fleet Server. ### APM Server - The [Secrets Keystore](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/7818/solutions/observability/apm/apm-server/secrets-keystore-for-secure-settings) is not supported. ### Filebeat - The [Secrets Keystore](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/keystore) is not supported. - The [Translate GUID processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/processor-translate-guid) is not supported. - The [Fingerprint processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/fingerprint) does not support the md5 and sha1 method. - The [Community ID Network Flowhash processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/community-id) is not supported. - The [Azure module](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/filebeat-module-azure) including the [Azure eventhub input](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/filebeat-input-azure-eventhub) and the [Azure Blob Storage Input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-blob-storage) are not supported. The [Add Cloud Metadata processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/add-cloud-metadata) does not support the Azure Virtual Machine provider. - The [Office 365 module (Beta)](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/filebeat-module-o365) and the [Office 365 input (Deprecated)](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-o365audit) are not supported. - The [GCP Pub/Sub input](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/filebeat/filebeat-input-gcp-pubsub) and the [Google Cloud Storage input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-gcs) are not supported. - The [Entity Analytics input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-entity-analytics) is not supported. ### Metricbeat - The [Secrets Keystore](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/keystore) is not supported. - The [Translate GUID processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/processor-translate-guid) is not supported. - The [Fingerprint processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/fingerprint) does not support the md5 and sha1 method. - The [Community ID Network Flowhash processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/community-id) is not supported. - The [Azure module](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-azure) is not supported. The [Add Cloud Metadata processor](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/add-cloud-metadata) does not support the Azure Virtual Machine provider. - The [Google Cloud Platform module](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-module-gcp) is not supported. - The [Beta KVM module](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-kvm) is not supported. - The [Mongo DB module](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-mongodb) is not supported. - The [MySQL](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-mysql), [PostgreSQL](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-postgresql), [MSSQL](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-mssql) and [SQL](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-sql) modules are not supported. - The [Oracle module](https://docs-v3-preview.elastic.dev/elastic/beats/tree/main/reference/metricbeat/metricbeat-module-oracle) is not supported. ### Elastic Agent and Fleet Server When you use Elastic Agent and Fleet Server, these limitations apply: - Some Elastic Integrations are not FIPS compatible, as they depend on functionality that is not supported for FIPS configuration. In general, when using Elastic Agent and Fleet Server, the same restrictions listed previously for Metricbeat and Filebeat modules, inputs, and processors apply. - Agent upgrade artifact verification uses GPG signature checking, which is outside Go's certified FIPS module boundary. ### Elastic Agent in OpenTelemetry mode (EDOT) When running Elastic Agent in [OpenTelemetry mode](https://github.com/elastic/elastic-agent/blob/main/internal/pkg/otel/README.md) (EDOT), these additional limitations apply: - **Azure integrations**: PKCS#12 (`.pfx`) client certificates are not supported for Azure Active Directory authentication. Use client secrets, workload identity, managed identity, or PEM-encoded certificate and key files instead. - **Kafka metrics receiver**: SASL GSSAPI (Kerberos) is not supported. SASL SCRAM (SCRAM-SHA-256, SCRAM-SHA-512) is not FIPS-compliant. Use SASL/PLAIN over TLS or mTLS. - **MongoDB receiver**: Not supported in FIPS mode. - **MySQL receiver**: Not supported in FIPS mode. - **Microsoft SQL Server receiver**: Not supported in FIPS mode. - **Kerberos authentication for beat receivers**: Kerberos/GSSAPI authentication for beat receivers (Filebeat receiver, Metricbeat receiver) is not supported. - **API key authentication extension**: Not FIPS-compliant. Uses a PBKDF2 implementation outside the certified FIPS module boundary when active. If you are using a component not listed here and are unsure whether it is FIPS compliant, contact [Elastic Support](https://www.elastic.co/support). ### Elastic Integrations that are not FIPS compatible The following Elastic Integrations (Fleet-managed) use cryptographic implementations outside Go's certified FIPS module boundary for core functionality and **cannot** be used in FIPS environments. For EDOT-specific limitations, see [Elastic Agent in OpenTelemetry mode (EDOT)](#ingest-limitations-edot). - [Azure Logs Integration (v2 preview)](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure/events) - [Azure Event Hub Input](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure/eventhub) - [Azure AI Foundry Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_ai_foundry) - [Azure App Service Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_app_service) - [Azure Application Insights Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_application_insights) - [Azure Billing Metrics Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_billing) - [Azure Functions Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_functions) - [Custom Azure Logs Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_logs) - [Azure Resource Metrics Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_metrics) - [Azure OpenAI Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/azure_openai) - [SQL Input](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/sql) - [PostgreSQL Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/postgresql) - [MongoDB Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/mongodb) - [MySQL Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/mysql) - [Microsoft SQL Server Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/microsoft_sqlserver) - [Oracle Integration](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/oracle) - [Elastic Defend](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference/endpoint)