<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Monitoring on CybersecurityOS</title><link>http://www.cybersecurityos.net/tags/continuous-monitoring/</link><description>Recent content in Continuous Monitoring on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 11:34:48 -0500</lastBuildDate><atom:link href="http://www.cybersecurityos.net/tags/continuous-monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-SPM 101: How to Continuously Assess, Monitor, and Secure AI Systems in Production</title><link>http://www.cybersecurityos.net/posts/ai-devsecops/ai-spm-101-ai-security-posture-management/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>http://www.cybersecurityos.net/posts/ai-devsecops/ai-spm-101-ai-security-posture-management/</guid><description>&lt;p&gt;Most organizations can tell you, within a reasonable margin, how many servers they run, which ones are exposed to the internet, and when they were last patched. Ask the same organization how many AI models and agents are running in production, what data each one can touch, which ones have had their system prompts changed in the last month, or whether any of them are currently vulnerable to prompt injection — and the answer, more often than not, is silence.&lt;/p&gt;</description></item></channel></rss>