Soda City Battleground Update: Remote Access Testing

We are happy to announce that remote access to the Soda City Battleground has been setup and is ready for testing!

If you are interested in testing remote connectivity to SCBG head over to the Enter the Fray page and follow the instructions there. https://www.colasec.org/enter-the-fray

Once you have signed up we will need to assign an account to you. You will receive an email from us with account information.

We will be available for connectivity troubleshooting at the next SCBG meetup. Please keep in mind that SCBG is operated on an “as needed” basis. The equipment is powered on during the SCBG meetups.

Our next Soda City Battleground meetup is
Thursday, August 13th 2020 @ 6PM

Click below to add event to your calendar:

Soda City Battlegrounds: Capture the Flag

We are excited to finally announce the first ever Soda City Battlegrounds Capture the Flag event!

Saturday, March 28th @ 6PM

Pre-Flight Equipment Check Events
Thursday, March 12th @ 6PM
Thursday, March 26th @ 6PM

Whit E. Octopus
404 Pendleton Street
Columbia, SC 29201

Live Demonstration by Alex Cummings

Live Demonstration

Alex Cummings will be performing a live demonstration of the CTF. Everyone is welcome to gather around and watch as Alex walks through how to capture the flags!

System Requirements:

• Laptop that can connect to wireless

• Kali (Live/installed/VM)

If you do not have a laptop or ability to run a Kali VM please let us know so that arrangements can be made.

We have been working diligently to get this event setup. It has been a long time coming, we know. Hopefully everyone will be able to join us on Saturday, March 28th @ 6PM to take part in the festivities!

There are two pre-flight equipment check events that we would suggest attending. We will have people available to help get you connected to the wifi and make sure that your equipment is ready for the event.

If you haven’t done so already please join the Soda City Battleground Slack here: https://join.slack.com/t/sodacitybattleground/shared_invite/enQtNjUwMzg1NjAxOTcyLWM1ZDJkNDAxN2I1NTQ4ZDYyNmYyNzc4NDhkYTMwNDU1N2M0YTdmZGI1NTNlYjA0NDY3YjFmYWI0OTA1MDNhMDA

Soda City Battlegrounds Update for March 2019

Lots of progress was made during the last meetup. We now have pfSense setup and running as our primary firewall and have a distinct wireless network setup for accessing the battleground. Our next point of discussion will be how the internal parts of the network should be configured to allow each team access into the battleground without allowing access into areas that they should not be able to interact with. For example, we want the Purple team environment to be inaccessible from the Blue and Red team environments. We will also need to look into getting the VPN setup at some point. For now, the good news is that we can get into the battleground by connecting to it via wireless rather than a cable.

As always, we would like to encourage everyone (experienced or not) to come out to the meetups. We have been having them consistently every other Thursday at Whit E. Octopus. We usually get started around 6:30 PM and go until 8ish (depending on how much progress we are making).

The next meetup at the time of posting this will be March 28th.

Soda City Battlegrounds Update

Tonight we completed a final inventory of our hardware and identified the go-forward hardware for SCBG.  We have a few systems that should be outstanding for phase 1 and are ready to get started after a couple more sessions.

We also permanently racked the firewall, switch, and KVM switch.  As a consequence of this, the cables that were previously run for this gear no longer works, so we've striped all of the networking cables.

Next up, on January 31: 

• Establish cable routes for data, KVM, and power.

• Re-cable every server such that they can be serviced independently.
  

• Establish basic connectivity with the gateway from each host.

Extra credit:

• Get the Dell storage array working so we can have a sweet SAN

When everything above has been accomplished we'll build a basic remotely accessible VM lab on a single host.  This lab will host a network segment for intentionally vulnerable training VMs, set to revert weekly. 

Once we get that working regularly, I want to get a contained subnet built with packet capture & security onion upstream to host the known compromised hosts for forensic analysis.

After that it's on to phase 2.