From 23851de29f2542a166726db5ff48ecf0c7637bf8 Mon Sep 17 00:00:00 2001 From: DeForest Richards Date: Mon, 13 Jan 2025 14:24:03 -0700 Subject: [PATCH 1/5] Initial commit --- .../azure_resource_manager.md | 2 +- .../agentless_scanning/cloudformation.md | 4 +-- .../setup/agentless_scanning/quick_start.md | 2 +- .../setup/agentless_scanning/terraform.md | 4 +-- .../setup/cloud_integrations.md | 28 ++----------------- layouts/shortcodes/csm-setup-aws.en.md | 10 ------- layouts/shortcodes/csm-setup-azure.en.md | 10 ------- .../shortcodes/csm-setup-google-cloud.en.md | 10 ------- 8 files changed, 8 insertions(+), 62 deletions(-) diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md b/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md index d48e2e1a2a3c6..62fdd9ca18bc5 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md @@ -42,7 +42,7 @@ Follow the instructions for setting up the [Datadog Azure integration][1]. 1. On the [Cloud Security Management Setup][3] 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 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**. ## Uninstall with Azure Resource Manager diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md b/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md index 6850371d0bcc6..0a260e6ca9ba6 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md @@ -38,7 +38,7 @@ If you've already [set up Cloud Security Management][3] and want to add a new cl {{% tab "Existing AWS account" %}} 1. On the [Cloud Security Management 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. 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 **Host Vulnerability Scanning**, **Container Vulnerability Scanning**, **Lambda Vulnerability Scanning**, and **Data Security Scanning** to the on position. 1. Click **Done**. @@ -65,7 +65,7 @@ Datadog recommends updating the CloudFormation stack regularly, so you can get a ## Disable Agentless Scanning 1. On the [Cloud Security Management Setup][3] 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. 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**. ## Uninstall with CloudFormation diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md b/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md index c8c95c9857bd6..f65258184ee97 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md @@ -47,7 +47,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. 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. 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**. ## Uninstall Agentless Scanning diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md b/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md index b9218c6db07f0..d1a613f50881c 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md @@ -37,7 +37,7 @@ If you've already [set up Cloud Security Management][4] and want to add a new cl {{% tab "Existing AWS account" %}} 1. On the [Cloud Security Management 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. 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**. 1. Follow the instructions for installing the [Datadog Agentless Scanner module][2]. @@ -72,7 +72,7 @@ If you've already [set up Cloud Security Management][4] and want to add a new cl ## Disable Agentless Scanning 1. On the [Cloud Security Management Setup][4] 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. 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**. ## Uninstall with Terraform 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 45423939ebcb3..589cf66da25a0 100644 --- a/content/en/security/cloud_security_management/setup/cloud_integrations.md +++ b/content/en/security/cloud_security_management/setup/cloud_integrations.md @@ -37,62 +37,38 @@ To enable resource scanning for your cloud accounts, you must first set up the i ## Disable resource scanning -To disable resource scanning for your cloud accounts, navigate to either the [**CSM Setup**][1] page or the cloud account integration page. Disabling resource scanning does not affect your ability to access historical findings. You can still review data from the past 15 months. +
You can access historical findings from the past 15 months even if resource scanning is disabled.
{{< tabs >}} {{% tab "AWS" %}} -### CSM Setup page - 1. On the [**Cloud Security Management Setup**][1] page, click **Cloud Integrations**. 1. Expand the **AWS** section. -1. To stop resource collection for an account, click the Edit button and switch the **Enable Resource Scanning** toggle to the off position. +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**. -### Amazon Web Services integration page - -1. On the [**Amazon Web Services Integration**][2] page, select an AWS account. -1. On the **Resource Collection** tab, clear the **Enable Cloud Security Management** checkbox. -1. Click Save. - [1]: https://app.datadoghq.com/security/configuration/csm/setup [2]: https://app.datadoghq.com/integrations/amazon-web-services {{% /tab %}} {{% tab "Azure" %}} -### CSM Setup page - 1. On the [**Cloud Security Management 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**. -### Azure integration page - -1. On the [**Azure Integration**][2] page, select an app registration. -1. On the **Resource Collection** tab, clear the **Enable Cloud Security Management** checkbox. -1. Click Save. - [1]: https://app.datadoghq.com/security/configuration/csm/setup [2]: https://app.datadoghq.com/integrations/azure {{% /tab %}} {{% tab "Google Cloud" %}} -### CSM Setup page - 1. On the [**Cloud Security Management 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**. -### Google Cloud Platform integration page - -1. On the [**Google Cloud Platform Integration**][2] page, select a Google Cloud account. -1. On the **Resource Collection** tab, clear the **Enable Cloud Security Management** checkbox. -1. Click **Save**. - [1]: https://app.datadoghq.com/security/configuration/csm/setup [2]: https://app.datadoghq.com/integrations/google-cloud-platform diff --git a/layouts/shortcodes/csm-setup-aws.en.md b/layouts/shortcodes/csm-setup-aws.en.md index 9d9ad4fa55fae..4f3b3a686e105 100644 --- a/layouts/shortcodes/csm-setup-aws.en.md +++ b/layouts/shortcodes/csm-setup-aws.en.md @@ -4,10 +4,6 @@ If you haven't already, set up the [Amazon Web Services integration][1]. You mus ### Enable CSM for your AWS accounts -Use one of the following methods to enable CSM for your AWS accounts: - -#### CSM Setup page - 1. On the [**Cloud Security Management Setup**][3] page, click **Cloud Integrations**. 1. Expand the **AWS** section. 1. To enable resource scanning for an account, click the **Plus** button, then switch the **Enable Resource Scanning** toggle to the on position. @@ -15,12 +11,6 @@ Use one of the following methods to enable CSM for your AWS accounts: 1. To create a filter that excludes certain resources from being evaluated by CSM, click the **Plus** (+) icon under **Resource Evaluation Filters (Optional)**. For more information, see [Use Filters to Exclude Resources from Evaluation][5]. 1. Click **Done**. -#### Amazon Web Services integration page - -1. On the [**Amazon Web Services Integration**][4] page, select an AWS account. -1. On the **Resource Collection** tab, select **Enable Cloud Security Management**. -1. Click **Save**. - [1]: https://docs.datadoghq.com/integrations/amazon_web_services/ [2]: /integrations/amazon_web_services/?tab=roledelegation#cloud-security-management-misconfigurations [3]: https://app.datadoghq.com/security/configuration/csm/setup diff --git a/layouts/shortcodes/csm-setup-azure.en.md b/layouts/shortcodes/csm-setup-azure.en.md index e4df30d8b9d3e..d94460f6bec3d 100644 --- a/layouts/shortcodes/csm-setup-azure.en.md +++ b/layouts/shortcodes/csm-setup-azure.en.md @@ -6,22 +6,12 @@ If you haven't already, set up the [Microsoft Azure integration][1]. ### Enable CSM for your Azure subscriptions -Use one of the following methods to enable CSM for your Azure subscriptions: - -#### CSM Setup page - 1. On the [**Cloud Security Management Setup**][2] page, click **Cloud Integrations**. 2. Expand the **Azure** section. 3. To enable resource scanning for a subscription, switch the **Resource Scanning** toggle to the on position. 4. To create a filter that excludes certain resources from being evaluated by CSM, click the **Plus** (+) icon under **Resource Evaluation Filters (Optional)**. For more information, see [Use Filters to Exclude Resources from Evaluation][4]. 5. Click **Done**. -#### Azure integration page - -1. On the [**Azure Integration**][3] page, select an Azure app registration. -2. Under **Resource Collection**, select **Enable Cloud Security Management**. -3. Click **Submit Changes**. - [1]: https://docs.datadoghq.com/integrations/azure [2]: https://app.datadoghq.com/security/configuration/csm/setup [3]: https://app.datadoghq.com/integrations/azure diff --git a/layouts/shortcodes/csm-setup-google-cloud.en.md b/layouts/shortcodes/csm-setup-google-cloud.en.md index f0835acf8ddb4..93bbcabbc45fe 100644 --- a/layouts/shortcodes/csm-setup-google-cloud.en.md +++ b/layouts/shortcodes/csm-setup-google-cloud.en.md @@ -15,22 +15,12 @@ The Datadog Google Cloud Platform integration uses service accounts to create an ### Enable CSM for your Google Cloud projects -Use one of the following methods to enable CSM for your Google Cloud projects: - -#### CSM Setup page - 1. On the [**Cloud Security Management Setup**][2] page, click **Cloud Integrations**. 2. Expand the **GCP** section. 3. To enable resource scanning for a project, switch the **Resource Scanning** toggle to the on position. 4. To create a filter that excludes certain resources from being evaluated by CSM, click the **Plus** (+) icon under **Resource Evaluation Filters (Optional)**. For more information, see [Use Filters to Exclude Resources from Evaluation][11]. 5. Click **Done**. -#### Google Cloud Platform integration page - -1. On the [**Google Cloud Platform Integration**][10] page, select a Google Cloud project. -2. Under **Resource Collection**, select **Enable Cloud Security Management**. -3. Click **Save**. - [1]: https://docs.datadoghq.com/integrations/google_cloud_platform [2]: https://app.datadoghq.com/security/configuration/csm/setup [4]: https://support.google.com/cloud/answer/6293499?hl=en From a189d4c61dc554d0d562c84f2f071a9ee53eab73 Mon Sep 17 00:00:00 2001 From: DeForest Richards Date: Mon, 13 Jan 2025 16:24:37 -0700 Subject: [PATCH 2/5] Update resource scanning instructions --- .../setup/without_infrastructure_monitoring.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) 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 ba58d01ba715e..90f05937f82c9 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 @@ -2,7 +2,7 @@ title: Setting Up CSM without Infrastructure Monitoring --- -In addition to setting up CSM with or without an Agent, you can also set it up 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. ## Set up CSM on your AWS account @@ -11,8 +11,9 @@ In addition to setting up CSM with or without an Agent, you can also set it up w 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. To turn on CSM, on the **Resource Collection** tab, turn on the **Enable Resource Collection** toggle, and select the **Enable Cloud Security Management** checkbox. -1. Click **Save**. +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 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. @@ -23,8 +24,9 @@ In addition to setting up CSM with or without an Agent, you can also set it up w 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. To turn on CSM, on the **Resource Collection** tab, turn on the **Enable Resource Collection** toggle, and select the **Enable Cloud Security Management** checkbox. -1. Click **Save**. +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. 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. @@ -35,8 +37,9 @@ In addition to setting up CSM with or without an Agent, you can also set it up w 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. To turn on CSM, on the **Resource Collection** tab, turn on the **Enable Resource Collection** toggle, and select the **Enable Cloud Security Management** checkbox. -1. Click **Save**. +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. 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. From e57f08a756f523690c36112d376ae25c341bd880 Mon Sep 17 00:00:00 2001 From: DeForest Richards Date: Tue, 14 Jan 2025 10:26:23 -0700 Subject: [PATCH 3/5] Update resource collection link --- layouts/shortcodes/csm-setup-aws.en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/layouts/shortcodes/csm-setup-aws.en.md b/layouts/shortcodes/csm-setup-aws.en.md index 4f3b3a686e105..8889f2044a27f 100644 --- a/layouts/shortcodes/csm-setup-aws.en.md +++ b/layouts/shortcodes/csm-setup-aws.en.md @@ -1,6 +1,6 @@ ### Set up the Datadog AWS integration -If you haven't already, set up the [Amazon Web Services integration][1]. You must also add the [required permissions][2] for resource collection. +If you haven't already, set up the [Amazon Web Services integration][1]. You must also [enable resource collection][2] by attaching the AWS-managed SecurityAudit Policy to the Datadog IAM role in your AWS account. ### Enable CSM for your AWS accounts @@ -12,7 +12,7 @@ If you haven't already, set up the [Amazon Web Services integration][1]. You mus 1. Click **Done**. [1]: https://docs.datadoghq.com/integrations/amazon_web_services/ -[2]: /integrations/amazon_web_services/?tab=roledelegation#cloud-security-management-misconfigurations +[2]: /integrations/amazon_web_services/?tab=roledelegation#cloud-security-management [3]: https://app.datadoghq.com/security/configuration/csm/setup [4]: https://app.datadoghq.com/integrations/amazon-web-services [5]: /security/cloud_security_management/guide/resource_evaluation_filters \ No newline at end of file From b2b40721c067582d4c6fbae4c4a94ea4cb35d579 Mon Sep 17 00:00:00 2001 From: DeForest Richards Date: Tue, 14 Jan 2025 11:50:13 -0700 Subject: [PATCH 4/5] Revert changes captured in other PR --- .../setup/agentless_scanning/azure_resource_manager.md | 2 +- .../setup/agentless_scanning/cloudformation.md | 4 ++-- .../setup/agentless_scanning/quick_start.md | 2 +- .../setup/agentless_scanning/terraform.md | 4 ++-- .../cloud_security_management/setup/cloud_integrations.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md b/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md index 62fdd9ca18bc5..d48e2e1a2a3c6 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md @@ -42,7 +42,7 @@ Follow the instructions for setting up the [Datadog Azure integration][1]. 1. On the [Cloud Security Management Setup][3] 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 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**. ## Uninstall with Azure Resource Manager diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md b/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md index 0a260e6ca9ba6..6850371d0bcc6 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/cloudformation.md @@ -38,7 +38,7 @@ If you've already [set up Cloud Security Management][3] and want to add a new cl {{% tab "Existing AWS account" %}} 1. On the [Cloud Security Management 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. 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 **Host Vulnerability Scanning**, **Container Vulnerability Scanning**, **Lambda Vulnerability Scanning**, and **Data Security Scanning** to the on position. 1. Click **Done**. @@ -65,7 +65,7 @@ Datadog recommends updating the CloudFormation stack regularly, so you can get a ## Disable Agentless Scanning 1. On the [Cloud Security Management Setup][3] 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. 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**. ## Uninstall with CloudFormation diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md b/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md index f65258184ee97..c8c95c9857bd6 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md @@ -47,7 +47,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. 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. 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**. ## Uninstall Agentless Scanning diff --git a/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md b/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md index d1a613f50881c..b9218c6db07f0 100644 --- a/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md +++ b/content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md @@ -37,7 +37,7 @@ If you've already [set up Cloud Security Management][4] and want to add a new cl {{% tab "Existing AWS account" %}} 1. On the [Cloud Security Management 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. 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**. 1. Follow the instructions for installing the [Datadog Agentless Scanner module][2]. @@ -72,7 +72,7 @@ If you've already [set up Cloud Security Management][4] and want to add a new cl ## Disable Agentless Scanning 1. On the [Cloud Security Management Setup][4] 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. 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**. ## Uninstall with Terraform 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..2eaa30efddbc5 100644 --- a/content/en/security/cloud_security_management/setup/cloud_integrations.md +++ b/content/en/security/cloud_security_management/setup/cloud_integrations.md @@ -44,7 +44,7 @@ To enable resource scanning for your cloud accounts, you must first set up the i 1. On the [**Cloud Security Management 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. 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**. [1]: https://app.datadoghq.com/security/configuration/csm/setup From 074afc3a22a7577918eb91be5a3c973461f0abf8 Mon Sep 17 00:00:00 2001 From: DeForest Richards Date: Tue, 14 Jan 2025 11:53:48 -0700 Subject: [PATCH 5/5] Add parentheses --- .../cloud_security_management/setup/cloud_integrations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 2eaa30efddbc5..589cf66da25a0 100644 --- a/content/en/security/cloud_security_management/setup/cloud_integrations.md +++ b/content/en/security/cloud_security_management/setup/cloud_integrations.md @@ -44,7 +44,7 @@ To enable resource scanning for your cloud accounts, you must first set up the i 1. On the [**Cloud Security Management 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. 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**. [1]: https://app.datadoghq.com/security/configuration/csm/setup