<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sandbox on Security Architects</title>
		<link>https://securityarchitects.com/tags/sandbox/</link>
		<description>Recent content in Sandbox on Security Architects</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 02 Oct 2026 12:00:00 -0700</lastBuildDate>
		
			<atom:link href="https://securityarchitects.com/tags/sandbox/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Eight components or eighty lines: two ways to keep an agent&#39;s secrets</title>
				<link>https://securityarchitects.com/post/eight-components-or-eighty-lines/</link>
				<pubDate>Fri, 02 Oct 2026 12:00:00 -0700</pubDate>
				<guid>https://securityarchitects.com/post/eight-components-or-eighty-lines/</guid>
				<description>&lt;p&gt;A reader asked how our agent sandbox and secrets scheme compare to&#xA;&lt;a href=&#34;https://github.com/onecli/onecli&#34;&gt;OneCLI&lt;/a&gt;, an open-source platform for&#xA;running AI agents as a team. Fair question, and the answer is more&#xA;interesting than &amp;ldquo;ours is better&amp;rdquo;, because on one axis theirs is, and&#xA;checking the comparison turned up a sentence on our own product page that&#xA;was not true.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-onecli-is&#34;&gt;What OneCLI is&lt;/h2&gt;&#xA;&lt;p&gt;A team control plane. One sandboxed agent per employee, provisioned from&#xA;your identity provider, under a team policy, with shared connections, memory,&#xA;scheduling, and a Slack identity each. It runs on your infrastructure. The&#xA;runner is outbound-only with no inbound ports, which is the same idea our&#xA;tunnel client uses to live behind NAT.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
