<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secure-Development on CuraSec</title><link>https://curasec.metacog.co.kr/tags/secure-development/</link><description>Recent content in Secure-Development on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 28 Aug 2026 21:21:40 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/secure-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Omarchy development practices lead to predictable security issues</title><link>https://curasec.metacog.co.kr/insights/2026-08-28-omarchy-development-practices-lead-to-predictable-security-i/</link><pubDate>Fri, 28 Aug 2026 21:21:40 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-28-omarchy-development-practices-lead-to-predictable-security-i/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Post-mortem style analysis of insecure development practices in a real project; worth reading to identify analogous patterns in your own dependency tree or internal tools, but no patch or immediate action required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>