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
Presentation Link : https://gamma.app/docs/OSINT-and-Public-Intelligence-Gathering-zplr4xeb80faewl
Hands-on lab: Meridian’s public footprint
Lab: Meridian's public footprint
Loading the lab...
Show the full step-by-step solution
Full solution: Lab: Meridian's public footprint
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.
Step 1: Work out the email format
Attackers who know the email format can guess every employee's address for phishing. Using the team page, write Meridian's email format in the form first.last@meridian.example or similar.
Answer: first.last@meridian.example
1. Open the "Website: our team" tab.
2. Dana Levin's address is dana.levin@meridian.example: first name, a dot, last name, then the domain.
3. Enter first.last@meridian.example.
Why it matters: with this format and the names on the page, an attacker can address phishing emails to every listed person.
Step 2: Identify the remote access product
Knowing the exact VPN product lets an attacker look up its known vulnerabilities. Which VPN product does Meridian use?
Answer: fortigate
1. In the "Job posting" tab, the first duty is to "Administer our FortiGate VPN".
2. The "Social media post" confirms it: the photo shows a FortiClient window on vpn.meridian.example.
3. Enter FortiGate.
Why it matters: job postings and photos often reveal the exact technology stack, which tells an attacker which exploits to try.
Step 3: Find the internal system that is exposed
One host name in public DNS points to a private, internal address. That reveals part of the internal network, and its certificate is in the public log. Which host is it?
Answer: dev-jira.meridian.example
1. Open the "DNS records" tab and read the Value column.
2. Every address starts with 203.0.113, except dev-jira.meridian.example, which points to 10.4.0.12, a private address.
3. The "Certificate log" tab lists dev-jira.meridian.example too, and the job posting says it runs Jira Server 8.13.
4. Enter dev-jira.meridian.example.
Why it matters: the attacker now knows an internal host name, its address and its software version.
Step 4: Search smart
You want pages on the paste site paste.example that mention exactly meridian.example. Which search finds them? Choose one.
Correct choices:
- "meridian.example" site:paste.example
- "meridian paste" searches the whole web for two loose words.
- site:meridian.example searches Meridian's own website, not the paste site.
- filetype: filters by file extension, and "paste" is not one.
- "meridian.example" site:paste.example matches the exact domain, only on the paste site. Choose that one; its results are in the "Search results" tab.
Step 5: Prioritise the findings
Which findings would you report to Meridian as high risk? Select all that apply.
Correct choices:
- A paste names the Jira admin account and mentions a temporary password
- An internal Jira host, its address and its version are publicly discoverable
- Staff names, roles, the email format and the VPN product together enable targeted phishing
- High risk: the paste with the admin account name (a direct path to an account), the exposed internal Jira host with its version (a target with known weaknesses), and the combination of names, roles, email format and VPN product (everything needed for a convincing phishing campaign).
- Low risk: an office address and a careers mailbox are normal public information.
Select the three high-risk findings.
Step 6: Recommend fixes
Which recommendations would you give Meridian? Select all that apply.
Correct choices:
- Remove dev-jira from public DNS and make it reachable only through the VPN
- Reset the Jira admin password, review its activity, and request removal of the paste
- Write job postings without exact product names and versions
- Train staff not to post photos of screens and badges
- Yes: take dev-jira out of public DNS and put it behind the VPN; treat the admin account as compromised (reset, review, remove the paste); keep product names and versions out of job ads; teach staff about photos of screens and badges.
- No: taking the website offline harms the business without fixing the root causes, and nobody can make the whole internet stop indexing.
Select the four practical fixes.