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

推荐订阅源

Recorded Future
Recorded Future
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Forbes - Security
Forbes - Security
N
News and Events Feed by Topic
SecWiki News
SecWiki News
T
The Exploit Database - CXSecurity.com
S
Security @ Cisco Blogs
H
Heimdal Security Blog
Security Latest
Security Latest
T
Threatpost
V2EX - 技术
V2EX - 技术
C
Cybersecurity and Infrastructure Security Agency CISA
GbyAI
GbyAI
The Last Watchdog
The Last Watchdog
Recent Announcements
Recent Announcements
P
Privacy International News Feed
K
Kaspersky official blog
P
Proofpoint News Feed
L
LangChain Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Security Archives - TechRepublic
Security Archives - TechRepublic
T
Threat Research - Cisco Blogs
博客园_首页
T
Tor Project blog
M
MIT News - Artificial intelligence
The Hacker News
The Hacker News
The GitHub Blog
The GitHub Blog
月光博客
月光博客
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
F
Full Disclosure
MyScale Blog
MyScale Blog
The Register - Security
The Register - Security
Engineering at Meta
Engineering at Meta
Y
Y Combinator Blog
Cyberwarzone
Cyberwarzone
L
LINUX DO - 最新话题
量子位
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
O
OpenAI News
T
The Blog of Author Tim Ferriss
S
Schneier on Security
小众软件
小众软件
The Cloudflare Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Know Your Adversary
Know Your Adversary
Microsoft Security Blog
Microsoft Security Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
L
Lohrmann on Cybersecurity
Vercel News
Vercel News

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
Integrate Sigma detection rules with Datadog Cloud SIEM
2023-08-21 · via Datadog | The Monitor blog

As organizations grow, they naturally need to analyze logs from more data sources. But as these data sources expand in number and type, it becomes more difficult for teams to scale their security detection rules to keep up with the ever-changing threat landscape. Sigma is an open source project that aims to address this challenge. By leveraging the expertise of the open source community, Sigma enables security teams to implement out-of-the-box rules that cover a wide range of threat scenarios.

We’re excited to announce that you can now integrate Sigma rules with Datadog Cloud SIEM, allowing your security teams to quickly and easily detect threats in your environment at an early stage and boost your detection landscape.

In this post you’ll learn how to:

Sending Sigma detection rules to Datadog Cloud SIEM allows your security teams to quickly and easily detect threats in your environment.

Understanding Sigma rules

The Sigma rules repository contains detection rules for popular log sources, such as AWS CloudTrail. These rules are written in a standardized format that simplifies the way rules are created, shared, and implemented across a variety of security tools.

The open source community contributes and regularly updates these rules to cover a wide range of threat scenarios, enabling security teams to continuously improve their security posture and keep up with emerging trends in the security world.

By integrating Sigma rules into Datadog Cloud SIEM, your security teams can leverage expertise from the open source security community to enhance your detection capabilities—without building detection logic from scratch.

Convert Sigma rules to Datadog format

To integrate Sigma rules with Datadog Cloud SIEM, you first need to install the Sigma CLI. Next, you will need to clone the Sigma rules repository. (Note that Datadog currently only supports AWS CloudTrail, Google Cloud, and Azure rules.) Then install the Datadog plugin using sigma plugin install datadog and enter the following command to convert a rule from Sigma format to Datadog format: sigma convert -t datadog [rule path]. For more detailed instructions, see the pySigma-backend-datadog documentation.

How to send a Sigma detection rule to Datadog Cloud SIEM

Once you have converted a Sigma rule to Datadog format, you should verify its content for accuracy before sending it to Datadog. By default, the Datadog pySigma backend maps attributes to Datadog log facets that can be used to query logs. Some rules may include field attributes that are not mapped by default, so verifying the accuracy of the field mappings within the queries is crucial for ensuring proper coverage. Unmapped fields that are not reflected in our pySigma backend’s cloud provider pipelines will be prefaced with an @ and should be updated to reflect your organization’s custom field mappings.

To check your field mappings, navigate to Logs > Configuration in the Datadog app and click the dropdown arrow next to the log source for the converted rule or query, as shown in the following screenshot. The remapper fields indicate how each field attribute is represented in Datadog’s query syntax. To learn more about standardizing log attributes, see our guide. For more information about how Datadog uses remapper processors to enrich logs, check out our documentation.

Verify attribute field mappings in Datadog Log Management after converting a Sigma rule to Datadog format.

As an example, in the screenshot above, we can see that the Azure log attribute, identity.claims.ipaddr is remapped to network.client.ip, which can be queried as @network.client.ip in Datadog. Attribute remappings help you standardize log attribute names from different sources, making it easier to search and analyze your logs. You can learn more by reading our documentation.

Once a rule has been converted and the facets have been validated for accuracy, you can import it to Datadog Cloud SIEM by sending a curl request to Datadog’s security_monitoring/rules API endpoint, as shown below. Note that you will need to pass the JSON output from the sigma convert command you ran earlier.

curl --location 'https://api.datadoghq.com/api/v2/security_monitoring/rules' \

--header 'DD-APPLICATION-KEY: ${APPLICATION_KEY}' \

--header 'Content-Type: application/json' \

--header 'DD-API-KEY: ${API_KEY}' \

--data-raw '${CONVERTED_SIGMA_RULE_AS_JSON_OBJECT}'

Once you’ve successfully sent the POST request, you can view the detection rule in your environment under Security > Cloud SIEM > Detection Rules. You can then modify your rule in the UI to fine-tune the coverage for your environment.

Editing a Sigma detection rule that has been integrated with Datadog Cloud SIEM. This rule detects if an Azure firewall has been modified or deleted.

Get started

With Datadog’s PySigma backend, you can now enhance your security detection coverage and expertise by implementing Sigma rules in Datadog Cloud SIEM. If you’re already a Datadog customer, you can start exploring the new Datadog pySigma backend now. And if you’re new to Datadog, get started today with a 14-day free trial.