Skip to content

Agentless prerequisites #4175

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Dec 2, 2025
+8 −2
Merged

Agentless prerequisites #4175

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
471e015
Agentless availability
lucabelluccini Dec 1, 2025
8ea9688
Another version of this PR
benironside Dec 1, 2025
ee60668
Creates requirements section for agentless integrations
benironside Dec 1, 2025
00775e0
fixes broken link
benironside Dec 1, 2025
74e0030
Merge branch 'main' into docs-agentless-faq-availablility
benironside Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions solutions/security/get-started/_snippets/agentless-integrations-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
Frequently asked questions and troubleshooting steps for {{elastic-sec}}'s agentless CSPM integration.


## When I make a new integration, when will I see the agent appear on the Integration Policies page? [_when_i_make_a_new_integration_when_will_i_see_the_agent_appear_on_the_integration_policies_page]

After you create a new agentless integration, the new integration policy may show a button that says **Add agent** instead of the associated agent for several minutes during agent enrollment. No action is needed other than refreshing the page once enrollment is complete.
Expand Down Expand Up @@ -76,4 +75,5 @@ When you create a new agentless CSPM integration, a new agent policy appears wit

## Can agentless integrations use a specific range of static IP addresses for configuring allow and deny rules for traffic?

No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.
No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.

6 changes: 6 additions & 0 deletions solutions/security/get-started/agentless-integrations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ During technical preview, there are no additional costs associated with deployin
There is a limit of 5 agentless integrations per project.
::::

## Requirements

* Agentless integrations are supported only on {{ech}}, {{sec-serverless}}, and {{obs-serverless}} deployments.
* On {{ech}}, agentless integrations require a working [{{fleet-server}}](/reference/fleet/fleet-server.md).
* To set up a new agentless integration, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).

## Generally available (GA) agentless integrations

Elastic fully supports agentless deployment for the Cloud Security Posture Management (CSPM) integration. 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.
Expand Down
Loading