Onward with the Attacker VM. In order to make the attack sequence easier during a presentation, everything will be scripted. The best tool for that in Kali Linux is Metasploit. Each phase of the Cyber Kill Chain introduced at the beginning of the series will have it’s own Metasploit script and will use it’s own set of ports so we can clearly separate each phase for our audience. Things will be much clearer in the final post wrapping up this series, but for now, onto the fun.
We are on to building the Victim VM. This VM will be built with Window 7 SP1 32-bit. Be aware that when SP1 was released, these vulnerabilities were either not known or were later zero day discoveries. More on the vulnerabilities in SP1 later during the post on the attacker VM.
The center piece of this demonstration is the Splunk Dashboard. The idea is to provide clear indicators when things are good (green) or bad (red) during the demo. In Part 1 we discussed the Cyber Kill Chain in 4 phases, so we will build a Splunk Dashboard that shows those 4 phases clearly.
Continuing the series on Selling Your Information Security Team, it’s now time to start building the Utility Virtual Machine that will host all the support programs and applications used in the demonstration. This post will cover building that very importation Swiss Army Knife of the demonstration … the Utility Virtual Machine. In Part 2 of this series, we built the host environment and defined the two networks joined by the firewall. Then in Part 3 we build the firewall to join the previously defined networks together.
As I continue this series on Selling Your Information Security Team, it’s now time to start building the Virtual Machines that will be used in the demonstration. This post will cover building the keystone of the demonstration … the Firewall Virtual Machine. In Part 2 of this series, we built the host environment and defined the two networks joined by the firewall.
While this walk-through looks fairly strait forward it was not in reality. There were a lot of dead-ends and attempts that didn’t work, or didn’t give me the results I wanted. Once I found the correct path though, it took only a few minutes to walk through it again and document it with screen shots.
If you have not had a chance to complete the PwnLab:Init challenge on VulnHub STOP READING NOW. This is a fun challenge and I recommend you try it.
In the previous installment of this series, we discussed how Information Security can be similar to insurance … it’s only discussed when bad things happen, and it’s rarely a revenue generating center. We also talked about how one might show return on investment in the Information Security Team. Finally we walked through a four phase Cyber Kill Chain that could be used to simplify a complex demonstration of Information Security that could be presented to non-InfoSec managers and Board of Directors. In this part of the series we will install Virtualization Software for the Virtual Penetration Lab that will be the foundation of our demonstration to the Board of Directors.
Information Security can be similar to insurance … it’s only discussed when bad things happen and it’s rarely a revenue generating center. So how does one show return on investment? I was recently asked to do just that by participating in a presentation to our Board of Directors. Senior management wanted to show off the new security operation center and the SOC team to the board. My first thought was: <sarcasm>That is a great idea … they can walk through a SOC and see all the “Security Bling” screens on the wall.</sarcasm> But after brain storming with the team, we actually came up with a great idea that I will be writing about over the next several weeks.