<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scope on VPNW.com</title>
    <link>https://vpnw.com/tags/scope/</link>
    <description>Recent content in Scope on VPNW.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/scope/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stolen VPN Login Case Study: Rules Learned From Two Weeks of Traffic Stop 136 of 144 Attempts</title>
      <link>https://vpnw.com/stolen-vpn-login-case-study-rules-learned-from-two-weeks-of-traffic-stop-136-of-144-attempts/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/stolen-vpn-login-case-study-rules-learned-from-two-weeks-of-traffic-stop-136-of-144-attempts/</guid>
      <description>&lt;p&gt;Many company VPNs are flat. Once a login is accepted, the VPN hands its owner the whole office network: every server, on every port. Staff like it that way because nothing ever gets in their way. Whoever steals a login likes it too, and stolen VPN logins are one of the commonest ways into a company today.&lt;/p&gt;&#xA;&lt;p&gt;The fix is old advice. Give each person the systems they use and nothing else. Few companies do it, because few have a list of who uses what, and one written by hand is out of date the day it&amp;rsquo;s done. Scope, the second VPN Works engine, writes that list from the traffic itself.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Next VPN Works Prototypes: A 14-Week Beta for AI Agents and a Real Gateway Pilot for Scope</title>
      <link>https://vpnw.com/the-next-vpn-works-prototypes-a-14-week-beta-for-ai-agents-and-a-real-gateway-pilot-for-scope/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/the-next-vpn-works-prototypes-a-14-week-beta-for-ai-agents-and-a-real-gateway-pilot-for-scope/</guid>
      <description>&lt;p&gt;The Agent&amp;rsquo;s Alpha answered one question. Can a small program seal an AI agent in and control every connection it makes? On Linux, on one machine, with a stand-in agent, the answer was yes. The next prototype, the Beta, takes on the harder question: does it hold up with real agents doing real work, on the machines where agents actually run? Scope, the second VPN Works engine, has an Alpha of its own now, and its next step, a pilot on a real company VPN, comes near the end of this post.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VPN Works Explained: How vpnw Gives Each AI Agent Its Own Network, and How Scope Narrows the Company VPN</title>
      <link>https://vpnw.com/vpn-works-explained-how-vpnw-gives-each-ai-agent-its-own-network-and-how-scope-narrows-the-company-vpn/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/vpn-works-explained-how-vpnw-gives-each-ai-agent-its-own-network-and-how-scope-narrows-the-company-vpn/</guid>
      <description>&lt;p&gt;VPN Works builds small programs that keep network access narrow and on the record. The first, vpnw, gives one program, usually an AI agent, a private network of its own on a Linux computer. vpnw decides where that program&amp;rsquo;s traffic may go, sends it out the way you choose and writes down every connection it makes. The second, Scope, does a similar job for the people on a company VPN, and gets its own section further down.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Where the Money Is in VPN Works: One Policy for Every AI Agent, and Least-Privilege Access on the Company VPN</title>
      <link>https://vpnw.com/where-the-money-is-in-vpn-works-one-policy-for-every-ai-agent-and-least-privilege-access-on-the-company-vpn/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/where-the-money-is-in-vpn-works-one-policy-for-every-ai-agent-and-least-privilege-access-on-the-company-vpn/</guid>
      <description>&lt;p&gt;VPN Works has two working prototypes today, so its business case is still a plan to test with customers. For the first engine, the Agent, here is the short answer to where the money is. The engine that seals one agent on one machine is the part that earns trust. The money comes from companies that run many agents and need one policy and one log across all of them, on every laptop, CI runner and server, plus exits they control. That&amp;rsquo;s worth a monthly fee per developer. There&amp;rsquo;s also a faster route: over the past year, security and network vendors paid between $180 million and $400 million each for AI and agent security startups.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
