Skip to content

Commit 6aeb9ba

Browse files
authored
CSPM for GCP and Agentless integrations updates (#1318)
Fixes #1317 — Incorporates feedback on the CSPM for GCP getting started guide, makes some minor updates to the Agentless Integrations page, and moves the Agentless Integrations FAQ to the appropriate location. Previews: [CSPM for GCP](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1318/solutions/security/cloud/get-started-with-cspm-for-gcp) [Agentless Integrations](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1318/solutions/security/get-started/agentless-integrations)
1 parent 0552400 commit 6aeb9ba

File tree

6 files changed

+19
-14
lines changed

6 files changed

+19
-14
lines changed

solutions/security/cloud/get-started-with-cspm-for-gcp.md

+11-3
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ You can set up CSPM for GCP either by enrolling a single project, or by enrollin
3535
1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
3636
2. Search for `CSPM`, then click on the result.
3737
3. Click **Add Cloud Security Posture Management (CSPM)**.
38-
4. Select **GCP**, then either **GCP Organization** to onboard your whole organization, or **Single Account** to onboard an individual account.
38+
4. Select **GCP**, then either **GCP Organization** to onboard your whole organization, or **Single Project** to onboard an individual account.
3939
5. 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`.
40-
6. Click **Advanced options**, then select **Agentless (BETA)**.
40+
6. Under **Deployment Options**, select **Agentless**.
4141
7. 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.
4242
8. Once you’ve provided the necessary credentials, click **Save and continue** to finish deployment. Your data should start to appear within a few minutes.
4343

@@ -53,7 +53,7 @@ Agentless deployment does not work if you are using [Traffic filtering](/deploy-
5353
1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
5454
2. Search for `CSPM`, then click on the result.
5555
3. Click **Add Cloud Security Posture Management (CSPM)**.
56-
4. Under **Configure integration**, select **GCP**, then either **GCP Organization** (recommended) or **Single Account**.
56+
4. Under **Configure integration**, select **GCP**, then either **GCP Organization** (recommended) or **Single Project**.
5757
5. Give your integration a name that matches the purpose or team of the GCP account you want to monitor, for example, `dev-gcp-project`.
5858

5959

@@ -124,6 +124,10 @@ gcloud organizations add-iam-policy-binding <ORG_ID> \
124124
--role=roles/browser
125125
```
126126

127+
::::{important}
128+
If running this command results in a warning related to conditions, try running it again with `--condition=None`.
129+
::::
130+
127131
::::{note}
128132
The `Cloud Asset Viewer` role grants read access to cloud asset metadata. The `Browser` role grants read access to the project hierarchy.
129133
::::
@@ -177,6 +181,10 @@ gcloud projects add-iam-policy-binding <PROJECT_ID> \
177181
--role=roles/browser
178182
```
179183

184+
::::{important}
185+
If running this command results in a warning related to conditions, try running it again with `--condition=None`.
186+
::::
187+
180188
::::{note}
181189
The `Cloud Asset Viewer` role grants read access to cloud asset metadata. The `Browser` role grants read access to the project hierarchy.
182190
::::

troubleshoot/security/agentless-integrations.md renamed to solutions/security/get-started/agentless-integrations-faq.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ For agentless integrations to successfully connect to {{elastic-sec}}, the {{fle
2424

2525
To troubleshoot this issue:
2626

27-
1. Find **{{fleet}}** in the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab.
27+
1. Find **{{fleet}}** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab.
2828
2. Under **{{fleet}} server hosts**, click the **Actions** button for the policy named `Default`. This opens the Edit {{fleet}} Server flyout. The policy named `Default` should have the **Make this {{fleet}} server the default one** setting enabled. If not, enable it, then delete your integration and create it again.
2929

3030
::::{note}
@@ -44,7 +44,7 @@ On the **{{fleet}}** page, the agent associated with an agentless integration ha
4444
```
4545
4646
47-
For instructions on checking {{fleet}} logs, refer to [{{fleet}} troubleshooting](../ingest/fleet/common-problems.md).
47+
For instructions on checking {{fleet}} logs, refer to [{{fleet}} troubleshooting](/troubleshoot/ingest/fleet/common-problems.md).
4848
4949
5050
## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]
@@ -56,7 +56,7 @@ Deleting your integration will remove all associated resources and stop data ing
5656
5757
When you create a new agentless CSPM integration, a new agent policy appears within the **Agent policies** tab on the **{{fleet}}** page, but you can’t use the **Delete integration** button on this page. Instead, you must delete the integration from the CSPM Integration’s **Integration policies** tab.
5858
59-
1. Find **Integrations** in the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), then search for and select `CSPM`.
59+
1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then search for and select `CSPM`.
6060
2. Go to the CSPM Integration’s **Integration policies** tab.
6161
3. Find the integration policy for the integration you want to delete. Click **Actions**, then **Delete integration**.
6262
4. Confirm by clicking **Delete integration** again.

solutions/security/get-started/agentless-integrations.md

+4-6
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ applies_to:
1212

1313
Agentless integrations provide a means to ingest data while avoiding the orchestration, management, and maintenance needs associated with standard ingest infrastructure. Using agentless integrations makes manual agent deployment unnecessary, allowing you to focus on your data instead of the agent that collects it.
1414

15-
We support the following agentless integrations:
15+
::::{important}
16+
There are currently no additional costs associated with deploying agentless integrations.
17+
::::
1618

1719
## Generally available (GA) agentless integrations
1820

19-
::::{note}
20-
For a single {{serverless-full}} project, a maxium of 30 agentless deployments are supported.
21-
::::
21+
We fully support the following agentless integrations:
2222

2323
Cloud security posture management (CSPM). Using this integration’s agentless deployment option, you can enable Elastic’s CSPM capabilities just by providing the necessary credentials. Agentless CSPM deployments support AWS, Azure, and GCP accounts.
2424

@@ -28,8 +28,6 @@ To learn more about agentless CSPM deployments, refer to the getting started gui
2828

2929
::::{warning}
3030
Agentless deployment for the following integrations is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
31-
32-
While agentless deployment for these integrations is in beta, for a single {{serverless-full}} project a maxium of five agentless deployments are currently supported.
3331
::::
3432

3533
1. AbuseCH

solutions/toc.yml

+1
Original file line numberDiff line numberDiff line change
@@ -467,6 +467,7 @@ toc:
467467
- file: security/get-started/automatic-migration.md
468468
- file: security/get-started/automatic-import.md
469469
- file: security/get-started/agentless-integrations.md
470+
- file: security/get-started/agentless-integrations-faq.md
470471
- file: security/get-started/spaces-elastic-security.md
471472
- file: security/get-started/data-views-elastic-security.md
472473
- file: security/get-started/create-runtime-fields-in-elastic-security.md

troubleshoot/security.md

-1
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,3 @@ This section covers common {{elastic-sec}} related issues and how to resolve the
1616
* [Troubleshoot detection rules](security/detection-rules.md)
1717
* [Troubleshoot {{elastic-defend}}](security/elastic-defend.md)
1818
* [Troubleshoot indicators of compromise](security/indicators-of-compromise.md)
19-
* [Agentless integrations FAQ](security/agentless-integrations.md)

troubleshoot/toc.yml

-1
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,6 @@ toc:
137137
- file: security/detection-rules.md
138138
- file: security/elastic-defend.md
139139
- file: security/indicators-of-compromise.md
140-
- file: security/agentless-integrations.md
141140
- file: ingest.md
142141
children:
143142
# - file: ingest/enterprise-search/crawls.md

0 commit comments

Comments
 (0)