<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor-Disclosure on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vendor-disclosure/</link><description>Recent content in Vendor-Disclosure on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 Oct 2026 15:44:28 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vendor-disclosure/index.xml" rel="self" type="application/rss+xml"/><item><title>Railway Platform Security Disclosure (Oct 21 2026)</title><link>https://curasec.metacog.co.kr/insights/2026-10-23-security-disclosure/</link><pubDate>Fri, 23 Oct 2026 15:44:28 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-23-security-disclosure/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your team deploys on Railway, read the full disclosure and assess whether any credentials, secrets, or deployed workloads require rotation or review; high community engagement (596 points) suggests the disclosure is substantive, but the summary provides no technical detail to judge scope.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A cloud deployment vendor issuing a public security disclosure warrants a vendor-risk check — confirm whether Railway is in your supply chain and, if so, request their incident report to assess any customer-data or credential exposure.&lt;/li>
&lt;/ul></description></item></channel></rss>