Overview

Sensitive data, such as credit card numbers, bank routing numbers, and API keys, can be revealed unintentionally in your logs, which can expose your organization to financial and privacy risks.

Use the Observability Pipelines Worker to identify, tag, and optionally redact or hash sensitive information before routing logs to different destinations and outside of your infrastructure. You can use out-of-the-box scanning rules to detect common patterns such as email addresses, credit card numbers, API keys, authorization tokens, and more. Or, create custom scanning rules using regex patterns to match sensitive information.

Select a log source to get started:

• Amazon Data Firehose
• Amazon S3
• Datadog Agent
• Fluentd or Fluent Bit
• Google Pub/Sub
• HTTP Client
• HTTP Server
• Kafka
• Logstash
• Splunk HTTP Event Collector (HEC)
• Splunk Heavy or Universal Forwarders (TCP)
• Sumo Logic Hosted Collector
• rsyslog or syslog-ng