CSRP BDO
-
About
About Cyber School -
About BDO
-
The CSRP program Syllabus
-
Module 1The Cyber World and CIA Triad6 Topics
-
The OSI Model and Network Layers6 Topics
-
IP Addressing, Subnetting and Routing6 Topics
-
IP Addressing, Subnetting and Routing Textbook
-
IP Addressing, Subnetting and Routing Lesson Companion
-
IP Addressing, Subnetting and Routing Lab Guide
-
IP Addressing, Subnetting and Routing Terminology Bank
-
IP Addressing, Subnetting and Routing Question Bank
-
IP Addressing, Subnetting and Routing Lesson Guide
-
IP Addressing, Subnetting and Routing Textbook
-
DNS and DHCP6 Topics
-
Windows Server Administration6 Topics
-
Active Directory and Identity Management6 Topics
-
Active Directory and Identity Management Textbook
-
Active Directory and Identity Management Lesson Companion
-
Active Directory and Identity Management Lab Guide
-
Active Directory and Identity Management Terminology Bank
-
Active Directory and Identity Management Question Bank
-
Active Directory and Identity Management Lesson Guide
-
Active Directory and Identity Management Textbook
-
Linux CLI Fundamentals6 Topics
-
Linux Permissions and Hardening6 Topics
-
Module 2 - Defense Technologies and Cyber ToolsFirewall Architecture and Rule Design5 Topics
-
NAT and Secure Traffic Mapping6 Topics
-
Enterprise VPN Solutions6 Topics
-
IDS and IPS5 Topics
-
Identity and Access Management5 Topics
-
Multi-Factor Authentication6 Topics
-
Data Loss Prevention6 Topics
-
Endpoint Security and EDR6 Topics
-
Mail Security6 Topics
-
Web Proxy and URL Filtering6 Topics
-
Regulation and Compliance6 Topics
-
Cloud Security6 Topics|1 Quiz
-
Module 3 - Ai in securityAI in Security5 Topics
-
ML Anomaly Detection5 Topics
-
AI Threats5 Topics
-
LLM Defense6 Topics
-
Module 4 - Offensive Cyber & Vulnerability ScanningCyber Kill Chain and Attacker Mindset6 Topics
-
OSINT and Public Intelligence Gathering6 Topics
-
Network and Port Scanning with Nmap6 Topics
-
Vulnerability Scanning6 Topics
-
Exploitation Fundamentals6 Topics
-
Web Application Security5 Topics
-
Social Engineering5 Topics
-
Password and Hash Cracking5 Topics
-
Module 5 - SOC and Advance Cyber AnalystSOC Structure and Operations6 Topics
-
SIEM Fundamentals with Splunk6 Topics
-
Alerting and Dashboards6 Topics
-
Incident Response5 Topics
-
Basic Digital Forensics
-
Capstone A - The Attack: Breaching Meridian
-
Capstone B - The Defense: Defending Meridian
-
ISC2 CC Mock Exam and CSRP Graduation2 Quizzes
HANDS-ON LAB GUIDE — STUDENT (v2.1)
L7 — Linux CLI Fundamentals
First CLI lesson. Expect to feel slow at first. That’s normal. Every senior engineer started where you are now.
Lesson 7 — the big picture
Topics
| # | Topic | Taught | Practiced |
| 1 | CLI rationale + anatomy of a command | Ch.1, TB §1 | 7-Quick |
| 2 | Filesystem (pwd / ls / cd / paths) | Ch.2, TB §2 | Lab 7.1 |
| 3 | Read/write + pipes + redirection + grep + find | Ch.3, TB §3 | Lab 7.2 |
| 4 | Processes (ps / top) + network (ss / ip / ping / curl) + kill | Ch.4, TB §4 | Lab 7.3 |
| 5 | Multi-step composition (Challenge) | Ch.5, TB §5 | Challenge |
Today’s environment
Browser-based SSH terminal to a per-learner Ubuntu 22.04 VM. Username jdoe. Working directory for today’s labs: ~/csrp-labs/lesson7/.
Prior knowledge
L1-L6.
Not yet (L8 territory)
File permissions (chmod/chown), sudo, SUID, SSH hardening, privilege escalation.
The five-lab arc
| # | Lab | Difficulty | Time | Earns |
| 0 | 7-Quick “Run whoami” | Quick-win | ~2 min | First point |
| 1 | Lab 7.1 “Linux Filesystem Navigation” | Intro | ~12 min | Points |
| 2 | Lab 7.2 “Search, Grep, Pipes, and Redirection” | Core | ~15 min | Points |
| 3 | Lab 7.3 “Processes and Network Checks” | Core | ~15 min | Points |
| 4 | Challenge — “Linux CLI Master” | Challenge | ~25-35 min | [Linux-CLI-Foundations] badge |
Lab 0 — 7-Quick — “Run whoami”
Why: every Linux engineer’s first command on a new machine is “who am I logged in as?” Goal: SSH; type whoami; read.
| Step | Do | Why | What you should see |
| 1 | Click SSH-launch. | Connect to Ubuntu VM. | Black terminal; prompt like jdoe@meridian-linux:~$. |
| 2 | Type whoami Enter. | First command. | jdoe |
| 3 | Mark complete. | First L7 point. | ✅ |
Reference: man whoami.
Lab 1 — Lab 7.1 — “Linux Filesystem Navigation”
Why as a cyber professional: every investigation, audit, install starts with “where am I, what’s here?”
Goal: Navigate /var/log; list with -la; return home; locate MERIDIAN_README.txt; print its absolute path.
| Step | Do | Why | What |
| 1 | pwd | Where am I? | /home/jdoe |
| 2 | cd /var/log | Change dir. | Prompt updates. |
| 3 | pwd | Confirm. | /var/log |
| 4 | ls -la | All files + details. | Long log list. |
| 5 | cd ~ then pwd | Home. | /home/jdoe |
| 6 | find / -name “MERIDIAN_README.txt” 2>/dev/null | Search whole filesystem; suppress errors. | Full path. |
| 7 | Submit the path. | Validation. | Pass. |
Common mistakes: case-sensitivity (/var/Log ≠ /var/log); missing 2>/dev/null (noisy output).
Reference: man pwd, man ls, man cd, man find.
Lab 2 — Lab 7.2 — “Search, Grep, Pipes, and Redirection”
Why: pipes are the CLI superpower. A one-liner replaces hours of scrolling.
Goal: Analyze /var/log/auth.log:
1. Tail last 20 lines.
2. Find the most-recent successful login.
3. Count failed-login attempts.
4. Extract failed-login timestamps to ~/failed_logins.txt.
| Step | Do | Why | What |
| 1 | tail -n 20 /var/log/auth.log | Last 20 lines. | 20 entries. |
| 2 | Scan for “Accepted password” or “Accepted publickey”. | Successful logins. | Find most-recent timestamp. |
| 3 | Submit timestamp. | Validation. | First check passes. |
| 4 | grep “Failed password” /var/log/auth.log | wc -l | Count failed-login lines. | A number. |
| 5 | Submit count. | Validation. | Second check passes. |
| 6 | grep “Failed password” /var/log/auth.log | awk ‘{print $1, $2, $3}’ > ~/failed_logins.txt | Extract first 3 fields (date) per line; save. | File created. |
| 7 | cat ~/failed_logins.txt | head | Verify first lines. | First few timestamps. |
| 8 | Submit. | Validation. | Pass. |
Common mistakes: – Used > when meant >> (overwrite vs append). – Case-sensitivity in Failed password (capital F). – Forgot the pipe order.
Reference: man bash (pipelines), man grep, man awk.
Lab 3 — Lab 7.3 — “Processes and Network Checks”
Why as a cyber professional: every SOC analyst, IR investigator, and sysadmin uses ps/top/ss/ip/ping/curl constantly. Knowing what’s running and what’s listening is the OTHER half of “first day on a Linux box.”
What this covers: Topic 4 — processes and network.
Goal (9 parts): ps + top + start a service + ss + curl + kill + ip + ping.
| Part | Do | Why | What |
| A | ps then ps aux | Snapshot of current shell vs all processes. | Many rows for ps aux. |
| A.1 | ps aux \| grep python and ps aux \| grep ssh | Filter by process name. | Filtered rows. |
| B | top for 30 seconds; press q. | Live process view. | Refreshing display. |
| C | cd ~/csrp-labs/lesson7 then python3 -m http.server 8080 | Start an HTTP server on port 8080. Leave running. | “Serving HTTP on 0.0.0.0 port 8080 …” |
| D | Open a SECOND terminal tab. Then ss -tuln | List listening TCP+UDP sockets. | List including :8080 line. |
| D.1 | ss -tulnp (or sudo ss -tulnp for full info) | Show PID/process per socket. | :8080 linked to python3 PID. |
| E | curl http://127.0.0.1:8080 then curl -I http://127.0.0.1:8080 | First gets the directory listing; second gets just headers. | HTML output then HTTP/1.0 200 OK. |
| F | ps aux \| grep “http.server” | Find the Python HTTP server PID. | Row with PID number. |
| G | kill <PID> then ss -tuln \| grep 8080 | Stop the service; verify port released. | grep 8080 returns nothing. |
| H | ping -c 4 <gateway-ip> then ping -c 4 8.8.8.8 | Test local + external reachability. | Both should succeed in lab env. |
| I | ip a then ip route | Show your IP and routing table. | Interfaces + routes. |
| J | Submit completion. | Lab validates state. | Pass. |
Common mistakes: – Closed the first terminal before checking with ss in the second. – Used kill -9 immediately instead of kill (use SIGTERM first; SIGKILL only if it doesn’t stop). – Forgot cd ~/csrp-labs/lesson7 before python3 -m http.server.
Reference: man ps, man top, man ss, man ip, man kill, man curl, man ping, Python docs on http.server.
Challenge — “Linux CLI Master”
Why as a cyber professional: real CLI investigations chain commands. The Challenge proves you can follow a multi-step chain across the filesystem, decoding payloads along the way — exactly what an IR or SOC investigation looks like.
Brief: A flag is hidden somewhere on the Meridian Linux box. Follow the clue chain in ~/csrp-labs/lesson7/ctf/. Each clue points to the next step. Combine commands (find, grep, cat, base64 -d). Submit the final ULC{…} flag.
What you know: – Start at ~/csrp-labs/lesson7/ctf/. Read clue1.txt first. – The chain uses find, grep, cat, and base64 -d. – The final payload is Base64-encoded. – Per-instance flag.
Strategy: 1. cat ~/csrp-labs/lesson7/ctf/clue1.txt — first clue tells you the next step. 2. Use find (per clue1’s instruction) to locate clue2.txt somewhere under the ctf folder. 3. cat <path/to/clue2.txt> — second clue tells you to grep a log. 4. grep “FLAGPATH” ~/csrp-labs/lesson7/ctf/logs/challenge.log — reveals FLAGPATH=hidden/encoded.txt. 5. cat ~/csrp-labs/lesson7/ctf/hidden/encoded.txt — Base64 string. 6. Decode: cat ~/csrp-labs/lesson7/ctf/hidden/encoded.txt | base64 -d — reveals the final flag. 7. Submit.
Tiered hints: 1. Read clue1.txt and follow its instruction. Each clue tells you what command to use next. 2. The chain is find → grep → cat → base64 -d. Use one per clue. 3. cat clue1.txt → find . -name “clue2.txt” → cat clue2 → grep FLAGPATH in logs/challenge.log → cat the revealed file → pipe through base64 -d.
Bonus investigation (optional): After getting the flag, do real post-incident SOC work: – wc -l ~/csrp-labs/lesson7/ctf/logs/challenge.log — count log lines. – grep “WARNING” ~/csrp-labs/lesson7/ctf/logs/challenge.log > warning-report.txt — save warnings. – cat warning-report.txt — review.
Reference: man find, man grep, man cat, man base64, man xargs. MITRE T1564.001 (Hidden Files), T1140 (Deobfuscate/Decode Files or Information).
What if you didn’t finish in class
All labs persist. Practice CLI 15 min/day this week — muscle memory is everything. Then take L7 Mastery Check; L8 unlocks.
Quick reference
Navigation
pwd · ls (-la -h) · cd (cd ~ home, cd .. up).
Read/write
cat · less · head -n N · tail -n N (-f follow). touch · nano (Ctrl+O save, Ctrl+X exit) · echo “x” > f · echo “y” >> f. cp · mv · rm (no undo) · mkdir.
Pipes & redirection
| pipe · > overwrite · >> append · < input · 2>/dev/null discard errors.
Search
grep “pat” file (-r recursive, -i case-ins, -v invert, -n line numbers, -l filenames only). find PATH -name “*.ext” (-size, -mtime, -user, -perm, -exec).
Processes
ps · ps aux · ps aux | grep <name> · top (q to quit) · kill <PID> · kill -9 <PID>.
Network
ss -tuln (listening sockets) · ss -tulnp (with PID) · ip a (IPs) · ip route (routes) · ping -c 4 <ip> · curl http://host · curl -I http://host.
Decode
base64 -d (decode standard base64). For other encodings: xxd -r -p (hex), tr ‘A-Za-z’ ‘N-ZA-Mn-za-m’ (rot13).