GreatCoder
MODULE 00 / 40 • LAB FOUNDATION & WORKSTATION COCKPIT
← HOME / CURRICULUM MODULE 01: ONBOARDING →
GREATCODER · ZERO-TRUST LAB FOUNDATION · MODULE 00

GreatCoder Lab Foundation:
Workstation Setup Cockpit

You are building the machine on which the entire GreatCoder Cyber Security journey will run. Interact with the live workstation cockpit below to assemble host memory, test CPU hardware acceleration, simulate isolated virtual network routing, and inspect protocol frames.

MODULE 00 / 40 UNIFIED LAB ENGINE LIVE COCKPIT LAB READY
GREATCODER CYBER SECURITY WORKSTATION READINESS COCKPIT
All modules below read and write to this unified workstation state model
82% LAB READY
CPU ALLOCATION 8 CORES ✓
RAM SIZING 16 GB ✓
VIRTUALIZATION VT-x ON ✓
NVMe STORAGE 180 GB FREE ✓
HYPERVISOR VIRTUALBOX 7.X ✓
PACKET TRACER INSTALLED ✓
KALI OPERATOR VM IMPORTED ✓
NET ISOLATION NAT NETWORK ✓
02 · UNIFIED HARDWARE & PARALLEL VM MATRIX

Hardware Resource Sizing & Parallel VM Execution Calculator

Compare host CPU cores, RAM, and Disk storage. Calculate exactly how many virtual machines your rig can run concurrently for GreatCoder Cyber Security labs without tab switching or memory paging.

01 · HOST PHYSICAL MEMORY SIZING
02 · HOST PHYSICAL CPU CORES
03 · HOST STORAGE DRIVE TYPE & CAPACITY
VISUAL MEMORY ALLOCATION SLICE 16 GB Total (8 GB Host / 4 GB Kali / 4 GB Target)
■ Host OS: 8 GB ■ Kali Operator: 4 GB ■ Target Lab VMs: 4 GB ■ Free Headroom: 0 GB
VM CAPACITY & CONCURRENCY 2-3 VMs PARALLEL
2–3 Concurrent Virtual Machines (Standard)

16 GB RAM with 8 CPU cores provides the optimal baseline: 4 GB Kali Linux + 4 GB Target Server + 8 GB Host OS with zero memory contention.

RESOURCE PRESSURE: OPTIMAL (No Swapping)
SWAP PAGING RISK: 0% (Clean Memory Headroom)
vCPU OVERSUBSCRIPTION: 1:1 Safe Ratio
DISK I/O BOTTLENECK: NVMe 3500 MB/s (Instant Boot)
■ CYBER SECURITY LAB APPLIANCES & HARDWARE REQUIREMENTS BREAKDOWN
Lab Machine Appliance Role in Cyber Security Minimum vRAM Recommended vRAM vCPUs VDI Storage Parallel Run Capability
Kali Linux 2024.x Attacker / Security Operator (Nmap, Burp, Metasploit, Wireshark) 2048 MB (2 GB) 4096 MB (4 GB) 2 Cores 20–40 GB VDI Always Active (Base)
Ubuntu Server 22.04 / Debian Defensive Target / Web App / Docker Containers / LAMP Stack 1024 MB (1 GB) 2048 MB (2 GB) 1–2 Cores 15–25 GB VDI ✓ Parallel with Kali (16GB+)
Metasploitable 2 / 3 Vulnerable Exploitation & Vulnerability Assessment Target 512 MB (0.5 GB) 1024 MB (1 GB) 1 Core 8–15 GB VDI ✓ Parallel with Kali (8GB+)
Windows 10 / 11 Enterprise Endpoint Hardening / Malware Triage / AD Domain Member 4096 MB (4 GB) 8192 MB (8 GB) 2–4 Cores 50–80 GB VDI ⚠ Requires 24GB+ for Parallel
Windows Server 2022 (AD DC) Active Directory Domain Controller / Kerberos / Group Policy 2048 MB (2 GB) 4096 MB (4 GB) 2 Cores 40–60 GB VDI ⚠ Requires 24GB–32GB RAM
Splunk / Security Onion (SIEM) SOC Log Ingestion, Alerting & Incident Triage Engine 4096 MB (4 GB) 8192 MB (8 GB) 4 Cores 40–100 GB VDI ⚠ Requires 32GB+ RAM
03 · HARDWARE VIRTUALIZATION ENGINE

CPU Virtualization Pipeline (VT-x & AMD-V)

Toggle hardware virtualization below. Observe how breaking the CPU virtualization path disables 64-bit hypervisor execution.

CPU HARDWARE VIRTUALIZATION SWITCH
Simulate toggling Intel VT-x / AMD SVM Mode in BIOS
01 · PHYSICAL CPUIntel / AMD Silicon
02 · VT-x / AMD-VHardware Ring -1
03 · HYPERVISORVirtualBox Engine
04 · VIRTUAL CPUvCPU Slicing
05 · GUEST OSVM READY ✓
WITH VT-x / AMD-V ENABLED: VirtualBox directly passes guest Ring 0 instructions to the physical CPU via hardware virtualization extensions (VMX Root/Non-Root operation). 64-bit Kali Linux boots at native hardware speeds.
ManufacturerKeyBIOS Section
DellF2 / F12Advanced → Virtualization Support → Enable Intel Virtualization Technology
HPF10 / EscAdvanced → System Options → Virtualization Technology (VTx/VTd)
LenovoF1 / F2Security → Virtualization → Intel Virtualization Technology
ASUS / MSIDel / F2Advanced Mode → CPU Configuration → SVM Mode / Intel Virtualization
04 · INTERACTIVE BROWSER SIMULATION

Virtual Machine Builder & Power Engine

Assemble your virtual machine components below, configure hardware resources, and trigger the simulated boot sequence.

ORACLE VM VIRTUALBOX · APPLIANCE POWER OFF
NAME: Kali-Linux-2024.x-vbox-amd64
PROCESSORS: 2 vCPUs
MEMORY: 4096 MB RAM
STORAGE: 40 GB Dynamic VDI
NETWORK: Adapter 1: NAT Network
[SYSTEM READY] Click "POWER ON VM" to start virtual machine execution.
05 · PRIMARY NETWORK TOPOLOGY SIMULATOR

VirtualBox Network Mode Interactive Workspace

Select any mode below. Watch the actual connection paths, packet routes, and isolation boundaries change dynamically.

INTERNET ACCESS
✓ CONNECTED (NAT Outbound)
HOST OS ISOLATION
✓ ISOLATED (Safe)
VM ↔ VM COMMUNICATION
✓ CONNECTED (Shared Subnet)
PHYSICAL HOME LAN
✓ 0% EXPOSURE (Hidden)
06 · SIMULATED PACKET ENGINE

Cisco Packet Tracer Educational Simulation

Click "SEND ICMP PING". Watch the packet traverse each device, inspect headers, and observe protocol translation.

SIMULATED NETWORK CANVAS: 2-HOP ROUTING
Source: Student PC (192.168.1.10) ➔ Destination: NetAcad Lab Server (10.10.14.1)
PC-01
Student PC
192.168.1.10
SWITCH-2960
Access Switch
VLAN 1 Default
ROUTER-2911
Lab Gateway
NAT & Routing
SERVER-01
Lab Target
10.10.14.1
SIMULATION STATE: IDLE. Click "SEND ICMP PING" to trigger packet transmission.
07 · PACKET CAPTURE & INSPECTION

Wireshark Protocol Dissector Simulator

Click any packet in the captured trace below to dissect its Layer 2 (Ethernet), Layer 3 (IP), and Layer 4 (TCP/UDP/ICMP) headers.

No.TimeSourceDestinationProtocolLengthInfo
10.000000192.168.1.10192.168.1.1ARP42Who has 192.168.1.1? Tell 192.168.1.10
20.001420192.168.1.1192.168.1.10ARP42192.168.1.1 is at 08:00:27:5a:32:bc
30.002810192.168.1.1010.10.14.1ICMP74Echo (ping) request id=0x0001, seq=1/256, ttl=64
40.02419010.10.14.1192.168.1.10ICMP74Echo (ping) reply id=0x0001, seq=1/256, ttl=63
50.035120192.168.1.1010.10.14.1TCP6649152 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460
Frame 1: 42 bytes on wire (336 bits), 42 bytes captured
Ethernet II: Src: 08:00:27:11:22:33, Dst: ff:ff:ff:ff:ff:ff (Broadcast)
Address Resolution Protocol (request): Who has 192.168.1.1? Tell 192.168.1.10
08 · RECOVERY & LAB HYGIENE

VM Snapshot State Machine

Interact with the snapshot engine below. Simulate breaking the VM during an exploit lab, then restore to the clean baseline snapshot.

01 · CLEAN STATE
Fresh Kali Import
Base OS + Default tools
02 · SNAPSHOT SAVED
00-Clean-Base-State
Read-only reference delta
03 · EXPERIMENT
Custom Tools Run
State modified during labs
04 · ROLLBACK STATE
Restore Snapshot
100% Clean in 2 seconds
09 · UNIFIED DEPENDENCY GRAPH

Workstation Dependency & Propagation Model

GreatCoder Cyber Security enforces strict prerequisites. If an upstream foundation fails (e.g. CPU virtualization), downstream virtual appliances automatically block.

PROPAGATION PIPELINE STATE
STEP 01
Host Hardware
16 GB RAM ✓
STEP 02
Virtualization
VT-x Active ✓
STEP 03
VirtualBox 7.x
Ext Pack OK ✓
STEP 04
Module 01 Gate
UNLOCKED ✓
10 · CONNECTED HOST TOOLCHAIN

Integrated Software Toolchain

Click any tool in the pipeline to see where it fits into your workflow and why GreatCoder Cyber Security utilizes it.

VIRTUALIZATION

Oracle VirtualBox 7.x

Cross-platform Type-2 hypervisor for guest OS isolation.

NETWORK SIMULATION

Cisco Packet Tracer

Layer 2-4 enterprise topology simulation and protocol analysis.

OPERATOR WORKSTATION

Kali Linux 2024.x

Pre-packaged security appliance with hundreds of testing utilities.

PACKET TELEMETRY

Wireshark

Deep packet inspection and pcap capture analysis.

CODE & CONFIG

VS Code

Configuration editor for Python scripts, Bash, and JSON telemetry.

ARCHIVE UTILITY

7-Zip 64-bit

Multi-part OVA and 7z appliance decompression engine.

Oracle VirtualBox 7.x: The core foundation of your local testing lab. Runs isolated Kali Linux and Target virtual machines without modifying host system files or registry.
11 · PREREQUISITE ASSESSMENTS

Knowledge Checkpoints: Prerequisite Validation

Confirm your understanding of the lab architecture before advancing.

CHECKPOINT 01 · VIRTUALIZATION
When attempting to start a 64-bit Kali VM in VirtualBox, you receive an error: "VT-x/AMD-V hardware acceleration is not available". What is the required resolution?
Explanation: 64-bit guest operating systems require CPU hardware virtualization extensions (VT-x/AMD-V) to be toggled to Enabled in the motherboard BIOS/UEFI.
CHECKPOINT 02 · NETWORK ISOLATION
Which VirtualBox network mode creates an isolated virtual subnet where guest VMs can communicate with each other AND reach the Internet, without exposing ports to your physical home WiFi network?
Explanation: NAT Network provides an isolated virtual router that lets VMs talk to each other on a private subnet while sharing outbound NAT internet access without exposing VMs to the physical LAN.
12 · VERIFIED OFFICIAL RESOURCES

Official Download Links & Documentation Directory

Always verify download URLs to prevent downloading trojanized hypervisors or malicious ISO images from third-party sites.

Resource Publisher Official Verified Link License
Cisco Networking Academy Cisco Systems netacad.com ↗ Free Educational Account
Cisco Packet Tracer 8.2+ Cisco Systems netacad.com/.../packet-tracer ↗ Free Student License
Oracle VM VirtualBox 7.x Oracle Corporation virtualbox.org/wiki/Downloads ↗ GPLv2 / Free PUEL
Kali Linux (VirtualBox Image) OffSec (Offensive Security) kali.org/get-kali ↗ Open Source (GPL)
Visual Studio Code Microsoft code.visualstudio.com ↗ MIT License
Wireshark Network Analyzer Wireshark Foundation wireshark.org ↗ GPLv2
7-Zip 64-bit Igor Pavlov 7-zip.org ↗ GNU LGPL
13 · ONBOARDING COMPLETION

Module 00 Readiness Gate

Complete the prerequisite readiness check to verify your workstation is primed for Module 01.

Workstation Readiness Verification

Hardware & System Validation

  • CPU Virtualization (VT-x / AMD-V) enabled in BIOS
  • At least 16 GB RAM & 100 GB+ SSD free space verified
  • 7-Zip & VS Code installed on Host OS

Academy & Hypervisor Validation

  • Cisco NetAcad profile created & active
  • Cisco Packet Tracer installed and logged in
  • Oracle VirtualBox 7.x & Extension Pack installed
  • Kali Linux VM imported with clean snapshot taken