All Apps and Add-ons

FireEye XML to Universal Forwarder

raziasaduddin
Path Finder

I am trying to set up FireEye to send events to our dedicated universal forwarder in XML Extended over port 8089 . I took the guts of the FireEye app, and set up the FireEye side according to the instructions and am still not getting events.

https://:8089/services/receivers/simple?source=FE_test&sourcetype=fe_xml&index=fe

Questions:

1) Does it have to run under the "admin" account?

2) Does it have to run under an account in the admin role?

3) How do we send these to a dedicated universal forwarder? Do we need anything in inputs.conf or server.conf?

4) Can the forwarder use an account created on a search head or must they be linked?

Thanks!

Tags (2)
0 Karma
1 Solution

monzy
Communicator

1) based on my testing, it does have to run under the admin account or a user in the admin role. based on your question, i created another splunk question to get help: http://splunk-base.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-recei...

2) seems to be the case. although, to be clear, this is not necessarily tied to the FireEye app but to anything that attempts to use the http simple receiver, REST endpoint.

3) you don't need anything in inputs.conf. the http post specifies the input and the neccesary parameters.

4) in your scenario, fireeye is sending the data to the forwarder. so the user/passwd you use in the fireeye config must have the appropriate permissions in the forwarder.

View solution in original post

khourihan_splun
Splunk Employee
Splunk Employee

Check out this pdf from FE. Describes non-admin user and using https to push data in.

https://www.fireeye.com/content/dam/fireeye-www/global/en/partners/pdfs/fireeye-splunk-intermediate-...

0 Karma

monzy
Communicator

1) based on my testing, it does have to run under the admin account or a user in the admin role. based on your question, i created another splunk question to get help: http://splunk-base.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-recei...

2) seems to be the case. although, to be clear, this is not necessarily tied to the FireEye app but to anything that attempts to use the http simple receiver, REST endpoint.

3) you don't need anything in inputs.conf. the http post specifies the input and the neccesary parameters.

4) in your scenario, fireeye is sending the data to the forwarder. so the user/passwd you use in the fireeye config must have the appropriate permissions in the forwarder.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...