<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Wallarm on Medium]]></title>
        <description><![CDATA[Stories by Wallarm on Medium]]></description>
        <link>https://medium.com/@wallarm?source=rss-78984bf6a74f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kaNWjE49-4LnIRdg.png</url>
            <title>Stories by Wallarm on Medium</title>
            <link>https://medium.com/@wallarm?source=rss-78984bf6a74f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:34:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wallarm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What The Actual WAF!?]]></title>
            <link>https://medium.com/wallarm/what-the-actual-waf-94c6735c1d12?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/94c6735c1d12</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Wed, 09 Oct 2019 04:59:05 GMT</pubDate>
            <atom:updated>2019-10-09T04:59:05.608Z</atom:updated>
            <content:encoded><![CDATA[<h4>InfoSec Family, we need to talk!!</h4><p>Every so often, there is a technological shift in the information security industry. Sometimes it is due to new cyberattack discovery, aka a Zero-day. Many times, the catalyst is legacy technology. When a legacy technology no longer adequately responds to the technological world around it, it is simply time to evolve. The recent increase in Web Application Firewall (WAF) related incidents make the writing on the wall clear: <em>Evolve or suffer!</em></p><p>InfoSec family! We need to come together and have a rather overdue discussion. Legacy WAFs live in the dark ages of security. On <a href="https://hubspot.wallarm.com/waf-security-considerations">October 10th at 10 am PST /1 pm EST</a>, we will have this conversation. Global strategist, <a href="https://www.linkedin.com/in/kavya-pearlman">Kavya Pearlman</a>, will moderate the discussion with two of the industry’s experts, <a href="https://www.linkedin.com/in/alissaknight">Alissa Knight</a> and <a href="https://www.linkedin.com/in/d0znpp">Ivan Novikov</a>.</p><p>Alissa Knight is a senior analyst with Aite Group’s cybersecurity practice. Ms. Knight covers cybersecurity in financial services, serving as a thought leader and trusted advisor to financial institutions, established technology vendors, startups, and venture capital firms. She has worked in cybersecurity for over 20 years as a penetration tester and incident responder, is a published author, was featured in the well known Brian Krebs Imperva data breach article for having a unique take and intimate knowledge of the incident.</p><p>This promises to be one of the most significant discussions around WAFs in a long time. If you care about application security, don’t miss this opportunity. It is more than just another webinar. It is an honest conversation that we, as an Information Security family, have never had. Let’s change that. Traditional Web Application Firewalls are failing us, resulting in security incidents and data breaches. We have to ask, <em>What happens when a Security product becomes the source of a security breach?</em></p><p>The following quote from DevSecOps Manifesto serves as an important reminder to all of us in InfoSec:</p><p><em>“We must adapt our ways to ensure data security and privacy issues are not left behind because we were too slow to change.” — DevSecOps Manifesto</em></p><p>In our discussion, <em>What the Actual WAF?!</em>, we will reflect on a few key points:</p><ul><li>The evolution of WAFs</li><li>Recognizing that legacy WAFs are inadequate</li><li>Critical lessons from recent security incidents</li><li>Imperva Security Incident (Aug 2019)</li><li>Cloudflare Outage (July 2019)</li><li>Capital One Data Breach (July 2019)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*uOAbLNCFJ_ZQhY2e" /></figure><p>Fig -1: Evolution of Web Application Firewall</p><p>Our conversation needs to cover all the bases — configuration issues, high rate of false positives, evasion of WAF, insider threats, Reg-Ex Based rules, and a whole bunch of other challenges surrounding WAFs.</p><p>Solutions do exist. Before we can properly recognize and apply them, we need to come to terms with the inadequacies that are currently taking up space in modern security landscapes. Consider it a scarcity for resources issue; we need to kick out the solutions that are no longer functioning to give ample room for the advanced WAF solutions. Join us in this discussion. Let’s think through how we can do better? Let’s explore what the consequences are if we don’t. As an industry, we need this moment of self-reflection and improvement.</p><p>Register now for <a href="https://hubspot.wallarm.com/waf-security-considerations"><em>What the Actual WAF!?</em></a></p><p>Can’t make it to the webinar? Sign up and we will send the slides afterward!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94c6735c1d12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/what-the-actual-waf-94c6735c1d12">What The Actual WAF!?</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wallarm connector to Apigee]]></title>
            <link>https://medium.com/wallarm/wallarm-connector-to-apigee-d45f9e38cd4e?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d45f9e38cd4e</guid>
            <category><![CDATA[apigee]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[api-security]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Sat, 28 Sep 2019 01:55:31 GMT</pubDate>
            <atom:updated>2019-09-28T01:55:31.996Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are a business undergoing a digital transformation, like Walgreens, Nike or Bechtel, heavy reliance on APIs is a key part of that digital transformation strategy.</p><blockquote>“The growing demand for information, delivered securely at any time, in any place and on any device has changed the way we think about applications — APIs are a critical part of our go forward strategy for meeting and exceeding our global business needs.” — Christian Reilly, BECHTEL CORP</blockquote><p>Since 2009, <a href="https://cloud.google.com/apigee/">Apigee</a> (now a subsidiary of <a href="https://about.google/intl/en_us/">Google</a>) played a significant role in making API management, monetization and metering easier and more scalable for the enterprises. Apigee is, rightfully, the most popular API gateway on the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMUKuUu6guakT8chOOBcZA.png" /></figure><h3>Security on Apigee — good but not complete</h3><p>In recent years it became obvious true digital transformation can only happen when the API design and application security come in lock-step. (The topic of API security is addressed in a recent Wallarm whitepaper, <a href="https://wallarm.com/resources/top-five-challenges-protect-api">Top Five Challenges Protecting APIs</a> )</p><p>Apigee has introduced many new security features to improve the security posture for their customers. Features such as encryption, certificate-based authentication, and role-based access control go a long way to satisfy compliance requirements and follow security best practices.</p><p>Apigee Edge. However, Apigee is an API gateway and not an especially built security product. According to Apigee,</p><blockquote><em>“Using the Apigee platform itself does not guarantee protection against issues identified by the </em><a href="https://www.owasp.org/"><em>Open Web Application Security Project (OWASP)</em></a><em>”.</em></blockquote><p>Product documentation further advises:</p><blockquote><em>“To protect APIs, Apigee provides several policies out of the box, such as rate limiting and spike arrest, along with other policies that can be custom developed for specific use cases.”</em></blockquote><p>These custom-developed use-case policies are defined as regular expressions. Apigee Edge allows developers to define explicit predefined regular expressions. The content of the API message sections URI Path, Query Param, Header, Form Param, Variable, XML Payload, or JSON Payload is evaluated against these regular expressions.</p><p>Unfortunately, this approach is fraught with the same problems and other common RegEx-based WAFs, like ModSecurity:</p><ul><li>Common WAFs require laborious creation, maintenance and continuous reconciliation of the regular expressions. <br>Below is an example of just one regular expression defined to detect a specific SQL Injection in the URI path. It obviously give a lot of room for making a mistake.</li></ul><pre>&lt;RegularExpressionProtection async=&quot;false&quot; continueOnError=&quot;false&quot; enabled=&quot;true&quot; name=&quot;Regular-Expression-Protection-1&quot;&gt;</pre><pre>&lt;DisplayName&gt;Regular Expression Protection 1&lt;/DisplayName&gt;&lt;Source&gt;response&lt;/Source&gt;&lt;IgnoreUnresolvedVariables&gt;false&lt;/IgnoreUnresolvedVariables&gt;</pre><pre>&lt;URIPath&gt;<br>    &lt;Pattern&gt;<br>[\s]*((delete)|(exec)|(drop\s*table)|(insert)|(shutdown)|(update)|(\bor\b))<br>    &lt;/Pattern&gt;<br>&lt;/URIPath&gt;</pre><pre>&lt;/RegularExpressionProtection&gt;</pre><ul><li>Detection itself is not always possible for complicated, nested or embedded API protocols. If the pattern is encoded with base64 encoding, for example, regular- expression detection would not be effective.</li><li>Anomalies in the length of parameters, number/depth of elements (JSONThreatProtection and XMLThreatProtection) and other advanced attacks cannot be detected.</li></ul><h3>Wallarm and Apigee</h3><p>Now customers who are concerned about the run-time API security can rely on Wallarm using newly developed integration of Wallarm AI-Powered Application Security platform with Apigee. You can get unprecedented visibility on malicious traffic coming to your XML and JSON based APis running on Apigee gateway.</p><blockquote><em>Says one of the early adopters of the Wallarm Apigee Extension,</em> “We are using Wallarm instead of configuring Apigee RegularExpressionProtection policy manually. The attack detection is accurate and automatic — and we don’t have to spend time on adjusting and redefining regular expressions on Apigee.”</blockquote><p>Deployment architecture assume asynchronous mode where Wallarm Node analyzes requests for malicious content but doesn’t affect traffic flow. There is no potential impact on the performance and additional latency introduced.</p><p>The integration is configured under <strong>Develop -&gt; API Proxy</strong> setting. Develop section is where you would also find configuration options for Apigee’s standard <strong><em>JSONThreatProtection</em></strong> and <strong><em>XMLThreatProtection</em></strong> as well as <strong><em>RegularExpressionProtection</em></strong><em> </em>policies. Wallarm JS-based extension is also added in this section.</p><p>The extension would redirect a copy of the traffic to Wallarm Node for automated analysis. IP of this node would be set in the source code of JS-connector. For this system to work, you will also need to deploy Wallarm node. The node can be deployed as a Docker container, virtual machine or any other available deployment options. The node would then parse the request, apply attack detection techniques and provide visibility in Wallarm Console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/0*PGPt69lEWWr9sYzw" /></figure><h3>Protect your Apigee now</h3><p>If you’re using Apigee and interested in participating in the evaluation program, please reach out to us at <a href="/service/mailto:request@wallarm.com">request@wallarm.com</a> or sign-up here: <a href="https://us1.my.wallarm.com/signup">https://us1.my.wallarm.com/signup</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d45f9e38cd4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/wallarm-connector-to-apigee-d45f9e38cd4e">Wallarm connector to Apigee</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Autoscaling Wallarm Nodes in AWS, GCP, and Azure]]></title>
            <link>https://medium.com/wallarm/autoscaling-wallarm-nodes-in-aws-gcp-and-azure-32b7562d1070?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/32b7562d1070</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[autoscaling]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 00:20:04 GMT</pubDate>
            <atom:updated>2019-09-25T00:20:04.694Z</atom:updated>
            <content:encoded><![CDATA[<p>Newly updated Wallarm Node images now natively support autoscaling capabilities in AWS, GCP, and Azure. Updated images are already available in cloud provider marketplaces and can rely on the native auto-scaling to adjust the number of nodes based on traffic, CPU load, and other parameters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dH__hMaZOKOO6Zf4Xy-wTQ.jpeg" /></figure><h3>What is Autoscaling?</h3><p>Many of our customers rely on autoscaling capabilities to horizontally scale their apps and APIs. Autoscaling mechanisms monitor your applications and automatically adjust capacity to maintain steady, predictable performance at the lowest possible cost.</p><p>Earlier releases already had the capability to automatically scale out Wallarm Nodes based on things like the load with native support of Kubernetes. Now, you can also dynamically add an additional node or remove underutilized ones using the native autoscaling mechanism of AWS, GCP, and Azure.</p><p>Native autoscaling is supported in Wallarm Node 2.12.0+. Find the images in <a href="https://aws.amazon.com/marketplace/pp/B073VRFXSD">Amazon Web Services</a>, <a href="https://console.cloud.google.com/marketplace/details/wallarm-node-195710/wallarm-security-platform?filter=solution-type:vm&amp;filter=price:byol&amp;filter=category:monitoring&amp;id=cc0beec4-8ef5-4b65-912f-6b156f4e8493&amp;pli=1">Google Cloud Platform</a>, and <a href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wallarm.wallarm-ng-waf-offer-1?tab=Overview">Microsoft Azure</a> marketplaces.</p><h3>Setting Up Autoscaling (AWS Example)</h3><p>Let’s take a look at setting up <a href="https://aws.amazon.com/autoscaling/">autoscaling in AWS</a>.</p><p>You can scale the number of instances based on several standard load parameters, including:</p><ul><li>the utilization of CPU; and</li><li>the amount of inbound/outbound traffic, etc.</li></ul><p>For example, in AWS you can set up the following policy for a group of Wallarm Node instances:</p><blockquote>If Average CPU Utilization exceeds 60% for over 5 min then add 2 more nodes.</blockquote><p>These are the steps required to set up autoscaling in AWS.</p><h4>1. Create an Autoscaling Group.</h4><ul><li><strong>Create a launch template.</strong> A launch template defines the instance type to be used during the deployment of an AMI and sets up some of the general virtual machine parameters. You need to choose the AMI of Wallarm Node that supports autoscaling.</li><li><strong>Create an Autoscaling Group.</strong> An Autoscaling Group is a group of instances that will scale out with the chosen scaling policy. You can configure the group size increase policy using the “Increase Group Size” parameter group as well as “Decrease Group Size”. Here are some of the variables AWS supports for autoscaling: CPU Utilization (in percentages); Network In (in bytes); and Network Out (in bytes).</li></ul><h4>2. Set up a load balancer for the Autoscaling Group.</h4><ul><li><strong>Create a load balancer.</strong> Once you have configured a filter node Autoscaling Group, you need to create and configure a load balancer that distributes incoming HTTP and HTTPS connections among several filter nodes from the Autoscaling Group.</li><li><strong>Set up an Autoscaling Group for using the created balancer. </strong>Configure your Autoscaling Group for using the load balancer you created earlier. This will allow the balancer to route traffic to the filter node instances that are launched in the group.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/0*8R64IoClunN-v8tX" /></figure><h3>Try It Now</h3><p>Detailed tutorials on how to set up autoscaling are available in Wallarm Docs for:</p><ul><li><a href="https://docs.wallarm.com/en/admin-en/installation-guides/amazon-cloud/autoscaling-overview.html">AWS</a></li><li><a href="https://docs.wallarm.com/en/admin-en/installation-guides/google-cloud/autoscaling-overview.html">GCP</a></li><li><a href="https://docs.wallarm.com/en/admin-en/installation-azure-en.html">Azure</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32b7562d1070" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/autoscaling-wallarm-nodes-in-aws-gcp-and-azure-32b7562d1070">Autoscaling Wallarm Nodes in AWS, GCP, and Azure</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defining Wallarm API-specific Rules]]></title>
            <link>https://medium.com/wallarm/defining-wallarm-api-specific-rules-2d9f5523650?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d9f5523650</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Tue, 23 Jul 2019 18:25:27 GMT</pubDate>
            <atom:updated>2019-07-25T00:13:00.044Z</atom:updated>
            <content:encoded><![CDATA[<h4>Case Study Using SugarCRM API As an Example</h4><p>A unique Wallarm AI feature is its ability to automatically detect and parse complicated API protocols and then set up security rules based on specific data or parameters deep inside the API.</p><p>Once parsed, the system creates the rules-based both on where in the HTTP request a specific set of data or a parameter is found and the actual data within the parameter.</p><p>The API parameters within the HTTP request are used in a number of security controls — from clusterization used to determine the application context and logic, to deep learning to setting rules specific to API-endpoints, triggered by the explicit data matches.</p><p>The technology can protect from lax input validation, behavioral attacks, and various threats.</p><p>That said, in some situations, it makes sense to input API definitions by hand. This approach can help if there is insufficient traffic to serve as a learning set or if you want to compare the rules that you enter manually and their business logic to what was set up automatically. In this article, we’ll show a step-by-step example of how it can be done.</p><h3>SugarCRM and its API</h3><p>To illustrate how the tandem parsing and rule-setting works, let’s look at a popular contact management application, SugarCRM. SugarCRM has no formally defined API description, like Swagger. So, the only way to understand the API parameters is to parse it manually from the HTML docs available <a href="https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.9/Integration/Web_Services/v10/Endpoints/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/0*_7TdvxoMbNQYnR8o" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*3JwtiYz4K-FhJnwi" /></figure><p>We parse that HTML-formatted doc by a simple curl+egrep combination followed below:</p><pre>$ curl -s https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.9/Integration/Web_Services/v10/Endpoints/ -o - | gunzip | egrep -o &#39;&gt;/[^GET|POST]+ (GET|POST)&#39; | tr &#39;&gt;&#39; &#39; &#39; &gt; sugarcrm.rest.endpoints</pre><p>This command gives us a list of all the 149 REST endpoints described there. It’s like this:</p><pre>/Accounts/:record/link/:link_name/filter GET<br>/Activities GET<br>/Activities/filter GET<br>...<br>/&amp;lt;module&amp;gt;/temp/file/:field POST<br>/&amp;lt;module&amp;gt;/temp/file/:field/:temp_id GET<br>/mostactiveusers GET<br>/oauth2/bwc/login POST<br>/oauth2/logout POST<br>/oauth2/sudo/:user_name POST<br>...<br>/theme GET<br>/theme POST</pre><p>As you can see, we have two ways of variable parameters representation here: :name and &lt;module&gt;. The second one means the list and the first one means one of the data types. To simplify, I want to avoid any conditions for those kinds of parameters and define the endpoints by static REST URL parts only.</p><h3>Understanding Wallarm API Endpoint Rules</h3><p>Now, it’s time to parse the list we got and create related endpoints at Wallarm API.</p><p>First, we need to parse URL from SugarCRM docs to extract parts of paths from there. So, it’s basically a split by /delimiter.</p><p>At this point, we can understand Wallarm requests representation a little bit. Wallarm processes requests by parsing them into a serialized format that covers everything, including data encodings like JSON, XML, Base64, Multipart, etc. Inside this serialized representation of the HTTP request, every single parameter can be accessible by a unique key that consists of ordered sequences of parsers and parameters’ names. For example, to identify the data of ?aaa=xxx URL parameter, we can describe the key GET_aaa_value (in a string form), or [&quot;GET&quot;, &quot;aaa&quot;, &quot;value&quot;] in an array form. These keys equal to coordinates of request data inside HTTP requests called <strong>points</strong> in the Wallarm API.</p><p>To describe API endpoint, we need to define some points and conditions for the data there. In fact, different parts of URL should be matched by some strings to make the decision that a particular request targets a particular API endpoint. These decisions are called actions in Wallarm API.</p><p>So, to describe the API endpoint for the/rest/v10/&lt;param&gt;/link we need to give Wallarm a hint as to how these requests could look. To do this, we can send a JSON request that looks like this:</p><pre>POST /v1/objects/hint/create<br>...<br>{ &quot;type&quot;:&quot;tag&quot;,<br>  &quot;name&quot;:&quot;API-type&quot;,<br>  &quot;value&quot;:&quot;REST&quot;,<br>  &quot;clientid&quot;:client_id,<br>  &quot;action&quot;:[<br>    { &quot;type&quot;:&quot;equal&quot;, &quot;value&quot;:&quot;rest&quot;, &quot;point&quot;: [&quot;path&quot;,0] },<br>    { &quot;type&quot;:&quot;equal&quot;, &quot;value&quot;:&quot;v10&quot;,  &quot;point&quot;: [&quot;path&quot;,1] },<br>    { &quot;type&quot;:&quot;equal&quot;, &quot;value&quot;:&quot;link&quot;, &quot;point&quot;: [&quot;path&quot;,3] }<br>   ],<br>  &quot;validated&quot;:true,}</pre><p>As you can see below, the action consists of three different conditions that should match and we have no condition for the third part of the URL ([&quot;path&quot;, 2] point because 0 is the first index in arrays). Type, name, and value parameters related to the type of hint we want to give Wallarm AI, (and it’s just a “tag” hint) serve nothing more than to mark this kind of traffic for later use.</p><p>The easiest way to do generate these hints automatically is using all the list exported from SugarmCRM documentation by making a short script, like this:</p><pre>#!/usr/bin/python</pre><pre>import sys<br>import re<br>import json<br>import requests</pre><pre>UUID= &quot;&quot; #if you don’t know your own, please ask support team or check console.wallarm.com<br>secret = &quot;&quot;<br>client_id = 31337</pre><pre>API_URL = &quot;https://us1.api.wallarm.com/v1/objects/hint/create&quot;</pre><pre>line = sys.stdin</pre><pre>for line in sys.stdin:<br>    parts = []<br>    parts = re.split(&#39;/|\s&#39;, line)<br>    parts.insert(0, &quot;rest&quot;)<br>    parts[1] = &quot;v10&quot; #for some reason, all the SugarCRM endpoints provided in their documentation without API URL prefix<br>    parts = parts[:-2] # cut first 2 and last 2 elements from the list<br>    points = []<br>    for i in range(len(parts)):<br>        if not re.match(&quot;[^0-9a-zA-Z\_]&quot;, parts[i]): #check if the REST URL part is static or variable (parameter)<br>         cur_point = {&quot;point&quot;:[],&quot;type&quot;:&quot;equal&quot;}<br>         cur_point[&quot;point&quot;].append(&quot;path&quot;)<br>         cur_point[&quot;point&quot;].append(int(i))<br>         cur_point[&quot;value&quot;] = parts[i]<br>         points.append(cur_point)<br>   api_request = {&quot;type&quot;:&quot;tag&quot;,&quot;clientid&quot;:client_id,&quot;validated&quot;:False,&quot;name&quot;:&quot;API-type&quot;,&quot;value&quot;:&quot;REST&quot;}</pre><pre>   api_request[&quot;action&quot;] = points<br>   print(json.dumps(api_request, separators=(&#39;,&#39;, &#39;:&#39;))</pre><pre>r = requests.post(<br>     url = API_URL,<br>     headers = {<br>         &quot;X-WallarmAPI-UUID&quot;:    UUID,<br>         &quot;X-WallarmAPI-Secret&quot;:  secret<br>         },<br>     json = api_request)</pre><pre>print(r)</pre><p>Using this is a great shortcut. We can check the results at the Wallarm interface. There we can ensure we really helped the machine learning engine to understand our REST API better:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*JeSn1T3_CR2AXxEUgHAAPg.png" /></figure><h3>API Security is Critical for DevSecOps</h3><p>APIs represent the core set of functionality for modular applications today. Their growth insignificance, impact, and sheer volume are unstoppable and practically unimaginable in scale. Because most legacy WAFs can only create security rules based on the source and destination URLs, they miss most of the potential API attacks leaving you significantly exposed.</p><p>We have shown you an example of how to work with strong API endpoint rules — whether generated manually or automatically with the help of machine learning — to create deeper protection. Security has to be able to reach deeper into APIs and truly understand their parameters to effectively protect against threats and vulnerabilities. Security solutions have to be able to truly understand the data and, also, the context and logic. All are subject to change at higher and higher rates, so this mission is only increasing in volume and complexity. Humans need helpful tools for intelligent automation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d9f5523650" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/defining-wallarm-api-specific-rules-2d9f5523650">Defining Wallarm API-specific Rules</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Threat Modeling in Cybersecurity to Hunt and Remediate]]></title>
            <link>https://medium.com/wallarm/using-threat-modeling-in-cybersecurity-to-hunt-and-remediate-2fd41b3abd2e?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fd41b3abd2e</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Sat, 18 May 2019 00:41:48 GMT</pubDate>
            <atom:updated>2019-05-18T00:41:48.761Z</atom:updated>
            <content:encoded><![CDATA[<p>Modern-day cyberattacks keep growing in sophistication and sheer volume. This dynamic makes it virtually impossible to detect and block all attacks using the traditional methods of comparing incoming requests to known attack signatures. To effectively operate in this new aggressive cyberthreat environment, it is paramount that IT operations, developers, and DevSecOps adopt a proactive defense mindset. Threat hunting is all about having that powerfully proactive mindset. The underlying goal of threat hunting is to detect, evaluate, and mitigate threats before they can impact core operational functions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tbHqypX_ydvA2JLU" /><figcaption>Threats can hide inside, taking their time to infiltrate and attack.</figcaption></figure><p>In this post, we will suggest a methodology of remediating threats based on the technique called Threat Modeling.</p><h3>Threat Hunting Methodology</h3><p>From a 1000-foot view, threat hunting methodology is not hard. As with most critical situations, your time is scarce and the information is insufficient. The methodology follows an Assess, Prioritize, Address flow.</p><p>It goes something like this:</p><ul><li>Understand new threats</li><li>Assess potential impact, or risk, of the new threats</li><li>Model the threats to determine where they may impact the software or the business process and prioritize risks</li><li>Implement protection measures and mitigating controls</li><li>Assess how effective the protection is</li><li>Repeat periodically as the threat landscape and your infrastructure change</li></ul><p>Lets dive in.</p><h3>New Generation of Threats for Cybersecurity</h3><p>Only one thing about tomorrow is certain: the cybersecurity threat landscape is under siege by a new, more sophisticated and challenging type of attacker than ever before. They are different than previous generations of hackers. New attacks will be stealthier and grow more covert every year. New threat vectors are coming, adding to a growing tally of variants from existing threats. Newer forms of phishing attacks, ransomware, social engineering, and even cryptojacking will proliferate — to name only a few. The key difference in the way attacks are launched than in previous years is in the modus operandi of the new hacker. Sophomoric attacks, like “Smash and Grab” campaigns, are gone. The new cyberattacker is patient and deliberate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvs-IXmo_q_241ucyeagjQ.jpeg" /><figcaption>Be vigilant about security so backdoors and deeper layers aren’t exploited by hackers.</figcaption></figure><p>The new cyberattacker takes their time to select a target (or victim) and study it completely for any unknown weaknesses and vulnerabilities. They determine the best possible backdoor in which they can enter into their target and stay in for longer periods of time than ever before. If the earlier cyberattacker could be likened to cat burglars, then the new cyberattacker could be likened to a cartel.</p><p>A cyberattacker may not stay in the confines of their target for months on end. They may leave and penetrate it again later via the backdoor that they left ajar. The point is that they now have the ability to go undetected for long periods of time. Rather than trying to take what they want all at once, they bleed their victim bit by bit.</p><p>The long game of residing in a hack, means businesses and corporations need to maintain the highest levels of alertness to track down the most covert cyberattackers before even the beginning stages of an attack can occur. A constant regimen of <a href="https://digitalguardian.com/blog/what-does-cyber-threat-hunter-do">Threat Hunting activities</a> by your IT security staff is a winning strategy.</p><h3>Understand What Is Vulnerable</h3><h4>Threat and Vulnerability Management</h4><p>Not all assets are vulnerable to all threats. First, you need to make sure your most critical assets are protected. Implement a classification schema in order to determine what is most at risk in your existing IT Infrastructure. All assets need to examined. But, in this case, you are using a top-down approach by classifying items that are at extremely high risk down to those assets that are least at risk.</p><h4>Identity Management</h4><p>Determine the identification mechanisms implemented (or planned for implementation) for employees or other parties trying to gain access to shared network resources.</p><p>Examples of identity management mechanisms are password managers, two-factor authentication (2FA), and biometrics (like fingerprint or voice recognition).</p><h4>Security Awareness Training and Education</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_biV1SMROdqgVzroi7bqQ.jpeg" /><figcaption>Work-life imbalance, wfh, remote workers, and vacations can leave devices vulnerable to hackers w/o the right security protocols and tools.</figcaption></figure><p>Evaluate the comprehensiveness of employee awareness and training in security best practices and policies. Everyone in the company plays a role in protecting IT resources — from on-premise use to mobile devices and laptops. Firmly relay the need for compliance and clearly explain the policies surrounding noncompliance or improper use of company resources.</p><p>Auditing your security awareness and training should include looking at internal traffic. Check that high-traffic areas are being properly secured and used with appropriate rights and permissions.</p><p>The line between work-life and personal time blur in the age of smartphones and remote work. Ensure that user practices, technology, and companywide policies are aligned is not solely in the hands of an isolated security team.</p><h4>Security Policy</h4><p>Periodic scrutiny of existing security policies that support security awareness and compliance is critical. Check whether security is being enforced. Address any weaknesses. Regular updates should be released, reflecting the current threat environment and organizational needs.</p><h4>Incident Response Plan</h4><p>Your company should have an <a href="https://www.incidentresponse.com/a-guide-to-creating-an-incident-response-plan/">Incident Response Plan</a>, which needs to be regularly updated and reviewed as part of threat hunting and remediation.</p><p>Check:</p><ul><li>Update frequency of the Incident Response Plan</li><li>Adoption and practice in real time</li><li>Employee contact information roster is correct</li><li>Effectiveness of the communications subcomponent</li></ul><h3>Review Existing Protections</h3><p>The meat of threat hunting is in auditing the existing IT infrastructure and security architecture. This is, objectively, the most complex part of the assessment and should be the most comprehensive.</p><p>A full audit of your existing monitoring tools identifies vulnerabilities and weaknesses. Assessing your security architecture will be sure that issues can be identified, the overall infrastructure has no holes, and that the most efficient solutions and tools for handling the threat landscape is in place.</p><h4>Security Management</h4><p>Part of establishing good protection is ensuring that your security team has an adequate ratio of staffing and resources, including up-to-date monitoring tools and support.</p><p>Incorporate security performance evaluations into your threat hunting process. Clearly defined responsibility and reviewing what the pain points and places for improvement are for the response teams can help address shortfalls and vulnerabilities that occur when teams are overextended or underperforming.</p><h4>Emerging Security Technologies</h4><p>Prioritize advances in tools and technology with every threat remediation activity. Newer security tools include incident response features that identify existing and impending threats. They arise from responsive industry specialization that looks into the consequences and weaknesses that come with technological growth. Attackers exploit weaknesses. Attack prevention is more complete with technologies as up-to-date with the current threat environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sO7jBrNOVBwbvvfbdkvetg.jpeg" /><figcaption>Know your threat landscape and equip yourself with the right, up-to-date security tools.</figcaption></figure><p>For example, the growth of APIs to keep business responsive to markets demanding rapid CI/CD means stronger protection at the API level (Layer-7 protection) is of new and paramount importance. Technology becomes more specialized as a technological landscape gets bigger.</p><p>Conducting a financial audit that aligns with your security audit can ensure critical financial resources are applied in the most cost-effective manner.</p><p>Evaluating the security budget and technology doesn’t mean “spend more”. It means evaluating whether money is being spent effectively in relation to the level of security you have. A budget review should evaluate:</p><ul><li>Are the tools I have the most up-to-date?</li><li>Are there new options that expose and prioritize new vulnerabilities or solutions?</li><li>Is our internal CI/CD impacting our security?</li></ul><p>It is crucial to question, the impact of CI/CD cycles. Rollouts that come at the cost of security can lead to high-cost recovery after an attack or breach.</p><p>Dispelling the myth that more security toys is better is also critical. The marketplace or a legacy of security solutions is not the same as having a fully defended infrastructure. In fact, more solutions piled onto one another can increase the attack surface for a cyberattacker.</p><h4>Third-Party Entities, Technology, and Services</h4><p>Outsourced entities conducting your daily business, accessing your systems, carry risks. Audit hiring practices of third parties that have any potential security risk. Increasing the due diligence around hiring criteria, processes, and background checks can reduce company vulnerability to an inside job. It’s also important that hired third parties, like contractors, are part of security training and awareness.</p><p>Once this Risk Assessment has been completed, the next step in any Threat Hunting Remediation exercise is determining what to exactly hunt for and the frequency of that hunt.</p><h3>Select a Threat Model to Use</h3><p>After performing a risk assessment, you should have a documented list of the kinds of threats and risks to hunt for. You are now ready to apply the list to one of four threat hunting models.</p><h4>Four threat hunting models:</h4><ul><li><a href="https://www.lockheedmartin.com/en-us/capabilities/cyber/cyber-kill-chain.html">Cyber Kill Chain</a> (Lockheed Martin)</li><li><a href="https://www.fireeye.com/solutions.html">Attack Lifecycle</a> (Fireye)</li><li><a href="https://blogs.gartner.com/ramon-krikken/2014/08/08/introducing-gartners-cyber-attack-chain-model/">Cyber Attack Model</a> (Gartner)</li><li><a href="https://attack.mitre.org/">ATT&amp;CK Lifecycle</a> (MITRE)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/0*gXobeWSKVmzB11eY" /><figcaption><a href="https://sqrrl.com/media/ebook-web.pdf">https://sqrrl.com/media/ebook-web.pdf</a></figcaption></figure><h3>The Cyber Kill Chain Model</h3><p>Cyber Kill Chain is the more popular one to use in threat hunting remediation exercises, so we will take you through this example of threat hunting below. A Cyber Kill Chain threat hunting approach revolves around the sequential way cyberattacks happen. A cyberattacker usually launches a particular threat in a series of phases. Each phase is a point where the cyber attack vector could be mitigated if the right security controls are in place.</p><h3>7 phases of cyberattack in the Kill Chain Model:</h3><h4>Reconnaissance</h4><p>Cyberattackers spend time researching their potential target. They determine the target’s weaknesses and vulnerabilities and the most opportune ways in — the most covert backdoor possible.</p><h4>Weaponization</h4><p>After identifying the best backdoor possible, the cyberattacker creates a malware weapon to deploy at the target. With newer attacks, these can be harder to identify because they are designed to match target-specific vulnerabilities and weaknesses.</p><h4>Delivery</h4><p>The tailored malware weapon is launched.</p><h4>Exploitation</h4><p>The malicious file in the malware weapon is now triggered. Exploiting the vulnerabilities and weaknesses of the target, whatever the attack’s aim, is in position — be that stealing data, harming software, et cetera.</p><h4>Installation</h4><p>The malware weapon creates an access point, or backdoor, into the target. Through this access point, the attack is able to further penetrate into the infrastructure.</p><h4>Command and Control</h4><p>At this stage, the cyberattacker has their hands on the target and can manipulate it to their own ends.</p><h4>Actions on Objective</h4><p>Once in location and installed, the cyberattacker can start taking action. This is the end of the hack, resulting in the theft of passwords, ransomware, data exfiltration, data leakage, or even the destruction of data.</p><h3>Fixing, Patching and Compensating Controls</h3><p>Now that you’ve run a risk assessment and chosen a threat hunting model you can understand what stages in the model represent the most risks and start putting counter-measures in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eUYX_4HOUp43Ru_A" /><figcaption>Start with the highest risks that come from your risk assessment.</figcaption></figure><h4>1: Create and test a threat hunting hypothesis</h4><p>Create a general hypothesis of what you expect to unveil in a threat hunting exercise. These should be easy to determine based on the findings of the risk assessment and application of those findings to the model.</p><p>Using our vulnerable network server example, one hypothesis could be: if a fileless based attack is launched, it would totally wipe out the memory banks of the network servers and destroy their processing capabilities.</p><h4>2: Collect relevant information and data</h4><p>Test hypotheses with all available threat hunting tools. Collect the resulting data for review.</p><p>Examine data for any anomalies and malicious patterns in the datasets that have been previously identified.</p><p>One method of threat hunting is to use these identified anomalies and malicious attacks to reconstruct the tactics, techniques, and procedures (TTPs) employed in cyberattacks. If no anomalies are detected, you can potentially determine no systems have been compromised.</p><h4>3. Lather, Rinse, Repeat</h4><p>After completing all manually helmed threat hunts with the tools at hand, look to automation. First, determine which steps can be expedited with automated threat hunting tools.</p><p><a href="https://www.csoonline.com/article/3254230/how-to-automate-threat-hunting.html">Automated threat hunting</a> tools intelligently use human and technological resources. Security teams are wasted on performing the same necessary tests over and over manually if there is a better, automated option. If the same threat hunting exercise needs to be repeated again a later time, automate as much as possible. Manual processes should only be used for new hunting exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n1zqkgcnXB14BEoX" /><figcaption>Happy Threat Hunting!</figcaption></figure><h4>4. Creating Security Solutions</h4><p>Once you’ve hunted down threats, you have to determine how to resolve them.</p><p>If a cyberattack is detected, determine where it is in its lifecycle. That will determine your next course of action. For example, if malicious patterns and anomalies show a cyberattack is in its beginning stages, your incident response team can handle the threat before it does damage.</p><p>If no threat is detected, you can start the threat hunting planning cycle again for a new exercise.</p><h3>How Effective was a Threat Hunting Exercise?</h3><p>Each threat hunting remediation exercise should be followed by a post-game evaluation to, and determine if it was successful or not. Establish realistic data-driven metrics that can measure real indicators of success around threats, like the turnaround time for responding to incidents.</p><p>Examples of security performance metrics to track are:</p><ul><li>Number of incidents by severity</li><li>Number of compromised hosts</li><li>Dwell time</li><li>The number of identified vulnerabilities</li><li>Corrected and identified insecure practices</li><li>False-positive rate of transitioned hunts</li></ul><h4>Incidents by Severity</h4><p>Monitoring the volume of incidents by severity establishes a running tally of the total number of previously known and unknown incidents.</p><p>Over time, this provides context as to how well security defenses are working.</p><h4>Compromised Hosts</h4><p>A running tally of the total number of compromised hosts in the IT Infrastructure is an especially useful metric when threat hunting on endpoint security tools. It is highly effective for revealing setting misconfigurations.</p><h4>Dwell Time</h4><p>Dwell time shows how long discovered security threats were active in your IT Infrastructure. Dwell time has three areas that add detail and insight::</p><ul><li>Time between infection and detection</li><li>Time from detection until to investigation</li><li>Time between investigation and remediation</li></ul><p>These various times allow you to evaluate where remediation resources should be put or fixes should be made to technology, processes, or teams.</p><h4>Vulnerabilities Identified</h4><p>This is the total number of vulnerabilities discovered based on the hunting exercises being conducted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YkkPQTQdv9EWU0W2" /><figcaption>Take a close look following your threat hunting practices and keep repeating good security hygiene and checkups.</figcaption></figure><h4>Corrected and Identified Insecure Practices</h4><p>The total number of identified and corrected IT-related insecure practices allows for internal measures to quickly up security health. Unaddressed, insecure practices can accidentally leave a backdoor open for future attacks.</p><p>False Positive Rate of Transitioned HuntsAutomation is critical to reducing the rate of false positives. Not only is it a waste of your security team’s time to manually tune, but it’s impossible to sort through high, repetitive numbers of false positives. Unassuaged volumes of false positives create too much noise around identifying real threats and vulnerabilities. There is no foreseeable time when data is going to slow down or lighten, so adding automation is key to keeping pace with security needs.</p><h3>Putting it all together</h3><p>There are several steps in applying risk assessment results to the model to prepare for staring threat hunting activities.</p><ol><li>Apply your prioritized list of risks and vulnerabilities, made in the risk assessment, to your selected threat hunting model.</li><li>Determine the kinds of activities that a cyberattacker could target as threat vectors for the identified risks, specific to your company.</li><li>Map the risks and cyberattacker opportunity activities to the phases of the threat hunting model. <br>Ex:) If the Network Servers in your IT Infrastructure is most at risk, determine the kinds of actions or activities a cyberattacker would take to attack them. Then, place them at the different phases of the threat hunting model accordingly.</li><li>Calendar routine threat hunting remediation activities. Based on risk level, rotate through regular threat hunts for each at-risk IT asset.</li></ol><p>The exact frequency will be limited by the available resources. However, it’s critical to do different threat detection tests as often as possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fd41b3abd2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/using-threat-modeling-in-cybersecurity-to-hunt-and-remediate-2fd41b3abd2e">Using Threat Modeling in Cybersecurity to Hunt and Remediate</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Latest Bypassing Techniques Beats SOAP/XML API Protection]]></title>
            <link>https://medium.com/wallarm/latest-bypassing-techniques-beats-soap-xml-api-protection-b6185f0aef8f?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6185f0aef8f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Fri, 10 May 2019 17:09:40 GMT</pubDate>
            <atom:updated>2019-07-23T20:24:28.323Z</atom:updated>
            <content:encoded><![CDATA[<h3>Latest Bypassing Techniques Beat SOAP/XML API Protection</h3><p>It is impossible to <a href="https://wallarm.com/resources/top-five-challenges-protect-api/">protect APIs</a> unless you take a deep dive into the protocols implemented over the standard HTTP. Most security tools are not protecting data where it’s most vulnerable, <em>inside</em> the <a href="https://en.wikipedia.org/wiki/XML_Schema_(W3C)">XML schema</a> itself. These encoding attacks are going unflagged by many application platforms, despite topline security tools and techniques they believe protect APIs. The problem is in the code and the relative inability to notice what malicious attack may be hiding inside at a fundamental level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Qb1bBi0RBtSdM4E" /></figure><p>You may already know that whitehat researchers have used data protocol-level encodings to avoid WAF filtration. This bypass hacking technique is no secret. Hackers can use a <a href="https://trustfoundry.net/bypassing-wafs-with-json-unicode-escape-sequences/">JSON Unicode escape sequences to bypass WAFs</a>. Most WAFs leave companies vulnerable and open to <a href="https://lab.wallarm.com/what-stealthy-attacks-are-hiding-in-api-data-and-why-do-most-waf-miss-them-c9f59e865d74">stealthy cyberattacks hide in API data</a>. Unicode escape sequences can pass through simple RegExp-based signatures, bypassing JSON API protection. But it’s not just a problem for JSON.</p><p>Now, we want to describe different <a href="https://www.tutorialspoint.com/digital_communication/digital_communication_data_encoding_techniques.htm">encoding techniques</a> for SOAP/XML APIs as a continuation of that research. We can show why you absolutely cannot have API protections without dealing with specific data encoding protocols.</p><h3>XML Encoding Security Issues</h3><p>Like JSON, XML allows the encoding of data in different ways, such as <a href="https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references">built-in entities</a>. This can leave APIs vulnerable to cyberattacks. Here are three ways XML variation can obscure code, leaving it unmonitored (even though it may seem covered). The first two are comparably easier to protect against. The third mechanism that can be used to hide malicious code is more sophisticated and harder to protect against.</p><p>Let’s consider the following statement, as an example:</p><p>union select password from users--a-</p><p>If successfully executed, this statement would allow a hacker to gain access to the passwords of all the users on the system. Naturally, WAFs and other protection systems would try to block it.</p><p>A signature for this kind of attack would look for a string “union select password” in the XML encoded data stream.</p><p>Now, let’s see how that can be circumvented.</p><h3>1. Internal Variables Replace Characters</h3><p>An internal variable can be used to replace some characters in strings inside XML tags. For example, you could use “&amp;nbsp;” instead of a space, like this:</p><p>‘ union&amp;nbsp;select password from users--a-</p><p>In this case, the <a href="https://www.w3schools.com/xml/xml_parser.asp">XML parser</a> will easily replace the named entity, “&amp;nbsp”, with a space character. However, the signature for union + select will not detect the replacement.</p><h3>2. HTML HEX-Codes</h3><p>The second encoding option is using HTML HEX-codes, such as “&amp;#85;” instead of “U” character, like this:</p><p>‘&amp;#85;nion select password from users — a-</p><p>Which is almost equal to \u0085 encoding for JSON previously described in <em>Bypassing WAFS with JSON Unicode Escape Sequences </em>or our article on <a href="https://lab.wallarm.com/what-stealthy-attacks-are-hiding-in-api-data-and-why-do-most-waf-miss-them-c9f59e865d74">why WAFs miss attacks hiding in API data</a>.</p><h3>3. Is Your WAF Fully Compatible with XML Data Encoding?</h3><p>The third obfuscation mechanism is the most complicated and dangerous one. Unlike the two other encoding options, this third mechanism requires the WAF to be fully compatible with XML data encoding to catch it. This evasion technique is based on XML-defined entities, which is almost equal to variables with defined values. This technique makes it possible to build any string inside XML tags using references for entities/variables defined earlier. Take a look:</p><p>&lt;!DOCTYPE a [&lt;!ENTITY u “uni”&gt;]&gt;&lt;a&gt;&amp;u;on select password from users — a-&lt;/a&gt;</p><p>In this example, a piece of the payload was defined at the beginning of the XML document as the “u” variable used later inside &lt;a&gt; XML tag.</p><p>No regular expressions can be used to detect the replaced code. As explained by the <a href="https://en.wikipedia.org/wiki/Chomsky_hierarchy">Chomsky Hierachy</a>, XML syntax is inherently not regular.</p><p>We have explained how grammar-based detection can bring the API parsing to the new level in a recent whitepaper <a href="https://wallarm.com/resources/evolution_of_detection/">Evolution of Real-Time Attack Detection</a>.</p><h3>Going Inside: Encoding Attack Block</h3><p>Obfuscation mechanisms can be incredibly sophisticated, planting seeds that are imperceptible until a dangerous security problem or breach surfaces. Most security tools are not set up to detect the hidden code and block XML encoding attacks. <a href="https://wallarm.com/">Wallarm</a> implements a full XML-compatible parser <em>inside </em>to block XML encoding attacks. It allows the protection of any SOAP, XMLRPC and other XML-based APIs out-of-the-box.</p><p>This screenshot shows how encoding attack block works:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1MuSk5JxCM5c8EAq" /></figure><p>This screenshot shows Wallarm solving for the custom entities-based evasion technique:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ztzmpEMIPlx3dQF9" /></figure><p>Cyberattackers can use your own code to infiltrate and change code completely undetected, bypassing standard API protections. Going deeper, by installing parsers inside, can strengthen the areas that are presently unpoliced by more superficial or traditional security tools.</p><p>If you enjoyed this article, take a look at our previous XML-related research in <a href="https://lab.wallarm.com/xxe-that-can-bypass-waf-protection-98f679452ce0"><em>XXE That Can Bypass WAF Protection</em></a><em>. </em>Find more information about different XML encodings for entire documents.</p><p>Follow <a href="https://lab.wallarm.com/">Wallarm Labs</a>’ research on Medium.</p><p>#Cybersecurity #Hacker #Cyberattack #Whitehat</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6185f0aef8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/latest-bypassing-techniques-beats-soap-xml-api-protection-b6185f0aef8f">Latest Bypassing Techniques Beats SOAP/XML API Protection</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is your org structure threatening your IT security infrastructure?]]></title>
            <link>https://medium.com/wallarm/is-your-org-structure-threatening-your-it-security-infrastructure-d98eb4930fbb?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d98eb4930fbb</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 20:29:04 GMT</pubDate>
            <atom:updated>2019-09-23T07:18:58.916Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 Tips to Solve API Security Issues in Any IT Security Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0NI647ue94WQ_8oA3huLGg.png" /><figcaption>Start listening. Integrating isn’t enough if your teams aren’t talking.</figcaption></figure><p>In a hyper-competitive environment, keeping up with customer usability demands often means adopting a hyper-agile development process. It’s a dangerous devil’s bargain. Security gets left on the cutting room floor in pursuit of highly responsive, first-to-market, code-to-customer feature flow.</p><p>Mobile and cloud applications increasingly rely on SaaS and APIs to quickly meet customer needs. It allows for more complex rich application logic without having to reimplement common integrations or reinvent customer experience and maintenance flows. It allows businesses to respond quickly. It allows for more adoption, quicker. But with each customer value point added, a new threat vector is added as APIs layer one after another. To deal with <a href="https://www.axway.com/en/products/api-management/manage-apis/top-10-security-risks">security risks for APIs</a>, we need to solve for a few challenges.</p><p>The effects of siloed business logic are continually making security solutions ineffective or even damaging — building contention instead of harmony between <a href="https://www.tripwire.com/state-of-security/featured/devsecops-the-marriage-of-secops-and-devops/">DevOps and Security</a> teams. For example, a security solution needs to know if it is normal to block users after a few failed attempts to log in. Does that block meet with your individual business data? Or, is blocking users an issue that will drastically disrupt business operations and affect revenue?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0fze5wdaja8NNxE6OaXGFg.png" /><figcaption>Security too often gets left as an afterthought rather than a fundamental part of business health.</figcaption></figure><p>It could be, in the case of logins, that the business goals for an app means not blocking users after numerous failed login attempts. Granted, there are almost no scenarios under which you would want to have zero limits on failed login attempts. It would be security suicide. But the example serves a point.</p><p>And the problem goes deeper than the development not providing sufficient API documentation. Security solutions need to sync with business intelligence and design to understand the instructions and significance of data within any given application or service.</p><p>This article tackles five hazardously overlooked considerations for actually solving security problems surrounding APIs.</p><h3>1. Total Security Thinking: Getting Buy-In Across Teams</h3><p>Everybody benefits when security is not treated as an afterthought or a way to check off compliance requirements. On the flip side, if security is overly aggressive, it is definitely possible to block legal users, partners, or other stakeholders in a way that would ensure security — while running a company into the ground. Business understands what “business” risk is. They know what it looks like internally, to customers, company-wide, and among key players. The balance between security and business goals is part of ensuring businesses stay afloat. Independently, though, business teams are not technical enough to understand what that necessitates.</p><p>The problem is organizational across industries. There is simply insufficient language between business and technical teams. Awareness needs to increase in both directions — sharing awareness and goals cross-functionally. DevSecOps needs a seat at the table to ask questions of business teams and figure out what needs to be protected as well as fully realizing the impact of new developments. It’s more than simply sharing user data or business processes.</p><p>Communication is needed to make possible prioritizing technical actions. There needs to be more cross-functional understanding and trust between business and technology teams. That way business can relate to the technology teams what the priorities are. Likewise, security can help business teams understand the challenges security teams are facing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*9k3a5NDzRudKVTKZpAkdAQ.png" /><figcaption>In addition to being more efficient, costs of recovery after an attack can cripple businesses. Integrating security health is good for bottom lines and CI/CD.</figcaption></figure><p>Taking risk assessment out of the security silo is like establishing a preventative healthcare policy instead of trying to stop an unchecked virus after an outbreak. Security and risk need to be a more distributed consideration. In fact, security thinking has to go even bigger and become a companywide consideration as part of the way we think about business every day.</p><p>Only when business and technology teams both have seats at the table will the right understanding inform: (1) what <em>exactly</em> you need to protect; (2) with what accuracy rate; and (3) how much time and resources should be spent to protect any one particular application or service.</p><h3>2. “Security as a Process” Model</h3><p>Second, we need to be ready — at any and every time, for existing and unforeseeable, new security challenges. Security, Operations, and Development teams all need to be able to respond to incidents. We need to do backups and be able to roll out backups as needed. We need to better train teams to be able to deal with hacking incidents and whatever might happen. But, we cannot stop there. We need to increase security awareness to reduce the number of security flaws developers unwittingly introduce into their code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Hn1u_jFzJBf1ALBqAKONbw.png" /><figcaption>Understanding security as a process can help assure more efficient processes and better-fit tools to help teams.</figcaption></figure><p>The basic processes and best practices should be implemented and refreshed on a regular basis. It is impossible to build a static security solution, mostly because of the changing interrelationships and new versions of your own APIs that evolve as part of the business process.</p><p>To build security for process-based business, you need to build <strong><em>security as a process</em></strong>. That means everything should be repeatable and the monitoring tools should allow you to monitor in almost in real time.</p><p>Without a process to accompany the right tools, you will never get any results that are actually effective in protecting APIs or your overall business.</p><h3>3. More than an Inventory: Business Logic for Security Design</h3><p>Think of a warehouse of inventory and a traditional security guard crew; you definitely need to understand what exactly you want to protect and where it’s placed. (There’s a big difference between a fenced impound lot and a busy, metropolitan embassy.) For an API, deciding how we monitor that inventory also depends on understanding the placement (infrastructure) and relative value vs security of each element. Our <a href="https://lab.wallarm.com/key-considerations-in-api-security-d1e8dc16ca4c">API security</a> inventory needs to be based on which version we used — that determines structure. And, it also has to consider why we are responsible for this service — it’s value or priority. Only at this point can we determine: (1) what represents a <a href="https://www.edts.com/edts-blog/whats-the-difference-between-a-security-incident-and-an-event-infographic">security incident</a> for each of the APIs; (2) who will be responsible for these incidents and should be notified; and (3) what resources the protection of each service demands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*uGGx6Dlxf-Ia_l2pUAIOuw.png" /><figcaption>The complexity and accelerating rate-of-change of technological, business, and security landscapes sum up to a highly-adaptive, constantly evolving, and process-oriented mindset to stay afloat.</figcaption></figure><p>Ultimately, the simplicity of our inventory analogy fails if we don’t go back to the difference between evaluating an impound lot and an embassy. The difficulty is not the dynamism of all the comings and goings of various dignitaries, attaches, valets, and support staff of the later. It’s more about the complex history and motivations of each person there — and how they interact. In thinking about our API’s “inventory”, instead of geopolitics and culture, we can think of the technological and business logic.</p><p>The only way to fully protect a service is to understand the business logic that makes it valuable. It’s critically important for security solutions to understand the logic underlying the choice of a particular API, SaaS service, or information system. We need to understand the logic to ascertain whether something is a mission-critical service to the overall business program.</p><p>Security thinking around APIs is not about securing just an inventory — or even a dynamic inventory. We need to go outside security teams and after-the-fact solution thinking where the good guys are always two steps behind. We don’t want to be police. We want to be the secret-agent level heroes who protect and ward off any-level attacks.</p><h3>4. Smarter Cybersecurity Allocation: You Don’t Need a Vault to Protect a Water Bill</h3><p>A big question in security is making sure that costs, efforts, and resources expended to protect specific services or APIs are in line with how critical the service is to the overall application. There is another factor here. Some services, though fairly simple or low-cost, have a catastrophic effect if attacked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0I_gjOADBajLKZg8dkEnmQ.png" /><figcaption>Policing isn’t enough given the increasing sophistication of cyberattackers.</figcaption></figure><p>A simple, inexpensive service can need disproportionate attention and protection. Consider a family car. Critical services for it to fulfill its function of transporting people to-and-from places are the engine, wheels, perhaps the shaft. We think of major, high-cost components. You may not think about oil as a critical part of operations since it’s so inexpensive and easy to replace. However, if you drive without oil in the engine, you will destroy the engine and end up with extensive, very expensive repairs. The context and impact of any functional element is extremely important. This is why security and business need to effectively coexist — symbiotically.</p><p>It’s not just a security environment; it’s a total business environment. Developers need to be in touch with business teams to understand that there is a mission-critical function to what they are developing. By understanding business goals, DevOps can ensure users do certain operations faster or within a time frame. It may not be a big deal in a non-banking context to have inactive users that remain logged on. So, determining how an app should function is about cross-departmental understanding.</p><p>Let’s say a developer builds a simple account management app and there is what would normally play out as a minor issue that affects the user’s browser. But in this case, the developer has not realized the application is for a crypto-exchange or bank. This seemingly minor issue could become high-risk and allow a hacker to take control of the user’s browser, like reroute the account or modify authentication cookies. Attackers count on minor issues in high-value environments for their own financial gain.</p><p>The simple truth is the amount invested in protection should be in-line with what a possible hacker would gain should this service or API be compromised. To do that the development and the security team both need to understand the business context of the application. This also saves resources. If your bike lock costs five thousand dollars, it’s probably not worth it.</p><h3>5. Scale and Structure: Organization and Company Culture Can Weaken Security</h3><p>Companies across the board experience security challenges, but the challenges shift depending on organizational influences, like structure and activity. Fortune 500 companies have different challenges than small businesses. The maturity of a company can also influence the security needs. No one can have a static security landscape. Scale and structure, as well as internal organizational elements like company culture, will influence how good your security is.</p><p>However, there are challenges to achieving truly comprehensive security common to their respective ends of the scale — startup to titan of industry.</p><h3>Large Companies Create Organizational Stress-Fractures in Security</h3><p>At the higher-end Fortune 500 corporations, the scale is too huge for any one person to have a grasp of all the business processes. And, it’s almost impossible to ask key executives and stakeholders to sit together in one room and even that would probably not help because of the nested and fluid organizational structures.</p><p>The result? Clashing priorities often throw security off-center. Each vertical answers what is priority or function a little bit differently, as related to their shared business. Especially as businesses scale, complex org structures increase internal friction. Comprehensive security of applications and APIs is a nuanced, enormous undertaking that often becomes kicked down the road.</p><p>Scale has to do with age, as well. To support a large company, you likely need to support a lot of legacy code and a lot of important technological and procedural elements introduced years ago, decades in some cases.</p><p>Hindering fully comprehensive security is that security work is never finished. It has to be dynamic to match the churning business environment.</p><h3>Startups Struggle to Gain Security Stability As They Grow</h3><p>Startups need to move faster than their engineering teams. Startups’ paths are fraught with unpredictable decision-making practices because they are all about moving faster. Security is non-existent or, at best, following instead of being part of the movement forward. Developers need to better understand that startups are based on a high rate of change. Even investors and founders may not be informed enough to <a href="https://biztechmagazine.com/article/2016/08/why-expanding-small-businesses-should-focus-it-infrastructure-upgrades">prioritize and make security decisions</a> with the speed they need to. In those cases, developers have to be able to forecast where the business, and its technology, is headed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*gJPe_Orf1f9TLPGavEnIew.png" /><figcaption>It’s not just on business teams to listen cross-functionally. Developers need to proactively understand the bigger business picture at a design and organizational level.</figcaption></figure><h3>Security Challenges at Every Size</h3><p>Across the board, there is a range, or balance, between security problems arising from quick progress and the challenges that surface over time with increased organizational complexity. For example, a company that has 10 years of history will likely face a couple of legacy project issues inside its code. At that age and size, it may also face problems like having four different business owners scattered across times zones and schedules. You cannot get the stakeholders together and talk over security very easily. You may also be large enough to have a new or growing team, meaning there are human integration problems.</p><p>These are going to be challenges for businesses: continually having to rethink, educate, update and invest in security because it is so fast moving.</p><h3>Conclusion</h3><p>APIs are central to the digital transformation and competitively conducting business to meet modern norms and market demands. This new way of delivering data and services must come with new ways of cross-organizational and collaborative thinking. Developers, Operations, and Security professionals need to work together with Business. It is the only way to establish truly comprehensive security as a process. Cross-functional communication is imperative to: understand application context and operational risks; and incorporate risk-focused thinking, security monitoring, and best practices throughout the <a href="https://developers.redhat.com/blog/2018/04/11/api-journey-idea-deployment-agile-part1/">API development and deployment process</a> and throughout the application lifestyle.</p><p>Only once cross-organizational thinking that integrates Business and DevSecOps happens will there be a happy balance of risk, costs, values resulting in happy customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d98eb4930fbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/is-your-org-structure-threatening-your-it-security-infrastructure-d98eb4930fbb">Is your org structure threatening your IT security infrastructure?</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What stealthy attacks are hiding in API data — and why do most WAF miss them?!]]></title>
            <link>https://medium.com/wallarm/what-stealthy-attacks-are-hiding-in-api-data-and-why-do-most-waf-miss-them-c9f59e865d74?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9f59e865d74</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Thu, 25 Apr 2019 18:41:24 GMT</pubDate>
            <atom:updated>2019-04-26T16:47:30.726Z</atom:updated>
            <content:encoded><![CDATA[<h3>What stealthy attacks are hiding in API data — and why do most WAF miss them?!</h3><h3>API Data: What is it and how is it saying it?</h3><p>APIs are the blood flow of today’s applications — from online browser-based apps to mobile apps to sophisticated distributed enterprise applications connecting dozens of individually packaged containerized microservices with APIs.</p><p>The most common objective of APIs is to communicate data. Let’s say it’s a rainy day (expect delays) and someone requests local bus schedules on their phone’s map app. Their mobile phone then sends their GPS location to the map service while cloud services send weather information to the update boards. The two most popular APIs calls, across all applications, are GET requests (request to read data) and PUT requests(request to put data).</p><p>So let’s ask a simple question: <em>What is data?</em> When your inlaw is ranting for 20 minutes, is that data? It is data in a way, but this type of data is called unstructured data. When APIs communicate data, <em>structured data</em> formats are most commonly used. Structured data means every piece of data (datum) comes with a label or a description. It’s like filling out a DMV form:</p><p>First Name: Joe<br>Last Name: Doe<br>Email: <a href="/service/mailto:joe.doe@aol.com">joe.doe@aol.com</a></p><p>There is a standardized way to structure data, apply proper labels, and specify data types, called metadata. This standard is called JavaScript Object Notation or JSON and it is in itself a variant of Extendable Markup Language or XML.</p><h3>Is JSON really a safer data encoding format? <br>(We explore a JSON vulnerability.)</h3><p><a href="https://json.org/">JSON</a> — by far the most popular data encoding format for APIs — looks simple, readable and <em>secure</em>. But is JSON really more secure than other data encoding formats? On close inspection, JSON is a serialization format that allows users to (1) send objects as strings and then (2) it sends applications to recover objects from those strings. That makes the JSON format as dangerous as other serialization formats (XML, Ruby Marshal, PHP unserialize) in terms of application security. At Blackhat 2017, a lot of issues related to ASP.NET and Java JSON parsers were presented. (See Hewlett Packard Enterprise’s <a href="https://www.blackhat.com/docs/us-17/thursday/us-17-Munoz-Friday-The-13th-JSON-Attacks-wp.pdf"><em>Friday the 13th JSON Attacks</em></a>.)</p><p><strong>In this article, we explore another vulnerable JSON feature: Unicode string encoding format (from </strong><a href="http://json.org/"><strong>json.org</strong></a><strong>).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*JUeK47LmFzPgmoqz" /><figcaption>Unicode String Encoding</figcaption></figure><p>The Unicode string encoding format is a feature designed to encode non-ASCII characters. But Unicode can also be used to encode any characters by their HEX code. This is commonly used for encoding languages using alphabets other than Latin. Chinese Kanji and Arabic letters, for example, are encoded with Unicode — obviously, this format is not uncommon in the least.</p><p>Here is what the actual Unicode string encoding might look like:</p><p>{“a”: “AAAA”}<br>is equal to<br>{“a”:”AAA\u0041”}<br>and also equal to<br>{“a”: “\u0041\u0041\u0041\u0041”}</p><p>Because Unicode converts data from a readable plain text to HEX, which is fully interpreted by the machines but not by human readers or by simple signature-based pattern detectors, this field is a hotbed for possible hacker attacks. Hiding in plain view — and bypassing most WAF protections!</p><p>Wallarm is only able to detect that attackers use this to bypass WAFs without a proper JSON parser onboard because Wallarm’s approach does not rely on patterns or signature.</p><p>(In case you missed it: relying on patterns or signatures to detect vulnerabilities can leave you open to attack.)</p><h3>Testing Unicode JSON for vulnerabilities to protect RESTful API</h3><p>Some attack payloads, like the ones illustrated by the screenshot below, were detected in real life:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gTDDTDBCn5SrJ0bJ" /></figure><p>To test what attacks can and cannot be detected, we have created a simple script enc.php that converts human readable text into Unicode. We have provided this script below. You can use it for yourself to encode data this way and test your current API protection solution, such as WAF:</p><pre>&lt;?php<br>$d = $argv[1];<br>$x = bin2hex($d);<br>for($i=0; $i+1&lt;strlen($x); $i+=2){<br>echo “\u00”;<br>echo $x[$i].$x[$i+1];<br>}<br>echo “\n”;</pre><p>To illustrate, let’s use an obvious attack which tries to steal users’ passwords from the system:</p><p>‘ union select password from users — a-</p><p>If a hacker tried this attack in a plain text, even a simple open-source WAF like mod-security should be able to detect it.</p><p>Using this script provided, let’s now encode this payload.</p><p>Try to send it to your protected apps, like this:</p><pre>$ php enc.php ‘“ union select password from users — a-’<br>\u0022\u0020\u0075\u006e\u0069\u006f\u006e\u0020\u0073\u0065\u006c\u0065\u0063\u0074\u0020\u0070\u0061\u0073\u0073\u0077\u006f\u0072\u0064\u0020\u0066\u0072\u006f\u006d\u0020\u0075\u0073\u0065\u0072\u0073\u002d\u002d\u0061\u002d<br>$ curl -d ‘{“test”:”\u0022\u0020\u0075\u006e\u0069\u006f\u006e\u0020\u0073\u0065\u006c\u0065\u0063\u0074\u0020\u0070\u0061\u0073\u0073\u0077\u006f\u0072\u0064\u0020\u0066\u0072\u006f\u006d\u0020\u0075\u0073\u0065\u0072\u0073\u002d\u002d\u0061\u002d<br>”}’ -H ‘Content-Type: application/json’ -X PUT <a href="https://api.youproject.local/">https://api.youproject.local</a></pre><p>If you are using a signature-based WAF, this attack has most likely gone undetected.</p><p>We were able to discover this kind of attack because Wallarm implements a full JSON parser that can parse data even if it’s encoded under Unicode JSON to protect any RESTful API.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9f59e865d74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/what-stealthy-attacks-are-hiding-in-api-data-and-why-do-most-waf-miss-them-c9f59e865d74">What stealthy attacks are hiding in API data — and why do most WAF miss them?!</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MTGOX: Crypto Failure is in the Name.]]></title>
            <link>https://medium.com/wallarm/mtgox-crypto-failure-is-in-the-name-875e0270371a?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/875e0270371a</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Sat, 13 Apr 2019 16:01:01 GMT</pubDate>
            <atom:updated>2019-06-10T17:21:17.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mt. Gox Bitcoin Heist: Takeaways from a $3.3B Crypto Exchange Breach</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*swIGVwrNx8pU7qNbqQxYGw.png" /><figcaption>It was all fun and games, until someone lost 850,000 BTC from a Tokyo-based exchange, MTGOX, in 2014.</figcaption></figure><p>Understanding how cryptocurrency exchanges evolved into hacker fantasy islands is all in the name. MTGOX, a company remembered for the largest crypto breach in history, is an acronym for Magic The Gathering Online Exchange (MTGOX). The absurd rise and fall of MTGOX is critical to understanding <a href="https://wallarm.com/cryptocurrency-security/">the fraught state of cryptocurrency exchanges</a> — and the high risks of investing in cryptocurrency. From cryptocurrency security systems architecture to the major players in the game, the crypto world is not for the faint of heart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f6jXo2azE_EBMhQkyfzxfg.jpeg" /><figcaption>Look at the entire <a href="https://wallarm.com/cryptocurrency-security/">Wallarm Labs Infographic</a></figcaption></figure><p>In 2018, four exchanges (NiceHash, Coincheck, BitGrail, Coinrail, and Bithump) lost over 765 million dollars in 2018 alone. The <a href="https://www.forbes.com/sites/tromero/2018/02/14/how-the-500-million-coincheck-hack-exposes-deeper-security-flaws-in-corporate-japan/#728b0fbd4113">$534,000,000 dollars stolen from Coincheck</a>, one of Japan’s largest crypto exchanges, dwarfs <a href="https://www.thrillist.com/culture/most-successful-bank-robberies-of-all-time-biggest-heists-in-history">the largest bank heists in history</a>. Eye-popping as the Coincheck theft was, it’s nothing compared to the estimated 3.3 billion dollar loss MTGOX and its investors suffered. As a result, MTGOX was forced to file for bankruptcy and liquidation. In 2019, the victims of MTGOX and the company still struggle to recover.</p><h3>What happened to MTGOX in 2014?</h3><p><em>Let’s preface the story with this: cryptocurrencies (blockchains) can be fairly secure in themselves, but there is a weak link in the exchange infrastructure that transactions move through. This story underscores how those undermining weaknesses evolved and persist</em>.</p><p>* * *</p><p>Collapse can come down silently. On February 23rd of 2014, the MTGOX Twitter feed went unceremoniously dead. The same day, the CEO, Mark Karpelės, resigned without explanation. When the MTGOX company website suddenly went dark on February 24th of 2014, the cryptocurrency world was turned upside down and the company that caused the ruckus was silent. Customers were left with nowhere to turn.</p><p>The events had transpired quickly in the public eye. In February of 2014, over 70% of the world’s total bitcoin trading was coursing through MTGOX. Its stability defined the cryptocurrency market. For weeks, worried investors had struggled to get answers from the Tokyo-based exchange. People complained about long delays followed by excuses when trying to cash in altcoins. Press inquiries and executive interviews were chock full of “no comment”. Next came a full suspension of withdrawals without comment as to when the exchange would come back into service.. People were taking to desperate measures. One customer flew from his home in the UK to wait in the snow outside MTGOX’s Tokyo headquarters for an answer to a simple question. “Where is my money?”</p><p>(Want to know the details of the criminal coinflow? <a href="https://blog.wizsec.jp/2017/07/breaking-open-mtgox-1.html">Check out this 2017 WizSec article</a>.)</p><p>When the silence finally broke, it was to a cold comfort. Investors were stunned by the announcement that 850,000 bitcoins (BTC) had gone missing. And the hapless company had no idea how to handle it. In fact, no one did. The fiasco was not contained to Tokyo; it was a multinational problem. The estimated value of the missing coins at the time was over $450M USD. According to professional estimates by Wallarm Labs, the value in today’s market exceeds $3 billion dollars. (Our hearts go out to the victims who lost their share of that.)</p><p>Ultimately, Mark Karpelės was arrested by the Japanese police. He had not tried to run.</p><h3>So, what happened in the MTGOX hack?</h3><p>The public shock gave way to an even more shocking truth. The loss of 850,000 BTC was not sudden. It wasn’t a Mission Impossible type of heist that caused the 2014 collapse of MTGOX. It was more than a hacking event. It was a hacking operation that spanned years, beginning in the infancy of MTGOX, in 2011.</p><p>Hackers were continually diverting altcoins by accessing hot wallets with stolen private keys. The money taken from hacked accounts was transferred to other wallets, where the coins could then be moved to other platforms.</p><p>For years MTGOX had faced both technical and regulatory challenges. They were annoyances, but had no direct effect on the confidence of the investors. Arguably, these sorts of obstacles were a regular and come-to-be-expected reason for the complaints. No one suspected hacking and money laundering.</p><p>CEO Mark Karpelės was arrested in 2015 for fraud and embezzlement charges unrelated to the attack. He was convicted of falsifying data to inflate holdings value. It’s unclear if Karpelės acted with malice. The harm, however, was clear to his victims. Five years later, lawsuits continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*g996PDlGa0dQv55HvHNtHA.png" /><figcaption>The bomb dropped on Karpeles — and investors. Over $4,000,000,000 USD were found laundered by a white collar bad guy with connections to Russian Mafia.</figcaption></figure><p>From Magic the Gathering to the Russian Mafia, the story unfolded into more unimaginable criminal turns. Insiders were part of the criminal enterprise. At the very top of the criminal ladder wasn’t Karpelės. BTC-e exchange owner Alexander Vinnik was discovered to be the “COO” of the hacking-and-laundering enterprise. Investigators found connections between Vinnik and underworld characters from the Russian Mafia and parliament alike. Karpelės appeared to be totally unaware of Vinnik’s scheme. While Karpelės spent 10 months in Japanese prison, Vinnik absconded to Greece, avoiding capture until 2017. Following an anonymous tip, Vinnik was finally arrested. He was connected to over $4,000,000,000 USD of laundered BTC from MTGOX and other locations. He awaits extradition on US Justice Department warrant. But, this should-be-mustachioed villain is still caught up in dubious affairs. The Russian authorities have been vying for extradition to Russia, arguing that Vinnik will be treated unfairly elsewhere.</p><p>The MTGOX hack may as well have been written in a black hat hacker comic book.</p><p>[Here’s a <a href="https://youtu.be/SfiiF1zHWU4">fun video from Fortune Magazine</a>.]</p><h3>Lasting Consequences of Crypto-crime</h3><p>The MTGOX hack was an attack that would have sweeping consequences. Bitcoin value dropped 36% globally during the two months surrounding the collapse of MTGOX. “The Tokyo-based platform’s closure cast a long shadow over the market, triggering a more than two-year slump in cryptocurrency prices and undermining faith in the exchanges that serve as gatekeepers in an industry that often operates with little to no regulation.” <a href="https://www.bloomberg.com/news/articles/2019-03-15/former-bitcoin-baron-mark-karpeles-gets-suspended-jail-term">Forbes’ Cybersecurity</a>. It makes sense. Cryptocurrency isn’t a loss of value the way Beanie Babies are.</p><p>Karpelės was heavily punished for foolheartedly endeavoring to run the largest bitcoin exchange in the world without security considerations. Karpelės was incarcerated for 11 months. He claimed he endured over 50 days of intense interrogation.</p><p>Outside criminal liability, civil court may mean lifelong consequences for Karpelės. In 2017, Karpelės discovered 200,000 BTC in a hardware wallet he had mysteriously forgotten about. He says he doesn’t want it, which makes sense when you consider the looming lawsuits.</p><p>As of March 2019, an Illinois court blocked an attempt by Karpelės to dismiss a US lawsuit against him. Don’t cry too much for him, though. According to a <a href="https://www.reddit.com/r/Bitcoin/comments/89o16y/im_mark_karpel%C3%A8s_exceo_of_bankrupt_mtgox_ask_me/">Reddit post </a>wherein Karpelės apologized for his bumbling, he stands to get 160,000 bitcoin should MTGOX bankruptcy go forward.</p><p>In his words:</p><blockquote>“I don’t want this billion dollars. From day one I never expected to receive anything from this bankruptcy. The fact that today this is a possibility is an aberration and I believe it is my responsibility to make sure it doesn’t happen. One of the ways to do this would be civil rehabilitation, and as it seems most creditors agree with this, I am doing my best to help make it happen. I do not want to become instantly rich. I do not ask for forgiveness. I just want to see this end as soon as possible with everyone receiving their share of what they had on MtGox so everyone, myself included, can get some closure.”</blockquote><p>The value of the recovered 160,0000 BTC is almost $633M USD per March 2019 estimates. That’s a lot of money to wipe Karpelės’ tears with.</p><p>Four years after filing for bankruptcy (2018), the defunct MTGOX remains tied up in <a href="https://www.ccn.com/mt-gox-whale-secures-rehabilitation-trustee-balance-of-623-million">ongoing legal proceedings </a>in an effort to repay lost funds to customers and creditors. Legally, the initial filing for bankruptcy was suspended. Hope remains alive that civil rehabilitation of the company might turn its insolvency into some sort of recovered funds.</p><p>Karpelės is fighting for civil rehabilitation of MTGOX, arguing it’s the only way to get money back to people. That money includes the millions he stands to gain if bankruptcy goes forward.</p><h3>Takeaways from MTGOX: Cryptocurrency Exchange Security Risks</h3><h4>The MTGOX fiasco highlights three things:</h4><p>1. The aimless evolution that is heir to an <strong>obvious lack of security of cryptocurrency exchanges</strong></p><p>2. A perilous <strong>lack of regulations</strong> overseeing an international market holding billions in virtual currency</p><p>3. The <strong>bountiful opportunity for hackers</strong>, who understandably love the previous two facts</p><p>While scandalous incidents like MTGOX feature criminal cyberattacks as the cherry on the bad-business sundae, it also reveals how problematic crypto exchange security can be. Years of poor management, regulatory problems, and other security challenges preceded the hack of MTGOX. But the effect of these huge security breaches is a lowering of consumer trust in cryptocurrency, which may be well deserved. It also threatens companies who aren’t thinking towards redesigning security protocols and regulations with cryptocurrency security as the cornerstone of its architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*e7FDo6wyUGzQa8Mt8FvaEw.png" /><figcaption>So, what do we do with bitcoins now?</figcaption></figure><p>The enormity of the cryptocurrency security problems is so obvious that cybercrime goes under-reported to consumers. And, it may also be a great cover for failures in asset management and company insolvency. That is the suspicion cast on Italy’s BitGrail after the company’s founder, Francesco Firano, blamed hackers for a <a href="http://fortune.com/2018/02/11/bitgrail-cryptocurrency-claims-hack/">$195M loss of cryptocurrency</a>. How can an alleged hack not be 100% provable? Simple: transaction dates aren’t recorded to BitGrail’s blockchain. And there is no one telling them — or anyone else — they have to be.</p><blockquote>“Many international exchanges are essentially unregulated, and even U.S.-based cryptocurrency exchanges are not protected by any sort of consumer insurance along the lines of FDIC coverage for bank deposits.” <a href="http://fortune.com/2018/02/11/bitgrail-cryptocurrency-claims-hack/">Fortune</a></blockquote><p>The MTGOX scandal ended nefariously, but started innocently. The Magic card exchange unwittingly evolved into the world’s largest BTC exchange. What we learn from MTGOX is that cryptocurrency exchanges have evolved unplanned. Security was a second thought instead of a central part of the architecture. The problems of this legacy are unresolved. There is a systemic risk-prone design flaw in the exchange architecture. (Read more about that in <a href="https://www.forbes.com/sites/forbestechcouncil/2018/09/17/why-are-crypto-exchanges-are-hacked-so-often/#1b0e31b13421"><em>Why Are Crypto Exchanges Hacked So Often?</em></a>)</p><h3>What Can You Do?</h3><p>Years may have breezed by since the 2014 hack of cryptocurrency exchange giant MTGOX, but the crypto world still bears the scars. It’s like a gash across the face of every crypto boom and bust. The lessons learned should remain just as visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyPuObUPyHFrJs04w8hhZg.jpeg" /><figcaption>Even with these losses, your bitcoin exchange may not be where you think.</figcaption></figure><p>First, read <a href="https://www.forbes.com/sites/forbestechcouncil/2017/08/24/what-to-consider-before-investing-in-initial-coin-offerings/#515e6f5d3604">expert security advice on what you should consider before investing in virtual currency</a>. But really, the problem is bigger than our personal wallets can cover. This is a problem of systemic shortcomings.</p><p>Cryptocurrency architecture needs to be redesigned with security in mind. The best advice in the meantime may be to leave assets in a local wallet. Do your due diligence on exchanges. Are they local? What security measures are they taking? Even if hot and cold wallets can be secured, the layers surrounding virtual currency, the transport of data and funds, and the laws that regulate exchanges are perilously lacking.</p><p>Even when exchanges are hacked, the customer and larger public may never know:</p><blockquote>“Some exchanges never announced [successful] hacks because attackers only stole GAS, not coins themselves and users never knew about these incidents.” [<a href="https://www.forbes.com/sites/forbestechcouncil/2018/09/17/why-are-crypto-exchanges-are-hacked-so-often/#1b0e31b13421">Forbes</a>]</blockquote><p>Yes, there is hope for the future of virtual currency. It may well be the future of the entire monetary system. However, it will take new security-centered thinking, regulation, and powerful <a href="https://securityboulevard.com/2018/12/3-ways-ai-is-securing-crypto-exchanges/">AI that will protect cryptocurrency</a> consumers and businesses alike.</p><h3>The Takeaway: Cryptocurrency Systemic Risk</h3><p>Bigger than a few blackhat hackers and exploitative businessmen with Russian Mafia connections, the problem with cryptocurrency goes back to its roots in Magic the Gathering. We aren’t trying to pick on virtual playing cards. However, billions of dollars isn’t play money.</p><p>The architecture and regulations of cryptocurrency exchanges have not been constructed with the same security-first mindset that other currency markets have. Wells Fargo got to begin with hard, cold bars of gold and build out a security supply chain that grew around new security risks to new forms of currency. It grew from shotgun mercenaries to complex regulations and banking relationships with an international network of governance. Cryptocurrency has erupted, gigantic and whole, into the world with little cryptocurrency security. The cryptocurrency market was born around virtual currencies on trading platforms that were ill-equipped for the high volume of real money at risk. They suffered being born without notice, without the oversight of governing bodies. Like a street urchin, its resilience is noble, but its place in the world remains contentious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUd9_7rE-rk3dzYRLPIirw.jpeg" /></figure><p>What we need to takeaway is higher demands and the deep work of securing distributed exchanges at all layers and in all locations. We need technological innovation, international coordination, and (despite crypto’s iconoclastic dreams) <em>governance</em>. Creating the technological, cultural, and legal infrastructure to support transformative monetary innovations will create real evolution instead of market mires.</p><p>#cryptocurrency #cybersecurity #hackers #mtgox #dataprivacy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=875e0270371a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/mtgox-crypto-failure-is-in-the-name-875e0270371a">MTGOX: Crypto Failure is in the Name.</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Tips and Best Practices to Build a Solid Cloud Migration Strategy for 2019]]></title>
            <link>https://medium.com/wallarm/8-tips-and-best-practices-to-build-a-solid-cloud-migration-strategy-for-2019-2a9a88e48df5?source=rss-78984bf6a74f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a9a88e48df5</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Wallarm]]></dc:creator>
            <pubDate>Fri, 05 Apr 2019 14:56:35 GMT</pubDate>
            <atom:updated>2019-09-23T08:20:18.247Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are eight fool-proof practices that can help you move your workloads to the cloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*7ASSpJiEOYlDiaYg" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:Cloud_computing.svg">https://commons.wikimedia.org/wiki/File:Cloud_computing.svg</a></figcaption></figure><h3>A quick look at cloud migration.</h3><p>Cloud migration involves moving an organization’s data storage and IT operations to a cloud network. Cloud computing services are hosted in a multi-tenant environment and can be delivered via the internet or direct connection.</p><p>The main types of cloud services are software as a service (SaaS), in which a subscription grants access to a cloud provider’s software; infrastructure as a service (IaaS), which involves renting computing resources like servers and storage; and platform as a service (PaaS), which is a combination of the two. SaaS requires the least involvement as you are simply using a pre-engineered service while the provider takes care of all the technological aspects. At the other end of the spectrum, IaaS gives you more control over your cloud environment. PaaS allows you to customize your cloud environment without having to build everything from scratch.</p><p>Clouds can be public, in which multiple users share the same cloud computing resources; private, which involves a platform dedicated to a single user; or hybrid, which combines the two. There are many cloud providers. Popular examples include <a href="https://azure.microsoft.com/en-us/">Microsoft Azure</a>, <a href="https://cloud.google.com/">Google Cloud</a>, and <a href="https://cloud.netapp.com/blog/ebs-volumes-5-lesser-known-functions">AWS EBS</a>.</p><h3>Why migrate to the cloud?</h3><p>Organizations choose to move to the cloud for a variety of reasons. Outsourcing your data storage to a cloud provider eliminates the need to build your own infrastructure, and simplifies your engineering and management requirements, so you can focus your energies on developing your software.</p><p>Cloud-enabled application development environments provide the scale and flexibility needed to expand your operations quickly and adapt to evolving customer needs. If you own your own physical hardware, it is more complicated and expensive to scale up or down. The economy of scale associated with the cloud reduces your costs, and you only pay for the storage capacity you use.</p><p>Another reason to migrate to the cloud is the burden of maintaining legacy infrastructure. Cloud services mitigate the risks of IT outages and data loss. While cloud computing has provided a competitive advantage, it is fast becoming a competitive necessity.</p><h3>The challenges of cloud migration</h3><p>Some key challenges for moving to the cloud include:</p><ul><li><strong>Complexity of Migration: </strong>depending on your cloud computing needs, it can be challenging to find the right cloud solution or decouple your application from your current architecture of licenses. Some applications are more difficult to migrate, such as those with a monolithic structure or those relying on older languages and systems.</li><li><strong>Cloud Management:</strong> the scale and flexibility of the cloud can be difficult to manage.</li><li><strong>Legacy Software: </strong>if you don’t adequately plan for it, it can be difficult to migrate your legacy applications or rehost your data center infrastructure on the cloud. This is especially the case if you lose track of legacy components.</li><li><strong>Vendor Lock-in:</strong> you may become too dependent on a particular service provider or vendor, which makes it difficult to adjust your service or switch to another cloud.</li><li><strong>Cloud Security:</strong> Security approach and strategies change as you migrate to the cloud. While cloud providers are responsible for the security of the infrastructure itself, the design of the applications becomes a lot more reliant of the APIs. In addition, application and data security remain within the scope of responsibility of the organization who owns the data, but the methods of eliminating vulnerabilities and protecting from threats can be different in the cloud than on premises. Further, cloud infrastructure itself and its own management layer, in a way, represent their own application. it can be a challenge to manage your security credentials for access to this client infrastructure. Your cloud service account may require access to sensitive information or root permissions.</li><li><strong>Organizational Changes:</strong> aside from the technical aspect, a smooth and effective transition to the cloud requires that your team is all on board. Some developers may resist changes to the established order. New skillsets may be required to manage DevOps and CI/CD processes as public clouds become a part of your deployment platform.</li></ul><h3>8 Tips to Build a Smart Cloud Migration Plan</h3><p>The following practices can help you move your operations to the cloud:</p><h4><strong>1. Choose the right cloud solution</strong></h4><p>Each cloud deployment model offers its own set of advantages and suits different needs. You should ensure that your cloud infrastructure is flexible and scalable, supports global deployment, and lets you keep track of usage and billing data. Data redundancy and backup are also essential aspects of a cloud service.</p><p>The most popular option is a public cloud, as it is often easy to use and cost-efficient. Private clouds can also take advantage of third-party computing power but provide better isolation than public clouds, which sometimes helps with compliance. Hybrid solutions allow you to protect sensitive areas in a private cloud while taking advantage of the efficiency of public cloud services for less sensitive requirements.</p><p>You can also opt for a multi-cloud solution, which combines services from multiple providers and helps prevent vendor lock-in. This sometimes involves splitting your database workloads. You should evaluate your needs in terms of security, flexibility, and usability. Likewise, you should consider whether you want a SaaS, IaaS, or PaaS model.</p><h4><strong>2. Adopt a phased migration strategy</strong></h4><p>It can be difficult to migrate heavy legacy applications, so you can do it in increments.</p><p>The most comprehensive migration strategy is re-architecting, or refactoring, which is challenging because it involves rebuilding your entire application environment. However, this strategy is ultimately the most rewarding as it allows you to engineer features to fit your application requirements, and can help improve developer agility.</p><p>If you have trouble refactoring your applications immediately, you can opt for a simpler strategy to begin with, which will buy you time to acquire new skills so you can successfully re-architect later.</p><p>An easier strategy you can employ in the meantime is rehosting, which involves deploying your application through a managed service provider or a local hosting service. This allows you to migrate your application quickly while minimizing the impact on your application’s functionality. The host provides your infrastructure and maintenance needs so you don’t have to perform the more complex aspects of migration.</p><p>Another strategy is re-platforming, which allows you to keep your core architecture and reduces management and operation costs. This is similar to rehosting but involves a slight modification of your infrastructure. The advantage is that you can move your database to a managed service while saving on licensing costs.</p><h4><strong>3. Identify and manage your components</strong></h4><p>When migrating to the cloud, you need to keep track of all your resources, including applications and software components. Developers often use open source components to save time and money, but they can easily lose visibility and neglect the maintenance of these resources. This can result in a failure to upgrade and resolve vulnerabilities.</p><p>Run a <a href="https://www.infoworld.com/article/3294201/discovery-is-the-most-underrated-phase-of-software-development.html">discovery</a> to identify open source components or legacy software so you can keep track of them in an inventory. You can then determine which components you want to move to the cloud, and which you can eliminate to reduce your migration footprint. You can easily replace certain architecture components on the cloud. Static code analysis can also help in this task.</p><h4><strong>4. Automate your migration</strong></h4><p>Cloud automation allows you to build infrastructure as code and deploy your applications automatically so you can avoid downtime. You can also automate your migration strategy. Many applications involve repeatable patterns, which you can identify and automate to improve consistency and accelerate the migration process. There are many tools that can help in this process, especially for applications that are already based on Dockers or other containers.</p><h4><strong>5. Apply good governance</strong></h4><p>You should establish policies for in-house use and third-party access to your cloud. You should also closely monitor the cloud environment during and after migration. This involves examining your network, system, application, and audit logs to identify areas for optimization. You can use a monitoring dashboard to visualize components and utilization patterns.</p><h4>6. Secure your cloud</h4><p>Together with re-engineering your application, you should re-engineer your approach to security. A move to public cloud often contributes to the agility of DevOps process and increases frequency of releases. Cloud security strategy should include good understanding of how to incorporate security into the DevOps process and ensure security of the APIs between the individual components of your application as well as interfaces between the cloud itself, your data and your payloads.</p><p>Securing your access points and limiting credentials is also very important, as compromised credentials can open your entire infrastructure to being compromised by a hacker. Don’t create an access key for your root account unless it is necessary. For example, when using AWS, you can provide limited credentials to Identity and Access Management (AIM) users that interact with the AWS system on a daily basis.</p><h4>7. Prepare a maintenance plan</h4><p>Outsourcing your hardware and software maintenance needs to a cloud provider reduces your management burden, but it does not mean you can simply adopt a cloud solution and forget about it altogether. You should allocate funds and time for ongoing management.</p><p>You should also ensure that you can scale capacity to respond to demand or switch providers when necessary. This requires an ongoing assessment of your changing needs and providing user alerts.</p><h4>8. Use a cloud-enabled disaster recovery solution</h4><p>A cloud-enabled <a href="https://searchdisasterrecovery.techtarget.com/definition/disaster-recovery">disaster recovery</a> (DR) solution involves a hot site, which replicates your on-premise infrastructure but is hosted in the cloud. It is continuously updated and cheaper than an on-premise DR solution. In case of a disaster that renders your normal hardware unusable, you can continue working via the cloud.</p><h3>Conclusion</h3><p>Cloud computing is a major transformative technology that is becoming indispensable to software developers. With the increasing complexity of both applications and IT infrastructures, it can be a challenge to migrate to the cloud. You can use these 8 tips to help streamline the process and ensure a secure and agile environment for your application development needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a9a88e48df5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wallarm/8-tips-and-best-practices-to-build-a-solid-cloud-migration-strategy-for-2019-2a9a88e48df5">8 Tips and Best Practices to Build a Solid Cloud Migration Strategy for 2019</a> was originally published in <a href="https://medium.com/wallarm">Wallarm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>