Log Management Security

This page is about the security of Datadog; if you're looking for the Security Monitoring product, see the Security Monitoring section.

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.

Information security

The Datadog Agent submits logs to datadog either through HTTPS or through TLS-encrypted TCP connection on port 10516, requiring outbound communication (see Agent Transport for logs).

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.

Logs filtering

For customers using release 6 or above, 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 the inclusion or exclusion rules supplied.

Logs obfuscation

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.

HIPAA-enabled customers

Datadog will sign a Business Associate Agreement (BAA) with customers that transmit protected health information (ePHI) via Datadog’s Log Management Service.

These features are not available to customers who have signed Datadog’s BAA:

Users cannot request support via chat.
Group-by dimensions are limited to host tags, source, service, and status for Log-based Metrics.
Notifications from Log Monitors cannot include log samples.
You cannot configure Log Monitors with a group-by clause.
You cannot share logs, security signals, or traces from the explorer through web integrations.
Security rules cannot include triggering group-by values in notification title.
Security rules cannot include message template variables.
Security rules cannot notify by webhooks.

If you have any questions about how the Log Management Service satisfies the applicable requirements under HIPAA, contact your account manager.

Note:

Previously, HIPAA-enabled customers needed to use specific endpoints to submit logs in order to enforce specific encryptions. This is no longer necessary. The encryptions are enabled on all log submission endpoints.

These legacy endpoints are still supported: