<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Security on carney.wiki</title><link>https://carney.wiki/tags/ai-security/</link><description>Recent content in AI Security on carney.wiki</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 04 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carney.wiki/tags/ai-security/index.xml" rel="self" type="application/rss+xml"/><item><title>How AI Clarifies and Fixes the Modern Data Stack</title><link>https://carney.wiki/blog/from-tool-sprawl-to-an-operational-data-platform/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/from-tool-sprawl-to-an-operational-data-platform/</guid><description>The modern data stack is incredible.
It is also exhausting.
Cloud elasticity, open table formats, modular tooling, and managed services let small teams do work that used to require a data center and a small army. That is the good news.
The bad news is that the same modularity created tool sprawl, half-finished pipelines, unclear ownership, and incident channels that never sleep.
Now AI is walking into that environment and asking for access.</description></item><item><title>Your AI Agent Is a Toddler With Root Access</title><link>https://carney.wiki/blog/your-ai-agent-is-a-toddler-with-root-access/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/your-ai-agent-is-a-toddler-with-root-access/</guid><description>Agentic AI is no longer a demo.
It calls APIs.
It writes to databases.
It triggers workflows that affect customers, revenue, and operations.
That is powerful.
It is also a fundamental shift in risk.
Once an AI system moves from advisory to execution, it becomes part of the control plane. Whether the organization admits that or not is mostly irrelevant. The risk already changed.
Agents expand the attack surface overnight The moment an AI system can execute actions, it becomes a privileged actor.</description></item><item><title>Prompt Injection Has Left the Chatbot</title><link>https://carney.wiki/blog/prompt-injection-has-left-the-chatbot/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/prompt-injection-has-left-the-chatbot/</guid><description>Prompt injection did not suddenly become dangerous.
We connected it to systems that matter.
For years, prompt injection was treated as a curiosity: a way to make a chatbot ignore rules, leak instructions, or say something awkward. Interesting for demos. Annoying in production. Easy to dismiss as a model behavior problem.
That framing is obsolete.
The recent reporting around ServiceNow AI agent vulnerabilities should make the shift clear. This is not just about a model getting confused.</description></item><item><title>The CISO's Guide to Governing Generative AI</title><link>https://carney.wiki/blog/the-cisos-guide-to-governing-generative-ai/</link><pubDate>Sat, 10 Jan 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/the-cisos-guide-to-governing-generative-ai/</guid><description>Generative AI is now part of the enterprise control surface.
That is the CISO&amp;rsquo;s problem, whether the CISO asked for it or not.
Employees are using AI tools. Vendors are embedding AI features. Engineering teams are experimenting with model APIs. Business teams are building copilots. Data teams are connecting retrieval systems to internal knowledge.
Some of this is useful.
Some of it is risky.
Most of it is moving faster than the policy process.</description></item><item><title>How Prompt Injection Attacks Actually Work</title><link>https://carney.wiki/blog/how-prompt-injection-attacks-actually-work/</link><pubDate>Wed, 10 Dec 2025 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/how-prompt-injection-attacks-actually-work/</guid><description>Prompt injection is not a clever chatbot trick anymore.
It is one of the core security problems in AI systems.
The reason is uncomfortable: large language models do not reliably separate instructions from data. They interpret text. That text may come from a user, a document, a webpage, a support ticket, an email, a retrieved knowledge base article, or another AI system.
To a human, some of that text is obviously content.</description></item><item><title>Why Most AI Security Failures Start With Data</title><link>https://carney.wiki/blog/why-most-ai-security-failures-start-with-data/</link><pubDate>Thu, 02 Oct 2025 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/why-most-ai-security-failures-start-with-data/</guid><description>Most AI security failures do not start with the model.
They start with the data.
That is not as exciting as a story about a rogue algorithm or a clever jailbreak, but it is usually closer to the truth.
If the data feeding an AI system is unclassified, unverified, poorly governed, over-permissioned, or impossible to trace, the model inherits the problem. Then it scales it.
AI does not make weak data practices disappear.</description></item></channel></rss>