<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Devs - Author - Incidental InfoSec Blog</title><link>https://incidentalinfosec.com/authors/devs/</link><description>Devs - Author - Incidental InfoSec Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 19 Jan 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://incidentalinfosec.com/authors/devs/" rel="self" type="application/rss+xml"/><item><title>Splunking DLP data with a side of active response</title><link>https://incidentalinfosec.com/posts/splunking-dlp-data-with-a-side-of-response/</link><pubDate>Wed, 19 Jan 2022 00:00:00 +0000</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/posts/splunking-dlp-data-with-a-side-of-response/</guid><description><![CDATA[<p>Recently, I was attending a corporate event via conference call and I noticed a distinct phrase being mentioned over and over by the event speakers. &ldquo;Please refrain from taking screenshots of these slides as they are not meant for public disclosure.&rdquo; Sound familiar to anyone? How many people are actually going to abide by this suggestion?</p>
<p>For in-person events, this warning may be enough to ward off the rogue mobile phone picture taker&hellip;but let&rsquo;s face it&hellip;when people are at home, in their office, not thinking that they are being &ldquo;watched&rdquo;, they definitely are going to take that screen capture (and potentially send it elsewhere). Don&rsquo;t believe me?</p>]]></description></item><item><title>WORMCON CTF - 2021</title><link>https://incidentalinfosec.com/posts/wormcon-ctf-2021/</link><pubDate>Mon, 30 Aug 2021 00:00:00 +0000</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/posts/wormcon-ctf-2021/</guid><description><![CDATA[<div class="featured-image">
                <img src="/posts/wormcon-ctf-2021/wormcon.webp" referrerpolicy="no-referrer">
            </div><p>WORMCON CTF occurred this weekend and I had a fun time digging through a handful of Forensics and Networking challenges.</p>
<h2 id="network-at-risk-part-2" class="headerLink">
    <a href="#network-at-risk-part-2" class="header-mark"></a>Network At Risk (Part 2)</h2><p>This challenge provided a PCAP file that contained quite a bit of FTP traffic. As I&rsquo;m sure most know, FTP does not encrypt data while in transit. This provided me with a good starting point to try and gather some information.</p>
<figure><img src="/images/network2_1.webp" width="800"><figcaption>
			<h4>Figure 1: Protocol hierarchy</h4>
		</figcaption>
</figure>

<p>Sure enough, one of the first things I noticed in the FTP requests is a username and password. I&rsquo;ll hold onto this information for later.</p>]]></description></item><item><title>CorCTF - 2021</title><link>https://incidentalinfosec.com/posts/corctf-2021/</link><pubDate>Tue, 24 Aug 2021 00:00:00 +0000</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/posts/corctf-2021/</guid><description><![CDATA[<div class="featured-image">
                <img src="/posts/corctf-2021/corCTF.webp" referrerpolicy="no-referrer">
            </div><p>Lately, I&rsquo;ve been keeping my eye out for interesting CTF&rsquo;s to compete in. This past weekend, the <a href="https://ctftime.org/event/1364" target="_blank" rel="noopener noreferrer">corCTF team</a> hosted their own event and boy was it a tough one. Being primarily a forensics guy, I was definitely out of my comfort zone with many of the challenges being binary exploitation, reversing, and cryptography. I clung onto anything that looked familiar and in the end was able to crack a web challenge for a few points. Here&rsquo;s to getting stronger with reversing + coding for the next go around!</p>]]></description></item><item><title>GuidePoint Security CTF - August 2021</title><link>https://incidentalinfosec.com/posts/guidepoint-security-ctf-august-2021/</link><pubDate>Fri, 20 Aug 2021 00:00:00 +0000</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/posts/guidepoint-security-ctf-august-2021/</guid><description><![CDATA[<div class="featured-image">
                <img src="/posts/guidepoint-security-ctf-august-2021/gps_ctf_august.webp" referrerpolicy="no-referrer">
            </div><p>It&rsquo;s been a while since I had a chance to sit down and tackle a CTF. Lucky for me, GuidePoint Security recently ran their <a href="https://www.guidepointsecurity.com/resources/guidepoint-security-capture-the-flag-august-10/" target="_blank" rel="noopener noreferrer">August iteration</a> and it gave me a chance to brush off some cobwebs! I wasn&rsquo;t able to solve all the challenges (damn you Python!) but had a pretty good idea on how to approach most of &rsquo;em. Below are some write-ups on ones that I had fun trying to solve.</p>]]></description></item><item><title>About</title><link>https://incidentalinfosec.com/about/</link><pubDate>Sun, 08 Aug 2021 18:47:21 -0400</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/about/</guid><description><![CDATA[<figure><img src="/images/avatar.svg#center" width="200">
</figure>

<h2 id="purpose" class="headerLink">
    <a href="#purpose" class="header-mark"></a>Purpose</h2><p>I run into wacky, interesting, and confusing things working within the InfoSec industry. Most of the time I don&rsquo;t know what I&rsquo;m doing and am scared. Hopefully I can share my trials and tribulations with others through this blog. After all, the best way to learn yourself is to teach others!</p>
<h2 id="about-me" class="headerLink">
    <a href="#about-me" class="header-mark"></a>About Me</h2><p>I&rsquo;ve spent the last 6 years working in cybersecurity operations. What does that mean? Hats&hellip;lots and lots of hats. Spend enough time in this field and you&rsquo;ll realize just how much information there is to learn.</p>]]></description></item><item><title>SOC work. A walk through the trenches. [Part 1]</title><link>https://incidentalinfosec.com/posts/soc-work-a-walk-through-the-trenches-part-1/</link><pubDate>Sun, 08 Aug 2021 00:00:00 +0000</pubDate><author><name>devs</name><uri>https://github.com/t-devs</uri></author><guid>https://incidentalinfosec.com/posts/soc-work-a-walk-through-the-trenches-part-1/</guid><description><![CDATA[<div class="featured-image">
                <img src="/posts/soc-work-a-walk-through-the-trenches-part-1/military.webp" referrerpolicy="no-referrer">
            </div><p>It&rsquo;s no secret that working in a Security Operations Center (SOC) can be a demanding, thankless, and tough job (with it only getting tougher). This is especially true for folks just getting started in the industry who are building the foundational skills required for career progression. Working long hours, weekends, holidays&hellip;this is the side of cyber they don&rsquo;t tell you about&hellip; If you&rsquo;re not prepared for it, you might start asking yourself &ldquo;What the hell did I just get myself into?&rdquo;. I know I did&hellip;</p>]]></description></item></channel></rss>