topic Re: Using Webhook to send data to internal server? in Splunk Enterprise Security

Using Webhook to send data to internal server?

st1 — Fri, 31 Oct 2025 14:18:48 GMT

I'm trying to set up an open-source SOAR tool and need to get the results of a correlation search from Splunk. Using a webhook would a way to do this but is there any way have the webhook not reach out externally and then come back into the internal server where the SOAR is hosted?

The internal server is not externally exposed so this causes issue with the Splunk search head being able to reach the server. We are running Splunk on-prem. Thanks.

Re: Using Webhook to send data to internal server?

livehybrid — Fri, 31 Oct 2025 15:59:52 GMT

Hi @st1

You can use any webhook address you want for the webhook URL from your Splunk SH - Does your SOAR tool present a webhook endpoint that you can send to? If not you will need some sort of middle-man webhook system to forward the request.

Ultimately if the endpoint you are sending to is internal then you can use this and it therefore wouldnt go externally.

🌟 Did this answer help you? If so, please consider:

Adding karma to show it was useful
Marking it as the solution if it resolved your issue
Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

Re: Using Webhook to send data to internal server?

st1 — Mon, 03 Nov 2025 16:29:44 GMT

The SOAR tool does present a webhook but the since the tool is hosted on an internal only server, our Splunk server is trying to reach the webhook by resolving the webhook address externally. Is there a way to force Splunk to only resolve that webbook address internally is what I'm wondering? Without having to use a middleman service

Re: Using Webhook to send data to internal server?

ITWhisperer — Mon, 03 Nov 2025 16:38:22 GMT

This sounds like a name resolution problem. Is your internal server on a fixed (internal) ip address? If so, use that in your webhook. If not, presumably the address is registered in a local name server? If so, configure your DNS lookup to query that server first. Alternatively, you might be able to hard-code the address resolution in your hosts file (/etc/hosts for example).