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

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hacker News: Front Page
P
Palo Alto Networks Blog
T
ThreatConnect
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
T
True Tiger Recordings
P
Privacy & Cybersecurity Law Blog
B
Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
F
Full Disclosure
Hacker News: Ask HN
Hacker News: Ask HN
C
Comments on: Blog
Microsoft Azure Blog
Microsoft Azure Blog
C
Cybersecurity and Infrastructure Security Agency CISA
Microsoft Security Blog
Microsoft Security Blog
博客园 - 【当耐特】
N
News and Events Feed by Topic
NISL@THU
NISL@THU
腾讯CDC
雷峰网
雷峰网
Security Latest
Security Latest
李成银的技术随笔
M
Microsoft Research Blog - Microsoft Research
L
LangChain Blog
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Check Point Blog
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
博客园 - Franky
N
News | PayPal Newsroom
V
V2EX
A
About on SuperTechFans
The Register - Security
The Register - Security
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google Online Security Blog
Google Online Security Blog
MyScale Blog
MyScale Blog
Cisco Talos Blog
Cisco Talos Blog
Vercel News
Vercel News
WordPress大学
WordPress大学
C
Cyber Attacks, Cyber Crime and Cyber Security
The Hacker News
The Hacker News
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
爱范儿
爱范儿
A
Arctic Wolf
L
LINUX DO - 最新话题
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Datadog | The Monitor blog

Reduce CVE noise with OpenVEX assessments in Datadog How we made a SQL query optimization agent 59% more accurate using autoresearch and LLM Observability How to audit and clean up monitors effectively Diagnose slow PostgreSQL queries faster with explain plan correlation Explore Datadog metrics with Natural Language Queries Toto 2.0: Time series forecasting enters the scaling era Simplify micro-frontend observability with Datadog RUM Attribute AI costs across providers with Datadog Cloud Cost Management Diagnose and resolve database performance issues faster with Database Investigator Datadog for Government achieves FedRAMP® High certification Analyze cloud costs with flexible spreadsheets in Datadog Sheets Inside Datadog’s AI Research Lab: Meet two PhD candidates behind Toto Connect triage and investigation in a single workflow with Datadog Cloud SIEM This Month in Datadog - April 2026 Monitor and optimize Supabase query performance with Datadog Database Monitoring Add dynamically updating context to logs with Reference Tables and Observability Pipelines Introducing ARFBench: A time series question-answering benchmark based on real incidents The product signal latency gap slowing your growth Test network paths with TCP, UDP, and ICMP in Datadog Turn developer feedback into operational insight with Datadog Forms and Sheets How to investigate cloud credential compromise with Bits AI Security Analyst Evaluate, optimize, and secure your Google Cloud AI stack with Datadog Bringing observability data hosting to the UK on AWS Identify and fix code issues faster with Datadog’s Azure DevOps Source Code integration Steganography at scale: Embedding share URLs in Datadog widget screenshots Every team should be A/B testing Centralize observability management with Datadog Governance Console Spotting CI/CD misconfigurations before the bots do: Securing GitHub Actions with Datadog IaC Security Route OTel data from AI apps to ClickHouse and Datadog using Observability Pipelines Manage service tracing across hosts with Single Step Instrumentation rules Offline evaluation for AI agents: Best practices Detect runtime threats in Python Lambda functions with Datadog AAP 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 How we built a real-world evaluation platform for autonomous SRE agents at scale 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 When upserts don't update but still write: Debugging Postgres performance at scale 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 Closing the verification loop: Observability-driven harnesses for building with agents When an AI agent came knocking: Catching malicious contributions in Datadog’s open source repos Closing the verification loop, Part 2: Fully autonomous optimization 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 Designing MCP tools for agents: Lessons from building Datadog's MCP server 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 Fine-tune Toto for turbocharged forecasts 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 How we reduced the size of our Agent Go binaries by up to 77% 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
Evolving security at Datadog: How we designed roles to support a growing organization
2025-12-08 · via Datadog | The Monitor blog

Defining success looks different for security organizations than it does for product, infrastructure, and other engineering teams. The latter group can often point to tangible outcomes, such as newly shipped features or performance improvements. Security orgs succeed when risks are lowered and the company’s posture improves over time, which are results that aren’t as easy to recognize but still valuable.

This gap in expectations becomes harder to ignore as the company grows. Both new technologies and shifting priorities, such as building edge environments and agentic AI systems, naturally expand a company’s attack surface. Without clear direction, a security org will struggle to support the larger organization effectively. When we combined Datadog’s SRE and security groups, we had to rethink what adapting to growth looks like. We learned that it comes down to three priorities:

A resilient security organization requires developing leaders and systems that can tackle these priorities, especially considering the fast pace of AI adoption and the rate at which cloud environments are growing more complex. When their leaders work together, security orgs can respond to new risks and adapt to industry trends without interfering with the goals of the larger organization.

Creating reliable systems that scale with the company

A primary focus for security organizations is building strong identity, data, and infrastructure guardrails that can grow with the company. This makes it possible to respond to risks, adopt new technologies, and scale safely without slowing down important work. One of the primary challenges with scaling efficient systems is continually keeping them up-to-date. This requires security leaders to translate long-term goals into repeatable workflows.

How Datadog’s security leaders create secure-by-default systems

At Datadog, each level of security leadership plays a distinct role in scaling reliable, secure systems. Identities in particular are a critical part of building these systems as they shape the perimeter of cloud environments. Additionally, data perimeters are quickly becoming the mechanism for ensuring that identities, resources, and networks interact safely.

We rely on the following leaders to help us accomplish our goals in these growing areas of focus:

  • Engineering managers (EMs) define team priorities and implement security guardrails for services
  • Directors translate organization-wide goals into policies that teams can use to deploy guardrails consistently
  • Vice presidents (VPs) anticipate bottlenecks by funding tooling and system improvements before gaps appear

EMs play an important part in implementing strong perimeters for their services while ensuring their teams still have autonomy. For example, EMs in Datadog’s Internal Trust and Core Observability teams collaborated on building an auto-approved roles system to grant engineers necessary permissions while reducing the number of admin-level users in our systems. This workflow enabled us to easily apply security best practices consistently throughout our platform.

Beyond building systems, EMs also work with directors and VPs to define and track meaningful success metrics, such as mean time to detect and the number of incidents and threats affecting their services. For example, tracking the false positive rate of our detection signals enables us to determine their accuracy. A consistently low percentage of false positives indicates that we have high-fidelity detection signals. If that rate increases at any point, EMs will work with their teams to determine the root cause, such as outdated signals that don’t account for changing indicators of compromise.

Ensuring that specialized teams stay connected and effective

A growing security organization naturally develops specialized domains—including application, platform, cloud security, detection and response, and customer trust—in parallel. Without bridging these domains, teams risk duplicating effort and creating inconsistent standards. This means that in order to maintain trust and consistency as the organization continues to grow, security leadership needs to actively guide investment in these domains. This enables security orgs to build the capabilities that the larger organization needs for faster, safer development. It also makes a compelling case for security’s role and overall involvement in product design and engineering.

How Datadog’s security leaders keep teams connected

We’ve found that ensuring our teams move in the same direction requires clear ownership, shared frameworks, and leadership transparency. Each leadership level builds on the other to reduce the risk of creating siloes:

  • EMs define clear team boundaries within their domains so teams can collaborate without duplicating work or introducing inconsistent standards
  • Directors maintain shared policies and metrics that help each domain leader remain up-to-date on priorities, standards, and progress
  • VPs ensure the priorities for each security domain match and support other company goals

Directors play an important role in this investment. They own and define the shared tools and policies, such as compliance baselines, for their teams. These resources enable them to connect business priorities to security goals and ensure that all domains within the org understand how their work reinforces the company’s area of focus.

Success depends on leaders who communicate clearly and set appropriate expectations for their teams. Deciding when to favor progress over perfection speaks to how security leaders need to balance speed, safety, and focus when company priorities constantly change. For example, as supply chain risks become a bigger concern for companies, security orgs need to consider how to update their existing policies and tooling to meet demand. Enforcing provenance, such as signing and vetting all supply chain artifacts, is one way we’ve helped our teams move quickly and safely as they adopt new technologies.

Anticipating what’s next

Growing a security organization requires scaling existing systems in addition to preparing for what’s next. This means understanding how to balance immediate needs, such as emerging security trends, with preparing for the future. There will always be new trends or areas of concern for a security organization to respond to, so their ability to adapt should be second nature. The challenge is in using new technologies to enhance security without introducing unmanaged risk.

How Datadog’s security leaders prepare for the future

We’ve found that our leadership is most successful when they proactively invest in new technologies. Adopting AI technology is one example of a growing priority for companies. At Datadog, the following leadership levels help shape the way we use AI responsibly:

  • EMs embed AI security and privacy controls into existing CI/CD pipelines so new technologies are safely integrated from the start
  • Directors develop model governance guidelines so LLMs and their training data are thoroughly vetted
  • VPs define risk tolerance, investment priorities, and organization-wide policies for responsible AI adoption

By embedding AI natively, security orgs can protect training data, models, and their output while addressing risks early on. This gives teams the confidence to use AI responsibly and keep up with business demands. For example, a VP might champion the integration of AI-powered anomaly detection into existing monitoring pipelines—a direction our teams have taken through LLM-assisted triage for detection signals, which allows us to significantly reduce manual reviews.

Integrating early, governing clearly, and designing for security by default applies to any new capability or tool a company adopts. At Datadog, we measure success for this in part by routinely reviewing our detection rules and security baselines to ensure they account for new vulnerabilities and threats. We do this by working closely with our security researchers, who are always working to stay on top of emerging security risks, to ensure our detection coverage and playbooks are complete.

Building a security organization that scales efficiently

Security organizations will always need to adapt to evolving threats, technologies, and company goals. Success requires scaling systems to meet demands, ensuring specialized teams remain effective, and addressing existing security risks while preparing for the future. To make this possible, we established leadership roles with clear ownership, which enables teams to operate independently without drifting away from the org’s goals.

To read more about how Datadog’s security organization operates, you can check out these posts about combining our SRE and security groups and our cloud infrastructure security playbook.

If you don’t already have a Datadog account, you can sign up for a free 14-day trial.