This article provides instructions for the new user quick start workflow that uses AWS CloudFormation to set up Agentless Scanning.
For existing users who want to add a new AWS account or enable Agentless Scanning on an existing integrated AWS account, see the instructions for
@@ -86,9 +86,9 @@ For existing users who want to add a new AWS account or enable Agentless Scannin
##### Installation
-1. On the [Intro to Cloud Security Management][4] page, click **Get Started with Cloud Security Management**.
+1. On the [Intro to Cloud Security][4] page, click **Get Started with Cloud Security**.
1. Click **Quick Start**. The **Features** page is displayed, showing the features included with Agentless Scanning Quick Start.
-1. Click **Start Using Cloud Security Management** to continue.
+1. Click **Start Using Cloud Security** to continue.
1. Select the AWS region where you want to create the CloudFormation stack.
1. Select an API key that is already configured for Remote Configuration. If the API key you select does not have Remote Configuration enabled, Remote Configuration is automatically enabled for that key upon selection.
1. Choose whether to enable **Sensitive Data Scanner** for cloud storage. This automatically catalogs and classifies sensitive data in Amazon S3 resources.
@@ -109,7 +109,7 @@ Datadog recommends updating the CloudFormation stack regularly, so you can get a
##### Disable Agentless Scanning
-1. On the [Cloud Security Management Setup][10] page, click **Cloud Integrations** > **AWS**.
+1. On the [Cloud Security Setup][10] page, click **Cloud Integrations** > **AWS**.
1. To disable Agentless Scanning for an account, click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) and toggle the **Agentless Scanning** section to the off position.
1. Click **Done**.
@@ -126,14 +126,14 @@ To uninstall Agentless Scanning, log in to your AWS console and delete the Cloud
The [Terraform Datadog Agentless Scanner module][6] provides a simple and reusable configuration for installing the Datadog Agentless scanner.
{{% collapse-content title="Terraform setup guide" level="h4" id="terraform-setup" %}}
-If you've already [set up Cloud Security Management][10] and want to add a new cloud account or enable [Agentless Scanning][1] on an existing integrated cloud account, you can use either Terraform, [AWS CloudFormation][2], or [Azure Resource Manager][5]. This article provides detailed instructions for the Terraform approach.
+If you've already [set up Cloud Security][10] and want to add a new cloud account or enable [Agentless Scanning][1] on an existing integrated cloud account, you can use either Terraform, [AWS CloudFormation][2], or [Azure Resource Manager][5]. This article provides detailed instructions for the Terraform approach.
-
If you're setting up Cloud Security Management for the first time, you can follow the
quick start workflow, which uses AWS CloudFormation to enable Agentless Scanning.
+
If you're setting up Cloud Security for the first time, you can follow the
quick start workflow, which uses AWS CloudFormation to enable Agentless Scanning.
{{< tabs >}}
{{% tab "New AWS account" %}}
-1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations > AWS**.
+1. On the [Cloud Security Setup][1] page, click **Cloud Integrations > AWS**.
1. At the bottom of the AWS section, click **Add AWS accounts by following these steps**. The **Add New AWS Account(s)** dialog is displayed.
1. Under **Choose a method for adding your AWS account**, select **Manually**.
1. Follow the instructions for installing the [Datadog Agentless Scanner module][2].
@@ -148,7 +148,7 @@ If you've already [set up Cloud Security Management][10] and want to add a new c
{{% tab "Existing AWS account" %}}
-1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations > AWS**.
+1. On the [Cloud Security Setup][1] page, click **Cloud Integrations > AWS**.
1. Click the **Edit scanning** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) for the AWS account where you want to deploy the Agentless scanner.
1. **Enable Resource Scanning** should already be toggled on. If it isn't, toggle **Enable Resource Scanning** to the on position.
1. In the **How would you like to set up Agentless Scanning?** section, select **Terraform**.
@@ -163,7 +163,7 @@ If you've already [set up Cloud Security Management][10] and want to add a new c
{{% tab "Existing Azure subscription" %}}
-1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations > Azure**.
+1. On the [Cloud Security Setup][1] page, click **Cloud Integrations > Azure**.
1. Expand the Tenant containing the subscription where you want to deploy the Agentless scanner.
1. Click the **Enable** button for the Azure subscription where you want to deploy the Agentless scanner.
1. Toggle **Vulnerability Scanning** to the on position.
@@ -183,7 +183,7 @@ If you've already [set up Cloud Security Management][10] and want to add a new c
##### Disable Agentless Scanning
-1. On the [Cloud Security Management Setup][10] page, click **Cloud Integrations**, and then expand the **AWS** or **Azure** section.
+1. On the [Cloud Security Setup][10] page, click **Cloud Integrations**, and then expand the **AWS** or **Azure** section.
1. To disable Agentless Scanning for an account, click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) and toggle **Vulnerability Scanning** to the off position.
1. Click **Done**.
@@ -210,9 +210,9 @@ For usage examples, refer to our [Github repository](https://github.com/DataDog/
Use the AWS CloudFormation template to create a CloudFormation stack. The template includes the IAM permissions required to deploy and manage Agentless scanners.
{{% collapse-content title="AWS CloudFormation setup guide" level="h4" id="aws-cloudformation-setup" %}}
-If you've already [set up Cloud Security Management][10] and want to add a new cloud account or enable [Agentless Scanning][1] on an existing integrated AWS account, you can use either [Terraform][7] or AWS CloudFormation. This article provides detailed instructions for the AWS CloudFormation approach.
+If you've already [set up Cloud Security][10] and want to add a new cloud account or enable [Agentless Scanning][1] on an existing integrated AWS account, you can use either [Terraform][7] or AWS CloudFormation. This article provides detailed instructions for the AWS CloudFormation approach.
-
If you're setting up Cloud Security Management for the first time, you can follow the
quick start workflow, which also uses AWS CloudFormation to enable Agentless Scanning.
+
If you're setting up Cloud Security for the first time, you can follow the
quick start workflow, which also uses AWS CloudFormation to enable Agentless Scanning.
Running Agentless scanners incurs additional costs. To optimize these costs while still ensuring reliable 12-hour scans, Datadog recommends setting up
Agentless Scanning with Terraform as the default template.
@@ -223,7 +223,7 @@ If you've already [set up Cloud Security Management][10] and want to add a new c
{{< tabs >}}
{{% tab "New AWS account" %}}
-1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations** > **AWS**.
+1. On the [Cloud Security Setup][1] page, click **Cloud Integrations** > **AWS**.
1. At the bottom of the AWS section, click **Add AWS accounts by following these steps**. The **Add New AWS Account(s)** dialog is displayed.
1. Select the AWS region where you want to create the CloudFormation stack.
1. Select an API key that is already configured for Remote Configuration. If the API key you select does not have Remote Configuration enabled, Remote Configuration is automatically enabled for that key upon selection.
@@ -236,7 +236,7 @@ If you've already [set up Cloud Security Management][10] and want to add a new c
{{% tab "Existing AWS account" %}}
-1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations** > **AWS**.
+1. On the [Cloud Security Setup][1] page, click **Cloud Integrations** > **AWS**.
1. Click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) for the AWS account where you want to deploy the Agentless scanner.
1. Verify that **Enable Resource Scanning** is toggled on. If it isn't, switch the **Enable Resource Scanning** toggle to the on position and complete Steps 3-7 in [New AWS Account][2].
1. In the **Agentless Scanning** section, toggle **Enable Vulnerability Management (Host, Container and Lambda)** to the on position.
@@ -264,7 +264,7 @@ Datadog recommends updating the CloudFormation stack regularly, so you can get a
##### Disable Agentless Scanning
-1. On the [Cloud Security Management Setup][10] page, click **Cloud Integrations** > **AWS**.
+1. On the [Cloud Security Setup][10] page, click **Cloud Integrations** > **AWS**.
1. To disable Agentless Scanning for an account, click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) and toggle the **Agentless Scanning** section to the off position.
1. Click **Done**.
@@ -280,7 +280,7 @@ To uninstall Agentless Scanning, log in to your AWS console and delete the Cloud
Use the Azure Resource Manager template to deploy the Agentless Scanner. The template includes the role definitions required to deploy and manage Agentless scanners.
{{% collapse-content title="Azure Resource Manager setup guide" level="h4" id="azure-resource-manager-setup" %}}
-If you've already [set up Cloud Security Management][10] and want to add a new Azure subscription or enable [Agentless Scanning][1] on an existing integrated Azure subscription, you can use either [Terraform][7] or Azure Resource Manager. This article provides detailed instructions for the Azure Resource Manager approach.
+If you've already [set up Cloud Security][10] and want to add a new Azure subscription or enable [Agentless Scanning][1] on an existing integrated Azure subscription, you can use either [Terraform][7] or Azure Resource Manager. This article provides detailed instructions for the Azure Resource Manager approach.
Running Agentless scanners incurs additional costs. To optimize these costs while still ensuring reliable 12-hour scans, Datadog recommends setting up
Agentless Scanning with Terraform as the default template.
@@ -309,7 +309,7 @@ Follow the instructions for setting up the [Datadog Azure integration][1].
##### Disable Agentless Scanning
-1. On the [Cloud Security Management Setup][10] page, click **Cloud Integrations** > **Azure**.
+1. On the [Cloud Security Setup][10] page, click **Cloud Integrations** > **Azure**.
1. Locate your subscription's tenant, expand the list of subscriptions, and identify the subscription for which you want to disable Agentless Scanning.
1. Click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) and toggle **Vulnerability Scanning** to the off position.
1. Click **Done**.
diff --git a/content/en/security/cloud_security_management/setup/cloud_integrations.md b/content/en/security/cloud_security_management/setup/cloud_integrations.md
index 589cf66da25a0..8298075a8a544 100644
--- a/content/en/security/cloud_security_management/setup/cloud_integrations.md
+++ b/content/en/security/cloud_security_management/setup/cloud_integrations.md
@@ -1,5 +1,5 @@
---
-title: Deploying Cloud Security Management via Cloud Integrations
+title: Deploying Cloud Security via Cloud Integrations
aliases:
- /security/cloud_security_management/setup/csm_enterprise/cloud_accounts
- /security/cloud_security_management/setup/csm_pro/cloud_accounts
@@ -10,7 +10,7 @@ Use the following instructions to enable Misconfigurations and Identity Risks (C
## Enable resource scanning
-To enable resource scanning for your cloud accounts, you must first set up the integration and then enable CSM for each AWS account, Azure subscription, and Google Cloud project.
+To enable resource scanning for your cloud accounts, you must first set up the integration and then enable Cloud Security for each AWS account, Azure subscription, and Google Cloud project.
{{< partial name="security-platform/CSW-billing-note.html" >}}
@@ -42,7 +42,7 @@ To enable resource scanning for your cloud accounts, you must first set up the i
{{< tabs >}}
{{% tab "AWS" %}}
-1. On the [**Cloud Security Management Setup**][1] page, click **Cloud Integrations**.
+1. On the [**Cloud Security Setup**][1] page, click **Cloud Integrations**.
1. Expand the **AWS** section.
1. To stop resource collection for an account, click the **Edit** button ({{< img src="security/csm/setup/edit-button.png" inline="true" style="width:24px;">}}) and switch the **Enable Resource Scanning** toggle to the off position.
1. Click **Done**.
@@ -53,7 +53,7 @@ To enable resource scanning for your cloud accounts, you must first set up the i
{{% /tab %}}
{{% tab "Azure" %}}
-1. On the [**Cloud Security Management Setup**][1] page, click **Cloud Integrations**.
+1. On the [**Cloud Security Setup**][1] page, click **Cloud Integrations**.
1. Expand the **Azure** section.
1. To stop resource collection for a subscription, switch the **Resource Scanning** toggle to the off position.
1. Click **Done**.
@@ -64,7 +64,7 @@ To enable resource scanning for your cloud accounts, you must first set up the i
{{% /tab %}}
{{% tab "Google Cloud" %}}
-1. On the [**Cloud Security Management Setup**][1] page, click **Cloud Integrations**.
+1. On the [**Cloud Security Setup**][1] page, click **Cloud Integrations**.
1. Expand the **GCP** section.
1. To stop resource collection for a project, switch the **Resource Scanning** toggle to the off position.
1. Click **Done**.
diff --git a/content/en/security/cloud_security_management/setup/cloudtrail_logs.md b/content/en/security/cloud_security_management/setup/cloudtrail_logs.md
index de44db7a5602a..c52a7bb623712 100644
--- a/content/en/security/cloud_security_management/setup/cloudtrail_logs.md
+++ b/content/en/security/cloud_security_management/setup/cloudtrail_logs.md
@@ -1,8 +1,8 @@
---
-title: Setting up AWS CloudTrail Logs for Cloud Security Management
+title: Setting up AWS CloudTrail Logs for Cloud Security
---
-Set up AWS CloudTrail Logs to get the most out of [CSM Identity Risks][1]. AWS CloudTrail Logs provides additional insights into the actual usage of cloud resources, helping you identify users and roles with significant gaps between provisioned and utilized permissions.
+Set up AWS CloudTrail Logs to get the most out of [Cloud Security Identity Risks][1]. AWS CloudTrail Logs provides additional insights into the actual usage of cloud resources, helping you identify users and roles with significant gaps between provisioned and utilized permissions.
## Set up AWS integration using CloudFormation
diff --git a/content/en/security/cloud_security_management/setup/iac_remediation.md b/content/en/security/cloud_security_management/setup/iac_remediation.md
index 91b3836dac768..9cb05981a86a5 100644
--- a/content/en/security/cloud_security_management/setup/iac_remediation.md
+++ b/content/en/security/cloud_security_management/setup/iac_remediation.md
@@ -1,20 +1,20 @@
---
-title: Setting up IaC Remediation for Cloud Security Management
+title: Setting up IaC Remediation for Cloud Security
aliases:
- /security/cloud_security_management/setup/source_code_integrations
further_reading:
- link: "/security/cloud_security_management/setup"
tag: "Documentation"
- text: "Setting up Cloud Security Management"
+ text: "Setting up Cloud Security"
- link: "/security/cloud_security_management/misconfigurations"
tag: "Documentation"
- text: "CSM Misconfigurations"
+ text: "Cloud Security Misconfigurations"
- link: "/security/cloud_security_management/identity_risks"
tag: "Guide"
- text: "CSM Identity Risks"
+ text: "Cloud Security Identity Risks"
---
-Use the following instructions to enable Infrastructure as Code (IaC) remediation for Cloud Security Management (CSM). IaC remediation is available for [CSM Misconfigurations][1] and [CSM Identity Risks][2].
+Use the following instructions to enable Infrastructure as Code (IaC) remediation for Cloud Security. IaC remediation is available for [Cloud Security Misconfigurations][1] and [Cloud Security Identity Risks][2].
Static IaC remediation supports GitHub for version control and Terraform for infrastructure as code.
@@ -29,7 +29,7 @@ Follow [the instructions][3] for creating a GitHub app for your organization.
After you set up the GitHub integration, enable IaC remediation for the repositories in your GitHub account.
-1. On the [CSM Setup page][4], expand the **Source Code Integrations** section.
+1. On the [Cloud Security Setup page][4], expand the **Source Code Integrations** section.
2. Click **Configure** for the GitHub account you want to configure.
3. To enable IaC:
- All repositories: Toggle **Enable Infrastructure as Code (IaC) Remediation** to the on position.
diff --git a/content/en/security/cloud_security_management/setup/iac_scanning/_index.md b/content/en/security/cloud_security_management/setup/iac_scanning/_index.md
index 07cdc54ec0a08..4ff44cb7de5a2 100644
--- a/content/en/security/cloud_security_management/setup/iac_scanning/_index.md
+++ b/content/en/security/cloud_security_management/setup/iac_scanning/_index.md
@@ -1,22 +1,22 @@
---
-title: Setting up IaC Scanning for Cloud Security Management
+title: Setting up IaC Scanning for Cloud Security
further_reading:
- link: "/security/cloud_security_management/setup"
tag: "Documentation"
- text: "Setting up Cloud Security Management"
+ text: "Setting up Cloud Security"
- link: "/security/cloud_security_management/misconfigurations"
tag: "Documentation"
- text: "CSM Misconfigurations"
+ text: "Cloud Security Misconfigurations"
- link: "/security/cloud_security_management/identity_risks"
tag: "Guide"
- text: "CSM Identity Risks"
+ text: "Cloud Security Identity Risks"
---
{{< callout url="https://www.datadoghq.com/product-preview/iac-security/" >}}
Static Infrastructure as Code (IaC) scanning is in Preview. To request access, complete the form.
{{< /callout >}}
-Use the following instructions to enable Infrastructure as Code (IaC) scanning for Cloud Security Management (CSM). IaC scanning is available for [CSM Misconfigurations][1] and [CSM Identity Risks][2].
+Use the following instructions to enable Infrastructure as Code (IaC) scanning for Cloud Security. IaC scanning is available for [Cloud Security Misconfigurations][1] and [Cloud Security Identity Risks][2].
Static IaC scanning supports GitHub for version control and Terraform for infrastructure as code.
@@ -31,7 +31,7 @@ Follow [the instructions][3] for creating a GitHub app for your organization.
After you set up the GitHub integration, enable IaC scanning for the repositories in your GitHub account.
-1. On the [CSM Setup page][4], expand the **Source Code Integrations** section.
+1. On the [Cloud Security Setup page][4], expand the **Source Code Integrations** section.
2. Click **Configure** for the GitHub account you want to configure.
3. To enable IaC:
- All repositories: Toggle **Enable Infrastructure as Code (IaC) Scanning** to the on position.
diff --git a/content/en/security/cloud_security_management/setup/iac_scanning/iac_scanning_exclusions.md b/content/en/security/cloud_security_management/setup/iac_scanning/iac_scanning_exclusions.md
index c8b32f26ba22d..1f5a4fe87d673 100644
--- a/content/en/security/cloud_security_management/setup/iac_scanning/iac_scanning_exclusions.md
+++ b/content/en/security/cloud_security_management/setup/iac_scanning/iac_scanning_exclusions.md
@@ -6,7 +6,7 @@ further_reading:
text: "IaC Scanning"
- link: "/security/cloud_security_management/setup/iac_scanning"
tag: "Documentation"
- text: "Setting up IaC Scanning for Cloud Security Management"
+ text: "Setting up IaC Scanning for Cloud Security"
---
{{< callout url="https://www.datadoghq.com/product-preview/iac-security/" >}}
diff --git a/content/en/security/cloud_security_management/setup/supported_deployment_types.md b/content/en/security/cloud_security_management/setup/supported_deployment_types.md
index 64b7c5b72d811..3e26768549d7c 100644
--- a/content/en/security/cloud_security_management/setup/supported_deployment_types.md
+++ b/content/en/security/cloud_security_management/setup/supported_deployment_types.md
@@ -4,37 +4,37 @@ title: Cloud Security Supported Deployment Types
{{< partial name="security-platform/CSW-billing-note.html" >}}
-The following table summarizes the CSM features available relative to each deployment type.
+The following table summarizes the Cloud Security features available relative to each deployment type.
-| Deployment type | Agent Required (7.46+) | CSM Misconfigurations | CSM Threats | CSM Vulnerabilities | CSM Identity Risks | CSM Agentless Scanning |
-|---------------------|------------------------|-----------------------|-------------|------------------------------|--------------------|------------------------|
-| AWS Account | | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} |
-| Azure Account | | {{< X >}} | | Agentless Scanning (Preview) | {{< X >}} | |
-| GCP Account | | {{< X >}} | | | | |
-| Terraform | | | | | | {{< X >}} |
-| Docker | {{< X >}} | {{< X >}} | {{< X >}} | | | |
-| Kubernetes | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
-| Linux | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
-| Amazon ECS/EKS | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
-| Windows | {{< X >}} | | {{< X >}} | {{< X >}} | | |
-| AWS Fargate ECS/EKS | {{< X >}} | | {{< X >}} | | | |
+| Deployment type | Agent Required (7.46+) | Misconfigurations | Workload Protection | Vulnerabilities | Identity Risks | Agentless Scanning |
+|---------------------|------------------------|-------------------|---------------------|------------------------------|----------------|--------------------|
+| AWS Account | | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} |
+| Azure Account | | {{< X >}} | | Agentless Scanning (Preview) | {{< X >}} | |
+| GCP Account | | {{< X >}} | | | | |
+| Terraform | | | | | | {{< X >}} |
+| Docker | {{< X >}} | {{< X >}} | {{< X >}} | | | |
+| Kubernetes | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
+| Linux | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
+| Amazon ECS/EKS | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | |
+| Windows | {{< X >}} | | {{< X >}} | {{< X >}} | | |
+| AWS Fargate ECS/EKS | {{< X >}} | | {{< X >}} | | | |
-The following table summarizes the scope of coverage available relative to each CSM feature.
-| Resources monitored | CSM Misconfigurations | CSM Threats | CSM Vulnerabilities | CSM Identity Risks | CSM Agentless scanning |
-|---------------------------------|-----------------------|-------------|---------------------|--------------------|------------------------|
-| Resources in AWS Account | {{< X >}} | | {{< X >}} | | {{< X >}} |
-| Resources in Azure Subscription | {{< X >}} | | | | |
-| Resources in GCP Project | {{< X >}} | | | | |
-| Kubernetes Cluster | {{< X >}} | {{< X >}} | | | |
-| Docker Host | {{< X >}} | | | | |
-| Linux Host | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} |
-| Windows Host | | {{< X >}} | {{< X >}} | | |
-| Docker Container | | {{< X >}} | | | |
-| Container Image | | | {{< X >}} | | {{< X >}} |
-| IAM in AWS Account | | | | {{< X >}} | |
+The following table summarizes the scope of coverage available relative to each Cloud Security feature.
+| Resources monitored | Misconfigurations | Workload Protection | Vulnerabilities | Identity Risks | Agentless scanning |
+|---------------------------------|-------------------|---------------------|-----------------|----------------|--------------------|
+| Resources in AWS Account | {{< X >}} | | {{< X >}} | | {{< X >}} |
+| Resources in Azure Subscription | {{< X >}} | | | | |
+| Resources in GCP Project | {{< X >}} | | | | |
+| Kubernetes Cluster | {{< X >}} | {{< X >}} | | | |
+| Docker Host | {{< X >}} | | | | |
+| Linux Host | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} |
+| Windows Host | | {{< X >}} | {{< X >}} | | |
+| Docker Container | | {{< X >}} | | | |
+| Container Image | | | {{< X >}} | | {{< X >}} |
+| IAM in AWS Account | | | | {{< X >}} | |
-**Note**: CSM Misconfigurations additionally monitors common resources used in your cloud accounts that are running Windows and AWS Fargate, such as EC2 instances, RDS, S3, and ELB.
+**Note**: Cloud Security Misconfigurations additionally monitors common resources used in your cloud accounts that are running Windows and AWS Fargate, such as EC2 instances, RDS, S3, and ELB.
-[1]: /security/cloud_security_management/setup/#csm-threats
-[2]: /security/cloud_security_management/setup/#csm-vulnerabilities
-[3]: /security/cloud_security_management/setup/#csm-identity-risks
+[1]: /security/cloud_security_management/setup/#cloud-security-threats
+[2]: /security/cloud_security_management/setup/#cloud-security-vulnerabilities
+[3]: /security/cloud_security_management/setup/#cloud-security-identity-risks
diff --git a/content/en/security/cloud_security_management/setup/without_infrastructure_monitoring.md b/content/en/security/cloud_security_management/setup/without_infrastructure_monitoring.md
index 90f05937f82c9..30b689df1fed2 100644
--- a/content/en/security/cloud_security_management/setup/without_infrastructure_monitoring.md
+++ b/content/en/security/cloud_security_management/setup/without_infrastructure_monitoring.md
@@ -1,47 +1,47 @@
---
-title: Setting Up CSM without Infrastructure Monitoring
+title: Setting Up Cloud Security without Infrastructure Monitoring
---
-In addition to setting up Cloud Security Management (CSM) with or without an Agent, you can also set it up without Infrastructure Monitoring.
+In addition to setting up Cloud Security with or without an Agent, you can also set it up without Infrastructure Monitoring.
-## Set up CSM on your AWS account
+## Set up Cloud Security on your AWS account
1. Navigate to the [AWS Integration configuration page][2] in Datadog.
-1. On the **Configuration** tab, select the account you want to enable CSM on.
+1. On the **Configuration** tab, select the account you want to enable Cloud Security on.
If you don't see the required account, add it by clicking **Add AWS Account(s)** and following the onscreen prompts.
1. To turn off infrastructure monitoring on the selected account, under the account number, navigate to the **Metric Collection** tab, then click the **disable metric collection** link. Then, click **Disable Metric Collection** to confirm.
-1. On the **Resource Collection** tab, click **Enable** next to Cloud Security Management. You are redirected to the Cloud Security Management Setup page, and a setup dialog automatically opens for the selected account.
+1. On the **Resource Collection** tab, click **Enable** next to Cloud Security. You are redirected to the Cloud Security Setup page, and a setup dialog automatically opens for the selected account.
1. On the setup dialog, switch the **Enable Resource Scanning** toggle to the on position.
1. Click **Done** to complete the setup.
-**Note**: In your CSM settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
+**Note**: In your Cloud Security settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
-## Set up CSM on your Azure subscription
+## Set up Cloud Security on your Azure subscription
1. Navigate to the [Azure Integration configuration page][3] in Datadog.
-1. Select the client ID or subscription you want to enable CSM on.
+1. Select the client ID or subscription you want to enable Cloud Security on.
If you don't see the required client ID, add it by clicking **Add New App Registration** and following the onscreen prompts.
1. To turn off infrastructure monitoring on the selected account, under the client ID, navigate to the **Metric Collection** tab, then turn off the **Enable Metric Collection** toggle.
-1. On the **Resource Collection** tab, click **Enable** next to Cloud Security Management. You are redirected to the Cloud Security Management Setup page, which automatically scrolls to the selected Azure subscription in the Cloud Integrations section.
+1. On the **Resource Collection** tab, click **Enable** next to Cloud Security. You are redirected to the Cloud Security Setup page, which automatically scrolls to the selected Azure subscription in the Cloud Integrations section.
1. Switch the **Resource Scanning** toggle to the on position.
1. Click **Done** to complete the setup.
-**Note**: In your CSM settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
+**Note**: In your Cloud Security settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
-## Set up CSM on your Google Cloud Platform account
+## Set up Cloud Security on your Google Cloud Platform account
1. Navigate to the [Google Cloud Platform configuration page][4] in Datadog.
-1. Select the service account you want to enable CSM on.
+1. Select the service account you want to enable Cloud Security on.
If you don't see the required account, add it by clicking **Add GCP Account** and following the onscreen prompts.
1. To turn off infrastructure monitoring on the selected account, under the account name, navigate to the **Metric Collection** tab. Then, above the Metric Collection table, click **Disable All**.
-1. On the **Resource Collection** tab, click **Enable** next to Cloud Security Management. You are redirected to the Cloud Security Management Setup page, which automatically scrolls to the selected Google Cloud Platform project in the Cloud Integrations section.
+1. On the **Resource Collection** tab, click **Enable** next to Cloud Security. You are redirected to the Cloud Security Setup page, which automatically scrolls to the selected Google Cloud Platform project in the Cloud Integrations section.
1. Switch the **Resource Scanning** toggle to the on position.
1. Click **Done** to complete the setup.
-**Note**: In your CSM settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
+**Note**: In your Cloud Security settings, set up [resource evaluation filters][1] to limit the number of hosts you need security on.
[1]: /security/cloud_security_management/guide/resource_evaluation_filters/
[2]: https://app.datadoghq.com/integrations/amazon-web-services
diff --git a/content/en/security/cloud_security_management/severity_scoring.md b/content/en/security/cloud_security_management/severity_scoring.md
index 7ff68a05fe476..a9217e6e5ac82 100644
--- a/content/en/security/cloud_security_management/severity_scoring.md
+++ b/content/en/security/cloud_security_management/severity_scoring.md
@@ -3,20 +3,20 @@ title: Severity Scoring
further_reading:
- link: "/security/cloud_security_management/misconfigurations/"
tag: "Documentation"
- text: "Start tracking misconfigurations with CSM Misconfigurations"
+ text: "Start tracking misconfigurations with Cloud Security Misconfigurations"
- link: "/security/cloud_security_management/identity_risks/"
tag: "Documentation"
- text: "Understand your identity landscape with CSM Identity Risks"
+ text: "Understand your identity landscape with Cloud Security Identity Risks"
- link: "/security/cloud_security_management/vulnerabilities/"
tag: "Documentation"
- text: "Learn more about CSM Vulnerabilities"
+ text: "Learn more about Cloud Security Vulnerabilities"
---
-Accurate severity scores help security teams understand the risks that vulnerabilities pose to their environment. This guide explains how Cloud Security Management (CSM) uses different measures of severity to calculate the scores.
+Accurate severity scores help security teams understand the risks that vulnerabilities pose to their environment. This guide explains how Cloud Security uses different measures of severity to calculate the scores.
-## CSM severity scoring framework
+## Cloud Security severity scoring framework
-CSM Misconfigurations, CSM Identity Risks, and Security Inbox misconfigurations use the CSM severity scoring framework to determine the severity of a finding. The framework compares the likelihood that an adversary would take advantage of a misconfiguration to the risk posed to your environment. By weighting both of these aspects, findings can be prioritized more accurately by real-world risks. The matrices below show how a misconfiguration's severity score is computed based on its likelihood of abuse and impact.
+Cloud Security Misconfigurations, Cloud Security Identity Risks, and Security Inbox misconfigurations use the Cloud Security severity scoring framework to determine the severity of a finding. The framework compares the likelihood that an adversary would take advantage of a misconfiguration to the risk posed to your environment. By weighting both of these aspects, findings can be prioritized more accurately by real-world risks. The matrices below show how a misconfiguration's severity score is computed based on its likelihood of abuse and impact.
### Likelihood
@@ -86,7 +86,7 @@ To explain how the framework is used here are a few examples.
The detection rule for [SNS Topic should have access restrictions set for subscription][1] checks if the SNS topic has a resource-based policy that contains a `Principal` of `*`, and an `Action` with the `sns:Subscribe` permission. This combination gives anyone the ability to subscribe to the SNS topic and receive its notifications.
-Using the CSM severity scoring framework, the rule would be scored as follows:
+Using the Cloud Security severity scoring framework, the rule would be scored as follows:
- **Likelihood score**: Highly Probable
- **Attack vector**: No Authorization
@@ -102,7 +102,7 @@ Using the CSM severity scoring framework, the rule would be scored as follows:
The detection rule for [EC2 instances should enforce IMDSv2][2] checks if an EC2 instance is using the Instance Metadata Service Version 1 ([IMDSv1][3]), which is vulnerable to common web application attacks. If exploited, an adversary can obtain access to the IAM credentials stored in the IMDS and use them to access resources in the AWS account.
-Using the CSM severity scoring framework, the rule would be scored as follows:
+Using the Cloud Security severity scoring framework, the rule would be scored as follows:
- **Likelihood score**: Possible
- **Attack vector**: Vulnerability
@@ -116,7 +116,7 @@ Using the CSM severity scoring framework, the rule would be scored as follows:
## CVSS 3.1
-CSM Vulnerabilities uses Common Vulnerability Scoring System version 3.1 ([CVSS 3.1][5]) to determine a base score for a vulnerability. It then modifies the base score to take into account the following:
+Cloud Security Vulnerabilities uses Common Vulnerability Scoring System version 3.1 ([CVSS 3.1][5]) to determine a base score for a vulnerability. It then modifies the base score to take into account the following:
- Whether the underlying infrastructure is running and how wide-spread the impact is.
- The environment in which the underlying infrastructure is running. For example, if the environment is not production, the severity is downgraded.
diff --git a/content/en/security/cloud_security_management/troubleshooting/_index.md b/content/en/security/cloud_security_management/troubleshooting/_index.md
index 67e997f465fcc..59c2314ea7bc9 100644
--- a/content/en/security/cloud_security_management/troubleshooting/_index.md
+++ b/content/en/security/cloud_security_management/troubleshooting/_index.md
@@ -1,11 +1,11 @@
---
-title: Cloud Security Management Troubleshooting
+title: Cloud Security Troubleshooting
disable_toc: true
---
{{< whatsnext desc="Troubleshooting Guides" >}}
- {{< nextlink href="/security/cloud_security_management/troubleshooting/threats" >}}Cloud Security Management Threats{{< /nextlink >}}
+ {{< nextlink href="/security/cloud_security_management/troubleshooting/threats" >}}Workload Protection{{< /nextlink >}}
- {{< nextlink href="/security/cloud_security_management/troubleshooting/vulnerabilities" >}}Cloud Security Management Vulnerabilities{{< /nextlink >}}
+ {{< nextlink href="/security/cloud_security_management/troubleshooting/vulnerabilities" >}}Cloud Security Vulnerabilities{{< /nextlink >}}
{{< /whatsnext >}}
\ No newline at end of file
diff --git a/content/en/security/cloud_security_management/troubleshooting/threats.md b/content/en/security/cloud_security_management/troubleshooting/threats.md
index 5a12c0d3f8a42..2528bac820585 100644
--- a/content/en/security/cloud_security_management/troubleshooting/threats.md
+++ b/content/en/security/cloud_security_management/troubleshooting/threats.md
@@ -1,15 +1,15 @@
---
-title: Troubleshooting Cloud Security Management Threats
+title: Troubleshooting Workload Protection
aliases:
- /security_platform/cloud_workload_security/troubleshooting/
- /security_platform/cloud_security_management/troubleshooting/
further_reading:
- link: "/security/cloud_security_management/troubleshooting/vulnerabilities"
tag: "Documentation"
- text: "Troubleshooting CSM Vulnerabilities"
+ text: "Troubleshooting Cloud Security Vulnerabilities"
---
-If you experience issues with Cloud Security Management (CSM) Threats, use the following troubleshooting guidelines. If you need further assistance, contact [Datadog support][1].
+If you experience issues with Workload Protection, use the following troubleshooting guidelines. If you need further assistance, contact [Datadog support][1].
## Security Agent flare
@@ -19,7 +19,7 @@ The flare asks for confirmation before upload, so you may review the content bef
In the commands below, replace `
` with your Datadog support case ID if you have one, then enter the email address associated with it.
-If you don't have a case ID, just enter your email address used to login in Datadog to create a new support case.
+If you don't have a case ID, enter your email address used to login in Datadog to create a new support case.
| Platform | Command |
| -------- | ------- |
@@ -29,7 +29,7 @@ If you don't have a case ID, just enter your email address used to login in Data
## Agent Self tests
-In order to ensure that the communication between the `security-agent` and the `system-probe` is working as expected and that Cloud Security Management Threats (CSM Threats) is able to detect system events, you can manually trigger self tests by running the following command:
+In order to ensure that the communication between the `security-agent` and the `system-probe` is working as expected and that Workload Protection is able to detect system events, you can manually trigger self tests by running the following command:
| Platform | Command |
| -------- | ------- |
@@ -50,18 +50,18 @@ You can now see events coming from the `runtime-security-agent` in the Log Explo
## Compatibility with custom Kubernetes network plugins
-The network based detections of CSM Threats rely on the traffic control sub-system of the Linux kernel. This sub-system is known to introduce race conditions if multiple vendors try to insert, replace, or delete filters on the "clsact" ingress qdisc. Follow the checklist below to ensure that CSM Threats is properly configured:
+The network based detections of Workload Protection rely on the traffic control sub-system of the Linux kernel. This sub-system is known to introduce race conditions if multiple vendors try to insert, replace, or delete filters on the "clsact" ingress qdisc. Follow the checklist below to ensure that Workload Protection is properly configured:
* Check if your vendor leverages eBPF traffic control classifiers. If they do not, you can ignore this paragraph.
* Check if your vendor returns TC_ACT_OK or TC_ACT_UNSPEC after granting access to a network packet. If they return TC_ACT_UNSPEC, you can ignore this paragraph.
* Check which priority your vendor attaches their eBPF classifiers to:
- * If they use priority 1, CSM Threats network detections do not work inside your containers.
+ * If they use priority 1, Workload Protection network detections do not work inside your containers.
* If they use priority 2 to 10, make sure to configure `runtime_security_config.network.classifier_priority` to a number strictly below the priority chosen by your vendor.
* If they use priority 11 or higher, you can ignore this paragraph.
For example, there is a known race with Cilium 1.9 and lower with the Datadog Agent (version 7.36 to 7.39.1, 7.39.2 excluded) that may happen when a new pod is started. The race can lead to loss of connectivity inside the pod, depending on how Cilium is configured.
-Ultimately, if the Datadog Agent or your third party vendors cannot be configured to prevent the issue from happening, you should disable the network based detections of CSM Threats by following the steps below:
+Ultimately, if the Datadog Agent or your third party vendors cannot be configured to prevent the issue from happening, you should disable the network based detections of Workload Protection by following the steps below:
* Add the following parameter to your `system-probe.yaml` configuration file on host based installations:
```yaml
@@ -81,9 +81,9 @@ datadog:
```bash
DD_RUNTIME_SECURITY_CONFIG_NETWORK_ENABLED=false
```
-## Disable CSM Threats
+## Disable Workload Protection
-To disable CSM Threats, follow the steps for your Agent platform.
+To disable Workload Protection, follow the steps for your Agent platform.
### Helm
@@ -113,7 +113,7 @@ DD_RUNTIME_SECURITY_CONFIG_ENABLED=false
Modify the `system-probe.yaml` and `security-agent.yaml` to disable the runtime config:
-1. Disable CSM in `/etc/datadog-agent/system-probe.yaml`. Ensure that `runtime_security_config` is set to `enabled: false`:
+1. Disable Workload Protection in `/etc/datadog-agent/system-probe.yaml`. Ensure that `runtime_security_config` is set to `enabled: false`:
{{< code-block lang="yaml" filename="system-probe.yaml" disable_copy="false" collapsible="true" >}}
##########################################
@@ -126,7 +126,7 @@ Modify the `system-probe.yaml` and `security-agent.yaml` to disable the runtime
runtime_security_config:
## @param enabled - boolean - optional - default: false
- ## Set to true to enable full CSM.
+ ## Set to true to enable full Workload Protection.
#
enabled: false
@@ -139,7 +139,7 @@ Modify the `system-probe.yaml` and `security-agent.yaml` to disable the runtime
#
# socket: /opt/datadog-agent/run/runtime-security.sock
{{< /code-block >}}
-2. Disable CSM in `/etc/datadog-agent/security-agent.yaml`. Ensure that `runtime_security_config` is set to `enabled: false`:
+2. Disable Workload Protection in `/etc/datadog-agent/security-agent.yaml`. Ensure that `runtime_security_config` is set to `enabled: false`:
{{< code-block lang="yaml" filename="security-agent.yaml" disable_copy="false" collapsible="true" >}}
##########################################
diff --git a/content/en/security/cloud_security_management/troubleshooting/vulnerabilities.md b/content/en/security/cloud_security_management/troubleshooting/vulnerabilities.md
index 9300532c3e6b6..ead4f8d5da118 100644
--- a/content/en/security/cloud_security_management/troubleshooting/vulnerabilities.md
+++ b/content/en/security/cloud_security_management/troubleshooting/vulnerabilities.md
@@ -1,11 +1,11 @@
---
-title: Troubleshooting Cloud Security Management Vulnerabilities
+title: Troubleshooting Cloud Security Vulnerabilities
aliases:
- /security/vulnerabilities/troubleshooting/
further_reading:
- link: "/infrastructure/containers/container_images/#enable-sbom-collection"
tag: "Documentation"
- text: "Enable SBOM collection in CSM Vulnerabilities"
+ text: "Enable SBOM collection in Cloud Security Vulnerabilities"
- link: "/security/cloud_security_management/setup/csm_enterprise/?tab=aws#hosts"
tag: "Documentation"
text: "Setting up host vulnerabilities"
@@ -16,7 +16,7 @@ further_reading:
## Overview
-If you experience issues with Cloud Security Management (CSM) Vulnerabilities, use the following troubleshooting guidelines. If you need further assistance, contact [Datadog support][1].
+If you experience issues with Cloud Security Vulnerabilities, use the following troubleshooting guidelines. If you need further assistance, contact [Datadog support][1].
## Error messages
@@ -61,7 +61,7 @@ unable to mount containerd image, err: unable to scan image named: {image-name},
The workaround for this issue is to disable image streaming in GKE. For more information, see the [Disable Image streaming][5] section of the GKE docs.
-## Disable CSM Vulnerabilities
+## Disable Cloud Security Vulnerabilities
In the `datadog-values.yaml` file for the Agent, set the following configuration settings to `false`:
diff --git a/content/en/security/cloud_security_management/vulnerabilities/_index.md b/content/en/security/cloud_security_management/vulnerabilities/_index.md
index bd4fd37b965e9..3e4a875346fa6 100644
--- a/content/en/security/cloud_security_management/vulnerabilities/_index.md
+++ b/content/en/security/cloud_security_management/vulnerabilities/_index.md
@@ -1,12 +1,12 @@
---
-title: Cloud Security Management Vulnerabilities
+title: Cloud Security Vulnerabilities
aliases:
- /security/infrastructure_vulnerabilities/
- /security/vulnerabilities/
further_reading:
- link: "/infrastructure/containers/container_images/#enable-sbom-collection"
tag: "Documentation"
- text: "Enable SBOM collection in CSM Vulnerabilities"
+ text: "Enable SBOM collection in Cloud Security Vulnerabilities"
- link: "/security/cloud_security_management/setup/csm_enterprise/?tab=aws#hosts"
tag: "Documentation"
text: "Setting up host vulnerabilities"
@@ -15,26 +15,23 @@ further_reading:
text: "Viewing Container Images"
- link: "/security/cloud_security_management/troubleshooting/vulnerabilities"
tag: "Documentation"
- text: "Troubleshooting CSM Vulnerabilities"
-- link: "https://www.datadoghq.com/blog/csm-vulnerability-management/"
- tag: "Blog"
- text: "Mitigate infrastructure vulnerabilities with Datadog Cloud Security Management"
+ text: "Troubleshooting Cloud Security Vulnerabilities"
- link: "https://www.datadoghq.com/blog/datadog-container-image-view/"
tag: "Blog"
text: "Enhance your troubleshooting workflow with Container Images in Datadog Container Monitoring"
---
{{< site-region region="gov" >}}
-Cloud Security Management Vulnerabilities is in Preview for your selected
Datadog site ({{< region-param key="dd_site_name" >}}).
+
Cloud Security Vulnerabilities is in Preview for your selected
Datadog site ({{< region-param key="dd_site_name" >}}).
Request access by
filling this form.
{{< /site-region >}}
## Overview
-Cloud Security Management Vulnerabilities (CSM Vulnerabilities) helps you improve your security posture and achieve compliance, by continuously scanning container images, hosts, host images, and serverless functions for vulnerabilities, from CI/CD pipelines to live production. Leveraging runtime observability, it helps you prioritize and remediate exploitable vulnerabilities in your daily workflows, all in a single view, and without any dependencies on other Datadog products.
+Cloud Security Vulnerabilities helps you improve your security posture and achieve compliance, by continuously scanning container images, hosts, host images, and serverless functions for vulnerabilities, from CI/CD pipelines to live production. Leveraging runtime observability, it helps you prioritize and remediate exploitable vulnerabilities in your daily workflows, all in a single view, and without any dependencies on other Datadog products.
-With CSM Vulnerabilities, you can manage your cloud security management strategy, all in one place:
+With Cloud Security Vulnerabilities, you can manage your cloud security management strategy, all in one place:
- Create a vulnerability management program, from CI/CD pipelines to production resources
- Pass compliance audits (such as SOC2, PCI, HIPAA, CIS, and FedRamp)
@@ -67,13 +64,13 @@ Explore reports
## Deployment methods
-Get started with CSM Vulnerabilities and cover your infrastructure in minutes, using:
+Get started with Cloud Security Vulnerabilities and cover your infrastructure in minutes, using:
- [Agentless Scanning][11]
- [Unified Datadog Agent][12]
You can also use both deployment methods to use the unified Datadog Agent where you already have it deployed, and Agentless elsewhere.
-After you've enabled it, Datadog starts scanning your resources continuously, and starts reporting prioritized vulnerabilities in your [CSM Vulnerability Explorer][1] within an hour.
+After you've enabled it, Datadog starts scanning your resources continuously, and starts reporting prioritized vulnerabilities in your [Cloud Security Vulnerabilities explorer][1] within an hour.
Use these tables to decide which solution to start with:
| Feature | Agentless | Unified Datadog Agent |
@@ -91,19 +88,19 @@ Use these tables to decide which solution to start with:
| Serverless | AWS Lambda | Not applicable |
| Container registries | Amazon ECR | Not applicable |
-For more information on compatibility, see [CSM Vulnerabilities Hosts and Containers Compatibility][13]. If you need any assistance, see the [troubleshooting guide][14], or reach out to support@datadoghq.com.
+For more information on compatibility, see [Cloud Security Vulnerabilities Hosts and Containers Compatibility][13]. If you need any assistance, see the [troubleshooting guide][14], or reach out to support@datadoghq.com.
## Continuously detect, prioritize, and remediate exploitable vulnerabilities
-The [CSM Vulnerabilities Explorer][1] helps you investigate vulnerabilities detected across your container images, host images, running hosts, and serverless functions using filtering and grouping capabilities.
+The [Cloud Security Vulnerabilities explorer][1] helps you investigate vulnerabilities detected across your container images, host images, running hosts, and serverless functions using filtering and grouping capabilities.
Focus on exploitable vulnerabilities first, using the Datadog Severity Score, combining the base CVSS score with many risk factors, including sensitive data, environment sensitivity, exposure to attacks, exploit availability, or threat intelligence sources.
-For vulnerabilities with available fixes, the Explorer provides guided remediation steps to assist Dev and Ops teams in resolving issues more quickly and effectively. You can also triage, mute, comment, and assign vulnerabilities to manage their lifecycle.
+For vulnerabilities with available fixes, the explorer provides guided remediation steps to assist Dev and Ops teams in resolving issues more quickly and effectively. You can also triage, mute, comment, and assign vulnerabilities to manage their lifecycle.
-{{< img src="security/vulnerabilities/csm-vm-explorer-actionability.png" alt="The CSM Vulnerability Explorer displaying a vulnerability and the actions a user can take to remediate it" width="100%">}}
+{{< img src="security/vulnerabilities/csm-vm-explorer-actionability.png" alt="The Cloud Security Vulnerabilities Explorer displaying a vulnerability and the actions a user can take to remediate it" width="100%">}}
## Automation and Jira integration
-Make CSM Vulnerabilities part of your daily workflow by setting up [security notification rules][17] and [automation pipelines (in Preview)][20]:
+Make Cloud Security Vulnerabilities part of your daily workflow by setting up [security notification rules][17] and [automation pipelines (in Preview)][20]:
- Get alerted upon detection of an exploitable vulnerability for your scope
- Automatically create Jira tickets
- Configure SLAs to remediate vulnerabilities
@@ -111,9 +108,9 @@ Make CSM Vulnerabilities part of your daily workflow by setting up [security not
{{< img src="security/vulnerabilities/csm-notifications.png" alt="The notification rule setup screen" width="100%">}}
## Tracking and reporting
-Use the out-of-the-box [CSM Vulnerabilities dashboard][18] to track and report progress to stakeholders. Clone and modify it as needed to fit your unique needs.
+Use the out-of-the-box [Cloud Security Vulnerabilities dashboard][18] to track and report progress to stakeholders. Clone and modify it as needed to fit your unique needs.
-{{< img src="security/vulnerabilities/csm-vm-reporting.png" alt="The CSM Vulnerabilities dashboard" width="100%">}}
+{{< img src="security/vulnerabilities/csm-vm-reporting.png" alt="The Cloud Security Vulnerabilities dashboard" width="100%">}}
## Explore infrastructure packages
@@ -125,9 +122,9 @@ Quickly assess the impact of a critical emerging vulnerability by searching for
## Video walkthrough
-The following video provides an overview of how to enable and use CSM Vulnerabilities:
+The following video provides an overview of how to enable and use Cloud Security Vulnerabilities:
-{{< img src="security/csm/how-to-use-csm-vulnerabilities.mp4" alt="Video that provides an overview of how to install and use CSM Vulnerabilities" video=true >}}
+{{< img src="security/csm/how-to-use-csm-vulnerabilities.mp4" alt="Video that provides an overview of how to install and use Cloud Security Vulnerabilities" video=true >}}
[1]: https://app.datadoghq.com/security/csm/vm
[2]: https://app.datadoghq.com/containers/images
diff --git a/content/en/security/cloud_security_management/vulnerabilities/hosts_containers_compatibility.md b/content/en/security/cloud_security_management/vulnerabilities/hosts_containers_compatibility.md
index d789fe45152f2..47c28074abed3 100644
--- a/content/en/security/cloud_security_management/vulnerabilities/hosts_containers_compatibility.md
+++ b/content/en/security/cloud_security_management/vulnerabilities/hosts_containers_compatibility.md
@@ -1,10 +1,10 @@
---
-title: CSM Vulnerabilities Hosts and Containers Compatibility
+title: Cloud Security Vulnerabilities Hosts and Containers Compatibility
---
## Operating systems
-Cloud Security Management Vulnerabilities supports vulnerability scanning for hosts and containers running the following operating system versions:
+Cloud Security Vulnerabilities supports vulnerability scanning for hosts and containers running the following operating system versions:
| Operating System | Supported Versions | Package Managers / Source | Agentless support | Agent support |
|--------------------------|-----------------------------------------------------|---------------------------|-------------------|-------------------|
@@ -33,7 +33,7 @@ Cloud Security Management Vulnerabilities supports vulnerability scanning for ho
## Application libraries
-Cloud Security Management Vulnerabilities supports vulnerability scanning for the following application languages and libraries on containers and Lambda instances:
+Cloud Security Vulnerabilities supports vulnerability scanning for the following application languages and libraries on containers and Lambda instances:
| Language | Supported Package Manager | Supported Files | Agentless support | Agent support |
|----------|---------------------------|----------------------------------------------------------------------|-------------------|-------------------|
diff --git a/content/en/security/cloud_siem/_index.md b/content/en/security/cloud_siem/_index.md
index 1c1b7893455de..daed7a6e70ec4 100644
--- a/content/en/security/cloud_siem/_index.md
+++ b/content/en/security/cloud_siem/_index.md
@@ -39,7 +39,7 @@ further_reading:
---
{{< learning-center-callout header="Join an enablement webinar session" hide_image="true" btn_title="Sign Up" btn_url="https://www.datadoghq.com/technical-enablement/sessions/?tags.topics-0=Security">}}
- Learn how Datadog Cloud SIEM and Cloud Security Management elevate your organization's threat detection and investigation for dynamic, cloud-scale environments.
+ Learn how Datadog Cloud SIEM and Cloud Security elevate your organization's threat detection and investigation for dynamic, cloud-scale environments.
{{< /learning-center-callout >}}
## Overview
diff --git a/content/en/security/cloud_siem/detection_rules/signal_correlation_rules.md b/content/en/security/cloud_siem/detection_rules/signal_correlation_rules.md
index 5c5128c93a5f5..724924728d96a 100644
--- a/content/en/security/cloud_siem/detection_rules/signal_correlation_rules.md
+++ b/content/en/security/cloud_siem/detection_rules/signal_correlation_rules.md
@@ -24,7 +24,7 @@ As another example, you can create a signal by combining these two rules:
And use the `expired account ID` attribute to correlate the two rules.
-You can correlate log detection rules, as well as log detection rules with Cloud Security Management Threats and Application Security Management rules.
+You can correlate log detection rules, as well as log detection rules with Workload Protection and App and API Protection rules.
## Create a Signal Correlation rule
diff --git a/content/en/security/cloud_siem/entities_and_risk_scoring.md b/content/en/security/cloud_siem/entities_and_risk_scoring.md
index a26825b5ce82c..da9f73e95c421 100644
--- a/content/en/security/cloud_siem/entities_and_risk_scoring.md
+++ b/content/en/security/cloud_siem/entities_and_risk_scoring.md
@@ -8,7 +8,7 @@ further_reading:
## Overview
-[Cloud SIEM's Risk Insights][4] consolidates multiple data sources, such as SIEM threats and CSM insights, into a profile representing a single security entity, such as an IAM user.
+[Cloud SIEM's Risk Insights][4] consolidates multiple data sources, such as SIEM threats and Cloud Security insights, into a profile representing a single security entity, such as an IAM user.
With Risk Insights, you can:
@@ -20,7 +20,7 @@ With Risk Insights, you can:
## Prerequisites
- For Risk Insights coverage, either [GCP][5] or [AWS must be configured for Cloud SIEM][1].
-- (Optional) To view associated Cloud Security Management (CSM) insights in the entity panel, [CSM must be configured][2].
+- (Optional) To view associated Cloud Security insights in the entity panel, [Cloud Security must be configured][2].
## Explore risk insights
diff --git a/content/en/security/cloud_siem/guide/how-to-setup-security-filters-using-cloud-siem-api.md b/content/en/security/cloud_siem/guide/how-to-setup-security-filters-using-cloud-siem-api.md
index 5ba7eb580aac4..78d9e4784753a 100644
--- a/content/en/security/cloud_siem/guide/how-to-setup-security-filters-using-cloud-siem-api.md
+++ b/content/en/security/cloud_siem/guide/how-to-setup-security-filters-using-cloud-siem-api.md
@@ -21,7 +21,7 @@ The following examples are covered in this guide:
* [Configure the default security filter to exclude certain logs](#add-an-exclusion)
* [Create custom security filters to specify which log sources to analyze](#create-a-custom-filter)
-**Note**: Security Filters are only required to control logs analyzed by the Cloud SIEM product. You do not need to write Security Filters to exclude logs generated by the Datadog Agent as part of the Cloud Security Management Threats (`source:runtime-security-agent`) and Cloud Security Management Misconfigurations (`source:compliance-agent`) products, as they're not billed as analyzed logs regardless.
+**Note**: Security Filters are only required to control logs analyzed by the Cloud SIEM product. You do not need to write Security Filters to exclude logs generated by the Datadog Agent as part of the Workload Protection (`source:runtime-security-agent`) and Cloud Security Misconfigurations (`source:compliance-agent`) products, as they're not billed as analyzed logs regardless.
## Prerequisites
diff --git a/content/en/security/code_security/iast/setup/compatibility/_index.md b/content/en/security/code_security/iast/setup/compatibility/_index.md
index 2aa29e071f358..2a3f36b781a67 100644
--- a/content/en/security/code_security/iast/setup/compatibility/_index.md
+++ b/content/en/security/code_security/iast/setup/compatibility/_index.md
@@ -4,10 +4,10 @@ type: multi-code-lang
further_reading:
- link: "/security/application_security/troubleshooting"
tag: "Documentation"
- text: "Troubleshooting Application Security Management"
+ text: "Troubleshooting App and API Protection"
- link: "/security/application_security/how-appsec-works/"
tag: "Documentation"
- text: "How Application Security Management Works in Datadog"
+ text: "How App and API Protection Works in Datadog"
---
The following capabilities are supported relative to each language's tracing library:
diff --git a/content/en/security/code_security/iast/setup/dotnet.md b/content/en/security/code_security/iast/setup/dotnet.md
index e72b4395a4b13..db137c99c2d65 100644
--- a/content/en/security/code_security/iast/setup/dotnet.md
+++ b/content/en/security/code_security/iast/setup/dotnet.md
@@ -95,7 +95,7 @@ ENV DD_IAST_ENABLED=true
{{% tab "Kubernetes" %}}
-Update your deployment configuration file for APM and add the ASM environment variable:
+Update your deployment configuration file for APM and add the AAP environment variable:
```yaml
spec:
diff --git a/content/en/security/code_security/iast/setup/nodejs.md b/content/en/security/code_security/iast/setup/nodejs.md
index 620ff1a10d167..0f5bdbb621224 100644
--- a/content/en/security/code_security/iast/setup/nodejs.md
+++ b/content/en/security/code_security/iast/setup/nodejs.md
@@ -37,7 +37,7 @@ Follow these steps to enable Code Security in your service:
```shell
node --require dd-trace/init app.js
```
- Then use environment variables to enable ASM:
+ Then use environment variables to enable AAP:
```shell
DD_IAST_ENABLED=true node app.js
```
diff --git a/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md b/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md
index 52d97d558e57f..649607501bf52 100644
--- a/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md
+++ b/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md
@@ -11,7 +11,7 @@ Before setting up runtime detection, ensure the following prerequisites are met:
1. **Supported Tracing Library:** The Datadog Tracing Library used by your application or service supports Software Composition Analysis capabilities for the language of your application or service.
2. **Datadog Agent Installation:** The Datadog Agent is installed and configured for your application's operating system or container, cloud, or virtual environment.
3. **Datadog APM Configuration:** Datadog APM is configured for your application or service, and web traces (`type:web`) are being received by Datadog.
-4. **Supported Tracing Library:** The Datadog Tracing Library used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page for each ASM product.
+4. **Supported Tracing Library:** The Datadog Tracing Library used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page for each AAP product.
## Software Composition Analysis enablement types
diff --git a/content/en/security/code_security/troubleshooting/_index.md b/content/en/security/code_security/troubleshooting/_index.md
index d2c4d9a5cb335..235e408c66579 100644
--- a/content/en/security/code_security/troubleshooting/_index.md
+++ b/content/en/security/code_security/troubleshooting/_index.md
@@ -168,8 +168,8 @@ There are a series of steps that must run successfully for vulnerability informa
If you have enabled runtime vulnerability detection on your services, you can use the metric `datadog.apm.appsec_host` to check if SCA is running.
1. Go to **Metrics > Summary** in Datadog.
-2. Search for the metric `datadog.apm.appsec_host`. If the metric doesn't exist, then there are no services running ASM. If the metric exists, the services are reported with the metric tags `host` and `service`.
-3. Select the metric, and in the **Tags** section, search for `service` to see which services are running ASM.
+2. Search for the metric `datadog.apm.appsec_host`. If the metric doesn't exist, then there are no services running AAP. If the metric exists, the services are reported with the metric tags `host` and `service`.
+3. Select the metric, and in the **Tags** section, search for `service` to see which services are running AAP.
If you are not seeing `datadog.apm.appsec_host`, check the [in-app instructions][3] to confirm that all steps for the initial setup are complete.
diff --git a/content/en/security/default_rules/_index.md b/content/en/security/default_rules/_index.md
index 522c2d6f25ed1..97e9f1374dce8 100644
--- a/content/en/security/default_rules/_index.md
+++ b/content/en/security/default_rules/_index.md
@@ -34,11 +34,11 @@ cascade:
subcategory: Security Detection Rules
---
-Datadog provides out-of-the-box (OOTB) [detection rules][1] to flag attacker techniques and potential misconfigurations so you can immediately take steps to remediate. Datadog continuously develops new default rules, which are automatically imported into your account, your Application Security Management library, and the Agent, depending on your configuration.
+Datadog provides out-of-the-box (OOTB) [detection rules][1] to flag attacker techniques and potential misconfigurations so you can immediately take steps to remediate. Datadog continuously develops new default rules, which are automatically imported into your account, your App and API Protection library, and the Agent, depending on your configuration.
Datadog's Security Research team continuously adds new OOTB security detection rules. While the aim is to deliver high-quality detections with the release of integrations or other new features, the performance of these detections at scale often needs to be observed before making the rule generally available. These rules contain a Beta tag. This gives Datadog's Security Research team time to either refine or deprecate detection opportunities that do not meet Datadog's standards.
-Click the following buttons to filter the detection rules. Security detection rules are available for [Application Security Management][5], [Cloud SIEM][2] (log detection and signal correlation), [CSM Misconfigurations][3] (cloud and infrastructure), [CSM Threats][4], [CSM Identity Risks][6], and [Attack Paths][7].
+Click the following buttons to filter the detection rules. Security detection rules are available for [App and API Protection][5], [Cloud SIEM][2] (log detection and signal correlation), [Cloud Security Misconfigurations][3] (cloud and infrastructure), [Workload Protection][4], [Cloud Security Identity Risks][6], and [Attack Paths][7].
[1]: /security/detection_rules/
[2]: /security/cloud_siem/
diff --git a/content/en/security/detection_rules/_index.md b/content/en/security/detection_rules/_index.md
index 5bf81efdbc99b..b91a47705462d 100644
--- a/content/en/security/detection_rules/_index.md
+++ b/content/en/security/detection_rules/_index.md
@@ -22,10 +22,10 @@ products:
- name: Cloud SIEM
url: /security/cloud_siem/
icon: siem
-- name: Cloud Security Management
+- name: Cloud Security
url: /security/cloud_security_management/
icon: cloud-security-management
-- name: Application Security Management
+- name: App and API Protection
url: /security/application_security/
icon: app-sec
---
@@ -36,16 +36,16 @@ Detection rules define conditional logic that is applied to all ingested logs an
## Out-of-the-box detection rules
-Datadog provides [out-of-the-box detection rules][2] to flag attacker techniques and potential misconfigurations. When new detection rules are released, they are automatically imported into your account, your Application Security Management library, and the Agent, depending on your configuration.
+Datadog provides [out-of-the-box detection rules][2] to flag attacker techniques and potential misconfigurations. When new detection rules are released, they are automatically imported into your account, your App and API Protection library, and the Agent, depending on your configuration.
Out-of-the box rules are available for the following security products:
- [Cloud SIEM][3] uses log detection to analyze ingested logs in real-time.
-- Cloud Security Management (CSM):
- - [CSM Misconfigurations][4] uses cloud configuration and infrastructure configuration detection rules to scan the state of your cloud environment.
- - [CSM Threats][5] uses the Datadog Agent and detection rules to actively monitor and evaluate system activity.
- - [CSM Identity Risks][6] uses detection rules to detect IAM-based risks in your cloud infrastructure.
-- [Application Security Management][7] (ASM) leverages Datadog [APM][8], the [Datadog Agent][9], and detection rules to detect threats in your application environment.
+- Cloud Security:
+ - [Cloud Security Misconfigurations][4] uses cloud configuration and infrastructure configuration detection rules to scan the state of your cloud environment.
+ - [Workload Protection][5] uses the Datadog Agent and detection rules to actively monitor and evaluate system activity.
+ - [Cloud Security Identity Risks][6] uses detection rules to detect IAM-based risks in your cloud infrastructure.
+- [App and API Protection][7] (AAP) leverages Datadog [APM][8], the [Datadog Agent][9], and detection rules to detect threats in your application environment.
## Beta detection rules
@@ -53,13 +53,13 @@ Datadog's Security Research team continually adds new OOTB security detection ru
## Custom detection rules
-There may be situations where you need to customize a rule based on your environment or workload. For example, if you're using ASM, you may want to customize a detection rule that detects users performing sensitive actions from a geolocation where your business doesn't operate.
+There may be situations where you need to customize a rule based on your environment or workload. For example, if you're using AAP, you may want to customize a detection rule that detects users performing sensitive actions from a geolocation where your business doesn't operate.
To [create custom rules](#create-detection-rules), you can clone the default rules and edit the copies, or create your own rules from scratch.
## Search and filter detection rules
-To view out-of-the-box and custom detection rules in Datadog, navigate to the [**Security Settings**][10] page. Rules are listed on separate pages for each product (Application Security, Cloud Security Management, and Cloud SIEM).
+To view out-of-the-box and custom detection rules in Datadog, navigate to the [**Security Settings**][10] page. Rules are listed on separate pages for each product (Application Security, Cloud Security, and Cloud SIEM).
To search and filter the rules, use the search box and facets to query by value. For example, to only show rules for a given rule type, hover over the rule type and select `only`. You can also filter by facets such as `source` and `severity` when investigating and triaging incoming issues.
@@ -72,9 +72,9 @@ To create a custom detection rule, click the **New Rule** button in the upper-ri
For detailed instructions, see the following articles:
- [Cloud SIEM][11]
-- [ASM][12]
-- [CSM Misconfigurations][13]
-- [CSM Threats][14]
+- [AAP][12]
+- [Cloud Security Misconfigurations][13]
+- [Workload Protection][14]
## Manage detection rules
@@ -119,8 +119,8 @@ Use Rule Version History to:
To see the version history of a rule:
1. Navigate to the [Security Settings][15] page. In the left navigation panel:
- - For ASM: Click **Application Security** and then click **Detection Rules**.
- - For CSM: Click **Cloud Security Management** and then click **Threat Detection Rules**.
+ - For AAP: Click **Application Security** and then click **Detection Rules**.
+ - For Cloud Security: Click **Cloud Security** and then click **Threat Detection Rules**.
- For Cloud SIEM: Click **Cloud SIEM** and then click **Detection Rules**.
1. Click on the rule you are interested in.
1. In the rule editor, click **Version History** to see past changes.
@@ -151,7 +151,7 @@ The rule deprecation process is as follows:
1. There is a warning with the deprecation date on the rule. In the UI, the warning is shown in the:
- Signal side panel's **Rule Details > Playbook** section
- - Misconfigurations side panel (CSM Misconfigurations only)
+ - Misconfigurations side panel (Cloud Security Misconfigurations only)
- [Rule editor][10] for that specific rule
2. Once the rule is deprecated, there is a 15 month period before the rule is deleted. This is due to the signal retention period of 15 months. During this time, you can re-enable the rule by [cloning the rule](#clone-a-rule) in the UI.
3. Once the rule is deleted, you can no longer clone and re-enable it.
diff --git a/content/en/security/guide/aws_fargate_config_guide.md b/content/en/security/guide/aws_fargate_config_guide.md
index 4340782998f52..992e1ff8f3370 100644
--- a/content/en/security/guide/aws_fargate_config_guide.md
+++ b/content/en/security/guide/aws_fargate_config_guide.md
@@ -7,12 +7,12 @@ aliases:
further_reading:
- link: "https://www.datadoghq.com/blog/threat-detection-fargate/"
tag: "Blog"
- text: "Get real-time threat detection for AWS Fargate ECS and EKS environments with Datadog CSM"
+ text: "Get real-time threat detection for AWS Fargate ECS and EKS environments with Datadog Cloud Security"
---
-This guide walks you through configuring [Cloud Security Management (CSM)][3], [Software Composition Analysis (SCA)][22], [Threat Detection and Protection (ASM)][4], and [Cloud SIEM][5] on AWS Fargate.
+This guide walks you through configuring [Cloud Security][3], [Software Composition Analysis (SCA)][22], [Threat Detection and Protection (AAP)][4], and [Cloud SIEM][5] on AWS Fargate.
-{{< img src="security/datadog_security_coverage_aws_fargate.png" alt="Flow chart showing how CSM, ASM, and Cloud SIEM are configured on AWS Fargate" width="90%">}}
+{{< img src="security/datadog_security_coverage_aws_fargate.png" alt="Flow chart showing how Cloud Security, AAP, and Cloud SIEM are configured on AWS Fargate" width="90%">}}
## Full stack coverage for AWS Fargate
@@ -33,13 +33,13 @@ Datadog Security provides multiple layers of visibility for AWS Fargate. Use the
Fargate Application |
Application Performance Monitoring |
Software Composition Analysis (SCA) and Code Security |
-
ASM - Threat Detection and Protection |
+
AAP - Threat Detection and Protection |
}}
@@ -166,11 +166,11 @@ Blocking advanced distributed attacks is often a business decision because attac
Here are three critical components for success in mitigating these attacks:
-1. Proper onboarding: Are you configured for blocking with ASM?
+1. Proper onboarding: Are you configured for blocking with AAP?
2. Proper configuration: Ensure you have correctly set client IPs and X-Forwarded-For (XFF) HTTP headers.
3. Internal communication plans: Communication with security teams, service owners, and product leads is critical to understanding the impact of mitigating large scale attacks.
-