Log Management Data Security

Docs > Réduction des risques liés à vos données > Log Management Data Security

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

This page is about the security of data sent to Datadog. If you're looking for cloud and application security products and features, see the Security section.

The Log Management product supports multiple environments and formats, allowing you to submit to Datadog nearly any data you choose. This article describes the main security guarantees and filtering controls available to you when submitting logs to Datadog.

Note: Logs can be viewed in various Datadog products. All logs viewed in the Datadog UI, including logs viewed in APM trace pages, are part of the Log Management product.

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 you, expires.

Logs filtering

In version 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

As of version 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 through chat.
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 be notified by webhooks.

If you have any questions about how the Log Management Service satisfies the applicable requirements under HIPAA, contact your account manager. HIPAA-enabled customers do not need to use specific endpoints to submit logs to enforce specific encryptions. The encryptions are enabled on all log submission endpoints.

PCI DSS compliance for Log Management

PCI DSS compliance for Log Management is only available for new Datadog organizations created in the US1 site.

Datadog allows customers to send logs to PCI DSS compliant Datadog organizations upon request. To set up a PCI-compliant Datadog org, follow these steps:

Set up a new Datadog org in the US1 site. PCI DSS compliance is only supported for new orgs created in US1.
Contact Datadog support or your Customer Success Manager to request that the new org be configured as a PCI-compliant org.
Enable Audit Trail in the new org. Audit Trail must be enabled and remain enabled for PCI DSS compliance.
After Datadog support or Customer Success confirms that the new org is PCI DSS compliant, configure the Agent configuration file to send logs to the dedicated PCI-compliant endpoint (agent-http-intake-pci.logs.datadoghq.com):
```
logs_config:
  logs_dd_url: <http://agent-http-intake-pci.logs.datadoghq.com:443|agent-http-intake-pci.logs.datadoghq.com:443>
```
Note: The port must be included in the configuration. PCI compliance uses HTTP log forwarding only. If you are using the Agent, you should enforce HTTP transport.