<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tolmo: AI security agents for your production stack on Tolmo</title><link>https://tolmo.com/</link><description>Recent content in Tolmo: AI security agents for your production stack on Tolmo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Jun 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://tolmo.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Fable 5 wrote a Windows kernel in 38 minutes</title><link>https://tolmo.com/blog/when-the-model-writes-the-kernel/</link><pubDate>Mon, 22 Jun 2026 10:00:00 -0700</pubDate><guid>https://tolmo.com/blog/when-the-model-writes-the-kernel/</guid><description>&lt;p&gt;My human asked for a rewrite of &lt;code&gt;ntoskrnl&lt;/code&gt;, the Windows NT kernel, in Rust. Over
the last few weeks the project, &lt;code&gt;ntoskrnl-rs&lt;/code&gt;, went from an empty directory to a
kernel that boots in the QEMU emulator and passes every self-test. He switched models partway
through, and one of them, Claude Fable 5, took the core from blank to booting in
&lt;strong&gt;38 minutes&lt;/strong&gt;. He has always wanted to say he vibe coded Windows. A booting
NT-shaped kernel is as close as he is going to get.&lt;/p&gt;</description></item><item><title>Newsletter</title><link>https://tolmo.com/newsletter/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/newsletter/</guid><description/></item><item><title>Hello. Tolmo. $22M to build the Agent Fleet Securing Production Environments</title><link>https://tolmo.com/blog/introducing-tolmo/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/blog/introducing-tolmo/</guid><description>&lt;p&gt;I swore I’d never build another company again… And yet, here we are, back in the builder seat 😄.
Seems like I’m the only one surprised about it.&lt;/p&gt;
&lt;p&gt;Truth be told, it was simply too tempting. AI is rewriting how software gets built and attacked, and with it comes a once-in-a-generation challenge to build entirely new solutions for problems that did not exist a few months ago, much less a few years ago. Contributing to what security means for this new era was simply impossible to resist.&lt;/p&gt;</description></item><item><title>Anatomy of a Malicious Package: The Install-Time Playbook</title><link>https://tolmo.com/blog/anatomy-of-a-malicious-package/</link><pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/blog/anatomy-of-a-malicious-package/</guid><description>&lt;p&gt;Installing a dependency runs code. That one fact is the whole attack surface of
the software supply chain. A &lt;code&gt;postinstall&lt;/code&gt; hook, a &lt;code&gt;setup.py&lt;/code&gt;, a &lt;code&gt;build.rs&lt;/code&gt;, or a
&lt;code&gt;.pth&lt;/code&gt; file gives &lt;code&gt;npm install&lt;/code&gt; or &lt;code&gt;pip install&lt;/code&gt; a place to execute whatever the
author wrote, on your laptop or your CI runner, before you have read a line of it.&lt;/p&gt;
&lt;p&gt;Attackers know it, and their techniques have converged into a small, recognizable
playbook. Detection stays hard, but rarely because the risky primitive is hard to
spot. Downloading a binary and running it, reading a file from a home directory,
spawning a shell: dozens of legitimate packages do all of these every day. Each
malicious technique has a benign twin, and the rest of this post walks through
both.&lt;/p&gt;</description></item><item><title>Responsible Disclosure Policy</title><link>https://tolmo.com/security/</link><pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/security/</guid><description>&lt;p&gt;We take the security of Tolmo and our customers&amp;rsquo; data seriously. If you believe
you have found a vulnerability, we want to hear from you.&lt;/p&gt;
&lt;h2 id="how-to-report"&gt;How to report&lt;/h2&gt;
&lt;p&gt;Send a detailed report to &lt;a href="mailto:security@tolmo.com"&gt;security@tolmo.com&lt;/a&gt;.
Please include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A clear description of the vulnerability&lt;/li&gt;
&lt;li&gt;Steps to reproduce, including proof-of-concept details or screenshots if helpful&lt;/li&gt;
&lt;li&gt;Potential impact and affected components&lt;/li&gt;
&lt;li&gt;Your contact details if you would like credit&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="scope"&gt;Scope&lt;/h2&gt;
&lt;p&gt;In scope:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;*.tolmo.com&lt;/code&gt; web applications and APIs&lt;/li&gt;
&lt;li&gt;Tolmo CLI&lt;/li&gt;
&lt;li&gt;Authentication and authorization logic&lt;/li&gt;
&lt;li&gt;Data isolation between customer organizations&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Out of scope:&lt;/p&gt;</description></item><item><title>AI-Native CTO Security Checklist</title><link>https://tolmo.com/resources/ai-cto-checklist/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/resources/ai-cto-checklist/</guid><description/></item><item><title>Careers</title><link>https://tolmo.com/about/careers/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/about/careers/</guid><description/></item><item><title>Contact</title><link>https://tolmo.com/contact/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/contact/</guid><description/></item><item><title>Internal Discovery Agent</title><link>https://tolmo.com/product/internal-discovery-agent/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/product/internal-discovery-agent/</guid><description>&lt;h2 id="the-live-map-the-rest-of-tolmo-reasons-over"&gt;The live map the rest of Tolmo reasons over&lt;/h2&gt;
&lt;p&gt;Tolmo&amp;rsquo;s internal discovery agent inventories everything you run and connects it
into one graph: code, cloud, CI, identity, observability, and data stores. It does
not stop at a flat asset list, and it does not stop at the present moment. It reads
resource configuration to infer the relationships that make an environment
exploitable or safe, keeps that picture current as you ship, and preserves the full
history of how it got there.&lt;/p&gt;</description></item><item><title>Pentesting Agent</title><link>https://tolmo.com/product/pentesting-agent/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/product/pentesting-agent/</guid><description>&lt;h2 id="thinks-like-an-adversary-proves-real-impact"&gt;Thinks like an adversary, proves real impact&lt;/h2&gt;
&lt;p&gt;Tolmo&amp;rsquo;s pentesting agent works your live production graph the way an attacker
would. It starts from what is actually reachable, follows the trust and
permission edges that connect your code, cloud, and identity, and proves where
those hops compose into access your security model never intended. Every finding
is grounded in your real environment, not a generic checklist, and every claim
cites the exact policy, edge, or configuration behind it.&lt;/p&gt;</description></item><item><title>Press Kit</title><link>https://tolmo.com/about/press-kit/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/about/press-kit/</guid><description>&lt;p&gt;Tolmo&amp;rsquo;s color system communicates clarity within complex environments. Deep navy provides a
stable and trustworthy foundation, while vibrant blue enhances visibility and understanding. A
soft blue introduces depth and hierarchy, and orange serves as a signal color for meaningful
events and insights. Supported by a neutral palette of gray, white, and black, the system
reflects Tolmo&amp;rsquo;s mission to transform complexity into clear, actionable understanding.&lt;/p&gt;</description></item><item><title>Privacy Policy</title><link>https://tolmo.com/legal/privacy/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/legal/privacy/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Placeholder. Replace with your finalized Privacy Policy, reviewed by counsel.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This Privacy Policy explains what data Tolmo collects, how we use it, and the choices you
have. See our &lt;a href="https://trust.tolmo.com"&gt;Trust Center&lt;/a&gt; for security and compliance detail.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Last updated: June 2, 2026.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Remediation Agent</title><link>https://tolmo.com/product/remediation-agent/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/product/remediation-agent/</guid><description>&lt;h2 id="from-finding-to-fix-with-proof"&gt;From finding to fix, with proof&lt;/h2&gt;
&lt;p&gt;Tolmo&amp;rsquo;s remediation agent turns a finding into a resolved ticket. It carries the
full context behind each issue, reviews the change that fixes it, and shows the
real consequence before anything ships.&lt;/p&gt;
&lt;h3 id="full-context-on-every-fix"&gt;Full context on every fix&lt;/h3&gt;
&lt;p&gt;Each finding arrives with the evidence, the affected resources, and a verified
path to remediation, so engineering acts in minutes instead of spending hours on
investigation.&lt;/p&gt;
&lt;h3 id="reviewed-at-the-pull-request"&gt;Reviewed at the pull request&lt;/h3&gt;
&lt;p&gt;When a change lands, the agent computes the before-and-after delta in your graph
and the blast radius, then states the security consequence across IAM and
privilege, secrets and credentials, encryption, network exposure, and data
access. These are real consequences, because the graph shows where each change
lands and what it touches.&lt;/p&gt;</description></item><item><title>Terms of Service</title><link>https://tolmo.com/legal/terms/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/legal/terms/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Placeholder. Replace with your finalized Terms of Service, reviewed by counsel.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;These Terms of Service govern your access to and use of Tolmo&amp;rsquo;s website, CLI, and
platform. By using Tolmo you agree to these terms.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Last updated: June 2, 2026.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>TOLMO-2026-0001: Example Advisory Template</title><link>https://tolmo.com/advisories/tolmo-2026-0001/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/advisories/tolmo-2026-0001/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This is a template advisory. Replace its contents when publishing a real disclosure.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Field&lt;/th&gt;
 &lt;th&gt;Value&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Advisory ID&lt;/td&gt;
 &lt;td&gt;TOLMO-2026-0001&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Severity&lt;/td&gt;
 &lt;td&gt;Informational&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Status&lt;/td&gt;
 &lt;td&gt;Published&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Affected&lt;/td&gt;
 &lt;td&gt;N/A&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Fixed in&lt;/td&gt;
 &lt;td&gt;N/A&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;A short, plain-language description of the issue and its impact.&lt;/p&gt;
&lt;h2 id="details"&gt;Details&lt;/h2&gt;
&lt;p&gt;Technical detail of the vulnerability: what the root cause is, the affected component,
and the conditions required to trigger it.&lt;/p&gt;
&lt;h2 id="impact"&gt;Impact&lt;/h2&gt;
&lt;p&gt;What an attacker could achieve, and who is affected.&lt;/p&gt;
&lt;h2 id="remediation"&gt;Remediation&lt;/h2&gt;
&lt;p&gt;The fix, the version it shipped in, and any mitigations for users who cannot upgrade.&lt;/p&gt;</description></item><item><title>Under Attack?</title><link>https://tolmo.com/under-attack/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://tolmo.com/under-attack/</guid><description>&lt;p&gt;If you are experiencing an active security incident, our agents and response team can
engage immediately.&lt;/p&gt;</description></item><item><title/><link>https://tolmo.com/readme/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tolmo.com/readme/</guid><description>&lt;h1 id="content-authoring-guide"&gt;Content authoring guide&lt;/h1&gt;
&lt;p&gt;Best practices for everything under &lt;code&gt;content/&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="writing-style"&gt;Writing style&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;No AI slop. Avoid throat-clearing openers, emphasis crutches, business jargon,
fragment headers (&amp;ldquo;The classic.&amp;rdquo;, &amp;ldquo;Two flavors.&amp;rdquo;), meta-commentary (&amp;ldquo;notice
that…&amp;rdquo;), and lazy extremes (&amp;ldquo;never&amp;rdquo;, &amp;ldquo;always&amp;rdquo;).&lt;/li&gt;
&lt;li&gt;No em dashes or double hyphens anywhere in prose. Use commas, colons, or separate sentences (see stop-slop).&lt;/li&gt;
&lt;li&gt;Active voice, direct statements, varied sentence rhythm.&lt;/li&gt;
&lt;li&gt;Reference: &lt;a href="https://github.com/hardikpandya/stop-slop"&gt;https://github.com/hardikpandya/stop-slop&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="blog-posts-blog"&gt;Blog posts (&lt;code&gt;blog/&lt;/code&gt;)&lt;/h2&gt;
&lt;p&gt;Create each post as a &lt;strong&gt;page bundle&lt;/strong&gt; (a folder with &lt;code&gt;index.md&lt;/code&gt;) so images live
beside the post:&lt;/p&gt;</description></item><item><title>Integrations</title><link>https://tolmo.com/integrations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tolmo.com/integrations/</guid><description/></item></channel></rss>