<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/feed.xsl" media="all"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Eduardo Bustamante | Cybersecurity Student &amp; SOC Analyst</title><link>https://ebustamante.dev/</link><description>Recent content on Eduardo Bustamante | Cybersecurity Student &amp; SOC Analyst</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ebustamante.dev/" rel="self" type="application/rss+xml"/><item><title>Automating the portfolio site, link checking, spell checking, Lighthouse, and security audits</title><link>https://ebustamante.dev/writeups/portfolio-site-part-4/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://ebustamante.dev/writeups/portfolio-site-part-4/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The site already had one GitHub Actions workflow handling build and deploy with pinned commit hashes and Dependabot monitoring the workflow file weekly. That covered getting the site live but nothing was checking the quality of what went live. This covers five new workflows I added to automate that side of things, broken link detection, spell checking, performance auditing, security header monitoring, and keeping security.txt compliant automatically.&lt;/p&gt;
&lt;p&gt;The foundation was already there. Pinned commit hashes, branch protection, PR workflow. These five workflows build on top of that rather than replacing anything. The goal was catching different categories of problems automatically so I am not manually checking things that a workflow can handle.&lt;/p&gt;</description></item><item><title>Redesigning the portfolio site, layouts, animations, and a SOC dashboard</title><link>https://ebustamante.dev/writeups/portfolio-site-part-3/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://ebustamante.dev/writeups/portfolio-site-part-3/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The first two writeups covered building the site and adding features. This one covers tearing most of the visual layer apart and rebuilding it. The functionality was solid but the design felt generic. The terminal widget on the homepage was the most obvious problem since I had seen it on enough other portfolios that it stopped feeling like mine. Everything else had the same issue in smaller ways, pages with narrow content columns leaving half the screen empty, section headers that blended into the background, inner pages that all looked the same regardless of what they were for.&lt;/p&gt;</description></item><item><title>Expanding the portfolio site, security, features, and dev workflow</title><link>https://ebustamante.dev/writeups/portfolio-site-part-2/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://ebustamante.dev/writeups/portfolio-site-part-2/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;After the first writeup I had a working site with a GitHub Actions workflow, branch protection, and a PR based deployment process. That was a solid foundation but there was a lot left to build out. This covers everything I added after that, the security improvements, new pages, and the smaller details that make the site feel more complete.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="gpg-key-and-commit-signing"&gt;GPG key and commit signing&lt;/h2&gt;
&lt;p&gt;The first thing I tackled was setting up a GPG key for commit signing. Every commit I push to GitHub now shows a green Verified badge, which is a small but meaningful signal for a security professional. It means the commits are cryptographically tied to my key and anyone can verify they actually came from me.&lt;/p&gt;</description></item><item><title>Building my portfolio site with Hugo and GitHub Pages</title><link>https://ebustamante.dev/writeups/building-portfolio-site/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://ebustamante.dev/writeups/building-portfolio-site/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;I wanted a portfolio site that actually looked like something I built rather than something I dragged and dropped together. Most security portfolio sites look identical, a template with a headshot, a skills progress bar, and a contact form. I wanted something cleaner and more intentional, so I built mine from scratch using Hugo and deployed it on GitHub Pages with a custom domain.&lt;/p&gt;
&lt;p&gt;This writeup covers how I built it, the problems I ran into, and the security decisions I made along the way.&lt;/p&gt;</description></item></channel></rss>