Target Device Reports As Source

[Aoc]

In Splunk the McAfee logging is showing that a few of the IDS alerts the web server we're protecting is the source of some of the attacks. The server that was the destination of the attack by the malicious IP is now the source. The malicious IP is the destination of alert. How can this happen?

[MarkCMc]

Are you talking about Host IPS or the Network Security Platform (NSP) IPS? Either way I'm not sure we have any control over how Splunk displays the events.

[Aoc]

Network IPS. Just to clarify and get on the same page, Splunk is just displaying the attributes in the logged event. It's not changing the event information, essentially. Of course the issue can be all the different logging formats out there make it difficult. In the logs from the IPS, pulled and displayed by Splunk, some attributes are listed as Unknown or Inconclusive. Is this what you mean about not controlling how Splunk displays?; (two ways to interpret that.) 
       It could be possible that Splunk mixed up the source and destination for an event. That's what I'm looking to determine. Or if there's compromise in some way where the server calls out...but with an attack signature? Looked strange so came to get feedback. 

[MarkCMc · Accepted solution]

I suppose it could be either. Network IPS however is a totally different product than Host IPS and questions should be posted here: https://community.mcafee.com/t5/Network-Security-Platform-NSP/bd-p/network-security-platform

Sorry I don't support NSP products or I would give a better answer than just a post redirection.  🙂

[Aoc]

My mistake. Moved: https://community.mcafee.com/t5/Network-Security-Platform-NSP/The-Targeted-Server-Becomes-A-Source-I...