Intrustion detection and malware analysis

Want to make an environment where I can test intrusion detection and to a small extent malware analysis. Does anyone have suggestion for software? Specifically I need to know how to detect when a piece of software is doing something malicious, also, if possible, I need some tutorials that can get me started in this area, it seems like you have to have some knowledge of what executables are supposed to be doing, i.e what registry changes are normal, and what is abnormal.
FYI, I am aware of tripwire, can someone tell me is it free? Is there a free windows version? I feel I will be doing mostly windows analysis as my environment is windows based at work, i'd like to spend my time focusing on that.
FYI, I am aware of tripwire, can someone tell me is it free? Is there a free windows version? I feel I will be doing mostly windows analysis as my environment is windows based at work, i'd like to spend my time focusing on that.
Comments
https://www.youtube.com/watch?v=zXh-1mK5FyU
The Volatility Framework in SecurityThroughObscurity's YouTube video link is probably worth checking out. I'm not a malware-analysis guy so understanding memory structure, debugging code, etc. is beyond me. Hopefully SANS FOR508 will eventually get me introduced to this area a bit more.
Detecting good vs bad "stuff"- You'll need a baseline understanding of how malware analysis tools work; volatility and redline are a good place to start. You can look into some online scanners too, like cuckoo sandbox (Malwr) and Anubis.
Regarding an IDS - Try running Security Onion with Snort for a NIDS.
IMO, anything involving true malware analysis and reversing is highly specialized. I dabbled with it on/off for a few weeks and I found that the learning curve is rather steep.
Harlan Carvey has some great books on forensics and investigations which can be helpful too. http://www.amazon.com/Harlan-A.-Carvey/e/B001JPCIY6
My recommendation for right now is to start a honeypot OS, compromise it, and watch what happens - Ultimately any major changes and/or network connections to unknown hosts at that point should be considered malicious until analysis proves otherwise. From there, you can begin to understand some of the basic things common malware families utilize to call home, hide their presence, evade detection, etc. Long term, you're going to want to learn the Windows operating system in-depth. It's one of the reasons I want to take SANS SEC408 so badly. FYI: if you want, I can provide you with a couple compromised domains which are serving malware - I find getting the environment owned naturally in the wild is a much better representation than downloading samples from malware libraries. It provides more context in my opinion.
I feel like to use Tripwire properly, you'd need to know what you don't know, which is how/where to monitor. I don't think using it indiscriminently would be beneficial for you right now.
Some suggestions on tools:
-Microsoft Sysinternals Suite: An excellent suite of tools to see under the hood of the OS. Specifically 'Process Monitor', which does a good job of showing you what Task Manager will not.
-RegShot: Compare the registry before and after infection
-Volatility: - Memory forensics
-Fiddler HTTP Proxy: - I use this when I compromise my VM via drive-by download, so I can see the interaction with the browser and grab copies of the malicious scripts
-Wireshark: Watch the wire. Because of the natural shiftiness of malware, I prefer to monitor network traffic outside of the compromised host. Right now I have a Raspberry Pi attached to a SPAN port on my switch, listening with TCPdump and collecting full pcap. But generally speaking Wireshark will give you what you want as well.
After that I would start suggesting code analysis tools, but I'm not at a level where I can confidently speak about that. And it sounds like you're more interested in the OS/Network level in terms of detection right now anyway, not the code of the malware itself.
I'm unsure of the exact setup of what will be running and when. Right now i'm thinking I will have SO, KL and Windows 7 in separate VM's on one box.
Would I be putting wireshark and the PSTools on the W7 host I intend to have compromised? Or should I just insure it oon the same network segment (virtual) with the SO box running in IDS mode?
That being said I have come across Fake A/V variants that would prevent me from starting non-essential applications - To work around this I renamed any app I wanted to open 'svchost.exe'. You likely won't run into this situation, it's just an FYI.
Right now i've got Autoruns, fiddle, ossec client, Process Explorer/Monitor, Regshot, tcpview, and wireshark. I think that's a decent start. I'll get them all installed.
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray
Something I'd like to add to NovaHax point about not running it in prod; additionally I would refrain from running Cryptolocker anywhere you have removable media or network shares of any kind within reach as it is capable of scanning and encrypting those as well.
I personally didn't test it against any AV products. Just basing my claims off of virus total. Cryptolocker has had several new versions/signatures since it was originally detected in the wild. The latest version available from GRC is currently being detected by 35 out of 51 on virus total. When ran less than a month ago (Jan 22), only was detected by only 6 out of 51.
IMO that is simply the cat-and-mouse nature of malware authors employing packing / obfuscation techniques, and doesn't have much to do with Cryptolocker being new. Had the binary you're referring to been run on a system, it's highly likely more of those vendors would have picked it up on heuristics alone. That being said I'm certainly not suggesting A/V products will find everything or even most things. I'm just offering my perspective
Along the same lines I have seen ZeroAccess infections go undetected by McAfee enterprise even two years after its release - not because McAfee didn't know what ZA looked like, but because malware authors make a living off of employing clever changes to their software.
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray
Care to share the specific tools, if you don't mind?
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray