<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>howtoit</title><link>https://howtoit.org/</link><description>Recent content on howtoit</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://howtoit.org/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a physical security monitoring system — and what it taught me about SOC work</title><link>https://howtoit.org/posts/unifi-surveillance-deployment/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/unifi-surveillance-deployment/</guid><description>How I designed and deployed an 11-camera 4K Unifi surveillance system with AI detection across a 40-room nonprofit facility — and why the lessons map directly to security operations.</description></item><item><title>TeamPCP published their own malware on GitHub — with an instruction manual</title><link>https://howtoit.org/posts/shai-hulud-open-source/</link><pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/shai-hulud-open-source/</guid><description>On May 12, TeamPCP posted the full source code for the Shai-Hulud worm to GitHub under the MIT license. Copycat actors were forking it within hours. Here&amp;#39;s what happened and what it means.</description></item><item><title>How a poisoned VS Code extension breached GitHub — and the npm attack that started it all</title><link>https://howtoit.org/posts/teampcp-supply-chain-attack/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/teampcp-supply-chain-attack/</guid><description>A breakdown of the TeamPCP supply chain campaign — from the TanStack npm compromise to the Nx VSCode extension that breached 3,800 GitHub internal repositories.</description></item><item><title>How I built this site for free (and how you can too)</title><link>https://howtoit.org/posts/about/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/about/</guid><description>A beginner-friendly guide to building a free cybersecurity blog using Hugo and GitHub Pages — no coding experience required.</description></item><item><title>How to actually make a strong password (and why most advice is wrong)</title><link>https://howtoit.org/posts/password-strength/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://howtoit.org/posts/password-strength/</guid><description>Most password advice focuses on complexity rules that don&amp;#39;t work. Here&amp;#39;s what actually makes a password hard to crack.</description></item><item><title>About Me</title><link>https://howtoit.org/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://howtoit.org/about/</guid><description>&lt;h2 id="hey-im-daniel"&gt;Hey, I&amp;rsquo;m Daniel&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m a cybersecurity analyst based in Winston-Salem, NC. I graduated from UNC Pembroke in December 2025 with a BS in Computer Science (Cybersecurity concentration) and hold CompTIA Security+ and CySA+ certifications.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m not a purely academic candidate. Last summer I interned at North Carolina&amp;rsquo;s Electric Cooperatives — a NERC CIP-regulated utility — where I worked on real security operations: monitoring SIEM alerts via CrowdStrike Falcon and ArcticWolf MDR, deploying Tenable Nessus across the fleet, co-authoring security policies, and responding to an active Tycoon2FA phishing campaign that targeted employees. That response involved pulling affected users from SIEM, reverse-engineering the obfuscated HTML payload, tracking how the attack evolved across multiple waves, and recommending full containment — laptop disposal, account deletion, and rotating the company&amp;rsquo;s email format to block the attacker from re-targeting.&lt;/p&gt;</description></item></channel></rss>