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

推荐订阅源

The GitHub Blog
The GitHub Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Microsoft Security Blog
Microsoft Security Blog
J
Java Code Geeks
S
SegmentFault 最新的问题
Apple Machine Learning Research
Apple Machine Learning Research
N
Netflix TechBlog - Medium
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园_首页
宝玉的分享
宝玉的分享
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
Hugging Face - Blog
Hugging Face - Blog
量子位
Blog — PlanetScale
Blog — PlanetScale
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
阮一峰的网络日志
阮一峰的网络日志
D
Docker
罗磊的独立博客
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
云风的 BLOG
云风的 BLOG
IT之家
IT之家
MyScale Blog
MyScale Blog
Microsoft Azure Blog
Microsoft Azure Blog

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
Detect vulnerabilities in minutes with Agentless Scanning...
Pronoy Chaudhuri · 2024-04-30 · via Datadog | The Monitor blog

Security teams require complete visibility into their hosts, containers, and functions in order to detect, prioritize, and remediate their most pressing security risks. The Datadog Agent helps you achieve this visibility by collecting deep insights in your environment through logs, distributed traces, infrastructure metrics, and other key telemetry.

As a complement to using the Datadog Agent for finding security risks in your environment, we are excited to announce the launch of Datadog Agentless Scanning.

Datadog Agentless Scanning provides visibility into risks and vulnerabilities within your hosts, running containers, and serverless functions—all without requiring teams to install agents on every host or where agents cannot be installed. This enables you to comprehensively monitor entire cloud accounts within minutes, in addition to misconfigurations, identity risks, and other capabilities provided by Datadog Cloud Security.

Agentless Scanning is now generally available for AWS cloud environments. In this post, we’ll show you:

  • How Agentless Scanning works

  • Best practices for getting started with Agentless Scanning

  • How to roll out the Datadog Agent across your cloud infrastructure to gain deep visibility without compromising coverage

How Agentless Scanning works

How Agentless Scanning works

Datadog’s Agentless scanners are EC2 instances that run within your environment. When they perform a scan, they analyze the hosts and Lambda functions that are deployed on your cloud accounts to identify all of their associated packages and running containers.

First, Datadog schedules a scan and sends a list of resources to an Agentless scanner through Remote Configuration. This initial list includes all hosts and Lambda functions in the associated cloud account. Before the list is read by the scanner, Datadog filters out:

  • Any cloud resources running the Datadog Agent with Cloud Security enabled

  • Any cloud resources to which the user has added the DatadogAgentlessScanner:false tag

Then, the Agentless scanner downloads and analyzes the dependencies of all Lambda functions it scans. In addition, the scanner makes snapshots of all host root volumes and identifies their packages and running containers. It will also analyze the Amazon Machine Images (AMIs) used in your cloud accounts; because a single AMI is typically used across many instances, the ability to identify and fix issues at the AMI level helps make remediations more impactful.

After a snapshot is read, it is promptly deleted and the Agentless scanner only forwards the list of packages it uncovers back to Datadog—no customer code or snapshots, encrypted or unencrypted, are sent back to Datadog. Often, such a list of packages is referred to as a Software Bill of Materials (SBOM).

Vulnerabilities found by Agentless Scanning in Datadog Cloud Security

Finally, Datadog checks these packages, containers, and AMIs against a list of known open source vulnerabilities and surfaces any findings via Cloud Security. Cloud Security leverages insights from security research alongside observability data from your infrastructure to prioritize vulnerabilities, taking into account the exploitability of the vulnerability and whether it is running in a production environment. You can find vulnerabilities uncovered by Agentless scanners by navigating to the Cloud Security Explorer view and filtering your results by the origin:”Agentless scanner” tag.

Best practices for getting started with Agentless Scanning

Now that we understand how Agentless Scanning works, we’ll look at how you can deploy Agentless scanners across your AWS cloud environments.

Option 1: Cross-account scanning

With this option, Agentless scanners are deployed to a single cloud account and distributed across multiple regions within the account. For example, if you have four AWS accounts spanning five regions, this option would deploy five scanners—one scanner per region in the AWS account you specify.

As a result, this deployment model grants Agentless scanners visibility across multiple accounts so as to avoid the high networking costs associated with cross-region scanning. Each scanning instance scans multiple accounts within the same region where it is located.

Cross-account scanning

We recommend this option for most organizations, as it is cost-effective and makes it easy to manage your Agentless scanners since they are in one account. You can either create a dedicated account for your Agentless scanners or choose an existing one. In addition, you can perform scans on the account where the Agentless scanners are located.

Option 2: Same-account scanning

This option involves deploying a single Agentless scanner to each account. For example, if you have three AWS accounts spanning four regions, this option would deploy three scanners—one scanner per AWS account.

We recommend this option if your organization is sensitive to granting cross-account permissions. Note that this approach can be more expensive since it will require each Agentless scanner to perform cross-region scans for the account it runs in.

Same-account scanning

To get started with either option using CloudFormation or Terraform, or to create your own custom deployment model, view our documentation.

Agentless Scanning and the Datadog Agent

Agentless Scanning makes it easy to get started with Cloud Security in minutes, so you can get visibility into risks across your cloud resources right away, with minimal configuration and upkeep. However, we still recommend installing the Datadog Agent where and when possible. In addition to getting results in real time instead of on a schedule, deploying the Agent will enable you to gain additional context through Cloud Security, including suspicious file, process, and network activity signals related to your cloud workloads.

We recommend that after enabling Agentless Scanning, you start to install the Datadog Agent on your core assets—Fleet Automation can help you simplify this process, especially if you are working with complex environments that contain many hosts. This way, you can work toward complete vulnerability coverage while receiving real-time updates on the health of your critical cloud resources.

Secure your environment in minutes with Agentless Scanning for Datadog Cloud Security

Agentless Scanning for Datadog Cloud Security is now generally available for AWS cloud environments—check out our documentation to get started. You can also check out the Cloud Security documentation for more information about getting started with Datadog Cloud Security. If you aren’t already a Datadog user, you can sign up for a 14-day free trial.