Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 12 additions & 11 deletions content/en/agent/configuration/fips-compliance.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,9 @@

## Supported platforms and limitations


Supported platforms:

|||
| | |
| --- | ----------- |
| Bare metal and VMs | RHEL >= 7<br>Debian >= 8<br>Ubuntu >= 14.04<br>SUSE >= 12<br>Windows Server >= 2016<br>Windows >= 10|
| Cloud and container| Amazon ECS<br>AWS EKS (Helm)<br>Docker|
Expand All @@ -49,14 +48,12 @@
The Datadog FIPS Agent does **not** support the following:
- Communication between Cluster Agent and Node Agents
- Outbound communication to anything other than GovCloud
- Datadog [DDOT Collector][1]
- Datadog [DDOT Collector][4]

[1]: /opentelemetry/setup/ddot_collector

## Compliance guidelines
<div class="alert alert-warning">
This is not an exhaustive list. These requirements are a baseline only. You are responsible for evaluating your environment and implementing any additional controls needed to achieve full FIPS compliance.
</div>
<div class="alert alert-warning">This is not an exhaustive list. These requirements are a baseline only. You are responsible for evaluating your environment and implementing any additional controls needed to achieve full FIPS compliance.</div>

The following baseline controls apply to each platform. Your system may require additional controls:

{{< tabs >}}
Expand Down Expand Up @@ -155,21 +152,24 @@

{{% tab "AWS Lambda" %}}

For AWS Lambda FIPS compliance, follow the instructions in the [AWS Lambda FIPS Compliance](/serverless/aws_lambda/fips-compliance/) documentation.
For AWS Lambda FIPS compliance, follow the instructions in the [AWS Lambda FIPS Compliance][1] documentation.

[1]: /serverless/aws_lambda/fips-compliance/

{{% /tab %}}

{{% tab "AWS ECS" %}}

When following the [ECS installation instructions](/containers/amazon_ecs/), make sure to use these FIPS-specific configuration values for your Task Definition:
When following the [ECS installation instructions][1], make sure to use these FIPS-specific configuration values for your Task Definition:
- Set `image` in the `containerDefinitions` object to `public.ecr.aws/datadog/agent:7-fips`
- Set `DD_SITE` environment variable to `ddog-gov.com`

[1]: /containers/amazon_ecs/
{{% /tab %}}

{{% tab "AWS EKS" %}}

When following the [Datadog Agent installation on Kubernetes](/containers/kubernetes/installation/) instructions, make sure to include these FIPS-specific configuration values in the `datadog-agent.yaml` file depending on your chosen installation method:
When following the [Datadog Agent installation on Kubernetes][1] instructions, make sure to include these FIPS-specific configuration values in the `datadog-agent.yaml` file depending on your chosen installation method:

Check notice on line 172 in content/en/agent/configuration/fips-compliance.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength

Suggestion: Try to keep your sentence length to 25 words or fewer.

For the Datadog Operator:
```yaml
Expand All @@ -186,6 +186,7 @@
useFIPSAgent: true
```

[1]: /containers/kubernetes/installation/
{{% /tab %}}

{{< /tabs >}}
Expand All @@ -207,4 +208,4 @@
[1]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4282
[2]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4282.pdf
[3]: /integrations/guide/fips-integrations
[4]: /integrations/guide/jmxfetch-fips
[4]: /opentelemetry/setup/ddot_collector
Loading