<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: zafar0506</title>
    <description>The latest articles on DEV Community by zafar0506 (@zafar0506).</description>
    <link>https://dev.to/zafar0506</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F858796%2Fd77aa69c-04a4-4d9a-bc7e-07f568bb9274.png</url>
      <title>DEV Community: zafar0506</title>
      <link>https://dev.to/zafar0506</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zafar0506"/>
    <language>en</language>
    <item>
      <title>Sharing my experience after scanning 400 APIs</title>
      <dc:creator>zafar0506</dc:creator>
      <pubDate>Wed, 25 May 2022 18:16:15 +0000</pubDate>
      <link>https://dev.to/zafar0506/sharing-my-experience-after-scanning-400-apis-3n9p</link>
      <guid>https://dev.to/zafar0506/sharing-my-experience-after-scanning-400-apis-3n9p</guid>
      <description>&lt;p&gt;We have recently launched a free instant API security testing DAST (Dynamic Application Security Testing) Ethical Check web tool on GitHub.&lt;/p&gt;

&lt;p&gt;Here is the GitHub URL for the tool:&lt;br&gt;
&lt;a href="https://apisec-inc.github.io/pentest/"&gt;https://apisec-inc.github.io/pentest/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What kind of vulnerabilities does EthicalCheck find?&lt;/strong&gt;&lt;br&gt;
Most automated scanners would find vulnerabilities like SQL Injections, NoSQL Injections, XSS, etc.&lt;br&gt;
EthicalCheck performs different checks, including OAuth 2.0, JWT, BasicAuth, OWASP API #2, and broken authentication defects in web, mobile, and public-facing APIs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How EthicalCheck work?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It requires two inputs:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;API (OpenAPI Spec/Swagger) documentation URL.&lt;/li&gt;
&lt;li&gt;Email address for receiving security testing report&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;After a soft launch across a couple of developer forums in the past three months. We weren't hoping that we would get anywhere close to 400 tests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Here are the stats:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Duration: &lt;strong&gt;Feb 2022 - Apr 2022 (3 months)&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Total APIs Tested: &lt;strong&gt;400&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Total APIs with Vulnerabilities: &lt;strong&gt;164&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Total APIs with 10+ Vulnerabilities: &lt;strong&gt;16&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Max vulnerabilities found in an API: &lt;strong&gt;65&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Total Vulnerabilities Found: &lt;strong&gt;948&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Total Bug Bounty Savings: &lt;strong&gt;$1,896,000&lt;/strong&gt; (Based on HackerOne's payout model)&lt;/li&gt;
&lt;li&gt;Total API Penetration Test Savings: &lt;strong&gt;$343,000&lt;/strong&gt; (Based on avg penetration testing cost)&lt;/li&gt;
&lt;li&gt;Percentage of APIs with Vulnerabilities: &lt;strong&gt;47.9%&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Conclusion:&lt;/strong&gt;&lt;br&gt;
On an average, close to 50% of the APIs tested had security vulnerabilities. These vulnerabilities can easily be picked up by automated bots and hackers alike. Security breaches are expensive and can cost exponentially upwards of $8.64m to startups and large organizations alike.&lt;br&gt;
Your public-facing mobile/web API has a close to 50% chance of having security vulnerabilities. You can instantly test your public-facing APIs for vulnerabilities @ &lt;a href="https://apisec-inc.github.io/pentest/"&gt;https://apisec-inc.github.io/pentest/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>api</category>
      <category>tutorial</category>
      <category>security</category>
    </item>
  </channel>
</rss>
