[Security] List more non-FIPS compliant integrations #2611
Conversation
karenzone
force-pushed
the
2367-non-fips
branch
from
192596c to
c18d6f1
Compare
🔍 Preview links for changed docs |
|
@shmsr, please review. Do we need approvals from any other people or teams? |
|
|
||
| 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) |
There was a problem hiding this comment.
should we choose wether or not to include integration in these titles, then do it consistently?
There was a problem hiding this comment.
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.
| - [Custom Azure Logs](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.
| - [SQL Input](integration-docs://reference/sql.md) | |
| - [SQL input](integration-docs://reference/sql.md) |
Just if you want to exactly match the integration name, but maybe the name should be capitalized. Either way. :-)
Feel free to ignore.
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.
Issue: #2367
Related: elastic/integrations#14769
Expands the list of non-FIPS compliant integrations
PREVIEW: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2611/deploy-manage/security/fips-ingest#ingest-limitations-integrations