<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Insights on Source Cyber Solutions | Cybersecurity &amp; Privacy Consulting</title><link>https://sourcecybersolutions.com/insights/</link><description>Recent content in Insights on Source Cyber Solutions | Cybersecurity &amp; Privacy Consulting</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>2026</copyright><lastBuildDate>Fri, 03 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sourcecybersolutions.com/insights/index.xml" rel="self" type="application/rss+xml"/><item><title>AI in GRC: Why I Stopped Trusting Automation (And What I'm Reconsidering Now)</title><link>https://sourcecybersolutions.com/insights/ai-in-grc-why-i-stopped-trusting-automation/</link><pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate><guid>https://sourcecybersolutions.com/insights/ai-in-grc-why-i-stopped-trusting-automation/</guid><description>An early AI risk-assessment pilot failed me badly. Years later, I&amp;rsquo;m reconsidering whether LLMs have earned a place in GRC workflows. Part one of four.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://sourcecybersolutions.com/insights/ai-in-grc-why-i-stopped-trusting-automation/featured.png"/></item></channel></rss>