The new modules are being dubbed vSploit because they are "virtualizing exploitation attributes." What does that mean? In Marcus' blog discussing vSploit, he states the "vSploit modules imitate compromised or vulnerable hosts on networks."
The idea is simple: Using these modules, a security pro can test whether his intrusion detection/prevention system (IDS/IPS), data leakage protection (DLP), and security information and event management (SIEM) solutions are working without endangering his production network.
Sure, you might say that you could test the same systems by actively exploiting vulnerabilities or by infecting a virtual machine with malware, but what if something were to go wrong? Suppose you put in the wrong IP address and crashed a critical server. Or maybe your infected virtual machine began attacking and infecting other systems on your network. While you might have tested your systems this way for years (I'm guilty of it in a past life), there are a whole slew of things that could go wrong. And, believe me, an accidental malware spread or crashed server is not the type of problem you want or have time to mop up when you're already overworked.
Marcus has two vSploit modules that he has demonstrated in videos posted at the Rapid7 blog. The first is a module designed to test solutions that monitor for personally identifiable information (PII). When run, the module creates a Web service that serves up randomly generated names, Social Security numbers, credit card numbers, passwords, and more. When a Web browser connects to the Web service, the fake PII is transferred and should cause alarms in any monitoring systems set to flag that type of data when seen on the network. Similarly, it can be used to test Web scanners that can detect PII hosted on websites.
The Web_PII module also has a feature that enables SSL, so the data transfer is encrypted and easily demonstrates how many network-based monitoring solutions can be evaded due to their inability to analyze encrypted Web traffic.
The second vSploit module simulates a compromised system requesting known malicious domains. In one example, Marcus demonstrates how the dns_beacon module can emulate a Windows system compromised by the ZeuS botnet. A network device monitoring for known malicious domains in DNS requests or a SIEM monitoring DNS logs for suspicious queries should immediately flag this traffic.
There is more in the works from Marcus, and the results should help enable everyone from the single-person security team on up to the security team of a Fortune 100 to perform easier testing and validation without live exploits and malware. I've provided a few updates to the Web_PII module that fit some testing scenarios that I've encountered, and I'm hoping to contribute more as the project matures. Look for more details as Defcon approaches in August.
John Sawyer is a Senior Security Analyst with InGuardians. The views and opinions expressed in this blog are his own and do not represent the views and opinions of his employer. He can be reached at [email protected]