-
Notifications
You must be signed in to change notification settings - Fork 205
[8.16] Updates CSPM guides to include agentless option #5863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 7 commits
69742e6
99c8b64
b9a2f29
02551f8
99d6284
a9dbee8
fbcda4b
75a273f
d45719b
8a76391
952df1f
6084b21
c97db47
3b81925
5760f6d
24b1b7b
9b0f464
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -38,15 +38,19 @@ You can set up CSPM for AWS either by enrolling a single cloud account, or by en | |
| . Click *Add Cloud Security Posture Management (CSPM)*. | ||
| . Select *AWS*, then either *AWS Organization* to onboard multiple accounts, or *Single Account* to onboard an individual account. | ||
| . 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`. | ||
| . beta:[] (Optional) Click **Advanced settings** to deploy the integration using agentless technology. | ||
|
|
||
|
|
||
|
|
||
| [discrete] | ||
| [[cspm-set-up-cloud-access-section]] | ||
| == Set up cloud account access | ||
| The CSPM integration requires access to AWS’s built-in https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_security-auditor[`SecurityAudit` IAM policy] in order to discover and evaluate resources in your cloud account. There are several ways to provide access. | ||
| The CSPM integration requires access to AWS's built-in https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_security-auditor[`SecurityAudit` IAM policy] in order to discover and evaluate resources in your cloud account. There are several ways to provide access. | ||
|
|
||
| For most use cases, the simplest option is to use AWS CloudFormation to automatically provision the necessary resources and permissions in your AWS account. This method, as well as several manual options, are described below. | ||
|
|
||
| NOTE: beta:[] Agentless deployments support two authentication methods: <<cspm-use-temp-credentials, temporary keys>> and <<cspm-use-keys-directly, direct access keys>>. | ||
|
|
||
| [discrete] | ||
| [[cspm-set-up-cloudformation]] | ||
| === CloudFormation (recommended) | ||
|
|
@@ -208,7 +212,7 @@ image::images/cspm-aws-auth-3.png[The EC2 page in AWS, showing the Modify IAM ro | |
| .. Click *Update IAM role*. | ||
| .. Return to {kib} and <<cspm-finish-manual, finish manual setup>>. | ||
|
|
||
| IMPORTANT: Make sure to deploy the CSPM integration to this EC2 instance. When completing setup in {kib}, in the *Setup Access* section, select *Assume role* and leave *Role ARN* empty. Click *Save and continue*. | ||
| IMPORTANT: Make sure to deploy the CSPM integration to this EC2 instance. When completing setup in {kib}, in the *Setup Access* section, select *Assume role*. Leave **Role ARN** empty unless you want to specify a role the ((agent)) should assume instead of the default role for your EC2 instance. Click *Save and continue*. | ||
|
|
||
| [discrete] | ||
| [[cspm-use-keys-directly]] | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @smriti0321 I think there are a few callouts or troubleshooting guide for missing regarding Agentless Onboarding.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Great inputs @Omolola-Akinleye There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the FAQ seems like a good option. Let's cover this in our next sync |
||
|
|
@@ -222,7 +226,7 @@ IMPORTANT: You must select *Programmatic access* when creating the IAM user. | |
| [discrete] | ||
| [[cspm-use-temp-credentials]] | ||
| === Option 3 - Temporary security credentials | ||
| You can configure temporary security credentials in AWS to last for a specified duration. They consist of an access key ID, a secret access key, and a security token, which is typically found using `GetSessionToken`. | ||
| You can configure temporary security credentials in AWS to last for a specified duration. They consist of an access key ID, a secret access key, and a session token, which is typically found using `GetSessionToken`. | ||
|
|
||
| Because temporary security credentials are short term, once they expire, you will need to generate new ones and manually update the integration's configuration to continue collecting cloud posture data. Update the credentials before they expire to avoid data loss. | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| [[agentless-integrations]] | ||
| = Agentless integrations | ||
|
|
Uh oh!
There was an error while loading. Please reload this page.