Differences

This shows you the differences between two versions of the page.

--- cyberconquest [2023/03/31 22:48] – [Building and Testing] gaelin
+++ cyberconquest [2024/02/06 07:11] (current) – gaelin
@@ Line 1: / Line 1: @@
-// This post is still under construction. I am adding more details and images //
+// This is my first post so I am still getting the hang of it :) //
 ====== Cyber Conquest @ DakotaCon 10.1 ======
 A purple team (offensive and defensive) cybersecurity competition that I designed, planned and lead a team to build.
@@ Line 7: / Line 7: @@
 **Competition Date:** 2023/03/25
+{{ :cyberconquest2023-laptop.jpg?nolink&600 |}}
-{{ :cyberconquest2023-room.jpg?nolink&600 |}}
 ===== Overview =====
@@ Line 55: / Line 54: @@
 ===== Infrastructure =====
-The virtual systems were hosted in the DSU [[https://ialab.dsu.edu|IALab]]((My favorite vCloud cluster, And also the largest one in the state of South Dakota)). Each team had their own virtual network holding their router and a few virtual systems. Each of these networks had its associated vlan trunked to the competition room and split out to physical ports on a switch in the room. Each team then had a switch at their table to connect the laptops and raspberry PI, which was connected back to the main switch. All of the team tables were arranged in a circle around a center table that had the actual physical systems (traffic lights, water towers, wind turbines). On the center table I had a scoring PI that used multiple MCP23008 GPIO expanders to get enough GPIO ports to support the 2 water sensors per team for scoring((Ironically not actually necessary with the 6 teams we had competing but still)).
+The virtual systems were hosted in the DSU [[https://ialab.dsu.edu|IALab]]((My favorite vCloud cluster, And also the largest one in the state of South Dakota)). There were two main competition networks, a 'Blue' network connecting all the teams' networks and a 'Red' network with the scoring engine as well as virtualized kali boxes and some laptops. Both networks were connected together through the [[https://defsec.club/doku.php?id=ialab:networks|DefSec Router]] where traffic could be monitored by white team. Each team had their own virtual network holding their router and a few virtual systems. Each of these networks had its associated vlan trunked to the competition room and split out to physical ports on a switch in the room. Each team then had a switch at their table to connect the laptops and raspberry PI, which was connected back to the main switch. Each team had two laptops which were scored and in scope (Atlantis and Metropolis) plugged directly into their team's switch. Each team also had two laptops which were on the competition wide ream team network. All of the team tables were arranged in a circle around a center table that had the actual physical systems (traffic lights, water towers, wind turbines). On the center table I had a scoring PI that used multiple MCP23008 GPIO expanders to get enough GPIO ports to support the 2 water sensors per team for scoring((Ironically not actually necessary with the 6 teams we had competing but still)).
@@ Line 76: / Line 75: @@
 ===== Lessons Learned and Final Thoughts =====
-I loved this project. It was very stressful and a lot of work((I logged almost 26 hours of dev time alone, not counting the actually physical testing, debugging and setup)) but it is also one of the most enjoyable projects that I have worked on. I got to work with cyber security (intentionally making systems vulnerable), blinky lights, motors, wiring, networking and of course infrastructure setup! I enjoyed figuring out how to wire up all of the physical components and learning about how things like the FT232H and MCP23008 work.
+I loved this project. It was very stressful and a lot of work but it is also one of the most enjoyable projects that I have worked on. I got to work with cyber security (intentionally making systems vulnerable), blinky lights, motors, wiring, networking and of course infrastructure setup! I enjoyed figuring out how to wire up all of the physical components and learning about how things like the FT232H and MCP23008 work.
 One of the coolest things I learned about was [[https://fritzing.org/|Fritzing]]. It is a FOSS wiring diagram creator which is such an awesome piece of software. I really wish I had known about it for [[https://www.firstinspires.org/robotics/frc|FIRST robotics]] in High School.
@@ Line 87: / Line 86: @@
 Everyone who helped with the initial soldering day where we soldered headers onto the GPIO breakout boards as well as the motor controller hats.
-The amazing on campus faculty who helped with acquiring resources((Beacom Wizard Tom)), 3d printing((Filament Pharaoh Tyler)), and network infrastructure((Cloud Master Eric)) setup.
+The amazing on campus faculty who helped with acquiring resources((Beacom Wizard Tom)), 3d printing((Filament Pharaoh Tyler)), and network infrastructure setup((Cloud Master Eric)).
+{{ :cyberconquest2023-room.jpg?nolink&600 |}}

Gaelin blog

User Tools

Site Tools

Differences

Page Tools