<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Cyberwox Unplugged]]></title><description><![CDATA[⚙️ Notes on cybersecurity, technology, engineering, and whatever I’m currently building or exploring.]]></description><link>https://www.cyberwoxunplugged.com</link><image><url>https://substackcdn.com/image/fetch/$s_!pA5b!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png</url><title>Cyberwox Unplugged</title><link>https://www.cyberwoxunplugged.com</link></image><generator>Substack</generator><lastBuildDate>Wed, 18 Nov 2026 01:18:49 GMT</lastBuildDate><atom:link href="https://www.cyberwoxunplugged.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Dayspring Johnson]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[cyberwox@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[cyberwox@substack.com]]></itunes:email><itunes:name><![CDATA[Day Johnson]]></itunes:name></itunes:owner><itunes:author><![CDATA[Day Johnson]]></itunes:author><googleplay:owner><![CDATA[cyberwox@substack.com]]></googleplay:owner><googleplay:email><![CDATA[cyberwox@substack.com]]></googleplay:email><googleplay:author><![CDATA[Day Johnson]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Complete Guide to GRC Engineering]]></title><description><![CDATA[A curated guide built from real conversations with GRC engineering leaders at Lovable and Datadog.]]></description><link>https://www.cyberwoxunplugged.com/p/the-complete-guide-to-grc-engineering</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-complete-guide-to-grc-engineering</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Wed, 28 Oct 2026 21:24:13 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/6de81621-cd46-4c9f-af85-f48aee576208_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Search &#8220;GRC&#8221; almost anywhere, and you will find a hundred guides on how to land a GRC job. Search &#8220;GRC engineering,&#8221; and you get a couple of conference talks and not much else.</p><p>That gap bothers me, because the practice is spreading fast inside real security teams. The discipline is ahead of its own content. So instead of writing another explainer from the outside, I went to the people doing the work.</p><p>This guide is built from long-form conversations I had on the Cyber Stories Podcast with two practitioners who shaped how I think about this space:</p><ul><li><p><strong><a href="https://www.youtube.com/watch?v=bPpnRVj-Xy0">Ayoub Fandi</a>, GRC Engineer at Lovable.</strong> Ayoub co-authored the <a href="https://grc.engineering/">GRC Engineering Manifesto</a> and hosts the GRC Engineering Podcast. His path runs through Big Four consulting, a startup, Salesforce, and GitLab, where he was a Staff Security Assurance Engineer when we spoke.</p></li></ul><div id="youtube2-bPpnRVj-Xy0" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;bPpnRVj-Xy0&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/bPpnRVj-Xy0?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><ul><li><p><strong><a href="https://www.youtube.com/watch?v=63nFUz0lx6Y">Izzy Vixsama</a>, a staff-level GRC professional at Datadog.</strong> Izzy has spent over a decade in information security, working at the intersection of cloud, compliance, and engineering teams.</p></li></ul><div id="youtube2-63nFUz0lx6Y" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;63nFUz0lx6Y&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/63nFUz0lx6Y?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>I added my own experience from years in security engineering, building automation so humans wouldn't have to do repetitive work by hand.</p><p>What follows is curated, not transcribed. I organized their ideas into one path: what GRC is, how GRC engineering is changing, what software can and cannot automate, and how to build a career in it. </p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-complete-guide-to-grc-engineering?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/the-complete-guide-to-grc-engineering?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><h1>Part 1: What GRC Actually Is</h1><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!4-3N!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!4-3N!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 424w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 848w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 1272w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!4-3N!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp" width="1456" height="1461" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1461,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!4-3N!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 424w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 848w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 1272w, https://substackcdn.com/image/fetch/$s_!4-3N!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F185922b3-bf46-4bbd-8594-0e98baf22b99_1601x1606.webp 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">The Three Elements of GRC. Source: <a href="https://secureframe.com/hub/grc/grc-components">Secureframe</a>.</figcaption></figure></div><p>Before engineering anything, it helps to understand the job.</p><p>Ayoub describes GRC as &#8220;the conduit between the business and security [and] the engineering org.&#8221; It sits between engineering, corporate security, legal, HR, finance, leadership, and the board&#8217;s audit committee. Engineering thinks in sprints and releases. The business thinks in quarters. GRC has to speak both languages.</p><p>That makes the skill set unusual. In Ayoub&#8217;s words, you need to be &#8220;an inch deep but a mile wide.&#8221; You do not need to be the deepest expert in every area. You need to understand enough of each to connect them.</p><p>Done well, that position gives GRC real leverage. When a security team wants to enforce MFA, add scanning, or put controls on incoming merge requests, GRC can help &#8220;win those battles&#8221; by tying the request to business impact: a customer deal, a certification renewal, a real risk to the company.</p><h3>Why GRC got a nontechnical reputation</h3><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!2WUf!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!2WUf!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 424w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 848w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 1272w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!2WUf!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png" width="1456" height="970" data-attrs="{&quot;src&quot;:&quot;https://bucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com/public/images/4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:970,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Surviving and thriving as a &#8220;non-technical&#8221; professional in cybersecurity&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Surviving and thriving as a &#8220;non-technical&#8221; professional in cybersecurity" title="Surviving and thriving as a &#8220;non-technical&#8221; professional in cybersecurity" srcset="https://substackcdn.com/image/fetch/$s_!2WUf!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 424w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 848w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 1272w, https://substackcdn.com/image/fetch/$s_!2WUf!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2de635-b4ef-4607-b336-2132ef6b4673_1600x1066.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">Surviving and thriving as a &#8220;non-technical&#8221; professional in cybersecurity. Source: <a href="https://ventureinsecurity.net/p/surviving-and-thriving-as-a-non-technical">Venture in Security</a>.</figcaption></figure></div><p>Many engineers think GRC is paperwork. Ayoub is honest about why. Audits can feel like check-the-box exercises. An audit might cover a narrow slice of the company while the certification gets presented under the whole company&#8217;s name. Engineers know the critical systems with the real problems, like unencrypted S3 buckets or keys that never rotate, and they watch the auditor ask about something else. It is easy to conclude the whole function has nothing to say about security.</p><p>Izzy pushes back on the idea that GRC means nontechnical. She describes a spectrum:</p><ul><li><p>People who are hands-on keyboard</p></li><li><p>People who used to be hands-on keyboard and now translate technology into strategy</p></li><li><p>People who are not hands-on keyboard but understand how information flows, what users need, and how systems operate</p></li></ul><blockquote><p>&#8220;You really have to understand where you fit in that spectrum and then how you enable compliance will kind of naturally flow.&#8221; Izzy Vixsama</p></blockquote><p>When Izzy got access to an AWS account, she went into the console and started looking at S3 bucket configurations. She looked at how often teams committed code and how often scans ran. She was not building those systems. She wanted to understand them well enough to make better recommendations. That curiosity is the bridge into GRC engineering.</p><h3>Why GRC is becoming more technical</h3><p>The cloud changed the ground under compliance. Static perimeters and fixed IP allowlists gave way to dynamic IPs, short-lived instances, Terraform, and Helm charts. Frameworks like ISO have updated to emphasize cloud environments, and auditors have had to follow suit.</p><p>Izzy frames cloud risk plainly: moving to the cloud is not inherently riskier. &#8220;It&#8217;s the same risk. You just either transfer it to someone else or you are choosing to ignore the risk.&#8221; The shared responsibility model still applies. The provider secures the cloud. You secure what you put in it. And somebody still has to govern, assess risk, and prove compliance.</p><blockquote><p>&#8220;As a security professional you should trust and verify, but you should still move forward in the direction that technology is taking you.&#8221; Izzy Vixsama</p></blockquote><div><hr></div><h2>Part 2: What GRC Engineering Is</h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!KNj6!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!KNj6!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 424w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 848w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 1272w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!KNj6!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png" width="1456" height="622" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:622,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:298076,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/218084462?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!KNj6!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 424w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 848w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 1272w, https://substackcdn.com/image/fetch/$s_!KNj6!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5e40e9d9-c893-4bc8-bab2-1146688465a0_1840x786.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">GRC Engineering 101. Source: <a href="https://grcengclub.com/learn/grc-engineering-101">GRC Engineering Club</a>.</figcaption></figure></div><p>GRC engineering is what happens when you apply real software engineering practices to governance, risk, and compliance. You encode controls as automated tests. You run them continuously instead of once a year. You plug compliance checks into the systems your engineering team already uses.</p><p>Ayoub breaks it into two goals.</p><h3>Goal 1: Make GRC more effective</h3><p>Traditional GRC tests controls once a year, every six months, or every quarter. GRC engineering aims for real-time data on control health and risk posture, with alerts when a control stops working. That applies even when a certification does not explicitly require continuous monitoring. The point is knowing, not passing.</p><p>Ayoub describes the end state as a &#8220;Minority Report dashboard&#8221;: one view across application security, vulnerability management, and every other function, showing what is healthy and what is drifting.</p><h3>Goal 2: Integrate GRC with engineering</h3><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!XLIo!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!XLIo!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 424w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 848w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 1272w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!XLIo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png" width="1456" height="389" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:389,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:198662,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/218084462?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!XLIo!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 424w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 848w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 1272w, https://substackcdn.com/image/fetch/$s_!XLIo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F22dc7640-84d3-4ced-9d0b-2e33791a45e3_2424x648.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">Open Policy Agent. Source: <a href="https://www.openpolicyagent.org/">openpolicyagent.org</a>.</figcaption></figure></div><p>Most GRC teams only talk to engineering during audit season. GRC engineering puts compliance inside engineering workflows instead.</p><p>This is where policy as code comes in. Tools like <a href="https://www.openpolicyagent.org/">Open Policy Agent</a> let you express a control as a machine-checkable rule. Ayoub&#8217;s example: a control that verifies SAST runs in every CI build. The check does not have to block the build. It can simply record a violation when SAST did not run. Over time, those violations show you patterns, and patterns tell you whether you have a people problem or a process problem.</p><p>The same idea extends to governance. Policies can live in Markdown in a Git repository, so every change has a history, a reviewer, and a reason.</p><blockquote><p>Checks do not have to block. Sometimes the most useful thing a control can do is tell you, honestly, how often it fails.</p></blockquote><h3>Where it is today</h3><div class="captioned-image-container"><figure><div class="image-link image2" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!uvex!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 424w, https://substackcdn.com/image/fetch/$s_!uvex!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 848w, https://substackcdn.com/image/fetch/$s_!uvex!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 1272w, https://substackcdn.com/image/fetch/$s_!uvex!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!uvex!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png" width="1456" height="300" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:300,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:147178,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/218084462?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uvex!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 424w, https://substackcdn.com/image/fetch/$s_!uvex!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 848w, https://substackcdn.com/image/fetch/$s_!uvex!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 1272w, https://substackcdn.com/image/fetch/$s_!uvex!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b7fb013-daf1-44a1-8771-405ce8fe7e4c_2482x512.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div></div></div></div><figcaption class="image-caption">GRC Engineering Manifesto. Source <a href="https://grc.engineering/">grc.engineering</a>.</figcaption></figure></div><p>When we spoke, while Ayoub was still at GitLab, he estimated the companies doing this seriously could be counted on two hands, with teams at places like Netflix leading the way. He called GRC engineering &#8220;just the beginning.&#8221; If you think you missed the window, you did not. The manifesto lives at <a href="https://grc.engineering/">grc.engineering</a>, and it accepts pull requests.</p><div><hr></div><h2>Part 3: Five Questions to Ask Any GRC Platform</h2><div id="youtube2-pTdtw26S2B4" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;pTdtw26S2B4&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/pTdtw26S2B4?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>A lot of software now says it &#8220;automates compliance.&#8221; I went deep on this in my video <a href="https://youtu.be/pTdtw26S2B4">GRC Engineering Explained: What GRC Software Actually Automates (and What It Doesn&#8217;t)</a>, which uses Vanta as a worked example of a modern compliance automation platform. If you want to see these ideas applied to a real product, start there. Here are the five criteria from that guide that I use to separate real GRC engineering from a compliance checklist with a nicer interface.</p><h3>1. Is it continuous, or point-in-time?</h3><p>If you have ever owned a SOC 2 audit, you know the old way. Inventory every resource. Screenshot a setting to prove it was configured correctly on the day someone asked. Do it again next quarter, because a January screenshot proves nothing about April.</p><p>A real GRC engineering setup runs automated tests against connected systems on a continuous schedule, often hourly. When a passing control starts failing, say a security setting gets reopened by accident, you hear about it within the hour, not at the next audit.</p><blockquote><p><strong>Ask:</strong> Is it actually watching, or is it a nicer spreadsheet?</p></blockquote><h3>2. How deep does the coverage go?</h3><p>Plenty of tools technically &#8220;integrate&#8221; with your cloud provider but only check a handful of surface-level settings. The real test is whether the checks map to something you would actually be audited against. For AWS, that usually means the <a href="https://www.cisecurity.org/benchmark/amazon_web_services">CIS AWS Foundations Benchmark</a>, the same reference an outside auditor would recognize.</p><blockquote><p><strong>Ask:</strong> Does it map what it finds to a benchmark someone outside the company would recognize?</p></blockquote><h3>3. Does evidence work across frameworks?</h3><p>Most companies do not stay on one framework forever. You start with SOC 2 because a customer asks. Eighteen months later, someone asks about ISO 27001 or HIPAA, or an EU customer brings up GDPR. If your tooling only speaks one framework, you rebuild your evidence trail every time.</p><p>Good GRC engineering treats evidence as reusable. The same connected accounts and control tests should map across SOC 2 Type II, ISO 27001, HIPAA, GDPR, NIST CSF, and CMMC.</p><blockquote><p><strong>Ask:</strong> If I add a framework next year, do I have to start over?</p></blockquote><h3>4. How much of the real work gets automated?</h3><p>This is where the category has moved most in the last year or two. Automation used to mean testing. Now some platforms use AI agents for the busywork around the testing:</p><ul><li><p><strong>Policy drafting.</strong> An agent asks how your business actually operates and drafts a policy that fits, instead of handing you a generic template.</p></li><li><p><strong>Trust centers.</strong> Instead of answering the same 50 questions from every prospect&#8217;s procurement team, you point them to a public page that already holds the proof.</p></li><li><p><strong>Vendor risk.</strong> Instead of someone reading forty pages of a vendor&#8217;s SOC 2 report every time the company adopts a tool, an agent reviews documentation, assigns a risk score, and recommends a decision.</p></li></ul><p>Ayoub described that vendor problem well. For &#8220;99% of companies,&#8221; third-party risk still means sending a questionnaire, checking whether the vendor uses SSO, and approving. He sees the future as connecting to vendors through APIs and monitoring their controls in real time, with alerts when something important stops working.</p><p>Notice the word &#8220;recommends.&#8221; You still make the final call. The agent removes the reading, not the responsibility.</p><blockquote><p><strong>Ask:</strong> Does &#8220;automation&#8221; only mean running tests, or does it also cover the paperwork?</p></blockquote><h2>5. What does it say it does not do?</h2><p>This matters most if you are going to rely on a platform. Software does not replace a compliance team.</p><p><strong>Genuinely automatable in a mature setup:</strong></p><ul><li><p>Discovering resources in your cloud accounts</p></li><li><p>Running control tests continuously</p></li><li><p>Collecting evidence the moment something passes</p></li><li><p>Flagging drift the instant a passing control fails</p></li><li><p>Drafting a first version of a policy</p></li><li><p>Scoring vendor risk from their own documentation</p></li></ul><p><strong>Not automatable, and probably never should be:</strong></p><ul><li><p>Writing and approving the actual security policies. An AI draft is a starting point, not a final answer.</p></li><li><p>Real risk assessments. The judgment about what matters to your specific business.</p></li><li><p>Vendor due diligence conversations, still between humans.</p></li><li><p>Accepting an exception when a control fails, and defending that decision to an auditor.</p></li></ul><blockquote><p><strong>Ask:</strong> What does it say, out loud, that it does not do? If the answer is &#8220;nothing,&#8221; be skeptical.</p></blockquote><div><hr></div><h2>Part 4: The Trap Nobody Talks About</h2><p>Ayoub raised something that stuck with me. Automation has a hidden cost.</p><p>When GRC teams were small, and everything was manual, they had to build relationships with product and engineering. You had to sit with the infrastructure team to understand how encryption actually worked. Connectors &amp; MCPs change that. You can now pull data from Slack, GitHub, and AWS without talking to anyone.</p><p>The problem is that connector data gives you a baseline, what Ayoub called the &#8220;lowest common denominator&#8221; view of security. It tells you whether a setting is on. It doesn't explain why a 15-year-old Oracle database cannot be replaced, or which architectural tradeoff makes a particular vendor dangerous for your company.</p><p>Izzy says the same thing from the other direction. Security works as a partnership, not a dictatorship. Understanding what a team is trying to accomplish and applying a security lens to it &#8220;is going to be a hundred times more successful&#8221; than dictating. Some requirements are firm. Many only say what must be achieved, not how, and that is where GRC earns its seat by finding a path that satisfies the control without getting in engineering&#8217;s way.</p><blockquote><p>Automation should buy you time for relationships, not replace them.</p></blockquote><p>Ayoub&#8217;s framing is the right one: &#8220;winning time on low leverage activity so you can spend time on high leverage where cognitive ability makes sense.&#8221; Automation is coming for GRC. The first result should be more interesting work, not fewer people.</p><div><hr></div><h2>Part 5: How to Get Into GRC Engineering</h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!jBug!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!jBug!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 424w, https://substackcdn.com/image/fetch/$s_!jBug!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 848w, https://substackcdn.com/image/fetch/$s_!jBug!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 1272w, https://substackcdn.com/image/fetch/$s_!jBug!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!jBug!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png" width="1974" height="912" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:912,&quot;width&quot;:1974,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:704487,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/218084462?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60f1490a-f114-434e-8191-5b8f09a8d743_1974x912.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!jBug!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 424w, https://substackcdn.com/image/fetch/$s_!jBug!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 848w, https://substackcdn.com/image/fetch/$s_!jBug!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 1272w, https://substackcdn.com/image/fetch/$s_!jBug!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7ea515b1-799e-498e-9a1a-8b33974c8f1c_1974x912.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">How to Break Into GRC Engineering. Source: <a href="https://grcengclub.com/learn/how-to-break-into-grc-engineering">GRC Engineering Club</a>.</figcaption></figure></div><p>Ayoub and Izzy came from very different places. Ayoub studied economics and linguistics and wrote a master&#8217;s thesis on how the YouTube algorithm polarized politics. Izzy studied business management and finance, spent six months in finance, hated it, and ended up doing risk assessments and building automated vulnerability reports at a major bank. Neither followed a straight line. Here is what they would tell you.</p><h3>Decide whether GRC fits you</h3><p>Izzy is direct: &#8220;Just because you want to do GRC doesn&#8217;t mean you&#8217;re going to be good at it.&#8221; Before committing, ask what you want your days to look like. Do you like meetings? Documentation? Audits? Strategy? Technical investigation?</p><p>Be realistic about the early years too. &#8220;In your first five years you might not be on that strategy track.&#8221; Expect a lot of documents, audit support, and policy work before the interesting strategic problems show up.</p><p>Pick your environment carefully. Izzy&#8217;s line: &#8220;If you do GRC for an old, archaic company, it&#8217;s 100% going to be boring.&#8221; GRC at a company shipping a new product every six weeks is a completely different job.</p><h3>Learn frameworks, but think in control objectives</h3><p>&#8220;You can&#8217;t be a GRC professional and not know anything about a framework,&#8221; Izzy says. &#8220;That&#8217;s literally our bread and butter.&#8221; She recommends starting with SOC 2 and ISO because they are non-prescriptive. They tell you what to achieve, not how, which leaves room to learn.</p><p>Ayoub adds the key shift: do not try to memorize every control in ISO or NIST 800-53. Start at a higher level, like the NIST Cybersecurity Framework. Take one control, look up what it means, and understand what problem it is trying to solve.</p><blockquote><p>&#8220;Instead of thinking controls, think control objectives.&#8221; Ayoub Fandi</p></blockquote><p>Izzy describes the core skill as translating &#8220;lawyer speak&#8221; into real-world applications. A control that says a system must have a mechanism to determine vulnerabilities really means you need a scanner, a process for finding vulnerabilities in your code, and a way to prove both.</p><h3>Build technical fundamentals</h3><p>Izzy&#8217;s list: networking fundamentals, how a basic computer works, the OSI model, TLS and data in transit, load balancing, proxies, vulnerability scanning, cloud configuration, and how repositories and scanning pipelines work. &#8220;How do you know what you&#8217;re securing if you don&#8217;t know what the OSI model is?&#8221;</p><h3>Learn to script</h3><p>Ayoub&#8217;s argument for coding is simple. User interfaces lie about what a system can do. With APIs and SDKs, you can do &#8220;a hundred times more than what you see in the UI.&#8221; Development experience also teaches you how software is actually built: Git, CI/CD pipelines, Markdown documentation, and machine-readable policies. That is the native language of GRC engineering.</p><p>The combination of software engineering and GRC is still rare. Ayoub calls it a &#8220;unicorn profile.&#8221; Many people leading the field come from detection and response, security operations, AppSec, or infrastructure security, not audit. If that sounds like your background, you are closer than you think.</p><h3>Build something you can show</h3><p>Both of them push hands-on work. Ayoub points to the Cloud Resume Challenge and its security-focused variant: build a small cloud environment, implement specific controls, and write about how you did it. Even hosting a blog and documenting how you secured it counts. Izzy&#8217;s version: &#8220;Get you a lab. Actually build a lab.&#8221; Start small. </p><p>A homelab is the perfect sandbox for GRC engineering. Pick a framework control, implement it, write a policy-as-code check for it, and track when it fails. That is a portfolio piece most applicants will not have.</p><h3>Make a realistic plan</h3><p>Izzy has seen too many learning plans that try to cover GRC, SOC work, pentesting, vulnerability scanning, and network engineering in nine months. &#8220;This is like seven jobs.&#8221; Pick a target role and build toward it over six months, nine months, or longer.</p><p>Keep certifications in perspective. The CISSP is not an entry-level cert. You need five years of experience to earn it, regardless of when you pass the exam. And be honest about pay. Izzy warns that entry-level offers can be closer to $45,000 than the six figures some people promise.</p><p>You do not need to spend much to learn. Google, YouTube, and Udemy go a long way. But if you skip structured programs, you have to supply the discipline yourself.</p><h3>Build relationships, not follower counts</h3><p>Izzy&#8217;s advice on mentorship is blunt: &#8220;Don&#8217;t just follow me on LinkedIn and immediately ask me to be your mentor because the answer is always going to be no. I don&#8217;t know you.&#8221; Know what you want, why you want it, and what specific help you need before you ask anyone.</p><div><hr></div><h2>Part 6: Growing Into Staff Level</h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ZSzJ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 424w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 848w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 1272w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png" width="727" height="264.17453505007154" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:508,&quot;width&quot;:1398,&quot;resizeWidth&quot;:727,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Typical dual-track engineering career ladder&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Typical dual-track engineering career ladder" title="Typical dual-track engineering career ladder" srcset="https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 424w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 848w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 1272w, https://substackcdn.com/image/fetch/$s_!ZSzJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9572ece2-7a14-485c-bcc4-ab10b14f6f7f_1398x508.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">Source: <a href="https://staffeng.com/guides/overview-overview/">Staffeng.com</a></figcaption></figure></div><p>Both guests hold staff-level roles, and they described the same shift.</p><p>At staff level, nobody tells you what to work on. Ayoub says you should have enough context, relationships, and experience to find important problems that aren't obvious or assigned. There is always more work than people, so you delegate important but noncritical work and mentor others through it, even when you could do it faster yourself.</p><p>Izzy describes her staff work as process improvements that benefit everyone: making security more visible and more effective, and helping engineering teams work more cohesively with security. &#8220;You are not responsible for any of the actual work, but you can kind of influence and guide the direction that the work goes.&#8221;</p><p>That is what GRC engineering looks like at its best. Not a person with a spreadsheet, and not a platform on autopilot. A systems thinker who uses automation to see clearly and relationships to act on what they see.</p>]]></content:encoded></item><item><title><![CDATA[I Almost Fried My Home Lab Server Over an extra 32GB of RAM]]></title><description><![CDATA[Wazuh was eating 30GB. Fixing that nearly cost me the whole box.]]></description><link>https://www.cyberwoxunplugged.com/p/i-almost-fried-my-home-lab-server</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/i-almost-fried-my-home-lab-server</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Tue, 22 Sep 2026 12:04:19 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/3d8d4387-236c-4b4e-aed5-40aa002357b1_1280x720.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I built this PC in June 2020, and I haven&#8217;t touched its hardware components since. I only know the date because it&#8217;s printed on one of the sticks I pulled out that night, and seeing it stopped me for a second. Peak pandemic, me putting a machine together on the dining table. Six years later it was still running everything I&#8217;d thrown at it, which is exactly why I never touched it.</p><div id="youtube2-dZc-QKqJ7Rs" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;dZc-QKqJ7Rs&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/dZc-QKqJ7Rs?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>The reason I finally had to was Wazuh.</p><p>My Proxmox host, lab0, was sitting on 32GB of RAM. I restarted it fresh, and it climbed right back to 63% memory utilization; on a normal day when I&#8217;m not touching anything, it drifts up to 70% or 71%. Almost all of that is one node. Wazuh was pulling around 18GB immediately after boot and creeping toward 30GB the longer it stayed up.</p><p>That&#8217;s what finally pushed me. It wasn&#8217;t that anything was broken; it&#8217;s that nothing new could ever get built. Every time I thought about spinning up another VM for a project, the math said no before I even got to the fun part. So I had to upgrade the memory.</p><p>Two <a href="https://amzn.to/4cFToSF">G.SKILL Ripjaws V DDR4 sticks</a>, 16GB each, to take the host from 32GB to 64GB. $239, which stung a little. If you&#8217;ve priced memory recently, you already know why: AI demand has RAM in a strange place right now, and DDR4 didn&#8217;t get a pass. Not an outrageous number for 32GB, but definitely a premium over what I paid for the original build.</p><p>Before I pulled power on anything, I did one small thing that I&#8217;d recommend to anybody about to do the same job. I went into the Wazuh VM options in Proxmox and turned on start at boot. It takes thirty seconds, and it means that when the host comes back, your important VMs come back with it. Then I shut the node down cleanly, powered off the machine, and unplugged it.</p><h2>Where it started going wrong</h2><p>Two open DIMM slots, two new sticks. I had this pegged as a fifteen-minute job.</p><p>The first one went in fine. Lined up the notch, pressed down, heard the click, felt pretty good about myself. I flipped the lever on the second slot, slid that stick in, and it felt locked, so I closed everything up, plugged the machine back in, and hit power.</p><p>Yellow light.</p><p>I gave it time, because I didn&#8217;t expect it to post instantly, and I kept refreshing the Proxmox page like that would help. It stayed yellow. Then, on a later attempt, it went red, and red is what actually worried me. So I looked both up, and it turns out the board had been telling me exactly what was wrong the entire time. </p><p>Solid yellow or amber on the DRAM light means memory failed the power-on self-test. Red means the system can&#8217;t detect a component at all.</p><p>Fine. Something&#8217;s loose. I powered down, opened it back up, and started reseating.</p><h2>The thing I didn&#8217;t know about DDR4</h2><p>This is where I burned most of the evening, and where the actual lesson lies.</p><p>I pulled the sticks and pushed them back in, and nothing changed. Did it again; still yellow. I was being careful, because these things are expensive and they feel fragile, and I kept thinking I was going to crack something. At one point I caught myself wondering if I was the problem, doing this on my office floor, in bad light, wearing jewelry, not grounded, which is a pretty complete list of what you&#8217;re <strong>not</strong> supposed to do.</p><p>I was the problem, just not in the way I assumed.</p><p>A stick can be locked at the bottom and completely loose at the top. It looks/looked seated, but it isn't.</p><p>DDR4 needs more force than feels acceptable, and it needs that force at both ends until each side clicks. Being gentle was why nothing worked. Once I pushed harder, every stick clicked twice, and suddenly they all looked properly seated in a way they hadn&#8217;t before. I had pushed one in earlier, and it wasn&#8217;t even sitting right, which is a little scary in hindsight.</p><p>So now everything was genuinely in. I closed it up, powered it on, and got yellow again.</p><h2>The part that wasn&#8217;t the RAM</h2><p>At that point I was lightheaded and out of ideas, so I went looking. I found people on Reddit describing the same lights and saying the fix was to reseat the big power cable that runs into the motherboard, which I hadn't touched once.</p><p>I grabbed my phone flashlight, which I should have done an hour earlier, and actually looked. The large connector was snug. The small one next to it wasn&#8217;t, and I&#8217;d been fighting it because I was going in the wrong order. There&#8217;s a little arrow stamped on it that had me second-guessing myself for a while, trying to work out which way it was supposed to point.</p><p>The small connector goes in first, and then the larger one seats on top of it and anchors, with a clip on the side. Once I did it in that order, it slid in and sat snug immediately.</p><p>Looking back, this is the part I&#8217;d want somebody to take from all of it. I was a hundred percent certain this was a memory problem, because memory was the thing I changed. It was partly memory, and partly a connector I never intended to move, and I only found the second half because I got desperate enough to stop trusting my own assumption. If you&#8217;re reading this thinking I was making it far harder than it needed to be, you&#8217;re right, and I knew it while it was happening.</p><h2>Back online</h2><p>I powered it on, and the light went yellow, then red, then white, then red again, then white, then green. I went through about six emotions in ten seconds.</p><p>Then the POST screen came up: ASUS TUF Gaming, total memory 65536MB.</p><p>It booted into safe mode, which makes sense after that many failed POST attempts and a few forced shutdowns. I went into the BIOS, checked the CPU temperature, confirmed DRAM status looked right, confirmed Proxmox was still first in the boot order, changed nothing, and saved and exited. One more reboot, and lab0 was back.</p><p>Proxmox reports 62GB usable rather than 64, which is normal. The BIOS sees the full 65536MB, and some gets reserved before the hypervisor ever counts it. Wazuh is now running around 59 percent of the 32GB I allocated to its VM, and that&#8217;s completely fine because it&#8217;s using what I gave it instead of squeezing the entire host. There&#8217;s finally room for the next VM.</p><p>Tailscale was the last loose end. The tail IP wouldn&#8217;t load at first and <code>tailscale status</code> reported it running but idle after all those hard resets. It came back on its own after a while, and by then it was the least of my concerns.</p><h2>What I&#8217;m taking away</h2><p><strong>Turn on start at boot before you power down.</strong> Thirty seconds of prep so you&#8217;re not troubleshooting two problems at once.</p><p><strong>Read the lights.</strong> Amber means DRAM, red means a component isn&#8217;t being detected. The board is specific. I guessed for twenty minutes before I looked it up.</p><p><strong>RAM needs real force, at both ends.</strong> No click on both sides means it isn&#8217;t in, no matter how snug it looks.</p><p><strong>Work on a flat surface with the light on.</strong> I did neither and made the whole thing harder than it had to be.</p><p><strong>Question the thing you changed.</strong> I was sure it was the memory. The power cable I never touched was half the problem.</p><h2>So, storage or a NAS?</h2><p>The bottleneck has now moved, and now I&#8217;ve got headroom for the projects I&#8217;ve been putting off.</p><p>Storage is the next constraint. I&#8217;m on a single 1TB drive, and I keep going back and forth. I could drop in another SSD, which is cheap, quick, and solves the immediate problem. Or I could build out a mini NAS, which costs more and takes real work but gets the lab closer to something that actually resembles infrastructure instead of everything living on one disk. That&#8217;s also just a better project.</p><p>Still deciding, and you&#8217;ll be the first to know when I decide.</p><p>Two questions for you in the meantime. Would you have done this upgrade differently, and if so, how? What should I hit next: another drive or the NAS?</p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p><div class="callout-block" data-callout="true"><p>This newsletter includes affiliate links from the original video sponsor. I may earn a commission if you purchase through them, at no additional cost to you.</p></div>]]></content:encoded></item><item><title><![CDATA[How I'd Approach College for Cybersecurity in 2026]]></title><description><![CDATA[The degree isn't the destination. Four years of evidence is.]]></description><link>https://www.cyberwoxunplugged.com/p/how-id-approach-college-for-cybersecurity</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/how-id-approach-college-for-cybersecurity</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Mon, 14 Sep 2026 11:01:39 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/71fb4eac-a8ee-4674-bb17-01f55d7eafd2_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I have a bachelor&#8217;s in Information Technology. Almost six years in this industry: tier-one and tier-two investigations in a SOC, then detection engineering at Datadog, now detection &amp; response at Amazon. College wasn&#8217;t a waste of time for me.</p><p>But 2026 isn&#8217;t the environment I came up in, and if I were 18 again walking into my first semester, I&#8217;d do this very differently.</p><p>Three things changed. More people hold a degree and a Security+ than there are entry-level seats for them. AI is already doing a chunk of what used to be somebody&#8217;s first job: summarizing logs, writing basic scripts, drafting first-pass triage. And the biggest threat to actually building skill now isn&#8217;t a lack of resources. It&#8217;s your attention.</p><p>Also, my goal wouldn&#8217;t be to graduate with a degree. It would be to graduate with four years of evidence, starting week one, that I belong in this industry.</p><h2>I wouldn&#8217;t assume I need a cybersecurity degree</h2><p>I&#8217;d be choosing one of three degrees: Computer Science, IT or Information Systems, and Cybersecurity. All three get you here. The real question is what foundation you want underneath security.</p><p>CS goes deeper on programming, algorithms, data structures, and computing theory. IT puts you on the systems side: networking, operating systems, infrastructure, cloud, server administration. Cybersecurity programs give you a security-focused curriculum from day one.</p><p>I did IT, and that systems foundation has been immensely useful because security engineering is still engineering. You can&#8217;t investigate a Linux server without understanding Linux. You can&#8217;t analyze network traffic without understanding networking. You can&#8217;t secure AWS if you&#8217;ve never deployed anything to it. However, I had to learn to code on my own.</p><p>There&#8217;s a newer wrinkle too. AI writes code, generates configs, and explains concepts faster than almost any professor. Genuinely useful. It also means the value isn&#8217;t in memorizing syntax anymore. It&#8217;s in understanding systems well enough to know when the AI system is wrong. In security and compliance work, being confidently wrong about a control is how you get breached, not just how you get a bad grade.</p><p>So I wouldn&#8217;t ask whether the degree says cybersecurity. I&#8217;d ask what I&#8217;ll actually know how to do when I finish it.</p><p>I&#8217;d weigh the boring stuff seriously, too: cost, flexibility, the real curriculum, and whether the school is thinking about what happens after graduation or just during it.</p><div class="pullquote"><p><strong>A note on this issue&#8217;s sponsor</strong></p><p>Grand Canyon University sponsored the <a href="https://youtu.be/asUtVbZyy24">video</a> behind this issue, and it fit the topic. GCU has over 400 programs, including cybersecurity, built around career preparation and hands-on skills. There&#8217;s a personal piece for me as well. I&#8217;m a Christian, and GCU builds faith into education the same way I think about it: not just earning a degree, but discovering your God-given purpose and living it out through learning, leadership, and service. GCU offers both campus and online paths, and in 2025 awarded more than $404 million in institutional scholarships. Private. Christian. Affordable. Nonprofit. </p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://gcu.edu/dayjohnson&quot;,&quot;text&quot;:&quot;Find Your Purpose At GCU&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://gcu.edu/dayjohnson"><span>Find Your Purpose At GCU</span></a></p></div><h2>Freshman year: apply before you feel ready</h2><p>This is the one part of my own story I&#8217;d repeat exactly, and lean into harder.</p><p>I got my first internship freshman year at a company called <a href="https://www.linkedin.com/company/benefitmall">BenefitMall</a>. Not by applying to Amazon or Google. I got it by applying to smaller local companies after getting turned down everywhere else. By sophomore year, I had a cybersecurity engineering internship offer from <strong>Intel</strong> in June, two months before the start date, after people told me it was already too late to try.</p><p>Most advice says spend years one and two getting ready, then chase internships junior year. In 2026, I think that&#8217;s dangerous. If the entry-level market is already tight and AI is already absorbing the easiest first-job tasks, waiting two years to build verifiable experience means starting the race two years behind.</p><p>So freshman year I&#8217;d do two things at once, not in sequence.</p><ul><li><p><strong>Learn fundamentals.</strong> Networking, Linux, Windows, basic programming, Git. How operating systems work. What DNS actually does. What happens when two computers talk to each other. Processes, permissions, authentication.</p></li><li><p><strong>Apply that same semester.</strong> Help desk, sysadmin, cloud, networking, anything that puts me around real infrastructure. You are never going to feel ready. I didn&#8217;t. You get the internship first, and the readiness catches up.</p></li></ul><p>And alongside both, a homelab. VirtualBox, VMware, Proxmox if I have spare hardware. A Linux box, a Windows machine, maybe a Windows Server. I&#8217;d break things on my own time and figure out how to fix them.</p><p>I broke down the full internship strategy (resume, technical prep, timing, target companies, interviews) here: </p><div id="youtube2-zbSlKmivbvk" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;zbSlKmivbvk&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/zbSlKmivbvk?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><h2>Sophomore year: the lab becomes cyber-focused</h2><p>Ideally, I&#8217;m interning again with more responsibility, and layering security onto that IT base. How Active Directory works and how attackers abuse it. What an EDR actually sees. What gets logged when someone authenticates. What malicious PowerShell looks like next to normal PowerShell.</p><p>That&#8217;s when the IT lab turns into a real security lab. Deploy Wazuh, Splunk, or Security Onion. Collect Windows logs with Sysmon and Linux logs alongside. Generate telemetry, attack your own environment, then go look at it from the defender&#8217;s chair.</p><p>This is also where I&#8217;d use AI deliberately: explain a concept I&#8217;m stuck on, debug a script, quiz me on what I just learned. Not generate a detection rule without understanding.</p><blockquote><p>If you can&#8217;t explain what the AI gave you, you haven&#8217;t learned anything. You&#8217;ve outsourced the exact part of the job that was supposed to make you employable.</p></blockquote><h2>Certifications, with receipts attached</h2><p>Somewhere in year one or two: Security+, maybe Network+ if networking is shaky, maybe a cloud cert.</p><p>I made this mistake myself. It&#8217;s easy to get addicted to collecting them. Every &#8220;congratulations, you passed&#8221; screen feels like progress, and it is. But passing an exam proves you can pass that exam. AI has made cramming multiple-choice easier than ever, so a cert alone tells an employer less than it did five years ago.</p><p>Certs support learning; they don&#8217;t replace it. Security+? Put a project next to it. AWS cert? Show me what you built in AWS.</p><h2>The fight that runs all four years</h2><p>When I was in school, there were distractions, but they weren&#8217;t engineered against me the way they are now. Short-form video, endless feeds, notifications, all designed to fragment your attention into smaller pieces.</p><p>The skills that matter here require the opposite. Reading logs carefully. Following a chain of reasoning through an investigation. Sitting with a problem you don&#8217;t understand yet. Sustained, boring, uninterrupted focus.</p><p>So I&#8217;d treat homelab time like a class I can&#8217;t skip. Phone in another room, one task, a timer if needed. And I&#8217;d be honest about the difference between learning and consuming content about learning. A two-hour video on AD attacks feels productive. Two hours building and attacking your own AD, getting it wrong four times before it works, is productive.</p><blockquote><p>Everyone has the same tutorials and the same AI now. The differentiator isn&#8217;t access to information. It&#8217;s who can sit still long enough to use it.</p></blockquote><h2>Years two and three: pick a direction</h2><p>Cybersecurity isn&#8217;t one job. Detection engineering, cloud security, AppSec, pentesting, security engineering, incident response, threat intel, GRC, identity. At some point you have to go deeper.</p><p>I didn&#8217;t start in detection engineering. I started in a SOC on tier-one alerts and worked my way in. Picking a direction doesn&#8217;t mean landing there day one. It means having a target instead of drifting.</p><p>Then build toward it. Detection engineering: write detections, generate telemetry, learn Sigma, learn how logs get parsed and normalized, learn Python. Cloud security: build environments, learn IAM, Terraform, containers, Kubernetes, cloud logging. AppSec: write a lot more code, learn CI/CD, learn how applications actually get built.</p><p>The goal is walking into an interview with something you built, broke, and fixed, not a summary of a course you watched.</p><h2>Senior year should be boring</h2><p>If the earlier years went right, I&#8217;m not scrambling for a first internship. I&#8217;ve had two or three, probably with a return offer or at least a team that knows my work. Degree nearly done, a couple certs, real projects, a homelab, a clear direction.</p><p>Now I document properly. GitHub. Writing about what I&#8217;m learning. Talking to people already doing the job I want. That&#8217;s literally what became Cyberwox for me. Documenting my own journey publicly turned into a body of work that speaks for itself in a way a resume never could.</p><p>And I&#8217;m applying for full-time roles before graduation, not after somebody hands me the degree.</p><h2>What I&#8217;m Taking Away From This</h2><p><strong>The shift is timing, not credentials.</strong> Not which degree or which certs. It&#8217;s refusing to split college into two years of preparing and two years of doing.</p><p><strong>Every piece has one job.</strong> Classes give structure. The degree gives a credential. Certs give focused learning. Projects give practical experience. The homelab gives somewhere to experiment. Internships starting freshman year give real exposure early enough to compound. Documenting all of it gives proof.</p><p><strong>Attention is the actual scarce resource.</strong> AI raised the floor on information access and did nothing for your ability to focus for three uninterrupted hours, which is exactly why that ability is worth more now.</p><h2>The Challenge</h2><p>You don&#8217;t need your career figured out at 18. I definitely didn&#8217;t. Explore, build things, break things, find what you&#8217;re actually interested in.</p><p>But don&#8217;t treat the degree as the destination, and don&#8217;t assume you have time to wait.</p><p>So do one thing this week: apply to one internship you feel unqualified for, or spin up one VM and start the lab. Then reply and tell me which, or drop it in the Discord.</p><p>Graduation shouldn&#8217;t be where your cybersecurity journey starts. It should be where you cash in four years of proof.</p><div><hr></div><p>Sources and further resources for this issue:</p><div id="youtube2-asUtVbZyy24" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;asUtVbZyy24&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/asUtVbZyy24?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div><hr></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/how-id-approach-college-for-cybersecurity?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public, so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/how-id-approach-college-for-cybersecurity?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/how-id-approach-college-for-cybersecurity?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Cyberwox Unplugged is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><h1><strong>Interested in sponsoring Cyberwox?</strong></h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, &amp; Substack &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p><div class="callout-block" data-callout="true"><p><em>This issue includes a sponsored mention from the original video sponsor.</em></p></div>]]></content:encoded></item><item><title><![CDATA[Stop Watching Cybersecurity Tutorials. Start Building These 5 Projects.]]></title><description><![CDATA[The summer project list I&#8217;d hand myself if I were starting over: network analysis, containers, password managers, Kubernetes, and a home SOC.]]></description><link>https://www.cyberwoxunplugged.com/p/stop-watching-cybersecurity-tutorials</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/stop-watching-cybersecurity-tutorials</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Tue, 01 Sep 2026 11:03:27 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/71b71f13-ed24-49f3-8720-7f523c568ad9_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I get the same message constantly, from comment sections, DMs, and every &#8220;how do I break into cybersecurity&#8221; conversation I&#8217;ve had this year: people are consuming a ton of content and building almost nothing.</p><p>Watching tutorials helps. Taking notes helps. Even stacking up certifications helps, a little. But none of that forces you to touch packets, break something on purpose, read your own logs, secure an app, deploy infrastructure, and then explain what you actually built.</p><p>So this issue is my answer to that gap: five cybersecurity projects that map directly to real skills, network analysis, cloud and container security, secrets management, Kubernetes, SOC operations, and detection engineering. I&#8217;ve either built these myself on the channel or worked through similar examples already, so I&#8217;m linking the receipts as I go.</p><h2>Why I Think Watching Isn&#8217;t Enough Anymore</h2><p>A lot of people say they want security operations, threat hunting, incident response, or blue team work, and then skip the fundamentals entirely.</p><p>The goal is not to become a packet wizard overnight. The goal is to build the muscle to look at traffic and say, &#8220;Okay, I understand what is happening here.&#8221;</p><p>That line applies to basically every project below. None of these are &#8220;beginner project&#8221; ideas that sound good on a resume and teach you nothing. Pick one, build it, and document it like you&#8217;d document work you actually got paid for.</p><h2>Project 1: Build a Network Traffic Analysis Lab</h2><p>So much of security still comes back to understanding what&#8217;s actually happening on the wire. Set up a couple of virtual machines, generate normal traffic (browse the web, SSH into a box, transfer a few files), and capture it with Wireshark.</p><p>Then start interrogating it:</p><ul><li><p>What does normal DNS traffic look like?</p></li><li><p>What does an SSH connection look like?</p></li><li><p>What changes once traffic is encrypted?</p></li><li><p>Can you identify the source, destination, protocol, port, and purpose?</p></li></ul><p>Once you&#8217;ve got a feel for &#8220;normal,&#8221; introduce something suspicious: run a basic port scan, simulate a file download from a shady host, or replay a PCAP from a malware analysis challenge. That skill translates directly into SOC work, incident response, and detection engineering.</p><p>I&#8217;ve already worked through this kind of analysis on the channel:</p><div id="youtube2-mgdbJApNfuQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;mgdbJApNfuQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/mgdbJApNfuQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div id="youtube2-CQk2RnS9r7w" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;CQk2RnS9r7w&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/CQk2RnS9r7w?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div id="youtube2-o99nZlTNGqQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;o99nZlTNGqQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/o99nZlTNGqQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><h2>A Quick Word on Python and SQL</h2><p>Many of these projects are hands-on, but two foundational skills make them easier: Python and SQL.</p><p>Python shows up everywhere in this field: parsing logs, hitting APIs, automating repetitive tasks. SQL matters just as much once you&#8217;re touching logs, SIEMs, and dashboards, because most security work is really just asking better questions of data.</p><p>Every modern SIEM you&#8217;ll touch- Splunk, Sentinel, Chronicle, Elastic- is essentially SQL under the hood. Pivoting through auth logs for lateral movement, correlating DNS queries against a threat feed, building a dashboard of failed logins by user: that&#8217;s SQL.</p><p>I partnered with <strong>DataCamp</strong> for this one, for exactly that reason. I&#8217;d point you to their Python Programming Fundamentals and SQL Fundamentals tracks, both around 12 hours and hands-on the whole way through, with a certification at the end for your resume or LinkedIn.</p><blockquote><p>You only retain about 20% of what you passively consume. When you&#8217;re actively writing code, that jumps to 75 or 90%.</p></blockquote><p>That&#8217;s the actual reason I&#8217;ve been using it myself to keep those skills sharp: <a href="https://datacamp.pxf.io/4aBByn">DataCamp Python Fundamentals</a> and <a href="https://datacamp.pxf.io/vDggQv">DataCamp SQL Fundamentals</a>.</p><h2>Project 2: Securely Containerize a Basic App</h2><p>This one is underrated. A lot of people want to jump straight to cloud security or DevSecOps without ever containerizing an application themselves, and I don&#8217;t mean copying a Dockerfile off the internet and running it <code>docker build</code>.</p><p>Take a basic Flask app, a Node app, or something intentionally vulnerable, containerize it, and then secure it. Ask yourself:</p><ul><li><p>Am I running this container as root?</p></li><li><p>Do I need every package inside this image?</p></li><li><p>Are there secrets hardcoded in the app?</p></li><li><p>Did I expose unnecessary ports?</p></li><li><p>Can I scan this image for vulnerabilities?</p></li></ul><p>This bridges the gap between &#8220;I know cybersecurity theory&#8221; and &#8220;I can actually secure something engineers use,&#8221; because in the real world, security teams spend as much time on how software is built and shipped as they do triaging alerts.</p><p>Reference points from past videos on the channel: </p><div id="youtube2-MBgtEkzPUcs" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;MBgtEkzPUcs&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/MBgtEkzPUcs?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div id="youtube2-DYmFW-cjKIA" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;DYmFW-cjKIA&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/DYmFW-cjKIA?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>Then take it further by documenting your own hardened version: write a README, show the before-and-after Dockerfiles, and include the scan results.</p><h2>Project 3: Self-Host a Password Manager</h2><p>Everyone understands passwords and why password managers matter. What most people skip is the security model underneath it.</p><p>You can run this locally in your homelab or host it in the cloud with something like Vaultwarden or Passbolt. The value isn&#8217;t in getting it running; it&#8217;s in thinking through the threat model: Is it exposed to the internet? Is it behind a VPN? Are backups handled safely? Are you monitoring authentication attempts? Are you actually applying updates?</p><p>That&#8217;s the difference between &#8220;I installed a password manager&#8221; and &#8220;I deployed a security-critical service, locked down access, configured backups, and monitored it.&#8221; One of those is a resume line. The other is a project.</p><p>The same reference video applies here:</p><div id="youtube2-DYmFW-cjKIA" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;DYmFW-cjKIA&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/DYmFW-cjKIA?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>And it stacks well with the other projects on this list: put it behind Tailscale, monitor it with Wazuh, write detection rules for failed logins.</p><h2>Project 4: Learn Kubernetes the Hard Way (or Break It With Kubernetes Goat)</h2><p>Kubernetes is intimidating the first time you look at it: containers, networking, certificates, YAML, RBAC, service accounts, ingress, all stacked together. That&#8217;s exactly why it&#8217;s worth learning properly.</p><p>Two paths here. Kubernetes the Hard Way has you manually build a cluster and actually understand the certificates, control plane components, and networking that a managed service normally hides from you: </p><div id="youtube2-Z-Pxl84WNGo" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;Z-Pxl84WNGo&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/Z-Pxl84WNGo?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>Kubernetes Goat is the security-focused path: it covers vulnerable scenarios such as misconfigurations, privilege escalation, secret exposure, and container escapes.</p><div id="youtube2-tIs0Q1_R7cE" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;tIs0Q1_R7cE&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/tIs0Q1_R7cE?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>If your goal is to understand infrastructure, do the Hard Way. If your goal is Kubernetes security specifically, do Goat. If you&#8217;re serious, do both: understand how it works first, then attack and defend an insecure version of it.</p><h2>Project 5: Build a Cybersecurity Homelab or Mini SOC</h2><p>This is probably the project most aligned with this channel, because if you&#8217;ve been around a while, you already know I love homelabs. And a homelab does not need to be expensive. You don&#8217;t need a rack, you don&#8217;t need enterprise gear, you don&#8217;t need ten servers humming in a closet. An old laptop, a mini PC, a Raspberry Pi, or even VirtualBox on your current machine is enough.</p><p>A simple version looks like: a hypervisor like Proxmox, a Windows endpoint, a Linux endpoint, a Wazuh manager and a few agents, a vulnerable machine, and some log sources. Then you start generating real questions: Can I see failed logins? Can I detect suspicious PowerShell? Can I collect logs from Linux and Windows and write a custom detection rule?</p><p>Installing Wazuh, Security Onion, or Splunk is not the project. The project is what you do after it&#8217;s installed: generating telemetry, tuning false positives, building dashboards, and documenting the incidents you investigate.</p><p>I&#8217;ve documented my own homelab journey across <a href="https://www.youtube.com/playlist?list=PLDqMNdDvMsRkIGOJBLz2VVJeyt6SKZonD">my Homelab and Detection playlist</a> and <a href="https://www.youtube.com/playlist?list=PLDqMNdDvMsRkIlufE77dKKiMURspfKKe4">Home SOC projects</a>, including the Proxmox build itself: </p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;6bd3d4e4-341c-4a0c-b772-a199dbeba472&quot;,&quot;caption&quot;:&quot;What began as a routine Proxmox upgrade turned into a surprisingly useful infrastructure-recovery exercise.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;I Upgraded My Cybersecurity Homelab From Proxmox 8 to Proxmox 9&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-08-21T20:55:01.569Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/687062e9-21cf-4ce3-8d1d-ded6145bde1c_1731x909.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/i-upgraded-my-cybersecurity-homelab&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:212205014,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:5,&quot;comment_count&quot;:0,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;278d679c-5a3d-4141-9f72-fcc9bbd0013b&quot;,&quot;caption&quot;:&quot;I was heading to D.C. for a cybersecurity conference (more on that another time), and I knew, before I even packed a bag, that I&#8217;d want access to my homelab while I was gone. Yep, this one:&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;How I Access My Cybersecurity Homelab From Anywhere&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-08-12T11:01:32.969Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/ff7ed916-43cc-41f3-9c72-536ae44732ed_1731x909.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:210691277,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:5,&quot;comment_count&quot;:0,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;a31c31f4-d720-40a0-a5ab-67e8dd807924&quot;,&quot;caption&quot;:&quot;It&#8217;s been about 9 months since my last homelab update. Back in September 2025.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Marriage Expanded My Attack Surface&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-08-01T11:00:53.050Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/faa36a93-b9df-4117-a57f-92b4fa7a8f6d_1730x909.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:209240771,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:7,&quot;comment_count&quot;:2,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;0ef68d80-6163-462e-8a72-73cabe76904e&quot;,&quot;caption&quot;:&quot;Five years ago, I was just a curious college freshman with a few spare computer parts, a lot of Google searches, and a dream of breaking into cybersecurity.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Why I&#8217;m Building a New Cybersecurity Homelab &quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-08-22T12:03:17.798Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f1ae16ec-e503-41e5-8bd3-4ce65b325387_1280x720.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/why-im-building-a-new-cybersecurity&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:171047974,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:9,&quot;comment_count&quot;:1,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div id="youtube2-gno9k9RxkQ8" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;gno9k9RxkQ8&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/gno9k9RxkQ8?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div id="youtube2-xRlzmovKLt8" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;xRlzmovKLt8&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/xRlzmovKLt8?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div id="youtube2-NMxXUwPcvQ4" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;NMxXUwPcvQ4&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/NMxXUwPcvQ4?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><h2>How I&#8217;d Actually Approach These Five</h2><p>If you&#8217;re new to the field, start with the Network Traffic Analysis Lab and either the Homelab or the SOC project. Those give you the strongest fundamentals.</p><p>If cloud security, DevSecOps, or AppSec is the goal, start with containerizing an app and self-hosting a password manager.</p><p>If you want to push into more advanced infrastructure, do Kubernetes the Hard Way or Kubernetes Goat.</p><p>But honestly, the real magic is connecting them. Build a homelab. Run a password manager inside it. Containerize a basic app. Monitor everything with Wazuh. Capture the traffic. Deploy Kubernetes Goat. Generate attacks. Write detections. Document the whole thing.</p><p>That&#8217;s the difference between someone who says &#8220;I&#8217;m interested in cybersecurity&#8221; and someone who can say &#8220;here is what I built, here is what I broke, here is what I secured, and here is what I learned.&#8221;</p><h2>What I&#8217;m Taking Away From This</h2><p><strong>Consumption isn&#8217;t the bottleneck anymore; application is.</strong> Between YouTube, certifications, and endless write-ups, information has never been easier to find. The people who stand out are the ones who actually built something with it.</p><p><strong>Documentation is the project.</strong> Building the lab and never writing it down is basically the same as not building it. A README, a set of screenshots, and an honest account of what broke turns a weekend project into a portfolio piece.</p><p><strong>Connected projects beat isolated ones.</strong> A password manager behind Tailscale, monitored by Wazuh, inside a homelab you built yourself, tells a far stronger story than five disconnected weekend experiments.</p><h2>Your Challenge</h2><p>Pick one of these five projects and actually build it. Not save it, not bookmark it, not add it to a Notion board. Build it, then document it: take the screenshots, write down the commands, explain what went wrong and what you fixed.</p><p>That documentation is what turns into a GitHub project, a blog post, a LinkedIn post, or your next interview talking point.</p><p>I genuinely want to know: which one of these five are you building this summer? Network Traffic Analysis Lab, Securely Containerizing an App, Self-Hosting a Password Manager, Kubernetes the Hard Way or Goat, or your own Homelab/SOC? Reply and let me know; I want to see what y&#8217;all are building.</p><div><hr></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/stop-watching-cybersecurity-tutorials?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public, so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/stop-watching-cybersecurity-tutorials?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/stop-watching-cybersecurity-tutorials?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Cyberwox Unplugged is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><h1><strong>Interested in sponsoring Cyberwox?</strong></h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, &amp; Substack &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p><div class="callout-block" data-callout="true"><p><em>This newsletter includes affiliate links from the original video sponsor. I may earn a commission if you purchase through them, at no additional cost to you.</em></p></div>]]></content:encoded></item><item><title><![CDATA[I Upgraded My Cybersecurity Homelab From Proxmox 8 to Proxmox 9]]></title><description><![CDATA[And almost broke everything...]]></description><link>https://www.cyberwoxunplugged.com/p/i-upgraded-my-cybersecurity-homelab</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/i-upgraded-my-cybersecurity-homelab</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Fri, 21 Aug 2026 20:55:01 GMT</pubDate><enclosure url="https://substackcdn.com/image/youtube/w_728,c_limit/dnhvkNXaQ0s" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>What began as a routine Proxmox upgrade turned into a surprisingly useful infrastructure-recovery exercise.</p><p>My primary homelab server <code>lab0</code> was still running Proxmox VE 8.4 on Debian 12 Bookworm. Since Proxmox VE 9 had been out for a while and moves the underlying distribution to Debian 13 Trixie, I decided it was time to make the jump.</p><p>This is the same host running much of the infrastructure from my homelab series, including my Wazuh VM.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;50b4485b-629e-4c03-829a-e6e45b45b2e5&quot;,&quot;caption&quot;:&quot;Five years ago, I was just a curious college freshman with a few spare computer parts, a lot of Google searches, and a dream of breaking into cybersecurity.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Why I&#8217;m Building a New Cybersecurity Homelab &quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-08-22T12:03:17.798Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f1ae16ec-e503-41e5-8bd3-4ce65b325387_1280x720.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/why-im-building-a-new-cybersecurity&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:171047974,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:9,&quot;comment_count&quot;:1,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>So before changing anything, I started where every major upgrade should start:</p><pre><code><code>pve8to9 --full</code></code></pre><p>The initial report was better than expected: 43 checks total, 29 passing, three warnings, and one failure.</p><p>The failure was the one that mattered most:</p><pre><code><code>FAIL: systemd-boot meta-package installed.</code></code></pre><p>There were a few other cleanup items too:</p><ul><li><p>AMD CPU microcode was missing.</p></li><li><p>Legacy settings remained in <code>/etc/sysctl.conf</code>.</p></li><li><p>LVM volumes were using the old autoactivation behavior.</p></li><li><p>Wazuh&#8217;s third-party repository appeared as an unusual APT suite.</p></li><li><p>One VM was still running.</p></li></ul><p>None of that was catastrophic. But this is precisely why pre-upgrade checks exist: they turn hidden technical debt into an actionable checklist.</p><div id="youtube2-dnhvkNXaQ0s" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;dnhvkNXaQ0s&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/dnhvkNXaQ0s?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><em>Full unedited upgrade process (with the help of ChatGPT).</em></p><h2>Confirming the Boot Path</h2><p>The first thing I wanted to understand was the bootloader warning.</p><p>Having the <code>systemd-boot</code> package installed does not necessarily mean the host actually boots using systemd-boot, so I checked the relevant state:</p><pre><code><code>proxmox-boot-tool status
efibootmgr -v
dpkg -l | grep -E 'systemd-boot|grub|proxmox-boot'</code></code></pre><p>The key detail was this EFI entry:</p><pre><code><code>Boot0004* proxmox ... \EFI\proxmox\shimx64.efi</code></code></pre><p>The host also had the full GRUB stack installed. In other words, it was booting through Proxmox&#8217;s GRUB/shim path&#8212;not systemd-boot. The package was simply an unnecessary meta-package left behind on the system.</p><p>I removed it, reran the checker, and the failure disappeared.</p><p>That took the host from one failure to zero.</p><h2>Cleaning Up Before the Upgrade</h2><p>Next, I worked through the remaining warnings.</p><h3>Updating LVM autoactivation</h3><p>Proxmox 9 changes how newly created LVM and LVM-thin guest volumes use autoactivation. One of my existing VM disks still had the older behavior enabled.</p><p>Proxmox provides a migration script for this:</p><pre><code><code>/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation</code></code></pre><p>It found the affected volume and corrected it.</p><p>One important lesson: I had to run this script a second time later in the upgrade </p><p>because another LVM-backed VM state volume appeared after the new LVM configuration was installed.</p><p>A clean pre-upgrade check does not guarantee that nothing changes during the distribution upgrade itself. Run the checker again afterward.</p><h3>Installing AMD microcode</h3><p><code>lab0</code> uses an <strong>AMD Ryzen CPU</strong>, and the upgrade checker correctly identified that <code>amd64-microcode</code> was not installed.</p><p>The reason was straightforward: my Debian repositories only included:</p><pre><code><code>main contrib</code></code></pre><p>The microcode package lives in:</p><pre><code><code>non-free-firmware</code></code></pre><p>After updating the Bookworm repository definitions, I installed the package:</p><pre><code><code>apt install amd64-microcode</code></code></pre><p>That rebuilt the initramfs and queued the updated microcode for activation at the next reboot.</p><p>Another warning resolved.</p><h3>Moving sysctl settings out of <code>/etc/sysctl.conf</code></h3><p>I also had these forwarding settings in the legacy <code>/etc/sysctl.conf</code>:</p><pre><code><code>net.ipv4.ip_forward=1
net.ipv6.conf.all.forwarding=1</code></code></pre><p>They are intentional. This host participates in networking within the lab&#8212;but Proxmox 9 wanted them moved into a dedicated file under <code>/etc/sysctl.d/</code>.</p><p>I created:</p><pre><code><code>/etc/sysctl.d/99-homelab-forwarding.conf</code></code></pre><p>With:</p><pre><code><code>net.ipv4.ip_forward=1
net.ipv6.conf.all.forwarding=1</code></code></pre><p>Then applied the configuration:</p><pre><code><code>sysctl --system</code></code></pre><p>Both forwarding values remained enabled.</p><p>After another upgrade-check run, I was down to:</p><pre><code><code>WARNINGS: 1
FAILURES: 0</code></code></pre><p>The remaining warning was simply that a VM was still running.</p><p>At that point, the host was ready.</p><h2>Moving to Proxmox 9</h2><p>Before changing repositories, I shut down Wazuh and temporarily disabled the Wazuh and Tailscale APT sources.</p><p>For a major Debian upgrade, I prefer to keep third-party repositories out of the transaction until the base OS and platform packages are stable. It reduces the number of variables involved if something goes sideways.</p><p>I then migrated the Debian repositories from Bookworm to Trixie and moved to the newer deb822-style APT configuration.</p><p>The Debian suites became:</p><pre><code><code>trixie
trixie-updates
trixie-security</code></code></pre><p>And the Proxmox repository became:</p><pre><code><code>trixie pve-no-subscription</code></code></pre><p>After updating package metadata:</p><pre><code><code>apt update</code></code></pre><p>I verified the intended upgrade path:</p><pre><code><code>apt policy proxmox-ve</code></code></pre><p>The output showed exactly what I wanted:</p><pre><code><code>Installed: 8.4.0
Candidate: 9.2.0</code></code></pre><p>Then came the real upgrade:</p><pre><code><code>apt dist-upgrade</code></code></pre><p>And that is where things became interesting.</p><h2>The APT Terminal Disappeared</h2><p>During the upgrade, Debian prompted for configuration-file decisions&#8212;normal things such as:</p><pre><code><code>/etc/issue
/etc/lvm/lvm.conf</code></code></pre><p>At some point, though, the shell running <code>apt dist-upgrade</code> disappeared due to a random glitch.</p><p>The upgrade process itself did not.</p><p>When I checked the Proxmox package state, I found a strange hybrid environment. Proxmox 9 packages were present:</p><pre><code><code>pve-manager: 9.2.11
proxmox-kernel-7.0.14-12-pve</code></code></pre><p>But many packages were listed as:</p><pre><code><code>not correctly installed</code></code></pre><p>That looks alarming, but it is exactly the moment when you should avoid making things worse.</p><p>My first check was:</p><pre><code><code>dpkg --audit</code></code></pre><p>It showed a long list of packages that had been unpacked but not yet configured.</p><p>I tried:</p><pre><code><code>dpkg --configure -a</code></code></pre><p>But APT still owned the package database.</p><p>So instead of deleting lock files or rebooting, I checked the process tree:</p><pre><code><code>ps auxf | grep -E '[a]pt|[d]pkg'</code></code></pre><p>There it was:</p><pre><code><code>apt dist-upgrade
&#9492;&#9472;&#9472; dpkg --configure --pending</code></code></pre><p>The original APT transaction was still running.</p><p>I inspected its file descriptors:</p><pre><code><code>ls -l /proc/&lt;PID&gt;/fd/{0,1,2}</code></code></pre><p>That revealed the actual problem: APT&#8217;s input and output were connected to a deleted pseudo-terminal.</p><pre><code><code>/dev/pts/0 (deleted)</code></code></pre><p>The terminal was gone. The process was not.</p><p>The upgrade had effectively become stranded while holding the package manager state.</p><h2>Recovering Safely</h2><p>Once I knew what I was looking at, the recovery path was clear.</p><p>I terminated the orphaned APT process normally:</p><pre><code><code>kill &lt;PID&gt;</code></code></pre><p>I did <strong>not</strong> delete the package manager lock files.</p><p>I did <strong>not</strong> remove files from <code>/var/lib/dpkg</code>.</p><p>I did <strong>not</strong> reboot halfway through the package configuration process.</p><p>After the orphaned process exited, I ran:</p><pre><code><code>dpkg --configure -a</code></code></pre><p>This time it completed successfully.</p><p>LVM configured. GRUB configured. The new Proxmox kernel was detected:</p><pre><code><code>Found linux image: /boot/vmlinuz-7.0.14-12-pve</code></code></pre><p>Then the Proxmox packages finished configuring:</p><pre><code><code>pve-manager configured
proxmox-ve configured</code></code></pre><p>I followed with:</p><pre><code><code>apt -f install</code></code></pre><p>Which returned:</p><pre><code><code>Upgrading: 0
Installing: 0
Removing: 0</code></code></pre><p>Then:</p><pre><code><code>apt-get dist-upgrade</code></code></pre><p>Returned:</p><pre><code><code>0 upgraded, 0 newly installed, 0 to remove</code></code></pre><p>That was the confirmation I was looking for: the package database had returned to a healthy state.</p><p><code>pveversion -v</code> Now showed:</p><pre><code><code>proxmox-ve: 9.2.0
pve-manager: 9.2.11
proxmox-kernel-7.0.14-12-pve-signed</code></code></pre><p>And the &#8220;not correctly installed&#8221; messages were gone.</p><h2>One Last Weird Service Failure</h2><p>There was still one failed service:</p><pre><code><code>chrony.service</code></code></pre><p>Chrony is responsible for time synchronization on this host. Its error was:</p><pre><code><code>Fatal error: Could not send notification to $NOTIFY_SOCKET</code></code></pre><p>At that moment, the host had a newly upgraded userspace (including systemd), but was still running the pre-upgrade kernel and runtime environment.</p><p>Rather than overcorrecting a failure that could be transient, I validated the essentials:</p><pre><code><code>dpkg --audit</code></code></pre><p>Returned clean.</p><p>The new Proxmox kernel was installed and set as the default:</p><pre><code><code>7.0.14-12-pve</code></code></pre><p>And the Proxmox upgrade checker showed no failures.</p><p>So I rebooted.</p><h2>The Moment of Truth</h2><p>The server came back cleanly.</p><pre><code><code>uname -r</code></code></pre><p>Returned:</p><pre><code><code>7.0.14-12-pve</code></code></pre><p>And:</p><pre><code><code>pveversion -v</code></code></pre><p>Confirmed:</p><pre><code><code>proxmox-ve: 9.2.0
pve-manager: 9.2.11</code></code></pre><p>Most importantly:</p><pre><code><code>systemctl --failed</code></code></pre><p>Returned:</p><pre><code><code>0 loaded units listed.</code></code></pre><p>Chrony had recovered after the reboot. A few seconds later:</p><pre><code><code>chronyc tracking</code></code></pre><p>Showed:</p><pre><code><code>Leap status : Normal</code></code></pre><p>With an active NTP source.</p><p>Storage was healthy too:</p><pre><code><code>pvesm status</code></code></pre><p>Both <code>local</code> and <code>local-lvm</code> were active.</p><p>Finally, I started Wazuh again:</p><pre><code><code>qm start 100
qm status 100</code></code></pre><p>And got:</p><pre><code><code>status: running</code></code></pre><p>The final validation was the best one:</p><pre><code><code>pve8to9 --full</code></code></pre><pre><code><code>WARNINGS: 0
FAILURES: 0</code></code></pre><p>Beautiful.</p><h2>Repository Cleanup</h2><p>The final step was restoring the repositories I had temporarily disabled.</p><p>Tailscale had a Debian 13 Trixie repository available, so I changed its suite from:</p><pre><code><code>bookworm</code></code></pre><p>To:</p><pre><code><code>trixie</code></code></pre><p>Then I re-enabled it.</p><p>Wazuh uses its own stable repository suite, so I re-enabled that source as well.</p><p>One last APT issue appeared: an enterprise Proxmox repository was still enabled.</p><pre><code><code>https://enterprise.proxmox.com/debian/pve trixie</code></code></pre><p>Since this lab uses the no-subscription repository, APT correctly returned:</p><pre><code><code>401 Unauthorized</code></code></pre><p>The fix was simple: disable the enterprise source and run:</p><pre><code><code>apt update</code></code></pre><p>This time:</p><pre><code><code>All packages are up to date.</code></code></pre><h2>The Actual Lesson</h2><p>This upgrade turned out to be a more valuable homelab exercise than I anticipated, mainly due to the circumstances surrounding it, not because Proxmox 9 introduced a significant breaking change.</p><p>Bootloaders. Repository management. CPU microcode. LVM behavior. Sysctl configuration. GRUB. systemd. NTP. Package state. Process trees. Terminal file descriptors. Recovering an interrupted package transaction.</p><p>Installing a SIEM is cool. Deploying Kubernetes is cool. Spinning up twenty containers is cool.</p><p>But maintaining infrastructure when the platform beneath it changes is where you build a different kind of engineering muscle.</p><p>At one point, I had:</p><ul><li><p>A Proxmox 9 userspace.</p></li><li><p>A Proxmox 8 kernel still running.</p></li><li><p>Dozens of unpacked-but-unconfigured packages.</p></li><li><p>An orphaned APT process holding the package database lock.</p></li><li><p>A deleted pseudo-terminal attached to that process.</p></li></ul><p>The negative reaction would have been:</p><blockquote><p>Delete the lock file and reboot.</p></blockquote><p>The right response was:</p><ol><li><p>Observe the actual state.</p></li><li><p>Identify what owns that state.</p></li><li><p>Fix the underlying failure.</p></li><li><p>Let the package manager finish the work it was already trying to do.</p></li></ol><p>That is infrastructure engineering.</p><p><code>lab0</code> is now running:</p><pre><code><code>Debian 13 Trixie
Proxmox VE 9.2
Kernel 7.0.14-12-pve
0 failed systemd services
0 pve8to9 warnings
0 pve8to9 failures</code></code></pre><p>And Wazuh is back online.</p><p>Not a bad Friday afternoon in the homelab.</p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p>]]></content:encoded></item><item><title><![CDATA[How I Access My Cybersecurity Homelab From Anywhere]]></title><description><![CDATA[No port forwarding, no exposed Proxmox, no exposed SSH. Just Tailscale, RustDesk, and a lesson I learned in a hotel room in D.C.]]></description><link>https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Wed, 12 Aug 2026 11:01:32 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/6b409947-f4a1-4da1-a8eb-da99d0bf21f2_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I was heading to D.C. for a cybersecurity conference (more on that another time), and I knew, before I even packed a bag, that I&#8217;d want access to my homelab while I was gone. Yep, this one:</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;e1cd5727-53cf-4e8b-8506-fcb4eacdcfaa&quot;,&quot;caption&quot;:&quot;It&#8217;s been about 9 months since my last homelab update. Back in September 2025.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Marriage Expanded My Attack Surface&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-08-01T11:00:53.050Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/faa36a93-b9df-4117-a57f-92b4fa7a8f6d_1730x909.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so&quot;,&quot;section_name&quot;:&quot;Labs&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:209240771,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:6,&quot;comment_count&quot;:2,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>So before I left, I made sure <a href="https://tailscale.com/">Tailscale</a> was already installed and running across the homelab: the Proxmox host, my laptops, all of it.</p><p>That one decision ended up being the whole point of this issue. Because once I was actually in D.C., sitting on hotel WiFi with zero trust in that network, I got to see firsthand just how powerful that setup really is.</p><p>So this issue is about showing that off: how I access my entire cybersecurity homelab from anywhere, without exposing Proxmox, SSH, or remote desktop services directly to the internet, and why setting it up before you need it is the move.</p><p>The two tools doing all the heavy lifting: <strong>Tailscale</strong> and <strong>RustDesk</strong>.</p><p>Watch the full walkthrough here: </p><div id="youtube2-A_pJYzAXafQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;A_pJYzAXafQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/A_pJYzAXafQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><h2>Why I Set This Up Before I Ever Needed It</h2><p>Here&#8217;s the thing about homelabs: the second you want to reach them from outside your own network, you&#8217;re one bad decision away from turning a learning environment into a real liability.</p><p>Port forward SSH to the router and you&#8217;ve got a service sitting on the open internet getting hammered by scanners or unrelentless AI agents within hours. Expose the Proxmox web UI the same way, and you&#8217;ve basically hung a sign that says <strong>&#8220;management plane, please attack me.&#8221;</strong></p><p>I never even considered either of those routes. I wanted something that felt like I was still on my home network, no matter where I actually was, and I wanted it working well before I needed it under pressure.</p><p>That&#8217;s the whole premise of <a href="https://tailscale.com/">Tailscale</a>: a mesh VPN built on WireGuard that quietly stitches all your devices into one private network (a &#8220;tailnet&#8221;), with no ports opened on your router at all.</p><h2>How Tailscale Connects My Homelab Devices</h2><p>The setup is almost anticlimactic in how simple it is. Install the Tailscale client on a device, authenticate, and it joins the tailnet. That&#8217;s it. No firewall rules, no static IP requirements, nothing crazy.</p><p>I&#8217;ve got it running across the homelab: the Proxmox host, individual VMs, my laptops, even devices that aren&#8217;t normally reachable from outside the house.</p><p>Once everything&#8217;s on the same tailnet, they can all talk to each other using stable, private IP addresses (or <a href="https://tailscale.com/docs/features/magicdns">MagicDNS</a> names, if you want something more human-readable). It doesn&#8217;t matter if I&#8217;m on hotel WiFi in D.C. or on my phone&#8217;s hotspot. As far as the network is concerned, I&#8217;m home.</p><h2>Configuring and Using Exit Nodes</h2><p>This is where it goes from &#8220;nice remote access&#8221; to genuinely useful: <strong>exit nodes</strong>.</p><p>An <a href="https://tailscale.com/docs/features/exit-nodes">exit node</a> lets you route your device&#8217;s entire internet traffic through another machine on your tailnet, in my case, a node sitting at home. Flip it on, and suddenly all my traffic looks like it&#8217;s coming from my home network, encrypted the whole way there.</p><p>Practically, that means I can be anywhere, connect through my home exit node, and get the same network posture I&#8217;d have sitting on my couch. For a security engineer who&#8217;s paranoid about hotel and conference WiFi (rightfully so), that&#8217;s a real upgrade over hoping a commercial VPN is trustworthy.</p><h2>Remotely Accessing Machines With RustDesk and Tailscale</h2><p>SSH gets you a terminal. Sometimes you need a screen or GUI.</p><p>That&#8217;s where <a href="https://rustdesk.com/">RustDesk</a> comes in, an open source remote desktop tool that I&#8217;m running entirely over the Tailscale network rather than exposing it to the open internet. Since RustDesk traffic rides on top of Tailscale&#8217;s already encrypted mesh, I get full remote desktop access to my homelab machines without opening a single port.</p><p>This combo (Tailscale for the private network, RustDesk for the actual screen access) means I can pull up a full desktop session on any lab machine from basically anywhere, and the attack surface stays exactly where I want it: nowhere on the public internet.</p><h2>Using Tailscale SSH Across My Tailnet</h2><p>Once devices are on the tailnet, Tailscale can also handle <a href="https://tailscale.com/docs/features/tailscale-ssh">SSH</a> directly, no separate key management, no exposed port 22, no fumbling with <code>.ssh/config</code> across a dozen machines.</p><p>Access control lives in Tailscale&#8217;s <a href="https://tailscale.com/docs/reference/examples/acls">ACLs</a> instead of a patchwork of firewall rules. Want to restrict which devices can SSH into which lab machines? That&#8217;s simple a policy.</p><p>For a homelab where I&#8217;m constantly spinning things up and tearing them down, this alone saves a meaningful amount of friction.</p><h2>Secure File Sharing With Taildrop</h2><p>Small feature, genuinely useful: <strong><a href="https://tailscale.com/docs/features/taildrop">Taildrop</a></strong>.</p><p>It lets me send files directly between devices on the tailnet, no cloud upload, no USB drive, no janky SCP command with a path I always mistype. Need to grab a config file off my macbook host onto my Proxmox while I&#8217;m out? Taildrop handles it, encrypted, peer-to-peer, done.</p><p>It&#8217;s not the headline feature, but it&#8217;s the kind of quality-of-life addition that makes the whole setup feel less like a workaround and more like an actual system.</p><h2>Security Considerations for Remote Homelab Access</h2><p>I&#8217;d be doing you a disservice if I didn&#8217;t call out the tradeoffs, because there always are some.</p><p>Tailscale and RustDesk dramatically shrink my attack surface compared to port forwarding, but they don&#8217;t eliminate risk. A few things I&#8217;m keeping in mind:</p><ul><li><p><strong>Identity is the new perimeter.</strong> Tailscale ties device access to your identity provider. If that account gets compromised, the blast radius is your entire tailnet. Multi-factor authentication on that identity provider isn&#8217;t optional.</p></li><li><p><strong>ACLs need actual attention, not defaults.</strong> It&#8217;s tempting to let every device talk to every other device once it&#8217;s all &#8220;private&#8221; anyway. Don&#8217;t. Scope access the same way you would on any internal network. I&#8217;ll make a future issue on that.</p></li><li><p><strong>RustDesk still needs auditing.</strong> Remote desktop access is powerful, which means it&#8217;s also exactly the kind of access an attacker wants if something upstream goes wrong. I&#8217;m treating it the same way I&#8217;d treat any privileged access path in production: logged, reviewed, with MFA and not left on indefinitely.</p></li></ul><p>None of this is a reason to avoid the setup. It&#8217;s a reason to run it the way I&#8217;d want anyone on my team running similar access in a real environment.</p><h2>What I&#8217;m Taking Away From This</h2><p><strong>Setting it up before you need it is clutch.</strong> The whole reason this trip went smoothly is that Tailscale was already running when I needed it. If I&#8217;d waited until I was in a hotel room trying to configure a VPN for the first time, this story would read very differently.</p><p><strong>Convenience and exposure aren&#8217;t the same tradeoff you think they are.</strong> I assumed secure remote access meant sacrificing convenience. Tailscale proved that wrong. The private mesh is often more convenient than the &#8220;exposed&#8221; version ever was.</p><p><strong>Identity-based access beats network-based access almost every time now.</strong> Instead of asking &#8220;what can reach this port,&#8221; I&#8217;m asking &#8220;who is this device, and should it be allowed to talk to that other device?&#8221; That mental shift matters more than any specific tool.</p><p><strong>The best security fix is usually the one that removes the exposure entirely</strong>, not the one that adds another layer on top of it. Zero open ports beats a hardened open port every time.</p><h2>What&#8217;s Next</h2><p>Now that I&#8217;ve seen how well this held up under real-world conditions, I want to push further into how I segment the tailnet itself: tighter ACLs between the Wazuh manager, the endpoints reporting to it, and everything else in the house.</p><p>If something in this house misbehaves while I&#8217;m three states away, I want to still catch it. If it breaks, I want to know why, from wherever I happen to be.</p><p>The homelab keeps getting more capable. Let&#8217;s see where it goes next.</p><div><hr></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/how-i-access-my-cybersecurity-homelab?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h1><strong>Interested in sponsoring Cyberwox?</strong></h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, &amp; Substack &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p>]]></content:encoded></item><item><title><![CDATA[Marriage Expanded My Attack Surface]]></title><description><![CDATA[Deploying Wazuh agents across every endpoint in the house: MacBooks, Proxmox, and a Windows box that almost didn&#8217;t make the video.]]></description><link>https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Sat, 01 Aug 2026 11:00:53 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/4971b252-909a-4218-b446-3290afa6231e_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It&#8217;s been about 9 months since my last homelab update. Back in September 2025.</p><p>That&#8217;s insane to say out loud. It&#8217;s July 2026 now.</p><p>Life&#8217;s been a whirlwind though, a good one. I got married. We went on our honeymoon. And somewhere in the middle of planning a wedding for six straight months, the homelab just&#8230; sat there. Dormant. Collecting dust.</p><p>But here&#8217;s the thing: now more than ever, this project matters. Because my wife and I living together has literally expanded our threat surface. New devices, new habits, new attack surface under one roof.</p><p>So this is a two-in-one issue, part homelab, part home security. Time to get this thing back on track.</p><p><strong>The mission:</strong> deploy the <a href="https://wazuh.com/?utm_source=ambassadors&amp;utm_medium=referral&amp;utm_campaign=ambassadors%20program">Wazuh</a> agent across four endpoints (three macOS machines and one Windows box) and make sure I have visibility into every single asset in this house.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Cyberwox Unplugged is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Endpoint 1: The Command Center</h2><p>First up is an old MacBook (M1, Apple Silicon) that used to be my daily driver, before it got demoted to &#8220;random stuff&#8221; duty once I upgraded. Still functional, still useful, so I gave it a new job: <strong>command center for the homelab.</strong></p><p>Everything still runs off the makeshift PC server, where Proxmox lives. But this MacBook is where I access the Wazuh dashboard and manage the whole operation.</p><p>Following the <a href="https://documentation.wazuh.com/current/installation-guide/wazuh-agent/wazuh-agent-package-macos.html">Wazuh macOS install docs</a>, the process is refreshingly simple:</p><ul><li><p>Log into the dashboard, click <strong>Deploy a new agent</strong></p></li><li><p>Confirm the architecture (Apple Silicon vs. Intel)</p></li><li><p>Point it at the manager IP; mine&#8217;s sitting on <code>192.168.1.133</code></p></li><li><p>Name the agent (I went with <strong>cwx-mac-cmd-ctr</strong>)</p></li><li><p>Copy, paste, run</p></li></ul><p>A few minutes later: agent active. To confirm it was actually working, I ran <code>sudo -i</code> to trigger a privileged session, and sure enough, Wazuh flagged it immediately: <em>&#8220;First time user executed sudo.&#8221;</em></p><p>That&#8217;s the whole point of a homelab, honestly. You don&#8217;t just install something and trust it works. You <strong>poke it</strong> until it proves itself.</p><h2>Endpoint 2: The Daily Driver</h2><p>Next up was my actual daily driver, an M4 MacBook, also silicon, also where all my content and work actually happens. Same install flow, new agent name: <strong>cwx-mac-daily-driver</strong></p><p>Ran the same <code>sudo -i</code> test. This time, four events came through: agent connected, agent stopped, agent started, first-time sudo. Clean.</p><p>Two active agents down. Two to go.</p><h2>Endpoint 3: My Wife&#8217;s MacBook (Yes, &#8220;Big Bertha&#8221;)</h2><p>This one came with a small hiccup, a connection refused error that turned out to be a missing <code>https://</code> in the manager address. Classic. Once fixed, the install went smoothly on her M1 MacBook, which (for reasons I will not fully explain in a newsletter) was <em>almost</em> affectionately named <strong>Big Bertha</strong>.</p><p>Same sudo test, same confirmation. Three agents active.</p><h2>Endpoint 4: The Proxmox Node </h2><p>This is the one that actually matters most, the bare-metal node running every virtual machine in the lab. Confirmed it was a Debian-based AMD64 system with <code>uname -m</code>, grabbed the Linux install command, and named it <strong>cwx-proxmox-lab0</strong>, after the lab itself.</p><p>Then it broke.</p><blockquote><p><strong>&#8220;The job for the wazuh-agent service failed because the control process exited with error code.&#8221;</strong><br><strong>&#8220;Invalid server address found for manager IP.&#8221;</strong></p></blockquote><p>Classic homelab moment. Turns out I had previously installed the <strong>Wazuh manager</strong> on this exact node (back when this box briefly played SIEM server), and the config was still pointing at itself instead of the actual manager IP. A quick edit to swap the manager IP field to <code>192.168.1.133</code>, a service reload, and it connected.</p><p>This is the part of homelabbing that never changes, no matter how many years in: <strong>trial and error is still the name of the game.</strong> Every fix teaches you something about how the system actually behaves under the hood, not just how the docs say it should.</p><h2>Endpoint 5 (Sort Of): The Windows Box</h2><p>Last endpoint: a Windows machine I picked up a couple years ago while (half-heartedly) studying for the SANS GCIH cert I never actually took. It&#8217;s been sitting around for VMware experiments and &#8220;special projects&#8221; ever since. Time to put it to work.</p><p>Here&#8217;s where I have to be honest with you: <strong>I goofed.</strong> OBS wasn&#8217;t configured to capture the screen properly, so the actual Windows install didn&#8217;t record. But the process is genuinely this simple:</p><ul><li><p>Copy the install command from the Wazuh dashboard</p></li><li><p>Run it as admin in PowerShell</p></li><li><p>Start the service</p></li></ul><p>And then, don&#8217;t skip this, <strong>install Sysmon.</strong> Raw agent telemetry is good, but Sysmon is what turns &#8220;I have an agent&#8221; into &#8220;I actually have visibility.&#8221; I recommend <a href="https://github.com/olafhartong/sysmon-modular">Olaf Hartong&#8217;s Sysmon-modular config</a>, probably the most useful config out there, or <a href="https://github.com/swiftonsecurity/sysmon-config">SwiftOnSecurity&#8217;s Sysmon config</a> as a solid alternative.</p><h2>What I&#8217;m Taking Away From This</h2><p>A few things stuck with me rewatching this lab session:</p><p><strong>Visibility isn&#8217;t a one-time project; it&#8217;s a maintenance habit.</strong> Nine months of dormancy meant nine months of blind spots. The moment life changes (new house, new person, new devices), your monitoring needs to catch up.</p><p><strong>The &#8220;boring&#8221; fixes are usually config, not code.</strong> Every issue in this session (a missing <code>https://</code>, a stale manager IP left over from an old install) was a five-second fix once I actually read the error message instead of assuming the worst.</p><p><strong>Test every agent the same way you&#8217;d expect a real event to fire.</strong> <code>sudo -i</code> isn&#8217;t glamorous, but it&#8217;s a fast, repeatable way to confirm an agent is actually alive and alerting, not just &#8220;installed.&#8221;</p><h2>What&#8217;s Next?</h2><p>The homelab&#8217;s back. Let&#8217;s see where it goes.</p><p><em>Watch the full episode:</em></p><div id="youtube2-NMxXUwPcvQ4" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;NMxXUwPcvQ4&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/NMxXUwPcvQ4?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div><hr></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public, so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/the-homelab-is-back-online-and-so?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h1><strong>Interested in sponsoring Cyberwox?</strong></h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, Substack, and Discord &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1><strong>Until Next Time</strong></h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p>]]></content:encoded></item><item><title><![CDATA[The Cost Of Ambition]]></title><description><![CDATA[What five months of unanswered questions taught me about ambition, faith, AI, and the edge that got me here.]]></description><link>https://www.cyberwoxunplugged.com/p/the-cost-of-ambition</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-cost-of-ambition</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Tue, 21 Jul 2026 11:03:07 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/96dccd3f-0651-4a32-b5a1-c3e6ad77c225_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>About five months ago, I posted across every platform I have, including LinkedIn, YouTube, X, and Substack, and asked people to send me questions for a massive Q&amp;A when I reached 60,000 YouTube subscribers.</p><p>I have now quickly surpassed 61,000, and until recently, I had not answered a single one. So I finally sat down, opened my laptop, pulled up the questions, and started working through them.</p><p>What came out of that process did not feel like a Q&amp;A. It felt more like a mirror.</p><p>The questions forced me to look at the person I was when I got into cybersecurity at 18, the person I have become over the last six years, and the person I am still trying to become now. They made me think about ambition, comparison, faith, <em>artificial intelligence</em>, content creation, and the kind of life I am building around all of it.</p><p>But one question sat underneath almost every answer:</p><blockquote><p>What do you do when the same qualities that gave you an edge also begin to cost you something?</p></blockquote><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Cyberwox Unplugged is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><h1>The Balance I Still Haven&#8217;t Found</h1><p>The first question was simple:</p><p><em>Do you enjoy your work-life balance?</em></p><p>No? Honestly, I don&#8217;t know.</p><p>To be more accurate, I am still figuring out whether I have one.</p><p>I started my career at 18. Cybersecurity has occupied almost my entire adult life. In the beginning, I was <strong>obsessed</strong>. I pulled all-nighters. I studied constantly. I learned everything I could get my hands on.</p><p>At the time, I did not really think about work-life balance because there was not much of a life outside of work to balance it against.</p><p>That obsession accelerated my career.</p><p>It also meant I went four or five years without taking a real vacation.</p><p>For a long time, I saw that intensity as an advantage. In many ways, it was. It helped me build skills quickly. It opened doors. It gave me the confidence to enter rooms I probably would not have entered otherwise.</p><p>But the things that give you an edge early in your career can become harder to carry as your life expands.</p><p>I just got married. I am entering a new season. My time is no longer mine alone.</p><p>My wife tells me I am a workaholic, and she is right.</p><p>I have not cracked the code on balance. I am not even sure balance is the right goal. Life rarely distributes itself evenly. Some seasons require more from your career. Others require more from your family, your faith, or your health.</p><p>Maybe the real question is not whether everything is perfectly balanced.</p><p>Maybe it is whether the right things are receiving your attention at the right time in the season of life you&#8217;re in.</p><p>I am still learning that.</p><div><hr></div><h2>The Career Plan I Outgrew</h2><p>Another question asked whether this is what I imagined when I first chose cybersecurity.</p><p>I turn 25 next year. I have been working in this field since I was 18 and thinking about it seriously since I was 15.</p><p>If people can have midlife crises, I may be somewhere in the middle of a <em>quarter-life one</em>.</p><p>When I chose cybersecurity, I had very specific ideas about what success would look like. At that age, career plans feel permanent. You pick a direction, commit to it, and quietly assume that changing your mind later would mean you failed.</p><p>My goal was simple.</p><p><strong>I wanted to become a CISO</strong>. Today, I have almost no desire to become a Chief Information Security Officer. At least <em>right now</em>, I would rather continue growing as an individual contributor.</p><p>That does not mean the younger version of me was wrong. He just did not have enough information yet.</p><p>Some of what I imagined has come true. I get to work on genuinely interesting problems. I have worked close to the edge of new technology. I have contributed to things with real global impact.</p><p>But I have also started wondering whether there are other things I am uniquely built for. More importantly, whether there are other things I am specifically <em><strong>purposed</strong></em> for.</p><p>I still enjoy cybersecurity. I am not trying to manufacture some <em>dramatic identity crisis</em>. But I have been allowing myself to sit with other passions instead of dismissing them because they do not fit the plan I created as a <strong>teenager</strong>.</p><p>We often treat persistence as the ability to stay on the same path forever.</p><p>Yes, sometimes persistence looks like staying. However, sometimes it looks like being honest enough to admit that your definition of success has changed.</p><div><hr></div><h2>Faith Isn&#8217;t Separate From the Work</h2><p>A few people asked how I integrate my work into a faith-led life.</p><p>Last year, I started a separate channel called <em><a href="https://www.youtube.com/@thegodlyengineer">The Godly Engineer</a></em> to explore that exact question: what it means to apply faith to a career in engineering, and what I have learned as a young Christian working in technology.</p><p>I will not repeat all of those lessons here.</p><p>The important thing is that faith is not a separate category in my life.</p><p>It is not cybersecurity over here, content creation over there, relationships somewhere else, and faith added on top when convenient.</p><p>Faith is the lens through which I try to understand all of it. It affects how I think about ambition. It changes how I define success. It shapes how I approach money, generosity, influence, and responsibility.</p><p>It also forces me to ask questions that a purely career-driven framework would never ask.</p><p>Not only, <em>How far can I go?</em></p><p>But also, <em>Who am I becoming while I get there?</em></p><p>Not only, <em>What can I build?</em></p><p>But also, <em>What am I supposed to do with what I have been given?</em></p><p>That distinction matters to me more now than it did when I started.</p><div><hr></div><h2>Aspiration Without Competition</h2><p>One question asked how I stay ahead of my peers.</p><p>The honest answer is that I no longer think much about &#8220;<em><strong>staying ahead&#8221;</strong></em>.</p><p>There is a healthy version of looking at someone else&#8217;s life and thinking, <em>That person did something incredible. I want to stretch myself in that direction.</em></p><p>That is aspiration. Maybe inspiration. Competition is different. Competition turns someone else&#8217;s progress into evidence that you are falling behind. </p><p>The problem is that you rarely know what you are actually comparing. You do not know someone else&#8217;s advantages. You do not know their background, relationships, private struggles, responsibilities, or what they sacrificed to reach the milestone you can see.</p><p>You are comparing the full weight of your life to the most visible parts of theirs.</p><p>People have watched my career grow over the years without seeing the depression, anxiety, unhealthy habits, coping, and personal battles that existed behind some of those milestones.</p><p>They saw the promotions, certifications, job titles, and subscriber counts. They never saw the cost.</p><p>That is why I stopped trying to become a better version of somebody else.</p><p>I am trying to become a better version of <strong>myself</strong>. <em>Soooooo</em> <em>clich&#233;, I know.</em></p><p>There is still room to admire people. There is still value in allowing someone else&#8217;s work to challenge you.</p><p>But aspiration sharpens you. Competition will wear you out.</p><p>Learning the difference has given me more peace than staying ahead ever could.</p><div><hr></div><h2>AI Isn&#8217;t Eliminating the Work. It Is Changing What Counts.</h2><p>Someone asked what I believe is the most AI-resistant path into offensive security.</p><p>I am not an ethical hacker, so I say this with some humility. But my read is that AI will not eliminate offensive security.</p><p>It will redefine the work.</p><p>One path is becoming deeply knowledgeable about AI systems themselves: how they work, how they fail, how they can be manipulated, and how they expand the attack surface.</p><p>Another is becoming the kind of operator who knows how to use AI as leverage to move faster, test more systems, analyze more data, and challenge both traditional and AI-native environments.</p><p>But I think the deeper shift is happening somewhere else.</p><p>Frontier models are becoming increasingly capable of finding vulnerabilities.</p><p>As vulnerability discovery gets faster and cheaper, the value of simply finding more flaws may begin to fall.</p><p>The more important question becomes:</p><p>How quickly can we fix them?</p><p>Can we distinguish the critical issues from the noise? Can we understand the root cause? Can we redesign the system so the same class of vulnerability does not keep reappearing? Can we make the fix without breaking everything around it?</p><p>AI may help with those problems too.</p><p>But someone still has to understand the system deeply enough to know whether the proposed solution is correct, safe, and durable. That is why I think the role of the cybersecurity engineer is becoming more explicitly a problem-solving role.</p><p>Some of those problems will be cybersecurity problems.</p><p>Some will not.</p><p>The durable skill is not simply knowing how to find a vulnerability. It is knowing how to understand the system, fix the weakness, prevent recurrence, and keep the organization moving while you do it.</p><p>As long as you can solve meaningful problems for people and organizations, you will remain valuable.</p><p>I share more of my thoughts in this newsletter issue:</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;c225333f-4956-44e1-9cc9-53348104e861&quot;,&quot;caption&quot;:&quot;&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Claude Mythos, Project Glasswing, and the New Defender Advantage&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-07-14T11:02:46.280Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/37a224f2-9e2e-4351-86df-1a5b85c31437_1730x909.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos&quot;,&quot;section_name&quot;:&quot;Think Pieces&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:199912814,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:6,&quot;comment_count&quot;:0,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div><hr></div><h2>Learn the System Before You Defend It</h2><p>Another question asked how to move from SOC fundamentals into detection engineering or cloud security without rushing or burning out.</p><p>For detection engineering, become a genuinely strong SOC analyst first.</p><p>Become a strong investigator.</p><p>Strong investigators develop strong detection instincts because they understand the evidence. They know what logs are available, what normal behavior looks like, what malicious activity looks like, and which signals actually matter during an investigation.</p><p>Detection engineering is an extension of that judgment.</p><p>It is the process of taking what an experienced investigator knows and turning it into something repeatable, testable, and scalable.</p><p>Cloud security requires a similar principle, but a different foundation.</p><blockquote><p>You cannot secure what you do not understand.</p></blockquote><p>Before trying to become a cloud security professional, become competent with the cloud itself. Understand how resources are deployed, how workloads communicate, how identities receive access, how systems scale, and how they are torn down.</p><p>Learn IAM beyond the definitions. Understand how permissions are evaluated, inherited, misconfigured, abused, and constrained.</p><p>Learn the system before you try to defend it. That order matters.</p><p>There is a temptation in cybersecurity to rush toward the word <em><strong>security</strong></em> before understanding the technology underneath it. That inevitably creates shallow expertise.</p><p>Fundamentals may feel slower, but they are usually the fastest path to becoming useful.</p><div><hr></div><h2>Content Opened Doors. It Did Not Carry Me Through Them.</h2><p>Someone asked whether content creation helped me land the roles I have had.</p><p>It would be disingenuous to say no.</p><p>It would also be inaccurate to say yes without qualification.</p><p>Content has helped me build credibility. It has helped me meet people. It has probably helped my r&#233;sum&#233; receive a second look. It has absolutely opened doors.</p><p>But <strong>it has not earned me a single offer by itself.</strong></p><p>I still had to interview for every role. I have also bombed plenty of interviews while having tens of thousands of people following my work online. An audience does not compensate for weak fundamentals.</p><p>Visibility may get you into the room. You still have to prove that you belong there.</p><p>For the people who asked how I grew a YouTube channel to nearly 61,000 subscribers with what has mostly been a one-person operation, the answer is not glamorous.</p><p>Consistency, improving the quality over time, understanding what my specific audience needs, and being willing to give people the answers they need to hear, not only the answers they want to hear.</p><p>The algorithm matters. Packaging matters. Titles and thumbnails matter.</p><p>But trust compounds longer than likes, subscribes, and clicks do.</p><div><hr></div><h2>Stewardship Over Hustle</h2><p>One question genuinely made me stop.</p><p>How do you balance stewardship, generosity, and gratitude with climbing the corporate ladder, chasing higher compensation, and avoiding greed?</p><p>My belief is that this career was given to me. I am managing it. I do not fully own it.</p><p>That is what <strong>stewardship</strong> means to me: taking responsibility for what you have been given, caring for it well, and multiplying its impact.</p><p>Content creation is one expression of that. It allows me to take the lessons, opportunities, and knowledge I have received and use them to help people at a scale I could never reach one conversation at a time.</p><p>Generosity is another part of stewardship. To me, generosity means creating enough margin in your life that giving is intentional rather than accidental. It means planning your finances, so you have room to help people, instead of waiting to see what remains after every personal desire has been satisfied.</p><p>And the antidote to <strong>greed</strong> is <strong>gratitude</strong>. Not <strong>complacency</strong>. <strong>Gratitude</strong>.</p><p>It is possible to desire growth while being thankful for where you are. It is possible to pursue a promotion without allowing the outcome to determine your peace. It is possible to earn more without allowing money to become the only evidence that your life is moving forward.</p><p>Climbing the proverbial <em>ladder</em> from desperation will exhaust you.</p><p>Climbing from a place of gratitude allows you to keep your footing, even when you do not receive the title, raise, or opportunity you wanted.</p><div><hr></div><h2>There Is No Perfect Age to Begin</h2><p>Someone asked whether 28 is too late to start a career in cybersecurity.</p><p>No.</p><p>I have received the same question from people in their 30s and 40s. It is not too late.</p><p>Your path may look different from that of someone who started at 18. You may have different responsibilities, less free time, or more risk associated with making a career transition. Those realities should shape your plan, not automatically disqualify you.</p><p>Starting later does not mean starting with nothing. You bring your previous experience, maturity, relationships, judgment, and understanding of the world with you. Those things count.</p><p>Build a realistic plan. Accept that it may take time. Then go after it.</p><div><hr></div><h2>Final Thoughts</h2><p>This was the last weekend before my wedding.</p><p>I had a broken microwave to replace and what felt like a hundred small tasks waiting for me before the ceremony, but I wanted to finally answer these questions before life became busier.</p><p>Looking back at all of my responses, I noticed one thread running through them.</p><p>The qualities that helped many of us build an edge, including the obsession, hunger, curiosity, discipline, and willingness to learn the hard way, are powerful. They can accelerate a career, but they can also consume a life if left unmanaged.</p><p>The challenge is not to abandon your edge. It is learning how to steward it.</p><p>You have to know when to push and when to rest. When to stay committed to the path and when to question where it is leading. When ambition is sharpening you and when comparison is hollowing you out.</p><p>Technology will continue to change. Artificial intelligence will reshape the work. New roles will emerge. Old ones will disappear. Life will move through seasons that require different versions of you.</p><p>But the ability to understand difficult systems, solve meaningful problems, and adapt without losing yourself will never go out of style.</p><p>Maybe work-life balance is not something you eventually solve. Maybe it is a question you have to keep answering as your life changes. And maybe the real question is not whether you still have the edge that got you here.</p><p>Maybe it is whether you have learned how to carry it without letting it cut everything else around you.</p><p>&#128173; <strong>What is the one question about your career&#8212;or your life&#8212;that you have been avoiding because you already suspect the answer?</strong></p><p>That may be the question worth sitting with next.</p><p><em>Watch the full, unscripted Q&amp;A here &#8594; <a href="https://youtu.be/-NSNMUihOv4">Brutally Honest Cybersecurity Career Advice From an Amazon Engineer</a></em></p><p><em>Read my piece on losing your edge:</em></p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;650d0df7-54af-4365-8e70-097e3b0c3104&quot;,&quot;caption&quot;:&quot;A few weeks ago, I came back from my first trip to Nigeria in 9 years.&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Don't Lose Your Edge&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:172540827,&quot;name&quot;:&quot;Day Johnson&quot;,&quot;bio&quot;:&quot;&#9881;&#65039;Engineering a meaningful life | Cybersecurity @Amazon // ex-@datadog | 61k on YouTube | Opinions are mine, not of past/present/future employers.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bbd53745-4b45-4abc-b056-4d9ac6849f36_1320x1320.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-10-16T14:31:20.684Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/8322c99b-3d62-44ff-ac45-a4814ee1e605_1024x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://www.cyberwoxunplugged.com/p/dont-lose-your-edge&quot;,&quot;section_name&quot;:&quot;Think Pieces&quot;,&quot;video_upload_id&quot;:null,&quot;id&quot;:173943224,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:15,&quot;comment_count&quot;:4,&quot;publication_id&quot;:1996296,&quot;publication_name&quot;:&quot;Cyberwox Unplugged&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!pA5b!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b1ed158-420f-4ae6-9aaa-adc23c31da06_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-cost-of-ambition?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-cost-of-ambition?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/the-cost-of-ambition?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h1>Interested in sponsoring Cyberwox?</h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, Substack, and Discord &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1>Until Next Time</h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p>]]></content:encoded></item><item><title><![CDATA[Claude Mythos, Project Glasswing, and the New Defender Advantage]]></title><description><![CDATA[This is truly the end of cybersecurity. Allegedly.]]></description><link>https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Tue, 14 Jul 2026 11:02:46 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/5bd03452-94c4-4b9f-84c7-a6293cfb9815_1200x630.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-h7RJDSzLYqc" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;h7RJDSzLYqc&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/h7RJDSzLYqc?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>Every few years, cybersecurity gets a new &#8220;end of the world&#8221; moment. Sometimes it is cloud. Sometimes it is ransomware. Sometimes it is generative AI. Now, with Claude Mythos and Project Glasswing, the conversation has shifted again.</p><p>On April 7, 2026, Anthropic announced <a href="https://www.anthropic.com/glasswing">Project Glasswing</a>, an initiative built around a frontier model called Claude Mythos Preview. The basic idea was simple: Anthropic had developed a model with cyber capabilities strong enough that they did not want to make it generally available to the public right away. Instead, they gave select organizations early access so they could identify and fix serious vulnerabilities in critical systems before similar capabilities became more widely available.</p><p>According to Anthropic, Mythos demonstrated the ability to find high-severity vulnerabilities, including long-standing issues in systems such as OpenBSD and FFmpeg, and to chain multiple vulnerabilities in complex software. The reason this matters is not just that the model can find bugs. Security researchers have been finding bugs for decades. What matters is that AI appears to be compressing the time between vulnerability discovery, exploit development, and operational use.</p><p>That is the actual problem.</p><p>Not that cybersecurity is over. Not that defenders are useless. Not that AI is some magical offensive weapon that immediately invalidates everything we know. The real issue is that AI continues to make certain parts of cyber operations faster, cheaper, and more scalable. And in cybersecurity, speed has always mattered.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Cyberwox Unplugged is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>True To This, Not New To This</h2><p>We have seen this pattern before.</p><p>The cloud era taught us this lesson clearly. Cloud-based infrastructure gave us faster deployment, easier scaling, and more flexible operation. But that same speed also created new failure modes. Misconfigured storage buckets, overly permissive IAM roles, public-facing admin panels, exposed keys, open security groups, and flat cloud environments all became part of the modern attack surface.</p><p><a href="https://www.capitalone.com/digital/facts2019/">The Capital One breach</a> became one of the clearest examples of this reality. Cloud was not the problem by itself. The problem was that the speed of cloud adoption outpaced the maturity of cloud security practices. A single misconfiguration, combined with an exploitable path through the environment, led to consequences on a massive scale.</p><p>That same pattern is now playing out with AI.</p><p>Early chatbots were quickly met with <a href="https://www.paloaltonetworks.com/cyberpedia/what-is-a-prompt-injection-attack">prompt injection</a>. Systems designed to follow user instructions were manipulated by users who understood that the instructions themselves had become part of the attack surface. As AI systems became more connected to tools, browsers, files, APIs, and enterprise data, the problem became bigger than getting a chatbot to say something weird. The concern became what happens when an AI system can act.</p><p>That is why exposed AI systems matter. If we have learned anything from cloud security, it is that organizations will expose things they do not fully understand. They will deploy fast. They will leave defaults in place. They will connect powerful systems to sensitive resources before security architecture catches up. The names change, but the foundational issue is familiar.</p><p>This is not new.</p><p>It is the same security debt showing up in a new format.</p><h2>The Real Problem Is Exploitability</h2><p> <em><a href="https://blog.cloudflare.com/cyber-frontier-models/">Cloudflare&#8217;s Project Glasswing update</a> displays this flawlessly.</em></p><p>Vulnerabilities do not exist in a vacuum. A bug becomes dangerous because surrounding conditions make it exploitable. That is why attack paths matter. An attacker does not just need a vulnerability. They need reachability, permissions, context, credentials, exposure, and a way to turn technical weakness into operational impact. </p><p>This is where models like Claude Mythos become interesting. The concern is not only that AI can identify a vulnerable code path. The concern is that AI can reason across multiple small primitives and assemble them into something meaningful. That starts to look less like automated scanning and more like the workflow of a capable vulnerability researcher.</p><p>That is a shift defenders should take seriously.</p><p>If AI can reduce the time required to discover, validate, and chain vulnerabilities, then defenders have less time to respond. Patch cycles become more compressed. Exposure windows become more costly. Asset inventory becomes more important. Vulnerability management becomes less about knowing that something is vulnerable and more about understanding which weaknesses can actually be reached, chained, and exploited in your environment.</p><p>This is why the conversation cannot stop at AI capabilities. The real conversation is about defensive readiness.</p><h2>Cybersecurity First Principles Still Matter</h2><p>When a technology feels new, the industry has a habit of pretending the fundamentals have changed. Most of the time, they have not. AI introduces new capabilities, new attack surfaces, and new operating models, but it does not remove the need for strong security foundations.</p><p><a href="https://github.com/ericyoc/gencyber_10_sec_principles_poc">Cybersecurity first principles</a> still matter because they give us a way to reason about new systems without being distracted by novelty.</p><ol><li><p><strong>Domain separation</strong> becomes critical when AI agents can interact with tools, data, users, and infrastructure. If an agent is compromised or manipulated, strong boundaries should prevent that compromise from spreading across the environment. An AI agent should not be able to move freely between sensitive domains simply because it was given access to a browser, a shell, an API, or an internal knowledge base.</p></li><li><p><strong>Process isolation</strong> matters for the same reason. AI-enabled workflows should not be treated as trusted monoliths. Models, tools, plugins, execution environments, and downstream systems should be isolated from one another as much as possible. If one component behaves unexpectedly, the rest of the system should not automatically inherit that failure.</p></li><li><p><strong>Resource encapsulation</strong> is also essential. AI systems should interact with resources through controlled interfaces, not through broad and undefined access. If an agent needs to query a database, call an API, or retrieve a document, that interaction should be mediated, logged, scoped, and governed. The agent should not receive unrestricted access just because the user has it.</p></li><li><p><strong>Least privilege</strong> might be one of the most important AI security principles. An agent should not inherit full user authority by default. It should receive the minimum capability required for the task. That means scoped tokens, limited tool access, narrow execution rights, and explicit boundaries around what actions it can take without human approval.</p></li><li><p><strong>Layering</strong> still matters because no single AI security control will be enough. Prompt injection defenses, model monitoring, tool permissioning, retrieval filtering, behavioral detection, human approval, and traditional security controls all need to work together. AI security will not be solved by one guardrail. It will require a defense-in-depth.</p></li><li><p><strong>Abstraction</strong> helps defenders manage complexity. AI systems are quickly becoming chains of models, tools, prompts, memory stores, retrieval systems, APIs, and user interfaces. Without clean abstractions, defenders will struggle to understand where trust boundaries exist and where security decisions are actually being made.</p></li><li><p><strong>Data hiding</strong> becomes more important as AI systems consume more context. Sensitive data should not be exposed to a model or agent simply because it exists somewhere in the environment. Data should be filtered, scoped, redacted, tokenized, or withheld when it is not necessary for the task. The more context we provide to autonomous systems, the more intentional we need to be about what they are allowed to see.</p></li><li><p><strong>Modularity</strong> enables organizations to contain failures and improve systems over time. If every AI workflow is tightly coupled to every other part of the business, securing it becomes nearly impossible. Smaller, well-defined components are easier to test, monitor, replace, and restrict.</p></li><li><p><strong>Simplicity and minimization</strong> may be the most underrated principles in AI security. The more tools an agent has, the more ways it can fail. The more permissions it holds, the greater the blast radius. The more context it receives, the more opportunities exist for leakage, manipulation, or misuse. Secure AI systems will not simply be the most capable systems. They will be the systems with the least unnecessary complexity.</p></li></ol><p>This is the point I keep coming back to: AI does not replace cybersecurity fundamentals. It punishes organizations that fail to implement them.</p><h2>Beyond Reactive Defense</h2><p>First principles give us the foundation, but AI also forces us to think more seriously about the economics of defense.</p><p>For most of cybersecurity history, defenders have operated in a difficult asymmetry. Attackers can reuse infrastructure, tooling, research, and techniques across many targets. Defenders have to protect their specific environment, business logic, legacy systems, and operational constraints.</p><p>AI has the potential to make that asymmetry <em>worse</em>.</p><p>If autonomous agents can conduct reconnaissance, summarize targets, generate payloads, test exploitability, and adapt based on results, then adversaries may be able to scale certain parts of cyber operations with less human effort. Even if AI does not produce perfect attacks, it can still increase volume, speed, and persistence. That alone matters.</p><p>This is why I think cybersecurity has to evolve beyond purely reactive defense. By active defense, I do not mean reckless retaliation or unauthorized access to adversary infrastructure. I am not talking about hack back. I am talking about defensive actions taken inside authorized environments to detect, deceive, delay, degrade, and increase the cost of malicious activity.</p><p>That distinction matters.</p><p>The future of active defense in the AI era should not be about defenders becoming attackers. It should be about defenders designing environments that are harder for autonomous adversaries to reason through, move through, and exploit at scale.</p><h2>Economic Friction</h2><p>One way to think about this is in terms of <strong>economic friction</strong>.</p><p>Traditional <a href="https://en.wikipedia.org/wiki/Economies_of_scale">economies of scale</a> teach that as production increases, the cost per unit can decrease because fixed costs are spread across a larger volume. This is part of why AI is attractive to both businesses and adversaries. If an attacker believes AI can reduce the human effort required for reconnaissance, targeting, exploit development, or phishing, then AI becomes a way to pursue malicious scale.</p><p>Defenders should respond by targeting that assumption.</p><p>If AI-enabled attacks depend on tokens, tool calls, context windows, model reasoning, browser automation, API usage, and agentic workflows, then defenders can design controls that make malicious automation more expensive, less reliable, and less efficient.</p><p>This is not just about blocking attacks. It is about degrading the economics of the attack.</p><p>A defender may not always be able to prevent an autonomous agent from scanning an exposed surface, but they may be able to identify it, slow it down, feed it low-value paths, force unnecessary reasoning steps, trigger additional tool calls, or route it into monitored deception resources. In other words, the defender can impose cost.</p><p>That cost can take different forms. It can be the token cost. It can be time. It can be uncertain. It can be false confidence. It can be a wasted tool execution. It can be a forced human review on the attacker&#8217;s side. It can be telemetry that exposes the agent&#8217;s behavior before it reaches anything sensitive.</p><p>This is where deception becomes very interesting.</p><h2>Deception Against Autonomous Agents</h2><p>AI agents are not humans, but they still make decisions based on context. They read pages, interpret instructions, follow links, inspect artifacts, summarize data, invoke tools, and decide what to do next. That means the environment itself can influence their behavior.</p><p>We already understand this concept with humans. Honeypots, canary tokens, decoy credentials, and deception environments exist because attackers make decisions based on what they see. The AI version of this idea is that autonomous agents can also be lured, redirected, slowed, or fingerprinted through the information they consume.</p><p>This is where techniques like <a href="https://atlas.mitre.org/techniques/AML.T0100">AI Agent Clickbaiting</a> (AML.T0100) become relevant. If an agent can be manipulated through content, interface cues, instructions, or task framing, then defenders can create canary-style resources designed specifically for AI-operated reconnaissance. These could be fake exposed panels, synthetic documentation, monitored API endpoints, decoy credentials, prompt-injection canaries, or high-token dead ends that cause malicious agents to waste resources while generating useful telemetry for defenders.</p><p>The goal is not to create chaos. The goal is controlled defensive friction.</p><p>A malicious autonomous agent conducting reconnaissance should not experience the environment as clean, cheap, and easy to reason through. It should encounter boundaries, uncertainty, deceptive paths, scoped access, monitored resources, and expensive decision points.</p><p>This is especially relevant when we look at AI-orchestrated campaigns. In <a href="https://www.anthropic.com/news/disrupting-AI-espionage">Anthropic&#8217;s report on the AI-orchestrated cyber espionage campaign they disrupted</a>, the actor used Claude&#8217;s agentic capabilities across phases like reconnaissance, vulnerability discovery, credential harvesting, and data collection. That is the kind of activity defenders need to study closely. If AI agents are going to be used to automate parts of the intrusion lifecycle, then defenders need to understand how those agents perceive environments, how they make decisions, and where they can be safely disrupted.</p><p>Cybersecurity researchers at <span class="mention-wrap" data-attrs="{&quot;name&quot;:&quot;Tracebit&quot;,&quot;id&quot;:143814041,&quot;type&quot;:&quot;user&quot;,&quot;url&quot;:null,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/4b3fc25c-afaa-44fd-9c1b-3494228fc185_1024x1024.png&quot;,&quot;uuid&quot;:&quot;5cdc9ea8-4669-40f8-bda9-5c4f7b2f21c8&quot;}" data-component-name="MentionToDOM"></span> also recently released a publication on the concept of <strong><a href="https://agentic.tracebit.com/context-bombs/">Context Bombs</a></strong>,<span> a defensive technique designed specifically for autonomous AI attackers.</span></p><div class="embedded-post-wrap" data-attrs="{&quot;id&quot;:206821863,&quot;url&quot;:&quot;https://newsletter.tracebit.com/p/context-bombs-stopping-ai-attackers&quot;,&quot;publication_id&quot;:7259408,&quot;embedding_publication_id&quot;:null,&quot;publication_name&quot;:&quot;Tracebit Dispatches&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!FLdk!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc78965ed-2660-4920-ae14-f687d5b9f57d_1280x1280.png&quot;,&quot;title&quot;:&quot;Context bombs: Canaries that stop AI attackers&quot;,&quot;truncated_body_text&quot;:&quot;Frontier AI agents can seize full admin of a cloud account in minutes - a critical action within 14 minutes on average, leaving defenders barely an 8-minute window to respond. When attacks move that fast, detection alone isn&#8217;t enough.&quot;,&quot;date&quot;:&quot;2026-07-13T16:46:41.782Z&quot;,&quot;like_count&quot;:3,&quot;comment_count&quot;:0,&quot;bylines&quot;:[{&quot;id&quot;:143814041,&quot;name&quot;:&quot;Tracebit&quot;,&quot;handle&quot;:&quot;tracebit&quot;,&quot;previous_name&quot;:&quot;A Name&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/4b3fc25c-afaa-44fd-9c1b-3494228fc185_1024x1024.png&quot;,&quot;bio&quot;:&quot;Notes from the team building Tracebit, the answer to assume breach - canaries, deception, detection, and what we're learning along the way.&quot;,&quot;profile_set_up_at&quot;:&quot;2023-10-31T09:36:32.892Z&quot;,&quot;reader_installed_at&quot;:null,&quot;publicationUsers&quot;:[{&quot;id&quot;:7408172,&quot;user_id&quot;:143814041,&quot;publication_id&quot;:7259408,&quot;role&quot;:&quot;admin&quot;,&quot;public&quot;:true,&quot;is_primary&quot;:true,&quot;publication&quot;:{&quot;id&quot;:7259408,&quot;name&quot;:&quot;Tracebit Dispatches&quot;,&quot;subdomain&quot;:&quot;tracebit&quot;,&quot;custom_domain&quot;:&quot;newsletter.tracebit.com&quot;,&quot;custom_domain_optional&quot;:false,&quot;hero_text&quot;:&quot;Notes from the team building Tracebit, the answer to assume breach - canaries, deception, detection, and what we're learning along the way.&quot;,&quot;logo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/c78965ed-2660-4920-ae14-f687d5b9f57d_1280x1280.png&quot;,&quot;author_id&quot;:143814041,&quot;primary_user_id&quot;:143814041,&quot;theme_var_background_pop&quot;:&quot;#FF6719&quot;,&quot;created_at&quot;:&quot;2025-12-14T11:02:06.758Z&quot;,&quot;email_from_name&quot;:&quot;Tracebit Dispatches&quot;,&quot;copyright&quot;:&quot;Tracebit Limited&quot;,&quot;founding_plan_name&quot;:null,&quot;community_enabled&quot;:true,&quot;invite_only&quot;:false,&quot;payments_state&quot;:&quot;disabled&quot;,&quot;language&quot;:null,&quot;explicit&quot;:false,&quot;homepage_type&quot;:&quot;newspaper&quot;,&quot;is_personal_mode&quot;:false,&quot;logo_url_wide&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/72bce7b4-2d89-449d-8fcf-79e2a47ebab6_2690x640.png&quot;}}],&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null,&quot;status&quot;:{&quot;bestsellerTier&quot;:null,&quot;subscriberTier&quot;:1,&quot;leaderboard&quot;:null,&quot;vip&quot;:false,&quot;badge&quot;:{&quot;type&quot;:&quot;subscriber&quot;,&quot;tier&quot;:1,&quot;accent_colors&quot;:null},&quot;subscriber&quot;:null}}],&quot;utm_campaign&quot;:null,&quot;belowTheFold&quot;:true,&quot;type&quot;:&quot;newsletter&quot;,&quot;language&quot;:&quot;en&quot;,&quot;source&quot;:null}" data-component-name="EmbeddedPostToDOM"><a class="embedded-post" native="true" href="https://newsletter.tracebit.com/p/context-bombs-stopping-ai-attackers?utm_source=substack&amp;utm_campaign=post_embed&amp;utm_medium=web"><div class="embedded-post-header"><img class="embedded-post-publication-logo" src="https://substackcdn.com/image/fetch/$s_!FLdk!,w_56,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc78965ed-2660-4920-ae14-f687d5b9f57d_1280x1280.png" loading="lazy"><span class="embedded-post-publication-name">Tracebit Dispatches</span></div><div class="embedded-post-title-wrapper"><div class="embedded-post-title">Context bombs: Canaries that stop AI attackers</div></div><div class="embedded-post-body">Frontier AI agents can seize full admin of a cloud account in minutes - a critical action within 14 minutes on average, leaving defenders barely an 8-minute window to respond. When attacks move that fast, detection alone isn&#8217;t enough&#8230;</div><div class="embedded-post-cta-wrapper"><span class="embedded-post-cta">Read more</span></div><div class="embedded-post-meta">4 months ago &#183; 3 likes &#183; Tracebit</div></a></div><p><br><span>The idea is simple but clever: plant carefully crafted text inside canary secrets, environment variables, or other artifacts that an AI agent is likely to read. Instead of simply detecting the attacker, the text is designed to trigger the model&#8217;s own safety guardrails, causing it to refuse to continue the attack.</span></p><p>That is the next layer of AI defense.</p><p>Not just protecting AI systems from attackers, but protecting our environments from attacker-controlled AI systems.</p><h2>Final Thoughts</h2><p>Claude Mythos does not prove that cybersecurity is ending. It proves that the timeline is shrinking.</p><p>The industry should take that seriously, but panic is not a strategy. Neither is pretending that every AI development requires a completely new security philosophy. Most of what we need still comes back to fundamentals: isolate systems, reduce unnecessary access, protect sensitive data, minimize attack surface, layer controls, and design systems whose failure modes are understood.</p><p>At the same time, AI does create a new defensive challenge. If adversaries use AI to scale cyber operations, then defenders have to think beyond detection and response. We have to think about cost. We have to think about friction. We have to think about how to make malicious automation less efficient.</p><p>That is the real shift.</p><p>AI does not replace cybersecurity fundamentals. It makes weak fundamentals more expensive. And for defenders, the opportunity is not just to use AI faster than attackers. It is to build environments where attacker-controlled AI systems are constrained, misled, slowed down, and forced to pay a higher price for every step they take.</p><div><hr></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Cyberwox Unplugged! This post is public, so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/the-unspoken-truth-about-claude-mythos?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h1>Interested in sponsoring Cyberwox?</h1><p style="text-align: center;">Sponsoring Cyberwox helps me continue creating practical cybersecurity education, labs, and industry analysis while connecting your brand with a trusted multi-platform audience of 120,000+ cybersecurity practitioners, engineers, students, founders, and technology leaders across the global cyber community on our YouTube, LinkedIn, X, Substack, and Discord &#127758;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/sponsorships&quot;,&quot;text&quot;:&quot;Learn More Here &#128640;&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/sponsorships"><span>Learn More Here &#128640;</span></a></p><div><hr></div><h1>Until Next Time</h1><p>That&#8217;s it for this one.</p><p>As always, keep learning, keep building, and keep thinking deeply about the systems we&#8217;re trusted to defend.</p><p>See you in the next one.</p><p>~ Day &#128153;</p>]]></content:encoded></item><item><title><![CDATA[Are Humans Really the Weakest Link?]]></title><description><![CDATA[My attempt at dispelling this notorious rhetoric, and an introduction to human-centered security.]]></description><link>https://www.cyberwoxunplugged.com/p/are-humans-really-the-weakest-link</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/are-humans-really-the-weakest-link</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Fri, 24 Apr 2026 12:03:49 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/25e150d6-b897-4fee-a56d-c50d823a50d9_1728x910.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>For as long as cybersecurity has existed, we&#8217;ve repeated one line like gospel:</p><blockquote><p><strong>&#8220;Humans are the weakest link.&#8221;</strong></p></blockquote><p>We&#8217;ve even made cybersecurity <a href="https://www.alertlogic.com/blog/why-humans-weakest-link-cybersecurity/">marketing</a> and product playbooks just to fit this rhetoric.</p><p>It&#8217;s said with a mix of conviction, some frustration, and resignation, as if the problem begins and ends with the user who clicked the phishing email or reused their password.</p><p>But lately, I&#8217;ve been rethinking that phrase, because maybe the problem isn&#8217;t the people.</p><p>Maybe it&#8217;s the way we design for them.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!iF0v!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!iF0v!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 424w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 848w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1272w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png" width="1456" height="570" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/ba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:570,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:188886,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:&quot;&quot;,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/159067704?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F913f1923-04a0-4fe6-afb6-5e0fca6d78b1_2500x2500.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!iF0v!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 424w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 848w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1272w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1456w" sizes="auto, 100vw" loading="lazy" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Join a vibrant cybersecurity community of over 7000 people who are constantly engaging in conversations and supporting one another, covering topics from cybersecurity and college to certifications, resume assistance, and various non-professional interests like reading, fitness, finance, anime, and other exciting subjects.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://discord.gg/cyberwoxacademy&quot;,&quot;text&quot;:&quot;Join Us!&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://discord.gg/cyberwoxacademy"><span>Join Us!</span></a></p><div><hr></div><h1><strong>A Flawed Premise</strong></h1><p>I&#8217;ve been reading (and have since paused) Don Norman&#8217;s <strong>The Design of Everyday Things</strong>. This is one of the most influential books on human-centered design.</p><p>Norman shares a story about investigating the <a href="https://en.wikipedia.org/wiki/Three_Mile_Island_accident">Three Mile Island nuclear accident</a>. The operators were blamed for &#8220;human error,&#8221; but as his committee later found, the real failure was design.</p><p>The control panels were so poorly laid out that it was inevitable that the wrong actions would be taken.</p><p>That story struck me hard because the same logic applies to cybersecurity. Hence, the reason why I&#8217;m writing this.</p><p>When we blame users for being &#8220;the weakest link,&#8221; what we&#8217;re really saying is: </p><blockquote><p><strong>We designed a system that expected humans to behave perfectly&#8230;and they didn&#8217;t.</strong></p></blockquote><div><hr></div><h1><strong>What Human-Centered Design Teaches Us</strong></h1><p>Norman&#8217;s philosophy is simple yet radical:</p><div class="pullquote"><p><strong>&#8220;It is the duty of machines and those who design them to understand people. It is not our duty to understand the arbitrary, meaningless dictates of machines.&#8221;</strong></p></div><p>Human-centered design starts from <strong>understanding humans</strong>.</p><p>It&#8217;s the belief that systems should be built around people, their capabilities, limitations, and behavior, not the other way around.</p><p>Now imagine applying that same principle to cybersecurity.</p><p>What if security were an <strong>enabler</strong> of trust, confidence, and resilience?</p><div><hr></div><h1>The Essence of Security</h1><p>I&#8217;ve been obsessed with word etymology recently and decided to find out the etymology of the word &#8220;security&#8221;.</p><p>Per <a href="https://www.etymonline.com/word/security">etymonline</a> (as recommended by Gemini), the word "security" originates from the Latin <em><strong>s&#275;c&#363;rit&#257;s</strong></em>, meaning <strong>freedom from care,</strong> apprehension, or danger, derived from <em><strong>s&#275;c&#363;rus</strong></em> ("safe" or "without care"). </p><p>It combines <em>se-</em> (without) and <em>cura</em> (care/concern), emerging into Middle English as <em>securite</em> in the early 15th century to describe a state of safety.</p><p>So, what this means is that security, at its core, is supposed to mean freedom from care. Freedom from anxiety. A state where you&#8217;re not constantly thinking about what could go wrong.</p><p>But that&#8217;s not what most people experience.</p><p>What they experience is friction. They experience getting locked out of their own accounts. They experience clicking through prompts they don&#8217;t fully understand. They experience being told to &#8220;be more careful&#8221; in systems that never really help them be.</p><p>Somewhere along the way, security stopped feeling like safety and started feeling like responsibility. And we handed that responsibility to the user.</p><p>That&#8217;s the part I keep coming back to, but that&#8217;s a letter for another day.</p><p><strong>What would it look like if we actually took that definition of security seriously?</strong></p><div><hr></div><h1><strong>Human-Centered Security</strong></h1><p>If security is supposed to feel like freedom from care, then what we build shouldn&#8217;t feel like something users have to constantly fight through. It should feel like something that quietly supports them.</p><p>That&#8217;s where I think human-centered security comes in.</p><p>Human-centered security, at least to me, isn&#8217;t about adding more shiny controls or features. It&#8217;s about rethinking security as an experience.</p><p>Reality shows that a well-designed system doesn&#8217;t rely on people memorizing policies or sitting through another awareness training session. It makes the right action obvious through its design. The experience aligns with what security is actually supposed to feel like: a sense of safety, not constant friction.</p><p>That distinction&nbsp;<strong>matters</strong>&nbsp;because if we over-index on the&nbsp;<em><strong>feeling</strong></em>&nbsp;of security without grounding it in reality, we end up with something worse than insecurity, a false sense of security.</p><p>And we know how dangerous that can be.</p><p>The better approach is simpler, but harder to execute. It&#8217;s the same principle you see everywhere else in good design, where you don&#8217;t need a manual to use a well-designed door. You don&#8217;t need a checklist to move through a clean interface. The design communicates intent. It guides behavior and meets you where you are.</p><p>Security should be doing the same thing.</p><p>Which means the questions start to change.</p><p>Not &#8220;how do we make users comply,&#8221; but how do users naturally understand what&#8217;s secure? How do we communicate risk in a way that actually lands, without overwhelming them? <strong>How do we make the secure choice the path of least resistance instead of the most difficult one</strong>? And how do we make security feel like an enabler instead of something that&#8217;s constantly in the way?</p><p>These questions are important because the reality is, people are going to make mistakes. That&#8217;s not a flaw in the system. That <em>is</em> the system.</p><p>Good design anticipates that. It doesn&#8217;t pretend it won&#8217;t happen. It builds around it.</p><p>In a security context, that means assuming an error will occur and designing for it anyway. It means putting guardrails in place that prevent small mistakes from turning into major incidents. It means creating feedback loops that actually teach and guide rather than punish people after the fact.</p><p>Once you start thinking about it this way, the &#8220;weakest link&#8221; framing starts to fall apart.</p><p>We start to undo this quiet assumption that&#8217;s shaped security for years. This bad assumption that the relationship between humans and security has to be adversarial, or that the user is the problem to be controlled.</p><p>It doesn&#8217;t have to be that way.</p><p>When you design with people in mind, the relationship shifts and becomes collaborative. The system supports the human, and in turn, the human strengthens the system.</p><div><hr></div><h1><strong>The Real Weak Link</strong></h1><p>Every incident I&#8217;ve ever investigated has reinforced a humbling truth:</p><blockquote><p>The system&nbsp;<strong>always</strong>&nbsp;works exactly as designed; it was just used for a different purpose or via a different mechanism than intended.</p></blockquote><p>This is the part we tend to move past too quickly because, when you really sit with it, much of what we label &#8220;human failure&#8221; doesn&#8217;t actually start with the human. It starts with the environment we placed them in.</p><p>If a developer can&#8217;t realistically follow an IAM policy because it&#8217;s too complex to reason about in the flow of their work, that&#8217;s not a training gap. If a phishing simulation leaves employees feeling embarrassed instead of better equipped the next time around, that&#8217;s not awareness. If a password rotation policy leads to credentials being written down and hidden under keyboards, that&#8217;s not defiance.</p><p>Those are signals.</p><p>Signals that the system, as designed, is asking people to operate in ways that don&#8217;t align with how they actually <strong>think</strong>, <strong>work</strong>, and <strong>make decisions.</strong></p><p>And this is where I think security always loses the plot.</p><p>We&#8217;ve spent years optimizing for technical correctness, tighter controls, more coverage, and logical completeness. But in doing so, we&#8217;ve overlooked something, the fundamental fact that humans don&#8217;t operate on logic alone.</p><p>They operate on trust, intuition, emotion, and habit.</p><p>And when those realities collide with systems that weren&#8217;t designed with them in mind, something has to give.</p><p>Most of the time, it&#8217;s the human who gets blamed.</p><p><strong>But if we&#8217;re being honest, the system did exactly what it was built to do.</strong></p><p>And until security starts accounting for that, we&#8217;ll keep building mechanisms that look strong on paper but end up working against the very people they&#8217;re supposed to protect.</p><div><hr></div><h1>AI, for humanity?</h1><p>I believe this is where AI starts to become interesting and useful in a very different way. Not just as a tool for detection or automation, but as a bridge between systems and people.</p><p>For the first time, we have systems that can adapt more closely to how humans think, rather than forcing humans to adapt to rigid machine logic.</p><p>And if that&#8217;s the direction things are moving, then the role of the security professional has to evolve with it.</p><p>It&#8217;s no longer enough to just understand systems. You have to understand people, their thought processes, how they make decisions, and how trust is formed and broken. The Social Engineering Community already has a head start on this.</p><p>As AI continues to accelerate the technical side of security, more of the differentiation will come from understanding the human side. Psychology, behavior, communication, and all areas that security has historically treated as secondary will become core to how effective systems are designed.</p><div><hr></div><h1><strong>Rethinking Security Through Human-Centered Design</strong></h1><p>Human-centered design doesn&#8217;t excuse mistakes or assign blame to humans; it approaches design with them in mind.</p><p>It utilizes iteration, observation, and empathy to design systems that adapt to human behavior, rather than requiring humans to adapt to systems.</p><p>So maybe the next evolution of cybersecurity isn&#8217;t just about AI-driven detections or zero-trust architectures.</p><p>Perhaps it&#8217;s also about human-centered security, which builds systems designed to work with people, not against them.</p><blockquote><p>The real weakest link isn&#8217;t the human. It&#8217;s our failure to design for humans.</p></blockquote><div><hr></div><p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/are-humans-really-the-weakest-link?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/p/are-humans-really-the-weakest-link?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[Cybersecurity Engineering Career Lessons You Won’t Get in Certification Courses]]></title><description><![CDATA[Lessons in Security Engineering from Jason Chan&#8217;s High-Velocity Framework (and My Own Battles in the Field).]]></description><link>https://www.cyberwoxunplugged.com/p/cybersecurity-engineering-career</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/cybersecurity-engineering-career</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Fri, 21 Nov 2025 14:49:21 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/d1ad9f07-e5c4-453e-ac28-ae20d91e521f_1440x810.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A few months ago, I read <a href="https://www.linkedin.com/in/jasonbchan/">Jason Chan&#8217;s</a> feature in the TL;DR sec newsletter titled&nbsp;<em><a href="https://tldrsec.com/p/security-for-high-velocity-engineering">"Security for High-Velocity Engineering</a></em>." If you&#8217;ve ever built security tooling or led engineering efforts under pressure, the piece might feel less like a framework and more like a mirror. </p><p>It&#8217;s a strategic blueprint from someone who helped Netflix scale security without slowing the company&#8217;s engineering engine&#8212;a balance that&#8217;s notoriously hard to get right.</p><p>It got me thinking about my own path as a Security Engineer and the various domains I&#8217;ve worked in. </p><p>What stuck with me wasn&#8217;t just Jason&#8217;s structured layers of <strong>context, strategy, and execution</strong>, but how those principles have shown up in my work again and again.</p><p>Sometimes explicitly. Sometimes, without realizing it until later.</p><p>So in this issue, I want to do two things:</p><ol><li><p>Walk you through a few pivotal moments in my security engineering career</p></li><li><p>Extract real, applicable lessons from each so that you can bring them into your own context</p></li></ol><p>This is not just &#8220;what I did.&#8221;</p><p> It&#8217;s &#8220;why it mattered, and what it could mean for you.&#8221;</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.cyberwoxunplugged.com/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!iF0v!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!iF0v!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 424w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 848w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1272w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png" width="1456" height="570" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/ba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:570,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:188886,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:&quot;&quot;,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/159067704?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F913f1923-04a0-4fe6-afb6-5e0fca6d78b1_2500x2500.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!iF0v!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 424w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 848w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1272w, https://substackcdn.com/image/fetch/$s_!iF0v!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba71e4f8-2d28-4fd6-9a78-c966708c46a6_2500x979.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Join a vibrant cybersecurity community of over 7,000 people who are constantly engaging in conversations and supporting one another, covering topics from cybersecurity and college to certifications, resume assistance, and various non-professional interests like fitness, finance, anime, and other exciting subjects.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://discord.gg/cyberwoxacademy&quot;,&quot;text&quot;:&quot;Join Us!&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://discord.gg/cyberwoxacademy"><span>Join Us!</span></a></p><div><hr></div><p>Watch the full video breakdown below:</p><div id="youtube2-HlGuOdY7Y2I" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;HlGuOdY7Y2I&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/HlGuOdY7Y2I?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><div><hr></div><h1><strong>When Speed Is the Priority</strong></h1><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!jADY!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!jADY!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 424w, https://substackcdn.com/image/fetch/$s_!jADY!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 848w, https://substackcdn.com/image/fetch/$s_!jADY!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!jADY!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!jADY!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png" width="1024" height="1024" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1024,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1559843,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/179558051?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!jADY!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 424w, https://substackcdn.com/image/fetch/$s_!jADY!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 848w, https://substackcdn.com/image/fetch/$s_!jADY!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!jADY!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9a0679f0-5099-4339-82bc-9d522b6dece3_1024x1024.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Jason discusses how security teams must make room for velocity, <em>not hinder it</em>. </p><p>That means knowing when to optimize for &#8220;good enough right now&#8221; versus &#8220;perfect later.&#8221;</p><p>That lesson hit me hard during an active cloud campaign while I was a cloud threat detection engineer. </p><p>We were watching an attacker group compromise cloud environments at scale, deploying crypto miners using consistent IAM roles and resource naming patterns.</p><p>We had <strong>clear indicators</strong>, but no time for elegant detection modeling or layered behavioral <strong>TTP-based detections</strong>.</p><p>So I made the call to build and deploy an <strong>IOC-heavy detection</strong>. </p><p>The logic was sharp but narrow. It was very atomic in nature. </p><p>Honestly, it wasn&#8217;t what I&#8217;d want to ship under normal conditions. But it bought us time. </p><p><em>Visibility first. Accuracy later.</em></p><p><strong>What I learned (and you can apply):</strong></p><ul><li><p>There is a time and place for precision, but don&#8217;t let the perfect detection delay critical visibility.</p></li><li><p>Your first iteration (for an atomic detection) doesn&#8217;t have to scale. It has to inform.</p></li><li><p>Build something quickly, but tag it for review. Revisit it once the fire&#8217;s out.</p></li><li><p>Sometimes, shipping quickly is <em>the</em> safest thing to do.</p></li></ul><p>And this applies far beyond cloud detection. </p><p>Whether it&#8217;s building IAM policies, hardening containers, or writing security automation, sometimes velocity is the first layer of resilience.</p><div><hr></div><h1><strong>Build Once, Scale Forever</strong></h1><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!UYjK!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!UYjK!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 424w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 848w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!UYjK!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png" width="1024" height="1024" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/788120c3-af76-4e50-a315-801158f020c9_1024x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1024,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1670405,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/179558051?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!UYjK!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 424w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 848w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!UYjK!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F788120c3-af76-4e50-a315-801158f020c9_1024x1024.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Jason describes &#8220;strategy&#8221; as choosing high-leverage work that scales your impact.</p><p>When I was tasked with building detections for Google Cloud (GCP) as a cloud threat detection engineer, I could have started cranking out detections service by service.</p><p>But I knew that wouldn&#8217;t scale, and frankly, I didn&#8217;t fully understand GCP yet. Instead, I stepped back and developed an understanding of the cloud provider and a <strong>cloud</strong> <strong>threat modeling framework</strong>.</p><p>I grouped GCP services into high-level domains - Compute, storage, IAM, databases, and then used those abstractions to understand attack surfaces.</p><p>From there, I could drill down into the specifics: </p><ul><li><p>What does identity misuse look like across IAM and storage? </p></li><li><p>How does lateral movement manifest in GCP&#8217;s managed services?</p></li><li><p>How are GCP services abused differently or similarly to other Cloud services?</p></li></ul><p><strong>What I learned (and you can apply):</strong></p><ul><li><p>Before building tooling or detections, have a mental model of the domain. It doesn&#8217;t have to be perfect&#8212;it just has to make complexity navigable.</p></li><li><p>Focus on identifying common patterns across services rather than isolated exceptions. This is where reliable detection logic starts.</p></li><li><p>If you&#8217;re onboarding into a new cloud provider, threat modeling isn&#8217;t a &#8220;nice to have&#8221;&#8212;it&#8217;s your best shot at building a reusable, scalable detection strategy.</p></li><li><p>Documentation is a weapon. When you build mental models, write them down. It&#8217;ll save the next person weeks of confusion&#8212;and save you from repeating work six months later.</p></li></ul><blockquote><p>If you&#8217;re early in your career, this is gold: <strong>don&#8217;t just solve the problem, try to solve the class of problems.</strong></p></blockquote><div><hr></div><h1><strong>Why Saying &#8220;No&#8221; is Strategic</strong></h1><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!s2fk!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!s2fk!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!s2fk!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png" width="1024" height="1536" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1536,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:3168081,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/179558051?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!s2fk!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!s2fk!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa32a7a88-7b24-43b5-92fd-506cbd41206e_1024x1536.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>One of the sharpest lines from Jason&#8217;s piece comes from Netflix&#8217;s former CEO, Reed Hastings: </p><blockquote><p>&#8220;Strategy is about what you don&#8217;t do.&#8221;</p></blockquote><p>In my current role, I work on differentiated threat intelligence for specific business units. </p><p>One thing I&#8217;ve learned the hard way is that <strong>not all intel is valuable</strong>, even if it&#8217;s technically correct or urgent elsewhere.</p><p>The internet is full of noise: threat feeds, CVEs, indicators, and intel reports. But my responsibility is to ask, <em>&#8220;Is this relevant to us?&#8221;</em> If not, I let it go&#8212;even if it seems scary or hyped.</p><p><strong>What I learned (and you can apply):</strong></p><ul><li><p>Intelligence without context is just a distraction.</p></li><li><p>Learn to filter based on <em>business impact</em> and <em>sector alignment</em>, not just raw severity.</p></li><li><p>It&#8217;s okay to ignore the noise&#8212;especially if you&#8217;re building a detection or IR strategy. Not every problem is <strong>your</strong> problem.</p></li><li><p>Write down your priorities or &#8220;filter criteria.&#8221; That makes your decisions repeatable and teachable.</p></li></ul><p>This applies equally across the SecOps team: don&#8217;t get caught writing detections or chasing rabbit holes just because something trended on Twitter.</p><div><hr></div><h1><strong>Institutional Memory is Security Engineering&#8217;s Secret Weapon</strong></h1><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!CAFu!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!CAFu!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!CAFu!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png" width="1024" height="1536" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1536,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:3567317,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/179558051?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!CAFu!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!CAFu!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F55fb27ec-422b-4438-9dcc-dc368cde0c46_1024x1536.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Chan stresses that true scalability requires building systems people can use long after you&#8217;re gone. </p><p>That lesson came alive for me recently.</p><p>There were two major internal systems my team was responsible for&#8212;critical to detection, response, and threat intelligence&#8212;but they were barely understood. </p><p>No central knowledge. No reusable playbooks.</p><p>So, I took it on: I studied the systems, documented their behaviors and <em>our </em>failure points in our interactions with them, hosted a team lunch-and-learn, and built an internal wiki that others could use.</p><p><strong>What I learned (and you can apply):</strong></p><ul><li><p>Documentation isn&#8217;t a chore&#8212;it&#8217;s a force multiplier.</p></li><li><p>If your knowledge lives only in your head, your impact dies when you take PTO.</p></li><li><p>Teach others how to operate what you&#8217;ve built. That&#8217;s when you know you&#8217;ve succeeded.</p></li><li><p>Institutional knowledge is a competitive advantage&#8212;don&#8217;t let it go to waste.</p></li></ul><p>If you&#8217;re early in your career, this is one of the fastest ways to stand out: </p><blockquote><p><strong>Be the person who makes the unclear clear.</strong></p></blockquote><div><hr></div><h1>Final Thoughts</h1><p>Jason Chan&#8217;s framework gave me words for things I was already doing&#8212;but it also challenged me to be more intentional about them. </p><p>His call to build guardrails, not gates&#8230; to prioritize reuse over heroics&#8230; to measure and iterate... all of it resonates more deeply the longer I&#8217;ve been in this space.</p><p>So here&#8217;s my version of his model in practice:</p><ul><li><p><strong>Context</strong>: Understand what your org <em>actually</em> needs, not what LinkedIn or Twitter&#8217;s yelling about.</p></li><li><p><strong>Strategy</strong>: Invest in models, processes, and documentation that outlive you.</p></li><li><p><strong>Execution</strong>: Move fast when needed&#8212;but reflect hard and revise often.</p></li><li><p><strong>Measurement</strong>: Let the data from real incidents teach you how to improve.</p></li></ul><p>If you&#8217;re a security engineer, a detection engineer, a threat hunter, or even just starting, this is your reminder that <em>speed and security don&#8217;t have to be enemies</em>. </p><p>They can be collaborators if you give them structure.</p><p>Keep building paved roads. </p><p>And when you do, leave signs behind for the next engineer.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.cyberwoxunplugged.com/p/cybersecurity-engineering-career?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://www.cyberwoxunplugged.com/p/cybersecurity-engineering-career?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p>]]></content:encoded></item><item><title><![CDATA[The 5 Cybersecurity Engineer Archetypes (and Why You Should Know Yours)]]></title><description><![CDATA[whoami?]]></description><link>https://www.cyberwoxunplugged.com/p/the-5-cybersecurity-engineer-archetypes</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-5-cybersecurity-engineer-archetypes</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Sat, 15 Nov 2025 15:27:21 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/f9a7bf81-50a6-4663-9db2-b051090cc3f7_1440x810.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Every security engineer, regardless of experience level, eventually reaches a point where they pause and ask:</p><p><strong>What kind of engineer am I?</strong></p><p>Not just what tools you use. Not just what your current title says. </p><p>But how do you show up? </p><p>How do you solve problems? </p><p>How do you instinctively approach complexity?</p><p>I&#8217;ve seen this question (and its answer) surface over a&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/the-5-cybersecurity-engineer-archetypes">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Operational Cost of Cybersecurity]]></title><description><![CDATA[The Hidden Cost of optimizing for &#8220;More&#8221; instead of &#8220;Better&#8221;.]]></description><link>https://www.cyberwoxunplugged.com/p/the-operational-cost-of-cybersecurity</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/the-operational-cost-of-cybersecurity</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Thu, 06 Nov 2025 17:18:29 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!R7vL!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2d2a85a7-6df8-4f01-ade1-1ade8caa01ca_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In finance, operational expenses, or OpEx, is the money it takes to keep something running.</p><p>Most of the time, you don&#8217;t just buy an asset and walk away; you continue to pay to maintain it. Take an investment property, for example. You pay for staff, maintenance, utilities, and software to sustain operations.</p><p>Cybersecurity is no different.</p><p>Every new detecti&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/the-operational-cost-of-cybersecurity">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Don't Lose Your Edge]]></title><description><![CDATA[What Returning to Nigeria After 9 Years Taught Me.]]></description><link>https://www.cyberwoxunplugged.com/p/dont-lose-your-edge</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/dont-lose-your-edge</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Thu, 16 Oct 2025 14:31:20 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/8322c99b-3d62-44ff-ac45-a4814ee1e605_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A few weeks ago, I came back from my first trip to Nigeria in 9 years.</p><p><strong>Nine years.</strong></p><p>Nine years of learning, grinding, building, and changing in ways I didn&#8217;t fully understand until I went back.</p><p>And somewhere between the chaos of Abuja&#8217;s traffic and the peace of being home again&#8230; I realized something.</p><p>Man&#8230;what an advantage. But also, what a paradox.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!DrMo!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!DrMo!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 424w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 848w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!DrMo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg" width="768" height="677" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/d389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:677,&quot;width&quot;:768,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:168642,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.cyberwoxunplugged.com/i/173943224?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b3afc3c-1725-4c2e-bf2e-ff9111898dbe_768x1024.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!DrMo!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 424w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 848w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!DrMo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd389bf77-bbd6-419a-8966-dd279cabe8b2_768x677.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption"><em>Walking on&#8230;</em></figcaption></figure></div>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/dont-lose-your-edge">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[HashiConf 2025 Recap - The Future of Cloud, AI, and Security]]></title><description><![CDATA[Expert insights from conversations around agentic infrastructure, GPU efficiency, and security that's actually shifting left.]]></description><link>https://www.cyberwoxunplugged.com/p/hashiconf-2025-recap-expert-insights</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/hashiconf-2025-recap-expert-insights</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Fri, 10 Oct 2025 16:51:24 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/ac8ef5a6-a1f6-4df8-a23d-d4c8f6c2662a_1440x810.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Three days in San Francisco. Hundreds of engineers, architects, and builders. And one central theme: <strong>infrastructure is getting smarter</strong>.</p><p><a href="https://bit.ly/3JQfHJD">HashiConf 2025</a> marked a turning point for how we think about automation, visibility, and security in the AI age. The announcements appear to be puzzle pieces forming a bigger vision of what HashiCorp plans for the future&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/hashiconf-2025-recap-expert-insights">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Cybersecurity Career Mistakes Keeping You Stuck (and How to Fix Them)]]></title><description><![CDATA[Five common mistakes that derail aspiring cybersecurity professionals and how to avoid them before they kill your career progress.]]></description><link>https://www.cyberwoxunplugged.com/p/how-to-kill-your-cybersecurity-progress</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/how-to-kill-your-cybersecurity-progress</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Fri, 03 Oct 2025 16:02:48 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/b815ffdc-4858-43cd-8762-239dfb0acac0_1382x778.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Let&#8217;s be honest: the internet is full of endless tutorials, bootcamps, and videos that promise to &#8220;<strong>get you into cybersecurity.</strong>&#8221; However, if you&#8217;re not careful, you could inadvertently sabotage your career instead of accelerating it.</p><p>I&#8217;ve been in this space for five years now, working as a security engineer, mentoring hundreds of students, and teaching th&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/how-to-kill-your-cybersecurity-progress">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Cybersecurity 101: Series Recap & Next Steps]]></title><description><![CDATA[A CYBERWOX Unplugged Epilogue.]]></description><link>https://www.cyberwoxunplugged.com/p/cybersecurity-101-series-recap-and</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/cybersecurity-101-series-recap-and</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Mon, 29 Sep 2025 12:01:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!wWgx!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe24ce18c-ab38-4eb3-8f95-d9f742e547da_1024x969.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Over the past few weeks, we&#8217;ve walked through the whole arc of my <strong>two-hour live workshop</strong> on cybersecurity.</p><p>What started as a room of students, career-switchers, and curious professionals asking simple questions &#8212; <em>&#8220;What exactly is cybersecurity?&#8221;</em> &#8212; turned into a deep dive on why this field matters, how attackers operate, and how you can build a career in &#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/cybersecurity-101-series-recap-and">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Cybersecurity 101, Part III: Defense, Offense, and Career Pathways]]></title><description><![CDATA[How Blue and Red Teams operate, and the practical ways you can build a career in cybersecurity.]]></description><link>https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-iii-defense</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-iii-defense</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Mon, 22 Sep 2025 14:22:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!9CvF!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F19d47e85-25e2-4437-8a49-ace6b3a21e4f_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In Part II, we outlined the fundamentals: the CIA Triad, threats, vulnerabilities, risk, and the most common attacks, such as ransomware and insider threats. </p><p>That provided us with a map of&nbsp;<em>what we&#8217;re defending against.</em></p><p>Now let&#8217;s talk about the people who do the defending, and those who play offense to make defenses stronger. From there, we&#8217;ll dive into t&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-iii-defense">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Cybersecurity 101, Part II: Foundations & Attacks]]></title><description><![CDATA[The CIA Triad, threats, vulnerabilities, and the real attacks shaking organizations and individuals today.]]></description><link>https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-ii-foundations</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-ii-foundations</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Mon, 15 Sep 2025 12:01:58 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!dF61!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb465120e-37bc-4382-9137-cba6a4c754b6_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In Part I, we discussed why cybersecurity matters in 2025: how it impacts every aspect of our lives, how data has become the new gold, and how finances can be compromised with a single breach.</p><p>Now it&#8217;s time to get a little more structured.</p><p>When I teach cybersecurity, I always emphasize that we need <strong>foundations</strong>&#8212;concepts that simplify a massive, complex fie&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-ii-foundations">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Cybersecurity 101, Part I: Why It All Matters]]></title><description><![CDATA[The mission behind security, how it shapes your everyday life, and why data and money make you a target.]]></description><link>https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-i-why-it-all</link><guid isPermaLink="false">https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-i-why-it-all</guid><dc:creator><![CDATA[Day Johnson]]></dc:creator><pubDate>Mon, 08 Sep 2025 12:02:57 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!BNAM!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbbd8279e-bd16-4556-96ff-854e6685b80c_1024x1536.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If you&#8217;ve been following CYBERWOX Unplugged for a while, you know this newsletter is where I pull back the curtain. </p><p>Not quick hot takes. Not polished LinkedIn posts. </p><p>This is where I reflect, document, and share the more profound lessons that shape my career and this community.</p><p>Earlier this year, I had the opportunity to give a <strong>two-hour live workshop</strong> on t&#8230;</p>
      <p>
          <a href="https://www.cyberwoxunplugged.com/p/cybersecurity-101-part-i-why-it-all">
              Read more
          </a>
      </p>
   ]]></content:encoded></item></channel></rss>