TE
Travis Eric
HomeNow
Work with meBook a 30-minute call
Travis Eric LogoTravis Eric

AI consulting and custom software, based in Fort Collins. Explore the work. Bring your next idea.

Travis Eric AI Consulting(720) 770-2979

Navigate

  • Home
  • Now
  • Projects
  • How I work

Deeper

  • Work with me
  • About
  • Share your experience
  • Case Studies
  • Resources
  • Impossible Vision
  • Technical Stack
  • Manifesto
  • Writings

Follow the work

New systems and field notes, sent when they ship.

Communities

AI Builder's LabView membershipTeneo Publishing CollectiveView details
@TravisEric_Travis Eric@TravisericLive Builds@travis_eric
PrivacyTerms© 2026 Travis Eric
/
/
Back to writings
Skills and playbooks

Security incident

Travis EricNovember 20, 20262 min read
Share this post:

The overnight build system brought our attention to a critical security incident. This post details the concrete steps we took to address it, grounded in evidence from our process files.

Initial Alert

The incident was initiated by an email notice. I verified its legitimacy by reading the .eml headers to ensure SPF, DKIM, and DMARC passed. This confirmed the sender's authenticity, a crucial first step before proceeding. I avoided clicking any links in the email, directly accessing the vendor's status page instead.

Freezing Evidence

Before making any changes, I ran python -I .claude/scripts/secret_census.py --seed-breach .claude/operations/<incident>/breach-fingerprints.json --incident <slug> --from railway. This command preserved the records of the stolen environment variables, which is essential since rotating secrets would otherwise erase this evidence.

Scope Determination

To determine the scope, I executed python -I .claude/scripts/secret_census.py --no-page --verbose. This script listed every storage location of the compromised values, including vault, AWS, Vercel, and local environments. For package-related breaches, I used python -I .claude/scripts/security_ioc_check.py --receipt on every machine. This indicated if any machine's vault and environment files were compromised.

Usage Verification

I verified whether compromised keys were used by running operations/railway-breach-2026-10-22/key_liveness.py. This script checked free read endpoints for any suspicious activity. I also examined Stripe and GitHub activities to ensure all created objects matched our records. The absence of misuse wasn't taken as a clean result; rotation was mandatory regardless.

Containment Actions

Containment began by removing unused public endpoints and revoking over-privileged tokens. I logged each action with timestamp and evidence in the incident README, as detailed in the worked example .claude/operations/railway-breach-2026-10-22/README.md.

Rotations in Waves

The rotation process was strategic, starting with money-related and founder accounts, followed by third-party provider keys. Each new key was smaller and more restricted, as per the "Rotate narrower" principle. Internal keys were rotated in a staged manner, allowing systems to accept both old and new keys temporarily, ensuring a smooth transition.

Closure

The incident was considered resolved when secret_census.py reported UNROTATED 0 for the incident, with no ACCOUNT findings or GAP. I finalized the incident report in the README with all actions and evidence logged, updating the threat brief for future reference.

This practical note from the overnight build highlights the importance of a structured, evidence-backed approach to handling security incidents. Each step was guided by our documented processes, ensuring thoroughness and clarity in response.

Join Pattern Insights

Get weekly insights on AI architecture, pattern recognition, and building platforms without permission.

On this page

  • Initial Alert
  • Freezing Evidence
  • Scope Determination
  • Usage Verification
  • Containment Actions
  • Rotations in Waves
  • Closure
Tags:
build-in-public

Read next

November 19, 2026

swipe-study — competitor/creator video → filed research

I recently ran an overnight build of the swipe-study system, which included several interesting outputs. One standout was the Savannah Case Media SMM teardown,...

Read it

November 18, 2026

speak-agent: being usable by an agent, and proving it

The "speak-agent" skill is designed to make a web product usable by AI agents while proving its utility live. The overnight build system provided some...

Read it

November 16, 2026

owner-console — give a client's owner a dashboard on their own site

When you're tasked with giving a client's owner a dashboard on their own site, the owner-console skill in the Local Business OS is your go-to tool. This skill...

Read it

Join the Discussion

Have thoughts on this post? I'd love to hear them! Join the conversation on X where we can discuss AI architecture, pattern recognition, and building platforms.

Discuss on X

Or reach out directly at @TravisEric_