<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Redteam on Zach Grace</title><link>https://zachgrace.com/tags/redteam/</link><description>Recent content in Redteam on Zach Grace</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 Jun 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://zachgrace.com/tags/redteam/index.xml" rel="self" type="application/rss+xml"/><item><title>Red Team Telemetry Part 1</title><link>https://zachgrace.com/posts/red-team-telemetry-part-1/</link><pubDate>Fri, 01 Jun 2018 00:00:00 +0000</pubDate><guid>https://zachgrace.com/posts/red-team-telemetry-part-1/</guid><description>&lt;p>After building and releasing &lt;a href="https://github.com/ztgrace/pwnboard">PWNboard&lt;/a>, I got some great feedback from many folks especially &lt;a href="https://twitter.com/vyrus001">Vyrus&lt;/a> (seriously thanks!). Vyrus gave me a little insight into what he and the National CCDC team were prepping which made me realize they were leagues ahead of PWNboard. But it served as pure inspiration.&lt;/p>
&lt;p>I started thinking about Red Ream Telemetry (RTT) beyond CCDC, what lengths could one take it to and how could I use telemetry to convey impact and insights on red team engagements. A few ideas came to mind almost immediately, have better insight into red team operations and have a log of all actions taken against a target/organization help the blue team improve their defenses.&lt;/p></description></item><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><item><title>Hybrid Cobalt Strike Redirectors</title><link>https://zachgrace.com/posts/cobalt_strike_redirectors/</link><pubDate>Tue, 20 Feb 2018 00:00:00 +0000</pubDate><guid>https://zachgrace.com/posts/cobalt_strike_redirectors/</guid><description>&lt;p>Working for an organization with a strict data security policy puts a few challenges on a Red Team, especially when it comes to building robust infrastructure. &lt;a href="https://twitter.com/m0ther_">m0ther_&lt;/a> and I set out to build a robust, multi-redirector infrastructure similar to what &lt;a href="https://twitter.com/armitagehacker">Raphael Mudge&lt;/a> described in his blog post, &lt;a href="https://blog.cobaltstrike.com/2014/01/14/cloud-based-redirectors-for-distributed-hacking/">Cloud-based Redirectors for Distributed Hacking&lt;/a>, except we wanted to host the team server on-prem. The post below describes two iterations of infrastructure we built to meet our needs.&lt;/p></description></item></channel></rss>