lesion.io Blog
  • Roadmap
  • Docs
    • Templates
      • Data Inventory
      • Access Control
      • Cybersecurity Roles & Responsibilities
      • Asset Inventory
      • Acceptable Use Policy
      • Change Management
      • Vendor Risk Assessment Form
      • Password Protection Policy
  • About Us
    • Manifesto
    • Metrics
  • CTF Team
    • CISA ICS CTF 2024
      • Virbank
        • Mission: Inconceivable - 1
        • Mission: Inconceivable - 2
        • Extend Your Stay - 1
        • Extend Your Stay - 2
        • Extend Your Stay - 3
        • Extend Your Stay - 4
        • Follow The Charts - 1
        • Follow The Charts - 2
        • Read Askew Manuscripts - 1
        • Read Askew Manuscripts - 2
        • Read Askew Manuscripts - 3
        • Read Askew Manuscripts - 4
        • Read Askew Manuscripts - 5
      • Anville
        • Genisys of the Problems - 1
        • Genisys of the Problems - 2
        • Genisys of the Problems - 3
        • Modeling Trains - 1
        • Modeling Trains - 2
        • Modeling Trains - 3
      • Castelia
        • Page
      • Driftviel
        • Page 1
Powered by GitBook
On this page

Was this helpful?

  1. CTF Team
  2. CISA ICS CTF 2024
  3. Anville

Modeling Trains - 3

PreviousModeling Trains - 2NextCastelia

Last updated 7 months ago

Was this helpful?

  1. We are tasked with finding the reason for why the Workstation stopped checking back in. When investigating the information given to us by Netbox we find that it gives us the Network Interfaces associated with each workstation. I started with checking to make sure that each workstation and Historian are in the same network.

  2. Here we see that Station 14's Historian has access to the 10.230.47.0 & 192.168.113.0 Networks assuming they are on /24 Subnets.

  1. Looking at Station 14's workstation we see that its network is either mistyped or has access to the wrong network.

  1. Giving us our flag of Station 14.