<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reporting on securecode.dev</title><link>https://securecode.dev/tags/reporting/</link><description>Recent content in Reporting on securecode.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://securecode.dev/tags/reporting/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating the Parts of Vulnerability Management That Don't Need a Human</title><link>https://securecode.dev/insights/automating-the-parts-of-vulnerability-management-that-dont-need-a-human/</link><pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/automating-the-parts-of-vulnerability-management-that-dont-need-a-human/</guid><description>&lt;p>A defined vulnerability management process is the prerequisite for automation, not a replacement for it. Teams that try to automate triage and reporting before the underlying process is clear usually end up automating confusion faster. Once the process exists, though, the mechanical parts of running it are exactly where automation earns its keep.&lt;/p></description></item></channel></rss>