<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on The Farah Stack</title><link>https://thefarahstack.com/tags/security/</link><description>Recent content in Security on The Farah Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thefarahstack.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Technical Analysis: IRREGULAR, Containment Failure, and What It Means for Agent Governance</title><link>https://thefarahstack.com/posts/irregular-containment-failure/</link><pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate><guid>https://thefarahstack.com/posts/irregular-containment-failure/</guid><description>&lt;p&gt;&lt;img src="https://thefarahstack.com/images/posts/irregular-containment-failure.png" alt="Containment failure"&gt;&lt;/p&gt;&#10;&lt;p&gt;If your eval can reach the open internet, it is not an eval. It is unsupervised deployment with better branding.&lt;/p&gt;&#10;&lt;p&gt;IRREGULAR sits in a weird place in the stack. Frontier labs hire it to run pre-deployment cyber evaluations: CTF-style scenarios, simulated corporate networks, multi-stage attack paths. The point is to measure whether a model can plan and execute real offensive campaigns before release. That work only works if the environment looks realistic. It also only works if &amp;ldquo;realistic&amp;rdquo; never becomes &amp;ldquo;actual production internet.&amp;rdquo;&lt;/p&gt;</description></item><item><title>OpenClaw: Full Danger Edition</title><link>https://thefarahstack.com/posts/openclaw-full-danger-edition/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://thefarahstack.com/posts/openclaw-full-danger-edition/</guid><description>&lt;p&gt;&lt;img src="https://thefarahstack.com/images/posts/openclaw-full-danger-edition.png" alt="OpenClaw"&gt;&lt;/p&gt;&#10;&lt;p&gt;OpenClaw is your local AI assistant that stays completely on your device with no cloud dependency. It runs on any operating system and platform, giving you full control without corporate oversight. Here is the unfiltered breakdown.&lt;/p&gt;&#10;&lt;h2 id="architecture-how-it-actually-flows"&gt;Architecture (how it actually flows)&lt;/h2&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;Messaging Channels&#10;(WhatsApp • Telegram • Slack • Discord • Signal • iMessage • Teams • Matrix • Google Chat • BlueBubbles • Zalo • WebChat…)&#10; ↓&#10;┌───────────────┐&#10;│ Gateway │ ← ws://127.0.0.1:18789&#10;│ │ sessions • presence • cron • config • tool router • webhook hooks&#10;└───────┬───────┘&#10; │&#10; ┌────┼────┐&#10; │ │ │&#10;Pi/RPC CLI UI / Apps&#10;Agent openclaw ├─ WebChat (browser lifeline)&#10; ├─ Control UI (admin dashboard)&#10; ├─ macOS menu bar (quick dopamine)&#10; └─ iOS / Android nodes (mobile eyes &amp;amp; ears)&#10;&#10; │&#10; ├─→ Tools (deep system reach)&#10; │ ├─ Browser (CDP + managed Chromium – full web control)&#10; │ ├─ Canvas (A2UI agent-driven visual workspace)&#10; │ ├─ Node actions (camera live feed, screen record, notify popups, location pings…)&#10; │ ├─ Cron / webhooks / session juggling&#10; │ └─ Skills (ClawHub registry – community poison or power)&#10; │&#10; └─→ LLMs (Claude Opus preferred, OpenAI backup, local LLMs, automatic failover)&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;A message arrives through any channel and gets routed to the Gateway. The Gateway decides what needs to happen next, then wakes the Pi/RPC agent or main agent. The agent uses tools and LLMs to process everything and sends the response back through the same path. It stays entirely local unless you deliberately configure remote access, which is the biggest gotcha — you will see later in the article.&lt;/p&gt;</description></item></channel></rss>