<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stratus - Security Guides on Webscale Product Documentation</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/</link><description>Recent content in Stratus - Security Guides on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/docs/reference/stratus/guides/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Stratus Security Guides - Blocking Countries</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/block-countries/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/block-countries/</guid><description>&lt;p&gt;Webscale STRATUS gives you the ability to block traffic from selected countries.&lt;/p&gt;
&lt;p&gt;To block certain countries from accessing a Webscale STRATUS install, use &lt;strong&gt;&lt;a href="https://docs.webscale.com/reference/stratus/control-panels/access-panel/block-countries/" target="_blank"&gt;Access &amp;gt; Block Countries&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
&lt;/strong&gt; in the Webscale STRATUS Control panel.&lt;/p&gt;</description></item><item><title>Stratus Security Guides - Securing a Magento Store</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/securing-your-store/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/securing-your-store/</guid><description>&lt;p&gt;Regardless of these efforts, an e-commerce store remains accessible by the public-at-large and therefore can be subject to additional attempts to compromise security.&lt;/p&gt;
&lt;p&gt;To give your store additional protections,&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Don&amp;rsquo;t use the default admin or backend login path. Using &lt;strong&gt;/admin&lt;/strong&gt; is a common path too often used by hackers to make repeated attempts to gain access. Magento 2 automatically creates an obscure admin path. For Magento 1.x stores, the default &amp;ldquo;admin&amp;rdquo; path should be changes to a obscure value resembling a very secure password (e.g., &amp;ldquo;Uy49kkT&amp;rdquo; or &amp;ldquo;j87PenM&amp;rdquo;).&lt;/li&gt;
&lt;li&gt;Install all updates and patches. The &lt;a href="https://magento.com/security" target="_blank"&gt;Magento Security Center&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 is a Magento resource for recent and past updates. The community site, &lt;a href="https://magesec.org/" target="_blank"&gt;magesec.org&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
, has open source scanning and patching tools.&lt;/li&gt;
&lt;li&gt;Many sites hosted on Mojo STRATUS use WordPress for their blog feature. Using &lt;a href="https://docs.webscale.com/docs/reference/stratus/control-panels/nginx-panel/includes/"&gt;Nginx Includes&lt;/a&gt;
 or the built-in &lt;a href="https://docs.webscale.com/docs/reference/stratus/control-panels/access-panel/controlling-access/"&gt;STRATUS panel access restriction&lt;/a&gt;
, restrict the WordPress login by IP and prevent brute-force attacks.&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;location ~* /wordpress/wp-login.php$ {
 allow 1.1.1.1;
 try_files $uri $uri/ /index.php?$args;
 location ~* \.php$ { try_files /dummy @proxy; }
 deny all;
}
&lt;/code&gt;&lt;/pre&gt;&lt;ul&gt;
&lt;li&gt;Remove all extraenous files from the Magento web root. Extra database dumps, un-needed files and test scripts, and other code that isnt necessary for production is often left exposed.&lt;/li&gt;
&lt;li&gt;Use strong passwords!&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.webscale.com/docs/reference/stratus/guides/security/block-countries/"&gt;Block countries for which shipping is not available.&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Stratus Security Guides - Traffic Limits</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/stratus-traffic-limits/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/stratus-traffic-limits/</guid><description>&lt;p&gt;Certain services are restricted in terms of how much CPU and memory they can use to prevent memory leaks and other issues from affecting your site.  Services that need fluid limits, like PHP, are handled differently.&lt;/p&gt;
&lt;p&gt;The Redis, memcache, Nginx and Elasticsearch services all have lower memory limits with less than 4GB as a maximum. A majority of stores do not exceed them and our team can adjust them if needed.&lt;/p&gt;</description></item><item><title>SStratus Security Guides - Securing Magento 1.x against malware and brute force attacks</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/securing-magento-1-x-against-malware-and-brute-force-attacks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/securing-magento-1-x-against-malware-and-brute-force-attacks/</guid><description>&lt;p&gt;Our support team at Webscale can help implement any of the changes below to help protect your store.&lt;/p&gt;
&lt;p&gt;To help protect your store against attacks, do the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Change the admin path&lt;/strong&gt; from &lt;em&gt;/admin&lt;/em&gt; to something less obvious. This is adjusted in the &lt;code&gt;local.xml&lt;/code&gt; file near the bottom. Change the &lt;strong&gt;frontName&lt;/strong&gt; variable and clear the Magento cache.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Password or IP restrict the downloader&lt;/strong&gt; using the Webscale STRATUS &lt;strong&gt;[Access &amp;gt; Protect URL][2]&lt;/strong&gt; panel access restrictions or a &lt;code&gt;.htaccess&lt;/code&gt; file. The downloader can also be moved out of the Magento web root completely when not actively using Magento Connect.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Update Magmi&lt;/strong&gt;, as older versions of Magmi are unsecure and can allow remote users to upload files for remote execution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep any WordPress installations up to date&lt;/strong&gt; within the Magento web root. WordPress plugins can often be found to introduce or allow malware.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Apply any missing patches for your store&lt;/strong&gt;. Our support can help apply these for you. Most Magento 1.x patches are **critical **to security&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="further-securing-your-magento-admin"&gt;Further securing your Magento admin&lt;/h2&gt;
&lt;p&gt;If changing the admin path is not sufficient, it is also possible to IP restrict it entirely. Contact stratus-support@webscalenetworks.com for details on how to restrict this.&lt;/p&gt;</description></item><item><title>Stratus Security Guides - External CDNs and Firewalls</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/using-external-services/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/using-external-services/</guid><description>&lt;h2 id="whitelisting-validation-for-sucuri"&gt;Whitelisting Validation for Sucuri&lt;/h2&gt;
&lt;p&gt;When using Sucuri&amp;rsquo;s firewall that adds a JS protector in front of the site, whitelist a specific path for our validation to work properly. Whitelisting this path will not compromise the protection on the rest of your site. Our validator uses a simple curl request and cannot process Sucuri&amp;rsquo;s JS.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Note&lt;/em&gt; the UUID of your Webscale STRATUS instance.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Go to&lt;/em&gt; &lt;strong&gt;Info&lt;/strong&gt; panel in the Webscale STRATUS Admin panel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Account Name&lt;/strong&gt; is the &lt;em&gt;UUID&lt;/em&gt; of the install.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Log into&lt;/em&gt; the Sucuri.net account&lt;/p&gt;</description></item><item><title>Stratus Security Guides - OSCP Stapling</title><link>https://docs.webscale.com/docs/reference/stratus/guides/security/oscp-stapling/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/security/oscp-stapling/</guid><description>&lt;p&gt;According to Amazon Web Services:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;When a viewer submits an HTTPS request for an object, either CloudFront or the viewer must confirm with the certificate authority (CA) that the SSL certificate for the domain has not been revoked. OCSP stapling speeds up certificate validation by allowing CloudFront to validate the certificate and to cache the response from the CA, so the client doesn&amp;rsquo;t need to validate the certificate directly with the CA.&lt;/p&gt;</description></item></channel></rss>