Documents traffic filtering support for agentless integrations

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

@@ -76,3 +76,16 @@
 
 No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.
 
+## Do agentless integrations work if I'm using traffic filtering?
+
+::::{applies-switch}
+
+:::{applies-item} serverless: ga
+Agentless integrations do not support traffic filtering.
+:::
+
+:::{applies-item} stack: ga 9.1+
+Agentless integrations support traffic filtering. No additional configuration is necessary.
+:::
+
+::::

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

@@ -22,9 +22,10 @@ There is a limit of 5 agentless integrations per project.
 
 ## Requirements
 
-* Agentless integrations are supported only on {{ech}}, {{sec-serverless}}, and {{obs-serverless}} deployments.
+* 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).
+* For {{serverless-short}} deployments, traffic filtering must not be enabled.
 
 ## Generally available (GA) agentless integrations