<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OWASP on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/owasp/</link><description>Recent content in OWASP on Eknix — Web security &amp; performance for the enterprise</description><generator>Hugo</generator><language>en-us</language><copyright>© {year} EKNIX LTD. All rights reserved.</copyright><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.eknix.com/tags/owasp/index.xml" rel="self" type="application/rss+xml"/><item><title>API Security in Ecommerce: What CTOs Get Wrong</title><link>https://www.eknix.com/blog/api-security-ecommerce/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/api-security-ecommerce/</guid><description>&lt;p&gt;Most ecommerce CTOs we talk to have a reasonable handle on their frontend security posture. WAF in place, DDoS protection sorted, bot management on the roadmap. The conversation gets uncomfortable when it turns to APIs.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not that they&amp;rsquo;re unaware. They know APIs need securing. The attack surface is just bigger than it looks, the tooling caught up later than it did on the web application side, and most API programmes have gaps nobody&amp;rsquo;s had time to close. Then on top of that, AI shopping agents have started hitting ecommerce APIs in volume over the last year, and that has changed what &amp;ldquo;normal&amp;rdquo; traffic even means.&lt;/p&gt;</description></item></channel></rss>