VM Setup Guide - Revision history

Isiadmin: /* Accessing the Attack System */

2019-04-25T13:16:07Z

Accessing the Attack System

← Older revision		Revision as of 13:16, 25 April 2019
Line 37:		Line 37:

	=== Accessing the Attack System ===		=== Accessing the Attack System ===
	Each team will be assigned an attack system that is available on any JHU network. The hostnames, usernames, and passwords will be given to you before the competition to allow you a little bit of time to set it up. By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] ~~yourself~~ to gain access to a complete desktop environment.		Each team will be assigned an attack system that is available on any JHU network. The hostnames, usernames, and passwords will be given to you before the competition to allow you a little bit of time to set it up. By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] to gain access to a complete desktop environment.

	=== Changing the IP Address of the Target Interface ===		=== Changing the IP Address of the Target Interface ===

Isiadmin: /* Accessing the Attack System */

2019-04-25T13:15:25Z

Accessing the Attack System

← Older revision		Revision as of 13:15, 25 April 2019
Line 37:		Line 37:

	=== Accessing the Attack System ===		=== Accessing the Attack System ===
	By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] yourself to gain access to a complete desktop environment.		Each team will be assigned an attack system that is available on any JHU network. The hostnames, usernames, and passwords will be given to you before the competition to allow you a little bit of time to set it up. By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] yourself to gain access to a complete desktop environment.
	Each team will be assigned an attack system that is available on any JHU network. The hostnames, usernames, and passwords will be given to you before the competition to allow you a little bit of time to set it up.

	=== Changing the IP Address of the Target Interface ===		=== Changing the IP Address of the Target Interface ===

Isiadmin: /* Accessing the Attack System */

2019-04-25T13:14:46Z

Accessing the Attack System

← Older revision		Revision as of 13:14, 25 April 2019
Line 38:		Line 38:
	=== Accessing the Attack System ===		=== Accessing the Attack System ===
	By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] yourself to gain access to a complete desktop environment.		By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding\|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] yourself to gain access to a complete desktop environment.
			Each team will be assigned an attack system that is available on any JHU network. The hostnames, usernames, and passwords will be given to you before the competition to allow you a little bit of time to set it up.

	=== Changing the IP Address of the Target Interface ===		=== Changing the IP Address of the Target Interface ===

Isiadmin: /* Pivoting */

2019-04-25T13:11:53Z

Pivoting

← Older revision		Revision as of 13:11, 25 April 2019
Line 69:		Line 69:

	=== Pivoting ===		=== Pivoting ===
	It is recommended that you become familiar with [[SSH#Port_Forwarding\|SSH]] and [https://www.offensive-security.com/metasploit-unleashed/pivoting/ Metasploit] ~~pivoting~~ techniques, as this will make traversal of these VM networks far easier.		It is recommended that you become familiar with [[SSH#Port_Forwarding\|SSH Port Forwarding]] and [https://www.offensive-security.com/metasploit-unleashed/pivoting/ Metasploit pivoting] techniques, as this will make traversal of these VM networks far easier.

	== VM Access ==		== VM Access ==

Isiadmin: /* Config via GUI */

2019-04-25T13:10:15Z

Config via GUI

← Older revision		Revision as of 13:10, 25 April 2019
Line 44:		Line 44:
	==== Config via GUI ====		==== Config via GUI ====
	When you connect via SSH, ensure you've enabled [[SSH#Using_X11_Forwarding\|X Forwarding]]. Run the following command:		When you connect via SSH, ensure you've enabled [[SSH#Using_X11_Forwarding\|X Forwarding]]. Run the following command:
	nm-connection-editor		student@TEAMX-ATTACK:~$ '''nm-connection-editor'''
	This should allow you to easily modify the Target network.		This should allow you to easily modify the Target network.

Isiadmin: /* The Attack System */

2019-04-25T13:09:20Z

The Attack System

@@ Line 32: / Line 32: @@
 == The Attack System ==
-When the challenge begins, your team will be granted [[SSH]] access to a fully updated [https://www.kali.org/ Kali Linux] system with two virtual network interfaces: One on the ISI DMZ and the other on the virtual network of the system (or systems) you will be attacking. You will have root on this system, so you are free to configure it however you choose.
+When the challenge begins, your team will be granted [[SSH]] access to a fully updated [https://www.kali.org/ Kali Linux] system with two virtual network interfaces: One (eth0) on the ISI DMZ and the other (eth1) on the virtual network of the system (or systems) you will be attacking. You will have root on this system, so you are free to configure it however you choose.
 '''Once you gain access to the attack system, change the password immediately.''' You do not want other teams gaining access to your system as this may grant them an unfair advantage while solving challenges.
@@ Line 38: / Line 38: @@
 === Accessing the Attack System ===
 By default, the only way to access Kali is via SSH. If you need to use GUI applications on this system, you can use [[SSH#Using_X11_Forwarding|X11 Forwarding]]. If this is still not adequate for your needs, you are welcome to install and configure something like [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04 VNC] yourself to gain access to a complete desktop environment.
 === Pivoting ===
 It is recommended that you become familiar with [[SSH#Port_Forwarding|SSH]] and [https://www.offensive-security.com/metasploit-unleashed/pivoting/ Metasploit] pivoting techniques, as this will make traversal of these VM networks far easier.
 == VM Access ==

Isiadmin: /* Official Rules */

2019-03-28T13:50:16Z

Official Rules

← Older revision		Revision as of 13:50, 28 March 2019
Line 20:		Line 20:
	* Reverse engineering		* Reverse engineering
	* Cryptology		* Cryptology
	* Wireless networking
	* At least 10 flags		* At least 10 flags
	* Unique identifiers for flags		* Unique identifiers for flags

Isiadmin: /* Windows */

2019-03-28T12:44:25Z

Windows

← Older revision		Revision as of 12:44, 28 March 2019
Line 123:		Line 123:
	The most recent version of Microsoft's Windows operating system is Windows 10 , but did you know that there are [https://en.wikipedia.org/wiki/Windows_10_editions 12 different editions], all with their own unique feature sets?		The most recent version of Microsoft's Windows operating system is Windows 10 , but did you know that there are [https://en.wikipedia.org/wiki/Windows_10_editions 12 different editions], all with their own unique feature sets?

	When choosing ~~to use~~ a Windows operating system for one of your VMs, make sure you're aware of what specific versions and editions are capable of demonstrating the attack you plan on having your challengers implement. A vulnerability in Windows Vista may not affect a Windows 7 machine or a service in Windows 10 Enterprise might not be available in Windows 10 Home.		When choosing a Windows operating system for one of your VMs, make sure you're aware of what specific versions and editions are capable of demonstrating the attack you plan on having your challengers implement. A vulnerability in Windows Vista may not affect a Windows 7 machine or a service in Windows 10 Enterprise might not be available in Windows 10 Home.

	We can acquire any version and/or edition of Windows you need, so if a license or ISO download for the version you wish to use is not already available to you on the [[Shared Drive#ISOs\|Shared Drive]], please contact [mailto:support@isi.jhu.edu support] Make sure you do your research ''before'' starting the build process, since acquiring licensing for some versions of Windows may take more time than others and you don't want to waste that time with an operating system you can't use.		We can acquire any version and/or edition of Windows you need, so if a license or ISO download for the version you wish to use is not already available to you on the [[Shared Drive#ISOs\|Shared Drive]], please contact [mailto:support@isi.jhu.edu support] Make sure you do your research ''before'' starting the build process, since acquiring licensing for some versions of Windows may take more time than others and you don't want to waste that time with an operating system you can't use.

Isiadmin: /* Virtual Machine Setup Recommendations */

2019-03-28T12:43:34Z

Virtual Machine Setup Recommendations

← Older revision		Revision as of 12:43, 28 March 2019
Line 113:		Line 113:

	= Virtual Machine Setup Recommendations =		= Virtual Machine Setup Recommendations =
	While every VM created for this project will be different, there are a few general considerations that should be minded to ensure your VMs are as efficient as possible~~, even~~ within the ~~time~~ constraints of the project. While these recommendations are not required, they will help you better manage your VMs to prepare them for distribution.		While every VM created for this project will be different, there are a few general considerations that should be minded to ensure your VMs are as efficient as possible within the constraints of the project. While these recommendations are not required, they will help you better manage your VMs to prepare them for distribution.

	== Choosing an Operating System ==		== Choosing an Operating System ==

Isiadmin: /* Example Network Configuration */

2019-03-28T12:40:44Z

Example Network Configuration

← Older revision		Revision as of 12:40, 28 March 2019
Line 92:		Line 92:
	\| Student Laptop \|\| WiFi \|\| JHU \|\| DHCP \|\| Assigned via DHCP \|\| Assigned via DHCP		\| Student Laptop \|\| WiFi \|\| JHU \|\| DHCP \|\| Assigned via DHCP \|\| Assigned via DHCP
	\|-		\|-
	\| Attack System \|\| eth0 \|\| JHU \|\| DHCP \|\| Assigned via DHCP \|\| Assigned via DHCP		\| rowspan="2" \| Attack System \|\| eth0 \|\| JHU \|\| DHCP \|\| Assigned via DHCP \|\| Assigned via DHCP
	\|-		\|-
	~~\| Attack System \|~~\| eth1 \|\| VM Network 1 \|\| Static \|\| 192.168.1.100 \|\| 255.255.255.0		\| eth1 \|\| VM Network 1 \|\| Static \|\| 192.168.1.100 \|\| 255.255.255.0
	\|-		\|-
	\| Web Server \|\| eth0 \|\| VM Network 1 \|\| Static \|\| 192.168.1.10 \|\| 255.255.255.0		\| rowspan="2" \| Web Server \|\| eth0 \|\| VM Network 1 \|\| Static \|\| 192.168.1.10 \|\| 255.255.255.0
	\|-		\|-
	~~\| Web Server \|~~\| eth1 \|\| VM Network 2 \|\| Static \|\| 10.1.1.10 \|\| 255.255.255.0		\| eth1 \|\| VM Network 2 \|\| Static \|\| 10.1.1.10 \|\| 255.255.255.0
	\|-		\|-
	\| Database Server \|\| eth0 \|\| VM Network 1 \|\| Static \|\| 192.168.1.20 \|\| 255.255.255.0		\| Database Server \|\| eth0 \|\| VM Network 1 \|\| Static \|\| 192.168.1.20 \|\| 255.255.255.0