<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mr Recruiter</title>
    <description>The latest articles on DEV Community by Mr Recruiter (@nodevguy).</description>
    <link>https://dev.to/nodevguy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4074583%2F83bbd473-c8a4-4d37-99e0-42ccfdf5603f.gif</url>
      <title>DEV Community: Mr Recruiter</title>
      <link>https://dev.to/nodevguy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nodevguy"/>
    <language>en</language>
    <item>
      <title>AI agents are shadow AI's more dangerous sequel</title>
      <dc:creator>Mr Recruiter</dc:creator>
      <pubDate>Wed, 12 Aug 2026 10:33:02 +0000</pubDate>
      <link>https://dev.to/nodevguy/ai-agents-are-shadow-ais-more-dangerous-sequel-32j6</link>
      <guid>https://dev.to/nodevguy/ai-agents-are-shadow-ais-more-dangerous-sequel-32j6</guid>
      <description>&lt;p&gt;The last two years of shadow AI were mostly about employees pasting things into chatbots. Risky, but bounded. A person can only copy so much, and a chatbot on its own just reads what you give it and hands text back. The damage has a ceiling.&lt;/p&gt;

&lt;p&gt;Agents remove the ceiling. An AI agent doesn't wait for a prompt and return a paragraph. It reads, decides, and acts. It can open your CRM, pull a list, write to a database, send an email, call another system, and do it again in a loop, in seconds, with no human watching any single step. The same autonomy that makes agents useful is exactly what makes them a different kind of risk.&lt;/p&gt;

&lt;p&gt;That's not a hypothetical worry anymore. Forrester named AI agent threats the top CISO risk for 2026, and the reason is structural, not speculative.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why agents slip past the tools you already have&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Here's what unsettles me about them. Most of your security tooling assumes a human is on the other end, and agents quietly break that assumption.&lt;/p&gt;

&lt;p&gt;An agent doesn't trigger an MFA prompt, because it authenticated once and kept going. It doesn't leave the kind of session logs your SIEM was built to parse. It doesn't stop when the employee goes home or takes the weekend. If a browser-extension agent can reach what your helpdesk can reach, it may already be doing things your security team will never see in an alert queue.&lt;/p&gt;

&lt;p&gt;So the whole detection model built around "a person did a thing at a time from a place" doesn't fit. The actor is software, running continuously, using credentials it was handed and never questioned.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The autonomy is the risk&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;With a chatbot, a bad instruction produces a bad sentence. You read it, you ignore it, no harm done. With an agent that has access to real systems, a bad instruction produces a bad action, and the action already happened by the time anyone notices.&lt;/p&gt;

&lt;p&gt;The Ponemon and DTEX 2026 insider risk report found that 92 percent of organisations say generative AI has changed how employees access and share data, while only 13 percent have a formal AI policy. Agents widen that gap in the worst way. They don't just change how data is accessed. They take the human out of the loop entirely, which means a single wrong instruction can read, transform, and move data across systems before a person could react.&lt;/p&gt;

&lt;p&gt;This is why I think "agent" is a misleading word for security purposes. It sounds like a helper. From an access standpoint it's closer to a new employee who never sleeps, was onboarded in thirty seconds with no paperwork, and got handed the keys to several systems because scoping them properly was annoying.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What actually changes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The uncomfortable answer is that most of the fix is not new. It's the same access discipline, applied to something that moves much faster and never rests.&lt;/p&gt;

&lt;p&gt;Treat every agent as its own identity, not a shortcut hanging off a human's account. Give it the narrowest access the task needs and nothing spare. Put a human checkpoint in front of the high-impact actions, the ones that send, delete, pay, or publish, so autonomy doesn't extend to the moves you can't undo. And watch what the agent does, not just whether it logged in, because with agents the login was never the interesting part.&lt;/p&gt;

&lt;p&gt;None of that is exotic. It's least privilege and monitoring, the advice security people have given for years. Agents just raise the price of ignoring it, because the gap between a mistake and its consequences has shrunk to about a second.&lt;/p&gt;

&lt;p&gt;At Arclogiq we're spending more and more time on exactly this: helping teams give their agents scoped identities, real limits, and a human in front of the actions that matter, before the agent count quietly outgrows anyone's ability to track it. Shadow AI taught companies that people route around missing tools. Agents are the same lesson at higher speed, with their hands on the controls&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>cybersecurity</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
