<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web Security on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/web-security/</link><description>Recent content in Web Security 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/web-security/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><item><title>How Bot Attacks Drain Fintech Revenue — And How to Stop Them</title><link>https://www.eknix.com/blog/bot-attacks-fintech/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/bot-attacks-fintech/</guid><description>&lt;p&gt;Bots now account for nearly half of all internet traffic. But not all bots are created equal — and the ones targeting your fintech platform aren&amp;rsquo;t browsing. They&amp;rsquo;re working.&lt;/p&gt;
&lt;p&gt;They&amp;rsquo;re testing stolen card numbers against your payment API. They&amp;rsquo;re taking over customer accounts. They&amp;rsquo;re scraping your pricing data. They&amp;rsquo;re stuffing credentials until one works. And while they do it, they&amp;rsquo;re quietly draining your revenue, degrading your infrastructure performance, and eroding the trust your customers place in you.&lt;/p&gt;</description></item><item><title>Is Google reCAPTCHA a DDoS Defence? The Cost Math Says No</title><link>https://www.eknix.com/blog/recaptcha-ddos-cost/</link><pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/recaptcha-ddos-cost/</guid><description>&lt;p&gt;There&amp;rsquo;s a category of question that gets asked quietly in Slack channels and in private post-incident reviews: &amp;ldquo;could we just use reCAPTCHA to handle this?&amp;rdquo; It&amp;rsquo;s not an unreasonable instinct. Google reCAPTCHA is already deployed on most sites, it can challenge suspicious traffic, and it costs nothing for the first ten thousand requests. As a lightweight speed bump, it has its place.&lt;/p&gt;
&lt;p&gt;But &amp;ldquo;speed bump against DDoS traffic&amp;rdquo; and &amp;ldquo;speed bump against spam submissions&amp;rdquo; are very different things — and running reCAPTCHA into a volumetric attack has a financial profile that most teams haven&amp;rsquo;t priced out before they need to.&lt;/p&gt;</description></item></channel></rss>