<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor-Compromise on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vendor-compromise/</link><description>Recent content in Vendor-Compromise on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jul 2026 11:51:11 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vendor-compromise/index.xml" rel="self" type="application/rss+xml"/><item><title>Ernst &amp; Young discloses data breach via support system hack</title><link>https://curasec.metacog.co.kr/insights/2026-07-18-ernst-young-discloses-data-breach-after-support-system-hack/</link><pubDate>Sat, 18 Jul 2026 11:51:11 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-18-ernst-young-discloses-data-breach-after-support-system-hack/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The breach originated through a third-party support ticketing system, illustrating a lateral entry path worth reviewing in your own vendor-managed tool integrations — no IOCs or TTPs published to act on yet.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> If EY is a vendor or auditor your organization uses, confirm whether your data was in scope and request EY&amp;rsquo;s incident report; brief leadership now, before this becomes a customer or auditor question.&lt;/li>
&lt;/ul></description></item></channel></rss>