<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vulnerability-Management on t0ul</title><link>https://t0ul.com/tags/vulnerability-management/</link><description>Recent content in Vulnerability-Management on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/vulnerability-management/index.xml" rel="self" type="application/rss+xml"/><item><title>The Risk Rancher Field Manual: Leave the Watchtower</title><link>https://t0ul.com/blog/risk-rancher-field-manual-intro/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-intro/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Most security programs are built in a watchtower. You buy a scanner, point it at your estate, and on day one it hands you fourteen thousand rows of red: Criticals stacked on Highs stacked on Mediums, every one of them screaming that the sky is falling. You stand up there with your binoculars and you shout, wolves, everywhere, wolves. And down in the dirt, where the actual work happens, nobody moves. Because you have cried critical so many times that the word stopped meaning anything.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 1: Do You Even Need a Fence?</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch1/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch1/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Before you spend a dollar on a scanner, answer a harder question: do you need a vulnerability management program at all, and if so, how big?&lt;/p&gt;
&lt;p&gt;Most people get this backwards. They buy the tool first, because the tool is the thing with a sales rep and a budget line. Then they spend a year drowning in its output, trying to build a program around a firehose they already turned on. Do it the other way. The program is the thing. The tools serve it.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 2: You Can't Brand a Ghost</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch2/</link><pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch2/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You cannot protect what you do not know you have. Every program that falls apart falls apart right here, at the very start, because somebody bought a scanner and pointed it at &amp;ldquo;the network&amp;rdquo; without first asking what was actually on it. The scanner found three thousand things. Nobody could say which of them mattered, who owned them, or whether half of them even still existed. The program drowned on day one, in a lake of its own output.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 3: Don't Throw PDFs Over the Fence</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch3/</link><pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch3/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Here is a fact that no tool will fix for you: you do not fix vulnerabilities. Somebody else does. You find the hole; an engineer, a sysadmin, a platform team closes it. Which means your entire program, every scanner and score and SLA, ultimately runs on one thing you cannot buy: whether the people holding the wrenches are willing to pick them up when you ask.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 4: Casting the Net</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch4/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch4/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Now you turn on the machine that finds the holes. But a scanner is not one thing. It is a whole category of tools, and the two ways people get this wrong are buying the one that does not fit their estate, or buying all of them at once and drowning. The goal is coverage of what matters, not maximum noise. You already did the hard part in chapter two: you know your crown jewels. Now you pick the net that actually covers them.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 5: The Deep Dive</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch5/</link><pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch5/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A scanner casts a wide, shallow net. A pentester dives deep in one spot. Both have their place, but they are not substitutes, and the single most common mistake in this whole field is paying for the second when you have not done the first.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 6: Sorting the Herd</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch6/</link><pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch6/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This is the chapter the whole book has been walking toward, and it is the one your spreadsheet does not survive. Everything before now was setup: you sized the program, mapped the herd, built the alliance with IT, cast the nets. Now the findings pour in from every scanner and pentest and bug report, thousands of them, and they arrive as one undifferentiated wall of red.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 7: Getting It Fixed</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch7/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch7/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A prioritized queue is not a fixed vulnerability. It is a to-do list, and to-do lists do not patch themselves. This chapter is the handoff and the follow-through: getting the right fix to the right person, with the right context, and then making sure the thing actually happened. We will do it on the finding you ranked first in the last chapter.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 8: Accepting Reality</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch8/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch8/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Not every finding gets fixed, and not every finding gets fixed on time. Anyone who tells you otherwise is running a program on a slide, not inside a real company with deadlines and legacy systems and humans. The mark of a mature program is not zero unfixed findings. It is that every unfixed finding is unfixed &lt;em&gt;on purpose, on the record, and on a clock.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 9: Automating the Herd</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch9/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch9/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Across chapters six, seven, and eight you worked one real file by hand: you triaged 29 raw findings into a ranked queue, turned the top one into a ticket with a verify step, and deferred two more with an owner and an expiry. You know how every step works because you did each one yourself. Which means you have finally earned the only honest version of this chapter: here is how to stop doing the parts that are not thinking.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual, Ch. 10: The Only Numbers That Matter</title><link>https://t0ul.com/blog/risk-rancher-field-manual-ch10/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-ch10/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You have built the engine and, if you want, automated it. Sooner or later someone, your boss, the board, a big customer, asks the question every program eventually faces: is it working? Answer it badly and good programs lose their funding to flashier ones. Answer it well and it is a short, honest handful of numbers, which we are going to actually compute.&lt;/p&gt;</description></item><item><title>The Risk Rancher Field Manual: The Daily Discipline</title><link>https://t0ul.com/blog/risk-rancher-field-manual-conclusion/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/risk-rancher-field-manual-conclusion/</guid><description>&lt;p&gt;&lt;em&gt;Part of &lt;a href="https://t0ul.com/blog/risk-rancher-field-manual-intro/"&gt;The Risk Rancher Field Manual&lt;/a&gt;, a hands-on guide to starting, scaling, and running a vulnerability management program.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We started in a watchtower, drowning in red, shouting about wolves while nobody down in the dirt fixed the fence. We are ending somewhere quieter: a short, prioritized list, an alliance with the people who hold the wrenches, and a steady rhythm of finding, deciding, fixing, and proving. That rhythm is the whole thing. That rhythm is the job.&lt;/p&gt;</description></item></channel></rss>