Day 3 (only 62 days late) of Advent of Code was a huge pain in the ass but a lot of fun.
Day 2 (only 13 days late) of Advent of Code was a throw-back to the Apollo moon landing…..Spoiler Inside.
Well I’m only 13 days late, but better late than never. I had some time to kill tonight and decided to finally jump on this year’s advent of code. Each day consists of 2 problems that you solve. So here goes Day 1…..Spoilers Inside
If you are looking for a fun way to work on your coding skills over the next 25 days or so I would encourage you to check out advent of code. This is a project run by Eric Wastle.
Last week was the 6th annual Army Cyber Skills Challenge (ACSC) hosted by my home unit, 780th MI Brigade. If you don’t recall, I first wrote about ACSC about this time last year. This was the 2nd year in a row that I served as the OIC for the event, and it was truly bigger »
Back in November I had the chance to attend the Splunk .conf conference here in DC. One of the big after hours events of the conference is the Boss of the SOC (BOTS) competition that puts teams against each other to try and analyze a set of data to identify a variety of indicators of compromise from an incident. After a little bit of talking, Splunk decided to release the BOTS app as an open-source project.
Here is another CTF problem from last years Army Cyber Stakes Challenge. You are provided a solid line of characters (see below) and have to turn it into the flag. The trick is that because there aren’t any line breaks, you have to figure it out.
Another problem from ACSC5. You’ve been able to get on a router and capture some traffic in an effort to map out the the corporate network. Your intelligence team has told you that your target device has an IP address of 172.16.58.47 but no one knows that actual location of it. Examine the network traffic and see if you can figure out the location of that device.
Yet another problem from ACSC5. Really not much of a clue needed, find the flag
Another problem from the 5th annual Army Cyber Skills Challenge. The problem is called slow_mover and can be found here.
Your boss just handed you this PCAP that one of your network sensors captured. He’s positive that there is something fishy going on here but has no clue what it is.