The Datadog FIPS Agent is available only in the US1-FED region.
The FIPS Agent is a flavor of the Datadog Agent that natively supports Federal Information Processing Standards (FIPS) compliance. The FIPS Agent includes limited support for integrations that need to collect observability data that is external to the host.
Supported platforms and limitations
The FIPS Agent’s compliance is based on its use of the FIPS 140-2 validated Cryptographic Module - Certificate #4282. See the related security policy for information about validated operating environments and restrictions.
It is your responsibility to ensure operating environment compliance with the security policy and wider FIPS guidance.
Supported platforms:
Bare metal and VMs
RHEL >= 7 Debian >= 8 Ubuntu >= 14.04 SUSE >= 12 Windows Server >= 2016 Windows >= 10
Cloud and container
Amazon ECS AWS EKS (Helm) Docker
Supported products (Agent 7.65.0 and above):
Metrics
Logs
APM traces
APM profiles
Processes
Orchestrator Explorer
Runtime Security
The Datadog FIPS Agent does not support the following:
Serverless Monitoring
Communication between Cluster Agent and Node Agents
Agent integrations
Outbound communication to anything other than GovCloud
Prerequisites
A non-containerized Linux host.
Your Linux OS must be in FIPS-compliant mode. See your OS vendor’s documentation on what steps are required to meet this requirement.
FIPS-compliant storage backing the host file system.
Note: FIPS support is only available on Agent versions 7.65.0 and above:
If you’re using the Agent install script, specify the DD_AGENT_FLAVOR="datadog-fips-agent" environment variable in your installation command. For example:
If you’re installing with a package, follow the instructions to install the latest datadog-fips-agent package available for your platform.
Add GOFIPS=1 to your Datadog environment variables, reload all service units, and restart the Datadog Agent service (datadog-agent.service). For example, if your host is using systemd:
echo"GOFIPS=1"| sudo tee -a /etc/datadog-agent/environment
systemctl daemon-reload
systemctl restart 'datadog-agent*'
Run the datadog-agent status command and make sure you see FIPS Mode: enabled in the status output.
Note: The program name for the FIPS Agent in Add or Remove Programs is “Datadog FIPS Agent.”
Security and hardening
You, the Datadog customer, are responsible for host security and hardening.
Security considerations:
While the Datadog images provided are constructed with security in mind, they have not been evaluated against CIS benchmark recommendations or DISA STIG standards.
If you rebuild, reconfigure, or modify the Datadog FIPS Agent to fit your deployment or testing needs, you might end up with a technically working setup, but Datadog cannot guarantee FIPS compliance if the Datadog FIPS Agent is not used exactly as explained in the documentation.
If you did not follow the installation steps listed above exactly as documented, Datadog cannot guarantee FIPS compliance.