0% Complete
0/0 Steps
  1. About

    About Cyber School
  2. About BDO
  3. The CSRP program Syllabus
  4. Module 1
    The Cyber World and CIA Triad
    6 Topics
  5. The OSI Model and Network Layers
    6 Topics
  6. IP Addressing, Subnetting and Routing
    6 Topics
  7. DNS and DHCP
    6 Topics
  8. Windows Server Administration
    6 Topics
  9. Active Directory and Identity Management
    6 Topics
  10. Linux CLI Fundamentals
    6 Topics
  11. Linux Permissions and Hardening
    6 Topics
  12. Module 2 - Defense Technologies and Cyber Tools
    Firewall Architecture and Rule Design
    5 Topics
  13. NAT and Secure Traffic Mapping
    6 Topics
  14. Enterprise VPN Solutions
    6 Topics
  15. IDS and IPS
    5 Topics
  16. Identity and Access Management
    5 Topics
  17. Multi-Factor Authentication
    6 Topics
  18. Data Loss Prevention
    6 Topics
  19. Endpoint Security and EDR
    6 Topics
  20. Mail Security
    6 Topics
  21. Web Proxy and URL Filtering
    6 Topics
  22. Regulation and Compliance
    6 Topics
  23. Cloud Security
    6 Topics
    |
    1 Quiz
  24. Module 3 - Ai in security
    AI in Security
    5 Topics
  25. ML Anomaly Detection
    5 Topics
  26. AI Threats
    5 Topics
  27. LLM Defense
    6 Topics
  28. Module 4 - Offensive Cyber & Vulnerability Scanning
    Cyber Kill Chain and Attacker Mindset
    6 Topics
  29. OSINT and Public Intelligence Gathering
    6 Topics
  30. Network and Port Scanning with Nmap
    6 Topics
  31. Vulnerability Scanning
    6 Topics
  32. Exploitation Fundamentals
    6 Topics
  33. Web Application Security
    5 Topics
  34. Social Engineering
    5 Topics
  35. Password and Hash Cracking
    5 Topics
  36. Module 5 - SOC and Advance Cyber Analyst
    SOC Structure and Operations
    6 Topics
  37. SIEM Fundamentals with Splunk
    6 Topics
  38. Alerting and Dashboards
    6 Topics
  39. Incident Response
    5 Topics
  40. Basic Digital Forensics
  41. Capstone A - The Attack: Breaching Meridian
  42. Capstone B - The Defense: Defending Meridian
  43. ISC2 CC Mock Exam and CSRP Graduation
    2 Quizzes
Lesson 41 of 43
In Progress

Capstone A – The Attack: Breaching Meridian

Cyber School 06/08/2026

Final project · Red Team. This is the offensive half of the CSRP capstone. Acting as an authorized red-team operator, you run a single, documented end-to-end engagement against the fictional organization Meridian — from one OSINT lead all the way to crown-jewel data, across every interface Meridian exposes. Everything runs in an isolated, synthetic lab range: authorized-simulation only, no real targets or credentials.

What you will do

  • Reconnaissance & OSINT — profile Meridian and map its attack surface (L25–L26).
  • Initial access via social engineering — a human-first foothold (L31).
  • Internal network mapping & vulnerability discovery with Nmap and a vuln scanner (L27–L28).
  • Exploitation with Metasploit and a web-application attack via OWASP flaws (L29–L30).
  • Credential access — dump, crack (John/Hashcat) and reuse to escalate and move laterally (L32).
  • Actions on objective — exfiltrate the crown-jewel data and write a MITRE ATT&CK-mapped attack report.

Mirror capstone: your attack report becomes the defender’s brief in Capstone B — The Defense, where you defend this exact Meridian against this exact attack.

Presentation

Open the interactive presentation (Gamma) →  |  Download PDF

Hands-on lab: breaching Meridian, step by step

Lab: Breaching Meridian, step by step (simulated range)

Loading the lab...

Show the full step-by-step solution

Full solution: Lab: Breaching Meridian, step by step (simulated range)

The complete solution for every step of the lab. Try the lab on your own first. Flags are personal to each learner, so this page explains how to reach each flag instead of printing it.

  1. Step 1: Confirm the scope

    Before touching anything, a professional confirms what is in scope. Read the rules of engagement in your home folder and submit the flag in it.

    Answer: your personal flag, found in the lab environment as described below.

    1. Type ls. You will see ENGAGEMENT.txt and the folders recon and loot.

    2. Type cat ENGAGEMENT.txt.

    3. Note what is in scope (10.10.0.0/24, *.meridian.lab) and what is not (denial of service).

    4. Copy the flag on the "Scope confirmed" line and submit it.

  2. Step 2: Find the weak service

    Follow the OSINT lead to the scan results for the portal. One service lets anyone log in without a password. Which port is it on?

    Answer: 21

    1. Type cat recon/osint.txt. It names portal.meridian.lab (10.10.0.20) and the scan file.

    2. Type cat recon/nmap_10.10.0.20.txt.

    3. The line under 21/tcp says "Anonymous FTP login allowed": anyone can log in to FTP as "anonymous".

    4. Enter 21.

  3. Step 3: Pull the leaked backup

    The files from the anonymous FTP are mirrored in loot/ftp. Somewhere in there is a hidden database backup. Find it and read it.

    Answer: your personal flag, found in the lab environment as described below.

    1. Type cd ~/loot/ftp/pub and then ls. You only see readme.txt.

    2. Type ls -a. Now a hidden folder .backup appears.

    3. Type cd .backup, then ls, then cat portal_db_2026-09.sql.

    4. The last line holds the flag. Note also the portal_admin line with a password hash: you need it in the next step.

  4. Step 4: Crack the admin password

    The backup stores portal_admin's password as a SHA-256 hash. Your team keeps a precomputed table of common passwords in loot/rainbow.txt. What is the admin password?

    Answer: Riverton2026

    1. In the backup, the portal_admin line ends with a 64-character hash. Copy its first 8 characters.

    2. Type cd ~/loot and then grep followed by those 8 characters and rainbow.txt, for example: grep 1a2b3c4d rainbow.txt

    3. One line appears. The word at the end is the password.

    4. Enter it exactly, including capital letters.

    Why it worked: an unsalted fast hash of a common password is in every precomputed table. jsmith's long random password is not in the table, so it stays safe.

  5. Step 5: Decode the leaked token

    The website mirror is in loot/web. Its robots.txt hides a path from search engines, which also tells you where to look. Find the legacy config file there and decode the API token.

    Answer: your personal flag, found in the lab environment as described below.

    1. Type cd ~/loot/web and cat robots.txt. It disallows /old-admin/.

    2. Type cd old-admin and cat config.php.txt. The api_token line holds a Base64 string between quotes.

    3. Copy only the string (without quotes) and type: echo THE_STRING | base64 -d

    4. The decoded text is the flag. Submit it.

    Why it matters: robots.txt is public, so it often points attackers straight at forgotten admin pages.

  6. Step 6: Map it to MITRE ATT&CK

    Your report maps each action to MITRE ATT&CK. Which techniques did you use in this engagement? Select all that apply.

    Correct choices:

    • T1595 Active Scanning (the Nmap scan of the portal)
    • T1552.001 Credentials in Files (the token in the legacy config)
    • T1110.002 Password Cracking (the admin hash)

    - Used: Active Scanning (the Nmap results), Credentials in Files (the token and the database backup), Password Cracking (the admin hash).

    - Not used: Denial of Service was explicitly out of scope, and no phishing happened in this walk-through.

    Select the three techniques you used. In Capstone B, the defenders get this report and close each gap.