
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Taylor Morgan</title>
      <link>https://taylor-dotcom.netlify.app/blog</link>
      <description>Taylor Morgan&apos;s personal site. Resume, blog posts, developer relations and software engineering stuff.</description>
      <language>en-us</language>
      <managingEditor>taylormorganttm@gmail.com (Taylor Morgan)</managingEditor>
      <webMaster>taylormorganttm@gmail.com (Taylor Morgan)</webMaster>
      <lastBuildDate>Mon, 31 Aug 2026 10:00:00 GMT</lastBuildDate>
      <atom:link href="https://taylor-dotcom.netlify.app/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20260831-securestack-ai-aws-infrastructure</guid>
    <title>Deploying SecureStack AI to Real AWS Infrastructure</title>
    <link>https://taylor-dotcom.netlify.app/blog/20260831-securestack-ai-aws-infrastructure</link>
    <description>The account-level decisions behind deploying SecureStack AI to real ECS and RDS infrastructure: a scoped IAM identity instead of root, two separate permissions boundaries to close a subtle PassRole gap, a compensating IP restriction for a longer-lived demo, and what it actually cost.</description>
    <pubDate>Mon, 31 Aug 2026 10:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>aws</category><category>security</category><category>iam</category><category>deployment</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20260830-securestack-ai-trustworthy</guid>
    <title>I Built an AI Tool to Review Code for Security Issues. Here&apos;s What It Took to Make It Trustworthy</title>
    <link>https://taylor-dotcom.netlify.app/blog/20260830-securestack-ai-trustworthy</link>
    <description>Building SecureStack AI taught me that grounding an LLM&apos;s answers is the easy part. The real work was a verification layer that checks citations, tool-call evidence, and deterministic scanners so nothing gets trusted just because it sounds confident, plus two AWS deployment gotchas along the way.</description>
    <pubDate>Sun, 30 Aug 2026 16:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>ai</category><category>security</category><category>llm</category><category>aws</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20260618-running-local-ai-models-with-ollama</guid>
    <title>Running Local AI Models With Ollama: A Complete Setup Guide</title>
    <link>https://taylor-dotcom.netlify.app/blog/20260618-running-local-ai-models-with-ollama</link>
    <description>Everything you need to go from a blank machine to a working local AI setup with Ollama: installation, pulling and running models, the CLI reference, the REST API, and Modelfile customization, all in one place instead of scattered across five doc pages.</description>
    <pubDate>Thu, 18 Jun 2026 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>ai</category><category>ollama</category><category>self-hosted</category><category>how-to</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20230320-verosint-automated-response-and-vera</guid>
    <title>From Flagged to Fixed: How Verosint Automates the Account Takeover Response</title>
    <link>https://taylor-dotcom.netlify.app/blog/20230320-verosint-automated-response-and-vera</link>
    <description>Detecting account takeover is half the problem. This one covers what Verosint actually does once a login gets flagged, from automated MFA enforcement to VERA, its agentic AI security analyst that handles triage over Slack.</description>
    <pubDate>Mon, 20 Mar 2023 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>security</category><category>identity</category><category>account-takeover</category><category>verosint</category><category>automation</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20230111-how-verosint-detects-account-takeover</guid>
    <title>How Verosint Detects Account Takeover Without Adding Friction for Real Users</title>
    <link>https://taylor-dotcom.netlify.app/blog/20230111-how-verosint-detects-account-takeover</link>
    <description>A technical look at how the Verosint platform I worked on as a Developer Relations engineer detects account takeover: unified observability across identity systems, AI-driven risk scoring, and a triage layer built for investigation speed.</description>
    <pubDate>Wed, 11 Jan 2023 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>security</category><category>identity</category><category>account-takeover</category><category>verosint</category><category>api</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20221005-attack-patterns-behind-account-takeover</guid>
    <title>The Attack Patterns Hiding Inside Logins That Look Completely Normal</title>
    <link>https://taylor-dotcom.netlify.app/blog/20221005-attack-patterns-behind-account-takeover</link>
    <description>Account takeover isn&apos;t one attack, it&apos;s a family of them. A walkthrough of the patterns identity security teams actually watch for: credential stuffing, session hijacking, impossible travel, MFA flooding, and more.</description>
    <pubDate>Wed, 05 Oct 2022 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>security</category><category>identity</category><category>account-takeover</category><category>verosint</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20220822-what-makes-account-takeover-different</guid>
    <title>What Makes Account Takeover Different From Every Other Kind of Breach</title>
    <link>https://taylor-dotcom.netlify.app/blog/20220822-what-makes-account-takeover-different</link>
    <description>Most breaches start with something broken. Account takeover starts with a login that looks completely normal, which is exactly why it&apos;s so hard to catch and so slow to remediate.</description>
    <pubDate>Mon, 22 Aug 2022 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>security</category><category>identity</category><category>account-takeover</category><category>verosint</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20211115-porting-inventory-system-to-verse</guid>
    <title>What Porting a Simple Inventory System to Verse Taught Me</title>
    <link>https://taylor-dotcom.netlify.app/blog/20211115-porting-inventory-system-to-verse</link>
    <description>A first look at Verse&apos;s failure-as-value model, effect specifiers, and structured concurrency, walked through by porting a simple key-and-door inventory device into UEFN.</description>
    <pubDate>Mon, 15 Nov 2021 10:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>verse</category><category>uefn</category><category>epic-games</category><category>game-development</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20210708-building-your-first-island-in-uefn</guid>
    <title>Building Your First Island in UEFN: A Practical Walkthrough</title>
    <link>https://taylor-dotcom.netlify.app/blog/20210708-building-your-first-island-in-uefn</link>
    <description>The build-test loop I walked new creators through during onboarding: installing UEFN, creating a project, adding your first Verse device, and the compile-drag-playtest cycle you&apos;ll repeat for as long as you build in it.</description>
    <pubDate>Thu, 08 Jul 2021 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>epic-games</category><category>uefn</category><category>fortnite</category><category>verse</category><category>how-to</category>
  </item>

  <item>
    <guid>https://taylor-dotcom.netlify.app/blog/20210420-what-creative-2-actually-changed</guid>
    <title>What Creative 2.0 Actually Changed About Building in Fortnite</title>
    <link>https://taylor-dotcom.netlify.app/blog/20210420-what-creative-2-actually-changed</link>
    <description>Creative 2.0 isn&apos;t a replacement for the original Fortnite Creative toolset, it&apos;s a second, deeper layer built on UEFN and Verse that sits alongside it. Here&apos;s what actually changed and why the distinction matters for creators deciding where to start.</description>
    <pubDate>Tue, 20 Apr 2021 09:00:00 GMT</pubDate>
    <author>taylormorganttm@gmail.com (Taylor Morgan)</author>
    <category>epic-games</category><category>uefn</category><category>fortnite</category><category>verse</category>
  </item>

    </channel>
  </rss>
