Skip to content

Commit 7df3b57

Browse files
committed
WIP
1 parent 68ddbef commit 7df3b57

File tree

6 files changed

+140
-42
lines changed

6 files changed

+140
-42
lines changed

content/en/glossary/terms/remote_configuration.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ synonyms:
66
core_product:
77
- apm
88
- appsec
9+
- workload protection
910
- observability pipelines
1011
---
1112
Remote Configuration enables users to remotely configure and change the behavior of Datadog components (for example Agents, tracing libraries, and Observability Pipelines Workers) deployed in their environment.

content/en/security/workload_protection/_index.md

Lines changed: 45 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -32,68 +32,71 @@ cascade:
3232

3333
---
3434

35-
Workload Protection monitors file, network, and process activity across your environment to detect real-time threats to your infrastructure. As part of the Datadog platform, you can combine the real-time threat detection of Workload Protection with metrics, logs, traces, and other telemetry to see the full context surrounding a potential attack on your workloads.
35+
## Overview
3636

37-
## Detect threats to your production workloads in real-time
37+
Datadog Workload Protection provides real-time visibility and defense for your infrastructure by continuously monitoring file, network, and process activity across your environments. It detects threats as they occur, helping you identify, investigate, and stop malicious behaviors before they impact your workloads.
3838

39-
Monitor file and process activity at the kernel level to detect threats to your infrastructure, such as Amazon EC2 instances, Docker containers, and Kubernetes clusters. Combine Workload Protection with [Cloud Network Monitoring][9] and detect suspicious activity at the network level before a workload is compromised.
39+
### Actionable, prioritized and contextual threat detection in real-time
4040

41-
Workload Protection Threats uses the Datadog Agent to monitor your environment. If you don't already have the Datadog Agent set up, [start with setting up the Agent][2] on a [supported operating system][1]. There are four types of monitoring that the Datadog Agent uses for Workload Protection:
41+
Workload Protection relies on event correlation to surface contextualized and prioritized alerts. As part of the Datadog Security platform, Workload Protection correlates runtime threat detection with findings from misconfiguration scans, vulnerability assessments, and code security. This deep integration enables you to link runtime attacks with preexisting weaknesses, providing the complete context you need to investigate and remediate security incidents. Because Workload Protection is built on the Datadog platform, it also connects with your infrastructure telemetry — including metrics, traces, and logs — so you can understand the scope and impact of threats across your systems. Simply put, investigations are enriched with full context so you can easily reconstruct the entire attack story from detection to resolution.
4242

43-
1. **Process Execution Monitoring** to watch process executions for malicious activity on hosts or containers in real-time.
44-
2. **File Integrity Monitoring** to watch for changes to key files and directories on hosts or containers in real-time.
45-
3. **DNS Activity Monitoring** to watch network traffic for malicious activity on hosts and containers in real-time.
46-
4. **Kernel Activity Monitoring** to watch for kernel-layer attacks like process hijacking, container breakouts, and more in real-time.
43+
{{< img src="security/workload_protection/workload_protection_signal.jpg" alt="Workload Protection signal with an investigation and a threat timeline" width="100%">}}
4744

48-
<!-- {{< img src="security/csm/csm_overview_3.png" alt="The Security Inbox on the Cloud Security Management overview shows a list of prioritized security issues to remediate" width="100%">}} -->
45+
### Response, remediation and hardening capabilities
4946

50-
## Proactively block threats with Active Protection
47+
You can also take action directly from the Datadog App to block malicious behaviors, trigger remediation workflows, or integrate with your existing response pipelines. Whether your goal is to enforce compliance, strengthen your runtime security posture, or address workload hardening use cases, Workload Protection can take action on your behalf to keep your environments secure and resilient.
5148

52-
By default, all OOTB Agent crypto mining threat detection rules are enabled and actively monitoring for threats.
49+
### Beyond threat detection: expanded use cases
5350

54-
[Active Protection][10] enables you to proactively block and terminate crypto mining threats identified by the Datadog Agent threat detection rules.
51+
Workload Protection is not limited to runtime threat detection. Many organizations leverage it across a range of security and operational use cases:
5552

56-
## Manage out-of-the-box and custom detection rules
53+
- **Compliance Validation:** Workload Protection helps you validate compliance with regulatory frameworks such as PCI, FedRAMP, and SOC 2 by continuously monitoring runtime activity for policy violations, risky configurations, and unauthorized changes.
5754

58-
Workload Protection Threats comes with more than 50 out-of-the-box detection rules that are maintained by a team of security experts. The rules surface the most important risks so that you can immediately take steps to remediate. Agent expression rules define the workload activities to be collected for analysis while backend detection rules analyze the activities and identify attacker techniques and other risky patterns of behavior.
55+
- **Runtime Security Posture:** Workload Protection improves your security posture by identifying unsafe runtime practices and sensitive configuration drifts, helping you catch weaknesses before they can be exploited.
5956

60-
Set up [Cloud Security][1] with {{< tooltip glossary="Remote Configuration" case="title" >}} to automatically deploy new and updated rules to the Agent. [Customize the rules][5] by defining how each rule monitors process, network, and file activity, [create custom rules][6], and [set up real-time notifications](#set-up-real-time-notifications) for new signals.
57+
- **Infrastructure Monitoring:** Acting as a Swiss army knife for runtime observability, Workload Protection enables teams to track any kind of runtime behavior — security-related or otherwise. From debugging custom workloads to monitoring system-level processes and remote user sessions, Workload Protection offers deep, real-time visibility into how your environments operate.
6158

62-
<!-- {{< img src="security/cws/threats_detection_rules.png" alt="Workload Protection detection rules in the Datadog app" width="100%">}} -->
59+
{{< img src="security/workload_protection/k8s_remote_access_image.jpg" alt="Breakdown of Kubernetes remote user sessions" width="100%">}}
6360

64-
## Set up real-time notifications
61+
### Detection Rules, automation, and fleet management
6562

66-
[Send real-time notifications][3] when a threat is detected in your environment, so that your teams can take action to mitigate the risk. Notifications can be sent to [Slack, email, PagerDuty, webhooks, and more][4].
63+
Workload Protection comes out of the box (OOTB) with a comprehensive set of security rules and visibility tools. It includes over 350 agent rules and 200 detection rules, carefully designed to cover most of the MITRE ATT&CK tactics and techniques used by attackers today. This extensive coverage allows teams to detect and mitigate threats across various stages of exploitation, even if they lack the time or specialized expertise to craft detection rules themselves. To complement these detections, the platform provides in-app coverage maps that help users visualize what’s deployed, where it’s active, and what’s protected — ensuring complete and transparent visibility across the entire infrastructure.
6764

68-
Use template variables and Markdown to [customize notification messages][5]. Edit, disable, and delete existing notification rules, or create new rules and define custom logic for when a notification is triggered based on severity and rule type.
65+
For advanced detection and response capabilities, our platform enables custom rule writing, correlation, and automated actions. It supports over 40 event types on Linux and Windows, spanning process, file system, kernel, and network activities. Security teams can define in-agent state machines, enabling contextual detection logic that triggers alerts only on meaningful and complex indicators of compromise (IOCs).
6966

70-
## Investigate and remediate security signals
67+
Managing and scaling protection across large environments is simplified with powerful agent fleet and rule management capabilities. Using {{< tooltip glossary="Remote Configuration" case="title" >}}, teams can push agent rules directly from the UI and receive automatic threat definition updates from Datadog to stay current with evolving attack techniques. The platform also offers flexible configuration and customization options through the UI, CLI, or Terraform, allowing security teams to tailor their detection strategy and deployment workflows to their specific operational needs.
7168

72-
Investigate and triage security signals in the [Signals Explorer][8]. View detailed information about the impacted files or processes, related signals and logs, and remediation steps.
69+
## High level architecture overview
7370

74-
<!-- {{< img src="security/cws/signals_explorer.png" alt="CSM Signals Explorer page" width="100%">}} -->
71+
Workload Protection is built on top of the Datadog Agent, which continuously collects real-time runtime telemetry from your workloads. Agent rules determine which security-relevant events are streamed to Datadog for centralized analysis. Once ingested, these events are processed by backend detection and finding rules, which analyze the data to generate detailed, prioritized Signals or Findings.
7572

76-
{{< callout url="https://docs.google.com/forms/d/e/1FAIpQLSfzQARsTPr3tiJDnS_4bGx7w35LDfAbGUggaUzHYoL0dIUMWQ/viewform" btn_hidden="false" header="Active Protection">}}
73+
Using Remote Configuration, you can manage agent rule deployments and trigger response or remediation actions directly from the Datadog app. In addition, Workload Protection integrates with the Datadog Terraform provider, allowing you to define, version, and maintain your rules as code outside the app.
7774

78-
Datadog is introducing a new feature called Active Protection to address the crypto threats detected in your environment automatically. Active Protection is in Preview. Fill out the form to request access.
79-
{{< /callout >}}
75+
{{< img src="security/workload_protection/workload_protection_architecture.jpg" alt="Workload Protection architecture overview" width="100%">}}
8076

81-
## Get started
77+
## Next steps
8278

83-
{{< whatsnext >}}
84-
{{< nextlink href="/security/cloud_security_management/setup/">}}Complete setup and configuration{{< /nextlink >}}
85-
{{< nextlink href="/account_management/rbac/permissions/#cloud-security-platform">}}Datadog role permissions for Workload Protection{{< /nextlink >}}
86-
{{< nextlink href="/security/workload_protection/workload_security_rules">}}Learn about Workload Protection detection rules{{< /nextlink >}}
87-
{{< nextlink href="/security/default_rules/#cat-workload-security">}}Start using out-of-the-box Workload Protection detection rules{{< /nextlink >}}
88-
{{< nextlink href="/getting_started/cloud_security_management">}}Getting Started with Cloud Security Management{{< /nextlink >}}
89-
{{< /whatsnext >}}
79+
### Getting started
80+
81+
Begin by exploring our Getting Started guide, which introduces the high-level architecture of Workload Protection. You’ll learn about supported environments, how to deploy the agent, and how to experiment with Workload Protection’s features using our playground scripts.
82+
83+
### Detect and Monitor
84+
85+
Dive into our Detect and Monitor resources to understand how agent events translate into Workload Protection signals and findings. These pages will help you explore the built-in (OOTB) detections and guide you in creating your own detection logic.
86+
87+
### Investigate and Triage
9088

91-
[1]: /security/cloud_security_management/setup/
92-
[2]: /agent/
93-
[3]: /security/notifications/
94-
[4]: /security/notifications/#notification-channels
95-
[5]: /security/notifications/#detection-rule-notifications
96-
[6]: /security/workload_protection/agent_expressions
97-
[8]: /security/workload_protection/security_signals
98-
[9]: /network_monitoring/performance/
99-
[10]: /security/workload_protection/guide/active-protection
89+
Visit our Investigate and Triage sections to discover the different explorers and in-app views available in Workload Protection. These pages will help you make the most of the events, signals, and findings generated by the platform.
90+
91+
### Respond and Report
92+
93+
Head to our Respond and Report pages to learn how to configure Workload Protection for automated remediation and team performance reporting. You’ll find guidance on mitigating threats and tracking metrics like Mean Time to Remediation (MTTR).
94+
95+
### Guides
96+
97+
{{< whatsnext desc="We've put together use case driven examples to help you discover and learn about Workload Protection:" >}}
98+
{{< nextlink href="/security/workload_protection/guide/active-protection" >}}Proactively block crypto mining threats with Active Protection{{< /nextlink >}}
99+
{{< nextlink href="/security/workload_protection/guide/tuning-rules" >}}Best Practices for Fine-Tuning Workload Protection Security Signals{{< /nextlink >}}
100+
{{< nextlink href="/security/workload_protection/secl_auth_guide" >}}Writing custom rule expressions{{< /nextlink >}}
101+
{{< nextlink href="/security/workload_protection/guide/ebpf-free-agent" >}}Threat Detection for Linux Without eBPF Support{{< /nextlink >}}
102+
{{< /whatsnext >}}
Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: Getting started with Workload Protection
3+
disable_toc: false
4+
---
5+
6+
This page will guide you through the process of enabling Workload Protection in your environment. You’ll start by activating Workload Protection in the Datadog app, then deploy the Datadog Agent to begin collecting runtime telemetry. Once setup is complete, you can explore Workload Protection’s capabilities using our playground scripts. Optionally, you can also enable Remote Configuration for centralized rule management and request access to enforcement capabilities to take automated remediation actions directly with the Datadog platform.
7+
8+
9+
## 1) Enable Workload Protection from the Datadog app
10+
11+
To get started with Workload Protection, you need to enable the Workload Protection product from the Datadog App. To do so, log in to your Datadog account, and follow the [Get Started][1] steps.
12+
13+
<div class="alert alert-info">Activating Workload Protection requires the Org Management <a href="https://docs.datadoghq.com/account_management/rbac/permissions/">permission</a>.</div>
14+
15+
## 2) Deploy the Datadog Agent
16+
17+
Workload Protection relies on the Datadog Agent to monitor your workloads and collect security relevant events for threats detection and security posture monitoring. You'll find below the supported environments and deployment methods
18+
19+
## Remote configuration
20+
21+
You can enable [Remote Configuration][3] for Workload Protection.
22+
23+
Remote Configuration can be used to:
24+
- Automatically stay up to date on the latest security detections
25+
- Block attackers and attacks
26+
27+
Remote Configuration can be set up using the Workload Protection [Get Started][1] steps in your Datadog account.
28+
29+
<div class="alert alert-info">To enable Remote Configuration, ask your admin for the <strong>API Keys Write</strong> permission.</div>
30+
31+
## Agent setup options for Workload Protection
32+
33+
Workload Protection supports **Agent-based-only deployments**.
34+
35+
## Supported deployment types
36+
37+
The following table summarizes Workload Protection relative to deployment types.
38+
39+
| | Docker | Kubernetes | Linux | Amazon ECS/EKS | Windows | AWS Fargate ECS/EKS | AWS Account | Azure Account | GCP Account | Terraform |
40+
|------------------------|-----------|------------|-----------|----------------|-----------|---------------------|-------------|---------------|-------------|-----------|
41+
| Agent Required (7.46+) | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | | | |
42+
| Workload Protection | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | | | |
43+
44+
45+
## Supported Linux distributions
46+
47+
Workload Protection supports the following Linux distributions:
48+
49+
| Linux Distributions | Supported Versions |
50+
|---------------------------------------------------------------|-------------------------|
51+
| Ubuntu LTS | 18.04, 20.04, 22.04 |
52+
| Debian | 10 or later |
53+
| Amazon Linux 2 | Kernels 4.14 and higher |
54+
| Amazon Linux 2023 | All versions |
55+
| SUSE Linux Enterprise Server | 12 and 15 |
56+
| Red Hat Enterprise Linux | 7, 8, and 9 |
57+
| Oracle Linux | 7, 8, and 9 |
58+
| CentOS | 7 |
59+
| Google Container Optimized OS (default on GKE) (Preview) | 93 and higher |
60+
61+
**Notes:**
62+
63+
- Custom kernel builds are not supported.
64+
- The [Workload Protection eBPF-less solution for eBPF disabled environments][8] uses a ptrace-based Datadog Agent. The ptrace-based Datadog Agent supports Linux kernel versions from 3.4.43 to 4.9.85.
65+
- For compatibility with a custom Kubernetes network plugin like Cilium or Calico, see [Troubleshooting Workload Protection][9].
66+
- Data collection is done using eBPF, so Datadog requires, at minimum, platforms that have underlying Linux kernel versions of 4.14.0+ or have eBPF features backported (for example, Centos/RHEL 7 with kernel 3.10 has eBPF features backported, so it is supported).
67+
68+
69+
## Deploy the Agent
70+
71+
You can enable Workload Protection on the Datadog Agent using [multiple tools and systems][6]:
72+
73+
- [Kubernetes][8]
74+
- [Docker][9]
75+
- [ECS EC2][10]
76+
- [Windows][11]
77+
- [Linux][12]
78+
79+
## Workload Protection Agent variables
80+
81+
The Datadog Agent has several [environment variables][7] that can be enabled for Workload Protection. This article describes the purpose of each environment variable.
82+
83+
[1]: https://app.datadoghq.com/security/workload-protection/onboarding
84+
[2]: /account_management/rbac/permissions/
85+
[3]: /agent/remote_config/?tab=configurationyamlfile
86+
[6]: /security/workload_protection/setup/agent
87+
[7]: /security/workload_protection/setup/agent_variables
88+
[8]: /security/workload_protection/setup/agent/kubernetes
89+
[9]: /security/workload_protection/setup/agent/docker
90+
[10]: /security/workload_protection/setup/agent/ecs_ec2
91+
[11]: /security/workload_protection/setup/agent/windows
92+
[12]: /security/workload_protection/setup/agent/linux
93+
[8]: /security/workload_protection/guide/ebpf-free-agent
94+
[9]: /security/workload_protection/troubleshooting/threats
889 KB
Loading
252 KB
Loading
1.46 MB
Loading

0 commit comments

Comments
 (0)