<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://noblemtk.com/rss.xml" rel="self" type="application/atom+xml" /><link href="https://noblemtk.com/" rel="alternate" type="text/html" /><updated>2026-10-18T10:36:04+01:00</updated><id>https://noblemtk.com/rss.xml</id><title type="html">noble.log</title><subtitle>SOC, pentesting and blue-team notes, homelab builds, and certification progress — written as I learn.</subtitle><author><name>Noble</name></author><entry><title type="html">My Roadmap: CPTS, BTL2 and OSCP</title><link href="https://noblemtk.com/article/my-roadmap-cpts-btl2-oscp/" rel="alternate" type="text/html" title="My Roadmap: CPTS, BTL2 and OSCP" /><published>2026-10-18T06:00:00+01:00</published><updated>2026-10-18T06:00:00+01:00</updated><id>https://noblemtk.com/article/my-roadmap-cpts-btl2-oscp</id><content type="html" xml:base="https://noblemtk.com/article/my-roadmap-cpts-btl2-oscp/"><![CDATA[<p>I’m aiming for SOC and vulnerability assessment roles, so I’m working both sides of the fence at once. Here’s the plan and how I’ll report on it.</p>

<h2 id="the-three-tracks">The three tracks</h2>

<table>
  <thead>
    <tr>
      <th>Track</th>
      <th>Side</th>
      <th>Why it’s on the list</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>HTB CPTS</td>
      <td>Offensive</td>
      <td>Deep, hands-on pentest methodology and report writing</td>
    </tr>
    <tr>
      <td>BTL2</td>
      <td>Defensive</td>
      <td>Threat hunting, detection and incident response at the next level up from BTL1</td>
    </tr>
    <tr>
      <td>OSCP</td>
      <td>Offensive</td>
      <td>The industry-recognised benchmark for practical pentesting</td>
    </tr>
  </tbody>
</table>

<blockquote>
  <p>Learning to attack makes me a better defender, and the reverse is true too. Running them together is slower, but the overlap is the point.</p>
</blockquote>

<h2 id="how-ill-track-it">How I’ll track it</h2>

<ul>
  <li>A <strong>progress post</strong> whenever I finish a major module or milestone</li>
  <li><strong>Writeups</strong> of retired boxes as I go through practice</li>
  <li>The <a href="/certs/">certs page</a> updated as each one moves from <em>in progress</em> to <em>earned</em></li>
</ul>

<h2 id="next-up">Next up</h2>

<p>The next post will cover my current CPTS module and the notes setup I’m using to keep everything organised.</p>]]></content><author><name>Noble</name></author><category term="progress" /><category term="roadmap" /><category term="CPTS" /><category term="BTL2" /><category term="OSCP" /><summary type="html"><![CDATA[I’m aiming for SOC and vulnerability assessment roles, so I’m working both sides of the fence at once. Here’s the plan and how I’ll report on it.]]></summary></entry><entry><title type="html">Why I’m Starting This Log</title><link href="https://noblemtk.com/article/why-im-starting-this-log/" rel="alternate" type="text/html" title="Why I’m Starting This Log" /><published>2026-10-18T05:00:00+01:00</published><updated>2026-10-18T05:00:00+01:00</updated><id>https://noblemtk.com/article/why-im-starting-this-log</id><content type="html" xml:base="https://noblemtk.com/article/why-im-starting-this-log/"><![CDATA[<p>Every lab I finish, every box I root and every detection rule I write ends up in a notes folder nobody else will ever read. That’s fine for revision, but it hides the actual work. This site is where some of those notes come out into the open.</p>

<h2 id="what-goes-here">What goes here</h2>

<ul>
  <li><strong>Writeups</strong> of retired Hack The Box machines and other labs I’m allowed to publish</li>
  <li><strong>Homelab builds</strong>: what I set up, what broke, and how I fixed it</li>
  <li><strong>Concept notes</strong>: short explanations of things I’ve just learned, written so future me can follow them</li>
  <li><strong>Progress posts</strong> for the certifications I’m working on</li>
</ul>

<h2 id="what-doesnt">What doesn’t</h2>

<p>No writeups for active HTB machines, exam content, or anything covered by a platform’s NDA. If it would spoil a live challenge or break a rule, it stays in my private notes.</p>

<h2 id="where-im-starting-from">Where I’m starting from</h2>

<p>I hold Security+, Linux+, BTL1, eJPT and INE Cloud Associate, and I’m working on <strong>CPTS</strong>, <strong>BTL2</strong> and <strong>OSCP</strong> in parallel. The live list is on the <a href="/certs/">certs page</a>.</p>

<h2 id="how-to-follow-along">How to follow along</h2>

<p>There’s an <a href="/rss.xml">RSS feed</a>, and everything behind this site is public on <a href="https://github.com/codeplayer12">GitHub</a>.</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">whoami
</span>noble
<span class="nv">$ </span><span class="nb">echo</span> <span class="s2">"let's go"</span>
<span class="nb">let</span><span class="s1">'s go
</span></code></pre></div></div>]]></content><author><name>Noble</name></author><category term="journal" /><category term="blogging" /><category term="career" /><summary type="html"><![CDATA[Every lab I finish, every box I root and every detection rule I write ends up in a notes folder nobody else will ever read. That’s fine for revision, but it hides the actual work. This site is where some of those notes come out into the open.]]></summary></entry></feed>