<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CCDC on Zach Grace</title><link>https://zachgrace.com/tags/ccdc/</link><description>Recent content in CCDC on Zach Grace</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 04 Mar 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://zachgrace.com/tags/ccdc/index.xml" rel="self" type="application/rss+xml"/><item><title>CCDC Red Team PWNboard</title><link>https://zachgrace.com/posts/ccdc_red_team_pwnboard/</link><pubDate>Sun, 04 Mar 2018 00:00:00 +0000</pubDate><guid>https://zachgrace.com/posts/ccdc_red_team_pwnboard/</guid><description>&lt;p>I built an operations tool for our &lt;a href="http://www.cssia.org/ccdc/">Midwest CCDC&lt;/a> Red Team called &lt;a href="https://github.com/ztgrace/pwnboard">PWNboard&lt;/a>. Our biggest challenge in these competitions is that we’re in a virtual environment where teams can revert the machines at any point and essentially kill our access. So monitoring the checkins and backdoors is essential to maintaining access for the duration of the event. And that’s why I made PWNboard, an operational board that monitors our implants and backdoors. As &lt;a href="https://twitter.com/malcomvetter">Tim MalcomVetter&lt;/a> put it, it&amp;rsquo;s &lt;a href="https://twitter.com/malcomvetter/status/970327699909521408">offensive inventory management&lt;/a>.&lt;/p></description></item></channel></rss>