The Targeted Server Becomes A Source In Logging

[Former Member]

When using Splunk to query the  FireEyeNX IDS the logging has an anomaly. It's showing  the source of the IDS attack signatures are the web server we're protecting. So what was the target is now the source and it's created an event with the attack signature. The malicious IP is now the destination of alert. How can this happen?

Splunk is just displaying the attributes in the logged event. A lot of the event attributes say 'Inconclusive' or 'Unknown.'  Is this because of logging formats?  Could this be the reason our target now becomes the source of the attack signature out to the suspicious IP?

[petermason]

Hi Aoc,

If your query is about Splunk and FireEye you're on the wrong support site.

If you mean a McAfee NSP manager and Splunk it's probably just the way you have your Syslog message set up, can you share the details of the variables you have set in NSP.

Regards

Peter Mason

[Former Member]

Hey, sorry if the question about McAfee IDS / NX is in the wrong forum because it has a relationship to Splunk in this question. It is  about FireEye's logging. My approach to this situation was to see why the FireEye device would report this way. I wanted to reach out to the community to see if anyone has had this occur. Tricky situation...did FireEye's log give the Splunk query the wrong information? Perhaps. Ty for the tip I'll research about syslog.