<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Security - Tag - EONYX Blog</title><link>https://eonyx.tech/blog/tags/security/</link><description>Security - Tag - EONYX Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>eonyx.tech@proton.me (EONYX)</managingEditor><webMaster>eonyx.tech@proton.me (EONYX)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 26 May 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://eonyx.tech/blog/tags/security/" rel="self" type="application/rss+xml"/><item><title>EONYX permissions and security: control over every action</title><link>https://eonyx.tech/blog/eonyx-security/</link><pubDate>Tue, 26 May 2026 00:00:00 +0300</pubDate><author><name>EONYX</name></author><guid>https://eonyx.tech/blog/eonyx-security/</guid><description><![CDATA[<div class="featured-image">
                <img src="/blog/eonyx-security/cover.svg" referrerpolicy="no-referrer">
            </div><p>An agent that reads and edits code and runs commands must operate <strong>within explicit permissions</strong>. In EONYX security is several layers: a static gateway, a file sandbox, plan mode and a coarse block on dangerous commands. Let&rsquo;s go through each of them.</p>]]></description></item></channel></rss>