<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bigcommerce on microsegment.io</title>
    <link>https://microsegment.io/tags/bigcommerce/</link>
    <description>Recent content in Bigcommerce on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/bigcommerce/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Platform Was Not Breached. The Delegated Key Was.</title>
      <link>https://microsegment.io/post/2026-09-22-delegated-saas-key-containment/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-22-delegated-saas-key-containment/</guid>
      <description>&lt;p&gt;The SaaS platform can remain intact while a trusted application identity becomes the attack path.&lt;/p&gt;&#xA;&lt;p&gt;That is the important distinction in the recent BigCommerce and Ribon incident. &lt;a href=&#34;https://www.bleepingcomputer.com/news/security/bigcommerce-alerts-merchants-of-data-breach-linked-to-ribon-apps/&#34;&gt;BigCommerce told BleepingComputer&lt;/a&gt; that credentials belonging to the third-party Ribon and Ribon 1.5 applications were compromised. According to the statement, the credentials were used to inject malicious scripts into a small number of merchant storefronts. The reporting also says attackers accessed shopper data between September 13 and September 17, 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
