# Issue with Elastic Agent Imperva Integration

**URL:** <https://discuss.elastic.co/t/issue-with-elastic-agent-imperva-integration/374357>\
**Category:** SIEM\
**Created:** [February 11, 2025, 11:26am UTC](https://discuss.elastic.co/t/issue-with-elastic-agent-imperva-integration/374357 "2025-02-11T11:26:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cyberm](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@cyberm](https://discuss.elastic.co/u/cyberm)\
**Post date:** [February 11, 2025, 11:26am UTC](https://discuss.elastic.co/t/issue-with-elastic-agent-imperva-integration/374357/1 "2025-02-11T11:26:07Z")

</div>

Hi all,

We are experiencing the same issue as described in this previous post ([Elastic Agent Imperva Integration](https://discuss.elastic.co/t/elastic-agent-imperva-integration/356718) , from @mgotechlock ), which was closed as unresolved.

We are investigating the cause of this anomaly. Have you managed to find a solution?

We tested the API call directly via Postman to:

[https://logs](https://logs){value}.incapsula.com/{value}/logs.index

docs: [Imperva Documentation Portal](https://docs.imperva.com/bundle/cloud-application-security/page/settings/log-integration.htm)

We successfully retrieved the list of log files that should be handled by the ELK integration. However, we haven't yet found a way to resolve the issue within Elastic Integration (Imperva Cloud WAF).

Any insights or suggestions would be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 11, 2025, 11:26am UTC](https://discuss.elastic.co/t/issue-with-elastic-agent-imperva-integration/374357/2 "2025-03-11T11:26:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.