<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Provider-Agnostic on Elliot Belt</title><link>https://felixbillieres.github.io/tags/provider-agnostic/</link><description>Recent content in Provider-Agnostic on Elliot Belt</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>felix.billieres@ecole2600.com (Elliot Belt)</managingEditor><webMaster>felix.billieres@ecole2600.com (Elliot Belt)</webMaster><copyright>© 2026 Elliot Belt</copyright><lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://felixbillieres.github.io/tags/provider-agnostic/index.xml" rel="self" type="application/rss+xml"/><item><title>Credential-Blind Agentic Pentesting — Part I: Bidirectional Tokenization of Secrets, Identities and Topology</title><link>https://felixbillieres.github.io/posts/credential-blind-agentic-pentesting-part-1/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><author>felix.billieres@ecole2600.com (Elliot Belt)</author><guid>https://felixbillieres.github.io/posts/credential-blind-agentic-pentesting-part-1/</guid><description>I want an AI agent that can do offensive and defensive security work without ever leaking a credential, a hostname, an IP or a domain to the model provider, and to keep that property no matter which provider sits behind the API. This is Part I of the research. It covers the threat model, the state of the art, the core mechanism (bidirectional tokenization with host-side resolution), and four experiments that run on real HackTheBox machines, including an autonomous agent that drives a real domain controller while seeing nothing but opaque tokens.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://felixbillieres.github.io/posts/credential-blind-agentic-pentesting-part-1/featured.png"/></item></channel></rss>