Skip to content

Commit c838d34

Browse files
authored
Updates CSPM deployment guides (#7074)
1 parent 887e8e2 commit c838d34

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

docs/cloud-native-security/cspm-get-started-aws.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You can set up CSPM for AWS either by enrolling a single cloud account, or by en
3232
. Click *Add Cloud Security Posture Management (CSPM)*.
3333
. Select *AWS*, then either *AWS Organization* to onboard multiple accounts, or *Single Account* to onboard an individual account.
3434
. Give your integration a name that matches the purpose or team of the AWS account/organization you want to monitor, for example, `dev-aws-account`.
35-
. Click **Advanced options**, then select **Agentless (BETA)**.
35+
. For **Deployment options**, select **Agentless**.
3636
. Next, you'll need to authenticate to AWS. Two methods are available:
3737
.. Option 1: Direct access keys/CloudFormation (Recommended). Under **Preferred method**, select **Direct access keys**. Expand the **Steps to Generate AWS Account Credentials** section, then follow the displayed instructions to automatically create the necessary credentials using CloudFormation.
3838
+
@@ -250,7 +250,7 @@ You can use the AWS CLI to generate temporary credentials. For example, you coul
250250

251251
[source,console]
252252
----------------------------------
253-
sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email<example-url> --duration-seconds 129600 --token-code 123456
253+
sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email@example.com --duration-seconds 129600 --token-code 123456
254254
----------------------------------
255255

256256
The output from this command includes the following fields, which you should provide when configuring the CSPM integration:

docs/cloud-native-security/cspm-get-started-azure.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You can set up CSPM for Azure by by enrolling an Azure organization (management
3232
. Click *Add Cloud Security Posture Management (CSPM)*.
3333
. Select *Azure*, then either *Azure Organization* to onboard your whole organization, or *Single Subscription* to onboard an individual subscription.
3434
. Give your integration a name that matches the purpose or team of the Azure subscription/organization you want to monitor, for example, `dev-azure-account`.
35-
. Click **Advanced options**, then select **Agentless (BETA)**.
35+
. For **Deployment options**, select **Agentless**.
3636
. Next, you'll need to authenticate to Azure by providing a **Client ID**, **Tenant ID**, and **Client Secret**. To learn how to generate them, refer to <<cspm-azure-client-secret, Service principal with client secret>>.
3737
. Once you've provided the necessary credentials, click **Save and continue** to finish deployment. Your data should start to appear within a few minutes.
3838

docs/cloud-native-security/cspm-get-started-gcp.asciidoc

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This page explains how to get started monitoring the security posture of your GC
2121
[[cspm-setup-gcp]]
2222
== Set up CSPM for GCP
2323

24-
You can set up CSPM for GCP either by enrolling a single project, or by enrolling an organization containing multiple projects. Either way, you need to first add the CSPM integration, then enable cloud account access. Two deployment technologies are available: agentless, and agent-based. <<cspm-gcp-agentless, Agentless deployment>> allows you to collect cloud posture data without having to manage the deployment of an agent in your cloud. <<cspm-gcp-agent-based, Agent-based deployment>> requires you to deploy and manage an agent in the cloud account you want to monitor.
24+
You can set up CSPM for GCP either by enrolling a single project, or by enrolling an organization containing multiple projects. Either way, you need to first add the CSPM integration, then enable access. Two deployment technologies are available: agentless, and agent-based. <<cspm-gcp-agentless, Agentless deployment>> allows you to collect cloud posture data without having to manage the deployment of an agent in your cloud. <<cspm-gcp-agent-based, Agent-based deployment>> requires you to deploy and manage an agent in the cloud project you want to monitor.
2525

2626
[discrete]
2727
[[cspm-gcp-agentless]]
@@ -30,9 +30,9 @@ You can set up CSPM for GCP either by enrolling a single project, or by enrollin
3030
. Find **Integrations** in the navigation menu or use the {kibana-ref}/introduction.html#kibana-navigation-search[global search field].
3131
. Search for `CSPM`, then click on the result.
3232
. Click *Add Cloud Security Posture Management (CSPM)*.
33-
. Select *GCP*, then either *GCP Organization* to onboard your whole organization, or *Single Account* to onboard an individual account.
34-
. Give your integration a name that matches the purpose or team of the GCP subscription/organization you want to monitor, for example, `dev-gcp-account`.
35-
. Click **Advanced options**, then select **Agentless (BETA)**.
33+
. Select *GCP*, then either *GCP Organization* to onboard your whole organization, or *Single Project* to onboard an individual project.
34+
. Give your integration a name that matches the purpose or team of the GCP subscription/organization you want to monitor, for example, `dev-gcp-project`.
35+
. For **Deployment options**, select **Agentless**.
3636
. Next, you'll need to authenticate to GCP. Expand the **Steps to Generate GCP Account Credentials** section, then follow the instructions that appear to automatically create the necessary credentials using Google Cloud Shell.
3737
. Once you've provided the necessary credentials, click **Save and continue** to finish deployment. Your data should start to appear within a few minutes.
3838

@@ -48,8 +48,8 @@ IMPORTANT: Agentless deployment does not work if you are using {cloud}/ec-traffi
4848
. Find **Integrations** in the navigation menu or use the {kibana-ref}/introduction.html#kibana-navigation-search[global search field].
4949
. Search for `CSPM`, then click on the result.
5050
. Click *Add Cloud Security Posture Management (CSPM)*.
51-
. Under *Configure integration*, select *GCP*, then either *GCP Organization* (recommended) or *Single Account*.
52-
. Give your integration a name that matches the purpose or team of the GCP account you want to monitor, for example, `dev-gcp-project`.
51+
. Under *Configure integration*, select *GCP*, then either *GCP Organization* (recommended) or *Single Project*.
52+
. Give your integration a name that matches the purpose or team of the GCP project you want to monitor, for example, `dev-gcp-project`.
5353

5454

5555
[discrete]
@@ -58,7 +58,7 @@ IMPORTANT: Agentless deployment does not work if you are using {cloud}/ec-traffi
5858

5959
NOTE: To set up CSPM for a GCP project, you need admin privileges for the project.
6060

61-
For most users, the simplest option is to use a Google Cloud Shell script to automatically provision the necessary resources and permissions in your GCP account. This method, as well as two manual options, are described below.
61+
For most users, the simplest option is to use a Google Cloud Shell script to automatically provision the necessary GCP resources and permissions. This method, as well as two manual options, are described below.
6262

6363
[discrete]
6464
[[cspm-set-up-cloudshell]]
@@ -67,8 +67,8 @@ For most users, the simplest option is to use a Google Cloud Shell script to aut
6767
. Under **Setup Access**, select **Google Cloud Shell**. Enter your GCP Project ID, and for GCP Organization deployments, your GCP Organization ID.
6868
. Under **Where to add this integration**:
6969
.. Select **New Hosts**.
70-
.. Name the {agent} policy. Use a name that matches the purpose or team of the cloud account or accounts you want to monitor. For example, `dev-gcp-account`.
71-
.. Click **Save and continue**, then **Add {agent} to your hosts**. The **Add agent** wizard appears and provides {agent} binaries, which you can download and deploy to a VM in your GCP account.
70+
.. Name the {agent} policy. Use a name that matches the purpose or team of the cloud project or projects you want to monitor. For example, `dev-gcp-project`.
71+
.. Click **Save and continue**, then **Add {agent} to your hosts**. The **Add agent** wizard appears and provides {agent} binaries, which you can download and deploy to a VM in GCP.
7272
. Click **Save and continue**.
7373
. Copy the command that appears, then click **Launch Google Cloud Shell**. It opens in a new window.
7474
. Check the box to trust Elastic's `cloudbeat` repo, then click **Confirm**
@@ -125,7 +125,7 @@ Provide credentials to the CSPM integration:
125125
. Enter your GCP **Organization ID**. Enter the GCP **Project ID** of the project where you want to provision the compute instance that will run CSPM.
126126
. Select **Credentials JSON**, and enter the value you generated earlier.
127127
. Under **Where to add this integration**, select **New Hosts**.
128-
. Name the {agent} policy. Use a name that matches the purpose or team of the cloud account or accounts you want to monitor. For example, `dev-gcp-account`.
128+
. Name the {agent} policy. Use a name that matches the purpose or team of the cloud project or project you want to monitor. For example, `dev-gcp-project`.
129129
. Click **Save and continue**, then follow the instructions to install {agent} in your chosen GCP project.
130130

131131
Wait for the confirmation that {kib} received data from your new integration. Then you can click **View Assets** to see your data.
@@ -172,7 +172,7 @@ Provide credentials to the CSPM integration:
172172
. Enter your GCP **Project ID**.
173173
. Select **Credentials JSON**, and enter the value you generated earlier.
174174
. Under **Where to add this integration**, select **New Hosts**.
175-
. Name the {agent} policy. Use a name that matches the purpose or team of the cloud account or accounts you want to monitor. For example, `dev-gcp-account`.
175+
. Name the {agent} policy. Use a name that matches the purpose or team of the cloud project or projects you want to monitor. For example, `dev-gcp-project`.
176176
. Click **Save and continue**, then follow the instructions to install {agent} in your chosen GCP project.
177177

178178
Wait for the confirmation that {kib} received data from your new integration. Then you can click **View Assets** to see your data.

0 commit comments

Comments
 (0)