BGP Security & Route Hijacking Defense
Intermediate90 min5 objectives

BGP Security & Route Hijacking Defense

Practice BGP Security & Route Hijacking Defense by producing and reviewing portable evidence without requiring unavailable host, cloud, hardware, or multi-node access.

Briefing

### Scenario You are a bgp practitioner handling a realistic client engagement. For BGP Security & Route Hijacking Defense, the client has provided a staging environment that mirrors production but is isolated to this lab. Your task is to demonstrate the core technique on the local target without touching external systems. The scenario is intentionally scoped to what you can verify inside the container. ### Environment and scope Use the Ubuntu 22.04 practice container. Working directory is `/home/student/lab-work` (create it with `mkdir -p`). Target is `127.0.0.1` and `127.0.0.1:8080` where a `python3 -m http.server` or service-specific daemon runs. Install only needed tools via `sudo apt-get update && sudo apt-get install -y bird, birdc, iproute2` then verify with `bird --version 2>&1 | head`. Credentials: `student:lab123` with `sudo` (created via `useradd` + `chpasswd` + `sudoers.d` as in `labs.service.ts:554`). Do not scan or query outside 127.0.0.0/8 or lab-work. Scope is strictly container-only; no external cloud, hardware, or nested container engines. ### Mission objective For BGP Security & Route Hijacking Defense: install and verify tooling, prepare the local target (`bird config in /etc/bird/bird.conf with local ASN`), execute the technique step-by-step, and collect evidence. Each walkthrough step produces a verifiable artifact (file, command output, or service state) that you will cite in your submission. ### Success criteria You have completed the lab when: - Tooling verification passes (`bird --version 2>&1 | head` returns expected version without error) - Local target is running and responds (`curl -s http://127.0.0.1:8080/` or `dig @127.0.0.1` or `tshark -r` shows expected output) - `solution.md` in `lab-work` documents each step's exact command, raw output excerpt, and your interpretation (what the output proves) - All flag answers are direct values from your local output (e.g., version string, status code, IP, header name) and no external hosts were targeted (`history | grep -E "nmap|dig|tshark|openssl|nikto|curl"` shows only 127.0.0.1) Runtime mode: portable artifact validation

Objectives

  • 1Prepare workspace and verify tooling
  • 2Prepare local target for BGP Security & Route Hijacking Defense
  • 3Execute BGP Security & Route Hijacking Defense technique
  • 4Capture evidence
  • 5Complete BGP Peering
  • 6Complete RPKI Deployer
  • 7Tune and interpret
  • 8Compile and verify submission

Flags

BGP Peering+200 pts

Submit the verifiable output value for BGP Peering as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

RPKI Deployer+200 pts

Submit the verifiable output value for RPKI Deployer as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

ROA Creator+200 pts

Submit the synthesized artifact value for ROA Creator (e.g., IP 127.0.0.2 or zone name) as verified by dig or cat /etc/bind/.

Prefix Announcer+150 pts

Submit the verifiable output value for Prefix Announcer as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

Hijack Simulator+250 pts

Submit the verifiable output value for Hijack Simulator as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

Deploy Lab — 30sCreate Free Account