Nmap/Short Course/Running the Labs - Revision history

Unknown user: /* Core Lab Infrastructure on EC2 */

2025-05-30T14:57:29Z

Core Lab Infrastructure on EC2

@@ Line 15: / Line 15: @@
 The core idea is to use a single, reasonably powerful EC2 instance as the hypervisor and host for your entire virtual network. Inside this EC2 instance, we'll use a combination of Vagrant (with libvirt/KVM) for managing any full virtual machines (like an attacker machine or specific OS targets) and Docker/Docker Compose for deploying a variety of lightweight target services and "machines" (containers). Ansible will be the glue for configuring everything consistently.
-==Core Lab Infrastructure on EC2==
+==Host EC2 "Big Boy" - Core Lab Infra Host==
 EC2 Instance Choice:
@@ Line 52: / Line 52: @@
 (Note: You'll need to log out and log back in for group changes to take effect, or use <code>newgrp libvirt</code> and <code>newgrp docker</code> in your current session.)
 ==Infrastructure as Code (IaC) Setup==

Unknown user: /* Virtual Network Design */

2025-05-30T14:35:38Z

Virtual Network Design

← Older revision		Revision as of 14:35, 30 May 2025
Line 173:		Line 173:
	Primary Lab Network:		Primary Lab Network:
	* Create one or more private virtual networks (e.g., <code>192.168.50.0/24</code>, <code>10.0.10.0/24</code>) that your Vagrant VMs and Docker containers will reside on.		* Create one or more private virtual networks (e.g., <code>192.168.50.0/24</code>, <code>10.0.10.0/24</code>) that your Vagrant VMs and Docker containers will reside on.
	V* ~~agrant~~'s libvirt provider can create these networks.		* Vagrant's libvirt provider can create these networks.
	* Docker Compose can define its own bridge networks. You can configure routing on the EC2 host or within an "attacker" VM to allow communication between these if they are separate. For simplicity, try to have them on the same logical network or ensure the attacker VM/container has routes to all target networks.		* Docker Compose can define its own bridge networks. You can configure routing on the EC2 host or within an "attacker" VM to allow communication between these if they are separate. For simplicity, try to have them on the same logical network or ensure the attacker VM/container has routes to all target networks.

Unknown user: /* Flags */

2025-05-27T00:02:32Z

Flags

@@ Line 265: / Line 265: @@
 This approach provides a powerful and adaptable environment. You can create different branches in your Git repository for different lab modules, each with unique network configurations, target vulnerabilities, and learning objectives.
 =Flags=
 {{NmapShortCourseFlag}}

Unknown user at 23:27, 26 May 2025

2025-05-26T23:27:44Z

← Older revision		Revision as of 23:27, 26 May 2025
Line 1:		Line 1:
			{{Main\|Nmap/Short Course}}

	This page describes how to run the labs for this nmap short course. Notes for myself, but also for anyone who might be interested.		This page describes how to run the labs for this nmap short course. Notes for myself, but also for anyone who might be interested.

Unknown user: /* Example of Defining a Simple Target */

2025-05-26T23:27:17Z

Example of Defining a Simple Target

@@ Line 220: / Line 220: @@
 ===Example of Defining a Simple Target===
 =Flags=
 {{NmapShortCourseFlag}}

Unknown user: /* Lab Customization and Deployment Workflow */

2025-05-26T22:50:34Z

Lab Customization and Deployment Workflow

@@ Line 203: / Line 203: @@
 IaC is Key: Your Vagrantfiles, Docker Compose files, and Ansible playbooks are your lab definition.
 =Flags=
 {{NmapShortCourseFlag}}

Unknown user: /* Student Access to the Cloud Lab */

2025-05-26T22:46:37Z

Student Access to the Cloud Lab

← Older revision		Revision as of 22:46, 26 May 2025
Line 185:		Line 185:
	There are a few options:		There are a few options:

	# SSH to a Dedicated "Attacker" VM/Container (Recommended for Simplicity & Control):		* SSH to a Dedicated "Attacker" VM/Container (Recommended for Simplicity & Control):
	## How it works: You provision an "attacker" VM (using Vagrant) or a Docker container within the lab network. This attacker machine has nmap and other necessary tools pre-installed. Students SSH into this attacker machine from their own computers. From there, they can scan the target VMs and containers on the internal lab network.		** How it works: You provision an "attacker" VM (using Vagrant) or a Docker container within the lab network. This attacker machine has nmap and other necessary tools pre-installed. Students SSH into this attacker machine from their own computers. From there, they can scan the target VMs and containers on the internal lab network.

	<s>		<s>
	# VPN (Virtual Private Network)		* VPN (Virtual Private Network)
	## How it works: Set up a VPN server (e.g., OpenVPN or WireGuard) on the EC2 instance. Students connect to this VPN from their local machines. Once connected, their machine effectively becomes part of the EC2 instance's private network, and they can run nmap directly from their own laptops against the lab targets.		** How it works: Set up a VPN server (e.g., OpenVPN or WireGuard) on the EC2 instance. Students connect to this VPN from their local machines. Once connected, their machine effectively becomes part of the EC2 instance's private network, and they can run nmap directly from their own laptops against the lab targets.
	</s>		</s>

	<s>		<s>
	# Bastion Host (EC2 acts as Bastion):		* Bastion Host (EC2 acts as Bastion):
	## How it works: Students SSH into the EC2 host itself (to a non-privileged user account). From this shell on the EC2 host, they can use nmap (installed on the EC2 host) to scan the IP addresses of the VMs/containers on the internal Docker/libvirt networks.		** How it works: Students SSH into the EC2 host itself (to a non-privileged user account). From this shell on the EC2 host, they can use nmap (installed on the EC2 host) to scan the IP addresses of the VMs/containers on the internal Docker/libvirt networks.
	</s>		</s>

Unknown user: /* Docker Compose (for Containerized Services/Targets) */

2025-05-26T22:45:51Z

Docker Compose (for Containerized Services/Targets)

@@ Line 120: / Line 120: @@
            gateway: 192.168.50.1
 </pre>
 =Flags=
 {{NmapShortCourseFlag}}

Unknown user: /* Infrastructure as Code (IaC) Setup */

2025-05-26T22:38:34Z

Infrastructure as Code (IaC) Setup

@@ Line 52: / Line 52: @@
 ==Infrastructure as Code (IaC) Setup==
 =Flags=
 {{NmapShortCourseFlag}}

Unknown user: /* Core Lab Infrastructure on EC2 */

2025-05-26T22:36:37Z

Core Lab Infrastructure on EC2

@@ Line 28: / Line 28: @@
 * KVM/QEMU & Libvirt: Install these on your EC2 host instance to enable running full virtual machines.
 =Flags=
 {{NmapShortCourseFlag}}