[Security] List more non-FIPS compliant integrations #2611
+20
−11
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -85,14 +85,23 @@ When you use {{agent}} and {{fleet-server}}, these limitations apply: | |||||
| * Running {{agent}} in [OpenTelemetry mode](https://github.com/elastic/elastic-agent/blob/main/internal/pkg/otel/README.md) is not yet supported. This includes all receivers, such as Filebeat Receiver, Metricbeat Receiver, [Prometheus Receiver](https://www.elastic.co/docs/reference/integrations/prometheus). | ||||||
| * Some Elastic Integrations are not FIPS compatible, as they depend on functionality that is not yet supported for FIPS configuration. In general, when using {{agent}} and {{fleet-server}}, the same restrictions listed previously for {{metricbeat}} and {{filebeat}} modules, inputs, and processors apply. | ||||||
|
|
||||||
| ### Elastic Integrations that are not FIPS compatible [ingest-limitations-integrations] | ||||||
|
|
||||||
| These Elastic Integrations have components that are **not** FIPS compatible, and **cannot** be used in FIPS environments, even if combined with other ingest tools that offer FIPS mode. | ||||||
|
|
||||||
| - [Azure Logs Integration (v2 preview)](integration-docs://reference/azure/events.md) | ||||||
| - [Azure Event Hub Input](integration-docs://reference/azure/eventhub.md) | ||||||
| - [Azure AI Foundry Integration](integration-docs://reference/azure_ai_foundry.md) | ||||||
| - [Azure App Service Integration](integration-docs://reference/azure_app_service.md) | ||||||
| - [Azure Application Insights Integration](integration-docs://reference/azure_application_insights.md) | ||||||
| - [Azure Billing Metrics Integration](integration-docs://reference/azure_billing.md) | ||||||
| - [Azure Functions Integration](integration-docs://reference/azure_functions.md) | ||||||
| - [Custom Azure Logs Integration](integration-docs://reference/azure_logs.md) | ||||||
| - [Azure Resource Metrics Integration](integration-docs://reference/azure_metrics.md) | ||||||
| - [Azure OpenAI Integration](integration-docs://reference/azure_openai.md) | ||||||
| - [SQL Input](integration-docs://reference/sql.md) | ||||||
|
There was a problem hiding this comment.
Suggested change
Just if you want to exactly match the integration name, but maybe the name should be capitalized. Either way. :-) There was a problem hiding this comment. Thank you, David. Tracking the fix in https://github.com/elastic/integration-docs/issues/859 to address inconsistencies in the target content. |
||||||
| - [PostgreSQL Integration](integration-docs://reference/postgresql.md) | ||||||
| - [MongoDB Integration](integration-docs://reference/mongodb.md) | ||||||
| - [MySQL Integration](integration-docs://reference/mysql.md) | ||||||
| - [Microsoft SQL Server Integration](integration-docs://reference/microsoft_sqlserver.md) | ||||||
| - [Oracle Integration](integration-docs://reference/oracle.md) | ||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we choose wether or not to include
integrationin these titles, then do it consistently?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link text accurately reflects the target page title. I've updated the link text for consistency, and also opened integration-docs#859 to address inconsistencies in the target content.