惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
P
Palo Alto Networks Blog
月光博客
月光博客
H
Hackread – Cybersecurity News, Data Breaches, AI and More
I
InfoQ
aimingoo的专栏
aimingoo的专栏
腾讯CDC
T
Threatpost
D
DataBreaches.Net
Vercel News
Vercel News
F
Fortinet All Blogs
Engineering at Meta
Engineering at Meta
C
Cybersecurity and Infrastructure Security Agency CISA
Forbes - Security
Forbes - Security
U
Unit 42
C
Check Point Blog
Blog — PlanetScale
Blog — PlanetScale
O
OpenAI News
量子位
TaoSecurity Blog
TaoSecurity Blog
Microsoft Azure Blog
Microsoft Azure Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
V
Visual Studio Blog
Recorded Future
Recorded Future
云风的 BLOG
云风的 BLOG
Security Archives - TechRepublic
Security Archives - TechRepublic
The Last Watchdog
The Last Watchdog
S
Security Affairs
Attack and Defense Labs
Attack and Defense Labs
罗磊的独立博客
Stack Overflow Blog
Stack Overflow Blog
Microsoft Security Blog
Microsoft Security Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
V2EX
小众软件
小众软件
S
SegmentFault 最新的问题
www.infosecurity-magazine.com
www.infosecurity-magazine.com
W
WeLiveSecurity
AI
AI
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
博客园 - 聂微东
I
Intezer
Know Your Adversary
Know Your Adversary
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
P
Proofpoint News Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Cloudflare Blog
博客园_首页
NISL@THU
NISL@THU
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO

Datadog | The Monitor blog

Introducing our open source AI-native SAST Instrument and monitor Boomi integration flows with OpenTelemetry and Datadog Not all index scans are equal: How we cut query latency by over 99% Platform engineering metrics: What to measure and what to ignore Integrate Recorded Future threat intelligence with Datadog Cloud SIEM CI/CD security: threat modeling using a MITRE-style threat matrix CI/CD security: How to secure your GitHub ecosystem Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API Operating agentic AI with Amazon Bedrock AgentCore and Datadog LLM Observability: Lessons from NTT DATA Introducing the Datadog Code Security MCP Capture and analyze custom heatmaps in Session Replay Understand session replays faster with AI summaries and smart chapters Monitor ClickHouse query performance with Datadog Database Monitoring How we designed empathetic alert sounds for on-call engineers Search and act across Datadog to resolve issues faster with Bits Assistant Measure the business impact of every product change with Datadog Experiments Analyzing round trip query latency Configuring JavaScript caches for better performance Introducing Bits AI Dev Agent for Code Security Datadog achieves ISO 42001 certification for responsible AI Monitor Nutanix clusters, hosts, and VMs with Datadog Monitor Juniper Mist in Datadog A new Host Map for modern infrastructure Annotate traces to improve LLM quality with Datadog LLM Observability What’s new in Cloud SIEM: AI-powered investigations, enhanced threat intelligence, and scalable security operations Explore Kubernetes with native OpenTelemetry data Monitor Oracle Fusion Cloud Applications with Datadog Announcing the Datadog Terraform provider v4.0.0 Scaling Kubernetes workloads on custom metrics How to design cloud environments for AI-powered threat analysis Monitor Aruba Central in Datadog How we centralize and remediate risks with Datadog Case Management Accelerate incident response with Datadog and ServiceNow Monitor your application and network load balancer logs Understanding Karpenter architecture for Kubernetes autoscaling Tools for collecting metrics and logs from Karpenter Monitor Karpenter with Datadog What your product data is actually saying Key metrics for monitoring Karpenter Securing Datadog’s platform in the AI age: The role of observability data Four ways engineering teams use the Datadog MCP Server to power AI agents Approaching your observability migration with the right mindset Meet the new Bits AI SRE: Deeper reasoning, twice as fast Key learnings from the 2026 State of DevSecOps study Use plain English to query your multi-cloud infrastructure in Resource Catalog Simplifying troubleshooting across the user journey with Datadog Synthetic Monitoring Protect your OCI resources with Datadog Cloud Security This Month in Datadog - February 2026 Amazon EC2 security: How misconfigured and public AMIs expand your cloud attack surface Enable end-to-end visibility into your Java apps with a single command Measure and improve mobile app startup performance with Datadog RUM Evaluating our AI Guard application to improve quality and control cost Identify untested code across every level of your codebase Make use of guardrail metrics and stop babysitting your releases Monitor Versa Networks SD-WAN performance in Datadog Improve performance and reliability with APM Recommendations Remediate transitive vulnerabilities faster with Datadog Software Composition Analysis Generate audit-ready vulnerability and compliance reports with Datadog Sheets Monitor Fortinet FortiManager performance in Datadog Improve test coverage across codebases with Datadog Code Coverage Move fast, don’t break things: Consistent testing standards at scale Enrich logs with ServiceNow CMDB context before routing to any SIEM or logging tool Monitor Lustre with Datadog Make faster, better product decisions with Datadog Product Analytics Surface and remediate runtime posture issues with Workload Protection Findings Protect agentic AI applications with Datadog AI Guard How to optimize JavaScript code with CSS Trace Google Pub/Sub workloads in Cloud Run with Datadog Detect human names in logs with ML in Sensitive Data Scanner How we cut our NLQ agent debugging time from hours to minutes with LLM Observability Debug PostgreSQL query latency faster with EXPLAIN ANALYZE in Datadog Database Monitoring Datadog acquires Propolis Unify and correlate frontend and backend data with retention filters Scale compliance across global frameworks with Datadog Cloud Security Monitor Arista VeloCloud SD-WAN performance with Datadog Building reliable dashboard agents with Datadog LLM Observability Simplify log collection and aggregation for MSSPs with Datadog Observability Pipelines Mitigation for Node.js denial-of-service vulnerability affecting Datadog APM Automate flaky test fixes with the Bits AI Dev Agent and Test Optimization How we built an AI SRE agent that investigates like a team of engineers Datadog integrations 2025 recap: Observability for AI, security, and hybrid cloud Design effective executive dashboards with Datadog Implement dbt data quality checks with dbt-expectations Bring faster visibility into AWS Lambda functions with remote instrumentation Troubleshoot faster with the GitLab Source Code integration in Datadog How Cambia Health Solutions saved $30,000 monthly with Cloud Cost Management and the Datadog Resource Catalog Normalize any logs for Cloud SIEM with Datadog's OCSF processor Optimizing Datadog at scale: Cost-efficient observability at Zendesk Detect, diagnose, and resolve network issues easily with CNM Network Health Connect engineering errors to user impact in early-stage products Cilium configuration for Kubernetes operations at scale Designing feedback loops for progressive delivery Ship features faster and safer with Datadog Feature Flags Choosing the right OpenTelemetry Collector distribution Route your monitor alerts with Datadog monitor notification rules Automate Cloud SIEM investigations with Bits AI Security Analyst Cloud threat detection: How to identify risky activity across control and data planes Collecting Kafka performance metrics Monitoring Kafka with Datadog Monitoring Kafka performance metrics
Discover, triage, and remediate sensitive data issues at scale with Sensitive Data Scanner
2023-11-27 · via Datadog | The Monitor blog
Tori Teng

Tori Teng

Aaron Kaplan

Aaron Kaplan

Managing sensitive information in your telemetry data poses many challenges to governance, risk management, and compliance (GRC) teams and overall security. Organizations in healthcare, finance, insurance, and other fields must carefully adhere to strict compliance requirements. But sensitive data comes in many forms and moves between many endpoints, and as a result, it can easily become exposed in telemetry data. What’s more, as organizations scale, troubleshooting and triaging sensitive data issues becomes an increasingly complex process, and the risks of alert fatigue, mismanagement, and oversights grow higher.

Datadog’s Sensitive Data Scanner helps you eliminate data exposure blind spots in order to ensure that you meet data compliance standards and regulations. You can use Sensitive Data Scanner to automatically identify sensitive data in your logs, APM traces, and real user monitoring (RUM) events; define high- and low-risk sensitive information using searchable tags; and redact or hash that information as needed.

In this post, we’ll show you how Sensitive Data Scanner provides fast, comprehensive visibility into potential data compliance issues through a focused central interface and context-aware classification. We’ll guide you through using Sensitive Data Scanner to:

Comprehensively manage data compliance issues

As sensitive data issues arise, GRC teams are under pressure to act fast in order to plug leaks and contain the fallout. Capturing detail along the way is also an urgent necessity, especially when it comes to providing auditors with incident reports. As these teams investigate sensitive data issues, they are confronted with a range of questions:

  • Which sensitive data has been exposed, and where has it come from?
  • Where, among many services, hosts, and environments, has the leak occurred? Which teams need to plug it, and how should they do so?
  • What caused the issue in the first place? What new security measures are called for?
  • How should this issue be prioritized alongside others?

Sensitive Data Scanner enables you to discover, triage, troubleshoot, and track data compliance issues through a central interface. The Sensitive Data Scanner summary page provides a high-level snapshot of every issue detected by your scanning rules, which define any data that might compromise the compliance, security, or privacy of your organization or users. Datadog provides a library of predefined rules that help you detect the exposure of data such as credit card numbers, email addresses, IP addresses, API keys, and more. You can also define your own regex-based scanning rules to identify business-specific sensitive information.

Datadog’s library of predefined rules for Sensitive Data Scanner.

To fine-tune Sensitive Data Scanner, you can define a keyword dictionary for each of your scanning rules. Keyword dictionaries can improve the accuracy of data classification and minimize the potential for false positives. For example, defining the keywords visa, credit, and card for a Visa credit card number scanning rule will ensure that any matches are preceded by these words within a range of 30 characters.

Keyword dictionaries help you fine-tune your scanning rules.

You can also define parameters for the rule’s target and actions that will be taken when a match is found, including setting a priority level.

You can set a priority level for when a rule finds a match.

When a scanning rule detects a match one or more times within any of the data sets you are scanning—called scanning groups—Sensitive Data Scanner designates it as an issue. It provides an overview of the sensitive data exposed in each issue and enables you to quickly create cases and Jira tickets, declare incidents, and collaborate on remediation.

Analysts can use Sensitive Data Scanner to access key information on each sensitive data issue, enabling them to start remediating without spending time gathering basic information, such as when a leak started or the number of events in which a specific set of sensitive information was exposed.

At the top of the summary page, you can find a tally of all sensitive data issues within the selected time frame. Issues are broken down by telemetry type, such as logs or traces, and priority level, which is defined as Low, Medium, High, or Critical for each issue according to your scanning rules.

The Sensitive Data Scanner summary page.

You can also quickly review all of the scanning rules you have enabled, as well as all of the cases associated with sensitive data issues in Datadog Case Management. Case Management enables you to track, triage, and troubleshoot issues like sensitive data leaks, assign troubleshooting and remediation to users or teams, and associate cases with Jira tickets.

The Issues Overview provides a detailed snapshot of each sensitive data issue identified by your scanning rules, sorted by priority level.

The Issues Overview provides a detailed snapshot of each sensitive data issue identified by your scanning rules, sorted by priority level.

The overview includes the following key information on each issue:

  • The specific scanning rule that has detected matches, so that you can easily determine which rules to modify as needed
  • The scanning groups—user-defined groups that specify relevant services, hosts, environments, or other classifying data—in which the issue has occurred, so that you can easily determine the blast radius of any leaks
  • The number of events associated with the issue, helping you quickly gauge its scope and severity
  • A trendline of these events and an index of when the most recent one occurred, allowing you to pinpoint when an issue started and get a quick picture of its development

You can select any issue from the summary page to open an expanded view. Here, you can find a timeseries graph of the leak, as well as a list of the sensitive-data events from Datadog Log Management, APM, RUM, and Event Management, which you can spot-check to quickly pinpoint where and how the sensitive information is being exposed.

From the summary page, you can access a side panel for each issue from which you can jumpstart your investigation and response.
From the summary page, you can access a side panel for each issue from which you can jumpstart your investigation and response.

Below that, you can assess the blast radius of each issue with the help of a breakdown of the services, hosts, and environments in which the data was exposed, as well as a list of the users who may have accessed it (via an integration with Audit Trail). Sensitive Data Scanner’s close integration with Datadog Service Catalog also helps you quickly determine which teams own any services involved in a leak, so you can resolve issues faster.

Quickly assess the blast radius of each issue and determine who to contact to plug leaks.

You can also pivot from the expanded view to Datadog Log Management, APM, RUM, or Event Management for a more detailed analysis of specific events, so that you can better identify patterns. Or you can pivot to Audit Trail to see related events involving Sensitive Data Scanner configuration changes or user queries with sensitive data tags.

Overall, these expanded views serve as strong starting points for troubleshooting data compliance issues and investigating potential leaks. And by identifying all affected services, environments, and hosts—as well as the teams responsible for them—in each expanded view, the Sensitive Data Scanner summary page enables you to quickly delegate and track remediation.

Kickstart investigations into potential data leaks

With its close integrations with Case Management and Incident Management, Sensitive Data Scanner helps you quickly start a coordinated response to any sensitive data issue. You can easily create cases or incidents directly from the summary page, create Jira tickets linked to issues in Case Management, delegate responders, and automatically point those responders to the relevant data.

Sensitive Data Scanner is closely integrated with Case Management, so you can easily manage a coordinated response to all of your sensitive data issues.

Case Management enables you to create a record of each issue, its causes, and the remediation actions that have been taken to resolve it. Along with Audit Trail’s ability to capture audit events of user queries of sensitive data, this can be particularly vital as analysts work with auditors and write postmortems.

Let’s say you’re a security analyst and the Sensitive Data Scanner detects JSON web tokens (JWTs) in your organization’s logs, APM traces, or RUM events. Since you have configured alerting based on the tags associated with your Sensitive Data Scanner rules, you immediately receive an alert from Datadog. From there, you can navigate to the Sensitive Data Scanner summary page to quickly gauge the blast radius of the leak and determine the owners of the affected services. Based on your findings, you can create a new case for each affected service—or, if the issue seems like it might have a significant impact on your end users, declare an incident—and delegate remediation tasks as needed.

Scale your data compliance posture

The Sensitive Data Scanner summary page enables you to effectively manage data compliance issues at scale. You can use it to discover and manage sensitive data issues in your logs, APM traces, and RUM events, conduct triage and troubleshooting, and assign and track remediation tasks.

Datadog users can start managing sensitive data issues via the Sensitive Data Scanner summary page today. To learn more about Sensitive Data Scanner, you can find more information on our blog or check out our documentation. If you’re new to Datadog, you can sign up for a 14-day free trial.