<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Vulnerability Management on WellScript</title><link>https://wellscript.io/tags/vulnerability-management/</link><description>Recent content in Vulnerability Management on WellScript</description><image><title>WellScript</title><url>https://wellscript.io/images/wellscript-cover.png</url><link>https://wellscript.io/images/wellscript-cover.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wellscript.io/tags/vulnerability-management/index.xml" rel="self" type="application/rss+xml"/><item><title>How Technical Findings Map to Security Controls</title><link>https://wellscript.io/rmf/how-technical-findings-map-to-security-controls/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://wellscript.io/rmf/how-technical-findings-map-to-security-controls/</guid><description>How ACAS scans and STIG checks connect to NIST 800-53 controls in eMASS, and what CCI and AP actually do behind the scenes.</description></item><item><title>How ACAS Findings Become Remediation Evidence</title><link>https://wellscript.io/rmf/how-acas-findings-become-remediation-evidence/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://wellscript.io/rmf/how-acas-findings-become-remediation-evidence/</guid><description>ACAS findings do not become remediation evidence on their own. Here is how scan data moves from Tenable.sc into the documentation your AO actually reviews.</description></item></channel></rss>