

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://some-natalie.dev/</id>
  <title>Some Natalie's corner of the internet</title>
  <subtitle>Things I'm learning, working on, or thinking about.  All opinions and snark my own.</subtitle>
  <updated>2026-04-03T19:11:02-06:00</updated>
  <author>
    <name>Natalie Somersall</name>
    <uri>https://some-natalie.dev/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://some-natalie.dev/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://some-natalie.dev/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Natalie Somersall </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Enterprise chargeback - a better quality of life for operations</title>
    <link href="https://some-natalie.dev/blog/chargeback-buildout/" rel="alternate" type="text/html" title="Enterprise chargeback - a better quality of life for operations" />
    <published>2026-03-31T00:00:00-06:00</published>
  
    <updated>2026-03-31T00:00:00-06:00</updated>
  
    <id>https://some-natalie.dev/blog/chargeback-buildout/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/chargeback-buildout/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>We left off with a laptop and a database serving as a bare-minimum proof of concept.  It works, but not enough to be usable.  Starting a project from scratch doesn’t have to be toil.  Moving this into “real infrastructure” gave me an opportunity to implement quality of life improvements.  Let’s do databases better this time  By this point, the project had expanded beyond one person’s exploratio...</summary>

  </entry>

  
  <entry>
    <title>There I FIPS’d it - misadventures in federal cryptography</title>
    <link href="https://some-natalie.dev/blog/fipsd-it/" rel="alternate" type="text/html" title="There I FIPS’d it - misadventures in federal cryptography" />
    <published>2026-01-25T00:00:00-07:00</published>
  
    <updated>2026-01-27T10:20:41-07:00</updated>
  
    <id>https://some-natalie.dev/blog/fipsd-it/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/fipsd-it/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>Cryptography seems deceptively simple until you get into implementation.  Tempted by shortcuts to save money, organizations ship something “just good enough” to pass compliance checks.  I see this all the time working with the public sector and companies in highly-regulated industries making new products or trying to enter the market for the first time.  Just when you think you’ve done everythi...</summary>

  </entry>

  
  <entry>
    <title>Enterprise chargeback - can we do this?</title>
    <link href="https://some-natalie.dev/blog/chargeback-basics/" rel="alternate" type="text/html" title="Enterprise chargeback - can we do this?" />
    <published>2026-01-04T00:00:00-07:00</published>
  
    <updated>2026-03-31T22:29:46-06:00</updated>
  
    <id>https://some-natalie.dev/blog/chargeback-basics/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/chargeback-basics/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>How do you know how much each business unit is using across any number of licensed software or consumably-billed SaaS or compute products?  Let’s scope actually doing this having done it before.  It sounds a lot easier when I started than it was when finished, yet it’s one of the most common stories I’m asked to tell.  There’s some trauma here, but lots of lessons learned too. 😅     This is the...</summary>

  </entry>

  
  <entry>
    <title>Images have their own risks, too</title>
    <link href="https://some-natalie.dev/blog/image-risks/" rel="alternate" type="text/html" title="Images have their own risks, too" />
    <published>2025-11-22T00:00:00-07:00</published>
  
    <updated>2025-11-23T08:53:14-07:00</updated>
  
    <id>https://some-natalie.dev/blog/image-risks/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/image-risks/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>You’ve locked down your runtime, orchestrator, and hosts.  Now how about what’s actually running inside of those containers?  Container images are too often treated as black boxes until something goes wrong. Different scanning tools can give wildly different results, vulnerabilities hide in plain sight, and that “secure” base image might do no good if you’re configuring it poorly.  Welcome to t...</summary>

  </entry>

  
  <entry>
    <title>Risks in the image registry</title>
    <link href="https://some-natalie.dev/blog/registry-risks/" rel="alternate" type="text/html" title="Risks in the image registry" />
    <published>2025-11-12T00:00:00-07:00</published>
  
    <updated>2025-11-22T21:09:08-07:00</updated>
  
    <id>https://some-natalie.dev/blog/registry-risks/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/registry-risks/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>All of these containers are images … somewhere.  That ‘somewhere’ is an artifact (or container) registry.  What risks can we find in our container registry?  Broadly speaking, there are two types of container registries - public registries and private registries.  Public registries are websites on the open internet that anyone can publish their software too.  These include a ton of popular webs...</summary>

  </entry>

</feed>


