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 29 of 43
In Progress

OSINT and Public Intelligence Gathering

Cyber School 06/07/2026

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.