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

推荐订阅源

freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Jina AI
Jina AI
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Troy Hunt's Blog
T
The Exploit Database - CXSecurity.com
Microsoft Security Blog
Microsoft Security Blog
V
Visual Studio Blog
F
Fortinet All Blogs
博客园_首页
P
Proofpoint News Feed
V
Vulnerabilities – Threatpost
The Cloudflare Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
H
Heimdal Security Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
A
About on SuperTechFans
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
AI
AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
S
Security Affairs
The Register - Security
The Register - Security
S
Security @ Cisco Blogs
Hugging Face - Blog
Hugging Face - Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 聂微东
Schneier on Security
Schneier on Security
WordPress大学
WordPress大学
Google DeepMind News
Google DeepMind News
GbyAI
GbyAI
T
Tailwind CSS Blog
Hacker News: Ask HN
Hacker News: Ask HN
W
WeLiveSecurity
D
Docker
L
LangChain Blog
B
Blog RSS Feed
The Last Watchdog
The Last Watchdog
Cloudbric
Cloudbric
TaoSecurity Blog
TaoSecurity Blog
N
Netflix TechBlog - Medium
酷 壳 – CoolShell
酷 壳 – CoolShell
I
InfoQ
The Hacker News
The Hacker News
AWS News Blog
AWS News Blog
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
宝玉的分享
宝玉的分享
I
Intezer
云风的 BLOG
云风的 BLOG
V2EX - 技术
V2EX - 技术
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
Key takeaways from the U.S. executive order on cybersecurity
Ari Shahar · 2021-07-20 · via Datadog | The Monitor blog

On May 12, 2021, President Biden signed an executive order calling on federal agencies to improve their cybersecurity practices. Following the recent SolarWinds and Colonial Pipeline attacks, it is clear that security incidents can severely impact the economy and civilians’ day-to-day lives and that cybersecurity needs to be a high-priority issue.

We encourage you to read the full executive order. In this post, we’ll summarize the key takeaways of the executive order and highlight the areas that we feel are most relevant to the DevSecOps space.

From a high level, the executive order includes several core statements:

  • Cybersecurity is a top priority and future government contracts will require agencies and vendors to work more closely with each other and share more security-related information.

  • Supply-chain security, security monitoring and operations, and endpoint detection and response (EDR) are becoming increasingly important.

  • Federal agencies will continue moving to cloud services with adherence to Zero-Trust architecture, which includes the use of multi-factor authentication (MFA) and encryption of data at rest and in transit.

  • Agencies will continue using and investing resources in FedRAMP.

  • Agencies will begin implementing steps toward cross-agency vulnerability detection and incident response.

With these points in mind, we’ll look at each of the executive order’s sections in more detail.

Section 1: Policy

The administration made it clear that cybersecurity is a top priority and essential to national and economic security. They strongly encourage partnership between the public and private sectors to create a more secure cyberspace. Additionally, all federal information systems should meet the standards and requirements that the executive order lists.

Section 2: Removing barriers to sharing threat information

A key part of improving incident detection and response is removing contractual barriers with service providers—such as the major cloud providers—that prevent or limit the sharing of information relevant to the security of federal information systems.

As cloud adoption accelerates, information systems have become more connected and the technology stack has become more modular—each component is actually composed of smaller parts that can be owned by many different service providers. In order to act with clarity and conduct effective security incident investigations, the administration will need to remove legal barriers that would hinder the ability to get visibility across all of these tools.

This section lays out requirements that will likely be included in future federal agency–issued contracts for products and services. Government vendors must:

  • Collect and store data relevant to security prevention, detection, response, and investigation

  • Share data about security incidents and threat intelligence with contracted agencies

  • Collaborate with federal cybersecurity agencies in investigations and incident response

  • Promptly report cyber incidents to contracted agencies and the Cybersecurity and Infrastructure Security Agency (CISA)

Section 3: Modernizing federal government cybersecurity

This section emphasizes the urgency of improving the government’s security posture and lays out several key steps that federal agencies must take to do so. These include:

  • Continuing to implement Zero Trust Architecture

  • Fully adopting multi-factor authentication (MFA) and encryption of data at rest and in transit

  • Accelerating adoption of secure cloud services, including infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS), and software-as-a-service (SaaS)

The spirit of the executive order encourages agencies to continue their cloud adoption journey—with a particular emphasis on security best practices—and to keep seeing cost savings and operational benefits as a result.

Fully adopting MFA, for example, will allow agencies to better restrict access to their newly adopted cloud services. SMS and authenticator apps are frequently used to implement multi-factor authentication, but some companies like Datadog also leverage a physical authentication factor (e.g., a YubiKey) to better protect against phishing. To learn more about how Datadog used YubiKeys to fully adopt MFA across our entire workforce, read this Yubico case study.

In addition, the CISA, the Office of Management and Budget (OMB), the National Security Advisor, and the General Services Administration’s (GSA) FedRAMP Program Management Office will form requirements for cloud service providers to be included in the modernization efforts. FedRAMP authorization will be an integral part moving forward, and there will be an effort to streamline FedRAMP authorization by providing additional training, standardization, and automation (which already began with the publication of the Open Security Controls Assessment Language).

The FedRAMP Program Management Office will also review other compliance frameworks as potential substitutes for aspects of FedRAMP authorization, which should allow for more flexibility in meeting some FedRAMP requirements. This should also allow agencies to choose from a greater number of approved IaaS, PaaS, and SaaS solutions, such as Datadog, to help them modernize and build new services.

Section 4: Enhancing software supply chain security

Over the past decade, more services have migrated to the cloud, software complexity and delivery pace have increased, and reliance on third-party software packages and tools has become commonplace. This shift requires us to make additional investments to ensure that every component of our supply chain is secure, from the initial build all the way to the user-facing product.

The SolarWinds attack, which has been attributed to Russia, impacted nine federal agencies as well as other vendors that work with the federal government, such as Microsoft and Intel. The length and impact of this cyberattack and espionage campaign caught the government unprepared. Now, the government is taking steps to prevent and mitigate future supply-chain attacks.

The National Institute of Standards and Technology (NIST) is partnering with FedRAMP PMO to provide guidance for securing supply chains, including:

  • Use of separate environments for development and production

  • Use of multi-factor and risk-based authentication

  • Use of encryption across the board

  • Responding quickly to incidents by implementing effective monitoring (i.e., automated alerts)

To help monitor the security of your supply chain, the Datadog Cloud Security Platform delivers real-time threat detection and continuous configuration audits across applications, hosts, containers, and cloud infrastructure. Datadog automatically detects MFA and encryption misconfigurations and lets you immediately initiate a response through out-of-the-box integrations.

In order for the end customer to leverage a product in a secure way and to understand the additional security risk associated with using that product, vendors will make software bills of material (SBOM) and vulnerability disclosures available to agencies. The Secretary of Commerce has published minimum requirements for the SBOM. In alignment with this guidance, you can read our engineering blog post to learn about the pioneering work Datadog has done to secure its supply chain from SolarWinds-style attacks—and how you may apply it to your own supply chain.

Section 5: Establishing a Cyber Safety Review Board

The Department of Homeland Security (DHS) will establish a Cyber Safety Review Board, with board members from the Department of Defense (DoD), National Security Agency (NSA), Federal Bureau of Investigation (FBI), Department of Justice (DOJ), CISA, and private-sector cybersecurity and software suppliers. The purpose of this board is to convene in the event of significant cybersecurity incidents and assess recommended steps for the administration’s response.

Section 6: Standardizing the federal government’s playbook for responding to cybersecurity vulnerabilities and incidents

We believe that one of the administration’s primary goals is to have a centralized overview of vulnerabilities and incidents across all agencies. In the case of another incident like the SolarWinds attack, this unified visibility will allow the government to coordinate remediation and investigation efforts across agencies faster and more effectively.

To that end, the executive order requires that agencies standardize the way in which they identify, remediate, and recover from vulnerabilities and incidents. DHS will lead this effort in collaboration with other agencies and create a playbook for vulnerability and incident response activities.

Section 7: Improving detection of cybersecurity vulnerabilities and incidents on federal government networks

Mean time to detection (MTTD) is a key performance indicator that security professionals track when evaluating the effectiveness of incident detection and response. Early detection can help contain and reduce the impact of cyber incidents. In order to strengthen agencies’ early-detection capabilities, the federal government will issue recommendations for increasing visibility and threat detection across government networks and endpoints. Agencies will also be required to execute an endpoint detection and response (EDR) initiative and proactively hunt for threats.

Agencies and public sector partners can leverage Datadog to hunt threats across their environment. The Cloud Security Platform is built on top of Datadog’s observability platform, which facilitates seamless collaboration between Security and DevOps teams and aligns them to shared organizational goals. If you’d like to learn more about how Datadog can help you proactively identify threats in authentication logs, read our blog post.

Logs are an invaluable data source for security investigations. The director of the OMB will publish requirements to ensure that agencies implement specific logging and log management processes. These will define what events should be logged, the required log retention period, and the appropriate cryptographic protections for logs.

Section 9: National Security Systems

The executive order’s recommendations and requirements apply primarily to agencies under the Federal Civilian Executive Branch (FCEB). However, the order also requires the DoD and intelligence agencies—which have unique cybersecurity-related concerns—to come up with requirements that are equivalent to or exceeding those in the order. These agencies are expected to formalize these requirements in a future National Security Memorandum.

Looking ahead

This executive order establishes a new baseline for agencies’ cybersecurity requirements. We anticipate that we will continue to receive new guidance with further specifications, similar to what we’ve already seen in the ransomware memorandum that was recently issued by the Deputy Assistant to the President and Deputy National Security Advisor for Cyber and Emerging Technology.

The administration has made it clear that improving the cybersecurity of the nation is a high priority, and we look forward to continuing to support the public sector and partners in the adoption of the cloud and enhancement of their cybersecurity capabilities.