<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Ross</title><link>https://www.seanross.us/</link><description>Recent content on Sean Ross</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.seanross.us/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://www.seanross.us/about/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://www.seanross.us/about/</guid><description>&lt;p&gt;I&amp;rsquo;m a systems administrator at Marchex by day, an adjunct instructor at WSU Tech by evening, and someone who keeps reaching for the same tool to solve both: PowerShell.&lt;/p&gt;
&lt;h2 id="day-to-day"&gt;
 Day to day
 &lt;a class="heading-link" href="#day-to-day"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;PowerShell is my main tool. Most of my time goes into building production automation services around the Microsoft stack — module design with proper public/private boundaries, dependency injection, structured logging with correlation IDs, Azure integrations through the Az SDK and Key Vault. I lean on PowerShell because it gives me both the shell ergonomics for ad-hoc work and a real language for shipping services that have to keep running unattended. Pester for tests, manifests with versioned deps, supply-chain-aware about what I pull in.&lt;/p&gt;</description></item><item><title>Janus: A Zero Trust OT Gateway for Wichita's Machine Shops</title><link>https://www.seanross.us/posts/janus-cmmc-wichita/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://www.seanross.us/posts/janus-cmmc-wichita/</guid><description>&lt;p&gt;A local machine shop shouldn&amp;rsquo;t need a six-figure compliance project just to keep doing business with Spirit or Textron. But that&amp;rsquo;s where CMMC 2.0 is putting them.&lt;/p&gt;
&lt;p&gt;The DoD&amp;rsquo;s final rule went into force at the end of 2024, and the phased rollout is now landing in real contracts. Any contractor or subcontractor that touches Controlled Unclassified Information has to demonstrate, on paper, that they meet the 110 controls in NIST 800-171. The big primes have been preparing for years. The 30-person shops in their supply chain, mostly, have not.&lt;/p&gt;</description></item><item><title>Projects</title><link>https://www.seanross.us/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.seanross.us/projects/</guid><description>&lt;p&gt;Things I&amp;rsquo;m building in the open. Most of this work lives at the intersection of cloud security, identity, and the unglamorous parts of operational infrastructure that don&amp;rsquo;t get enough attention.&lt;/p&gt;
&lt;h2 id="janus--zero-trust-ot-gateway"&gt;
 Janus — Zero Trust OT Gateway
 &lt;a class="heading-link" href="#janus--zero-trust-ot-gateway"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;A stateless admission control service for accessing OT devices — CNC machines, welding robots, SCADA HMIs — from the IT side of a manufacturing network. Three gates: device registry, Entra group membership, Intune device compliance. Every decision lands in an append-only audit log designed as the &lt;strong&gt;CMMC 2.0 evidence artifact&lt;/strong&gt;, not as an afterthought.&lt;/p&gt;</description></item></channel></rss>