That information is NOT on the wire. So it is not a task for Wireshark to sink it’s teeth into.
You are looking for tools that should run on the host in question.
As simple `netstat –nab` run as administrator might be usefull when the connection is there.
All you can gather form the wire is the exact connection details.
You try to hit a nail with a toothbrush at the moment. That is not a very effective tool for the job of hitting nails. You need a hammer.
Met vriendelijke groet / With kind regards,
Hugo van der Kooij
From: Turritopsis Dohrnii Teo En Ming
Sent: Monday, October 22, 2018 11:02 PM
To: wireshark-users@xxxxxxxxxxxxx
Cc: Turritopsis Dohrnii Teo En Ming
Subject: How do I use wireshark to investigate Snort IDS alert "A Network Trojan was Detected"?
Good evening from Singapore,
I have the following alert "A Network Trojan was Detected" in my Snort Intrusion Detection System (IDS) which is in my pfSense Network Security Appliance.
Thread: [Snort-users] Snort IDS in pfSense Network Security Appliance: "A Network Trojan was Detected"
URL:
https://lists.snort.org/pipermail/snort-users/2018-October/071833.html
Is there any way I can use wireshark to pin-point the operating system process in memory or filesystem object which is triggering the above-mentioned Snort IDS/IPS alert? I am hoping to know which executable file is triggering this IDS/IPS alert.
Please advise.
Thank you very much.
===BEGIN SIGNATURE===
Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017
[1]
https://tdtemcerts.wordpress.com/
|
Historical Records, Office of the Grand Historian
|
[2]
http://tdtemcerts.blogspot.sg/
|
Historical Records, Office of the Grand Historian
|
[3]
https://www.scribd.com/user/270125049/Teo-En-Ming
===END SIGNATURE===