<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Explanation on Webscale Product Documentation</title><link>https://docs.webscale.com/docs/explanation/</link><description>Recent content in Explanation on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/docs/explanation/index.xml" rel="self" type="application/rss+xml"/><item><title>About bot attacks</title><link>https://docs.webscale.com/docs/explanation/explanation-about-bot-attacks-commerce-sites/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/explanation/explanation-about-bot-attacks-commerce-sites/</guid><description>&lt;h2 id="what-attackers-are-trying-to-do"&gt;What attackers are trying to do&lt;/h2&gt;
&lt;p&gt;Most attacks we see on commerce sites are &lt;strong&gt;profit-driven&lt;/strong&gt;, not purely destructive.&lt;/p&gt;
&lt;p&gt;Broadly, attackers want to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Test stolen payment cards&lt;/strong&gt; to see which ones are still valid (carding).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Abuse business logic&lt;/strong&gt; such as coupons, loyalty points, or free-trial flows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Harvest data&lt;/strong&gt; from product catalogs or customer accounts.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The goal is nearly always to turn someone else’s infrastructure and payment flows into &lt;strong&gt;cheap testing infrastructure&lt;/strong&gt; for stolen data.&lt;/p&gt;</description></item><item><title>Security Stance On Unbutu Package Versions</title><link>https://docs.webscale.com/docs/explanation/explanation-security-stance-on-unbuntu-package-versions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/explanation/explanation-security-stance-on-unbuntu-package-versions/</guid><description>&lt;h2 id="introduction"&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;At Webscale, we prioritize the long-term stability and security of our customer environments. A frequent question arises: &lt;em&gt;&amp;ldquo;Why is Webscale using an older version of Nginx instead of the latest mainline release?&amp;rdquo;&lt;/em&gt; To understand our stance, one must understand the trade-off between &lt;strong&gt;feature velocity&lt;/strong&gt; and &lt;strong&gt;proven stability&lt;/strong&gt;, and how the Linux ecosystem manages security through a process called &amp;ldquo;Backporting.&amp;rdquo;&lt;/p&gt;
&lt;h2 id="the"&gt;&lt;strong&gt;The &amp;ldquo;Latest&amp;rdquo; vs. &amp;ldquo;Secure&amp;rdquo; Myth&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;In the world of consumer software (like phone apps), a higher version number almost always means better security. In enterprise server infrastructure, this isn&amp;rsquo;t always the case.&lt;/p&gt;</description></item></channel></rss>