This article is part of a series on data security.
The Log Management product supports multiple environments and formats, allowing customers the flexibility to submit to Datadog nearly any data they choose. This article describes the main security guarantees and filtering controls available to users when submitting logs to Datadog.
The Datadog Agent submits logs to Datadog over a TLS-encrypted TCP connection, requiring an outbound communication over port
10516. The Datadog Agent can also be configured to send logs over secured HTTPS requests, requiring an outbound communication over port
443. Datadog uses symmetric encryption at rest (AES-256) for indexed logs. Indexed logs are deleted from the Datadog platform once their retention period, as defined by the customer, expires.
For customers using release 6, the Agent can be configured to filter logs sent by the Agent to the Datadog application. To prevent the submission of specific logs, use the
log_processing_rules setting, with the exclude_at_match or include_at_match
type. This setting enables the creation of a list containing one or more regular expressions, which instructs the Agent to filter out logs based on a whitelist or blacklist.
For customers using release 6, the Agent can be configured to obfuscate specific patterns within logs sent by the Agent to the Datadog application. To mask sensitive sequences within your logs, use the
log_processing_rules setting, with the mask_sequences
type. This setting enables the creation of a list containing one or more regular expressions, which instructs the Agent to redact sensitive data within your logs.
Datadog will sign a Business Associate Agreement (BAA) with customers that transmit protected health information (ePHI) via Datadog’s Log Management Service.
Prior to executing a BAA, customers transmitting ePHI to the Datadog Log Management Service must implement the following configurations:
lambda-tcp-encrypted-intake.logs.datadoghq.comby setting the
DD_URLenvironment variable as well as setting
The following sample configuration can be used with the Datadog Agent to submit logs to a HIPAA-ready endpoint directly (i.e. without a proxy):
logs_enabled: true logs_config: logs_dd_url: tcp-encrypted-intake.logs.datadoghq.com:10516 logs_no_ssl: false
With the Docker Agent, pass in
DD_LOGS_CONFIG_LOGS_DD_URL=tcp-encrypted-intake.logs.datadoghq.com:10516 as an environment variable.
Additionally, certain features are not available at the moment to customers who have signed Datadog’s BAA, notably:
If you have any questions about how the Log Management Service satisfies the applicable requirements under HIPAA, please contact your account manager.
Additional helpful documentation, links, and articles: