<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Security on Onur Baydaş</title><link>https://onurbaydas.online/en/tags/security/</link><description>Recent content in Security on Onur Baydaş</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://onurbaydas.online/en/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Authorization with OPA: The Silent Fail-Open and Other Production Lessons</title><link>https://onurbaydas.online/posts/docker-authz-opa-en/</link><pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate><guid>https://onurbaydas.online/posts/docker-authz-opa-en/</guid><description>The plugin looks enabled, the policy is correct, yet Docker allows everything. A silent security gap I hit with opa-docker-authz in production, and its lessons.</description></item></channel></rss>