Bitdefender's agent VPN opens a disposable container for each prompt

The moment the product is built for is narrow. An agent in Cursor fetches a page in the middle of a task, and the site records the request against the home address of whoever typed the prompt. Bitdefender's own suggested uses are checking that a geolocalised page renders correctly for another market, running a research agent from a conference network, and stopping a site correlating dozens of daily requests back to one household ^[19].

The five listed protections stop at the network ^[20]. The product page says the tool protects network transport and IP exposure and leaves prompt content alone, so the model behind the agent still receives everything it normally would, including account identity ^[9].

Ciprian Istrate, who runs consumer operations at Bitdefender, said on Tuesday: "Security can no longer stop at protecting the person behind the screen. It has to extend to the agent itself acting on their behalf." ^[2]

The pitch rests on two outside findings. Pew Research Center found that 71% of US adults think more AI use will make their personal information less secure ^[17]. The Cloud Security Alliance puts agents in what it calls an identity grey area, where they borrow workload identities, shared service accounts, or the credentials of whoever is running them ^[18].

Merchants and payment networks are pulling the other way. Amazon blocked Meta's Muse from its store on Sunday night and is suing Perplexity over shopping agents ^[15]. Visa, Mastercard and Ant International have been building Know Your Agent schemes, on the principle that a merchant should know what is buying from it ^[16].

The attachment point is the part likely to outlive the beta. The plumbing is a Model Context Protocol server ^[5], and Google used the same protocol last week to open its Home platform to outside agents ^[7]. The Next Web's account names no other consumer product that scopes egress to the agent ^[21].

The sorting rule falls out of the coverage line. The question, call by call, is whether the receiving party needs to know who you are. A rendering check in another market, a public price lookup, a documentation fetch: identity is noise there, and a throwaway container per prompt is a reasonable default. Anything logged in is the other half. The session already names the user, so the exit address buys nothing, and on a store like Amazon's an unfamiliar non-residential address can be the reason the request is refused ^[15].