<?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 Ayomide Odukoya on Medium]]></title>
        <description><![CDATA[Stories by Ayomide Odukoya on Medium]]></description>
        <link>https://medium.com/@ayomikoya?source=rss-c0dae941eea6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cwK0PzdMDVwS5pl6</url>
            <title>Stories by Ayomide Odukoya on Medium</title>
            <link>https://medium.com/@ayomikoya?source=rss-c0dae941eea6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:16:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayomikoya/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[Bridging SAST and DAST: An Autonomous Pentesting Workflow with Gemini, Cline, and Burp Suite]]></title>
            <link>https://medium.com/@ayomikoya/bridging-sast-and-dast-an-autonomous-pentesting-workflow-with-gemini-cline-and-burp-suite-d318ccc48c76?source=rss-c0dae941eea6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d318ccc48c76</guid>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[appsec]]></category>
            <dc:creator><![CDATA[Ayomide Odukoya]]></dc:creator>
            <pubDate>Thu, 26 Mar 2026 13:31:00 GMT</pubDate>
            <atom:updated>2026-03-26T13:31:00.781Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI-Assisted Application Security: Building an Autonomous AppSec Agent with Gemini, Cline and Burp Suite</h3><p>Stop manually copy-pasting between your SAST reports, Burp Suite, and ChatGPT. Here is the step-by-step guide to turning Visual Studio Code into a human-in-the-loop penetration testing command center.</p><p>The days of treating Large Language Models (LLMs) as glorified chatbots are over. Our task today is giving AI the ability to get a sast finding, read your codebase to contextualize the vulnerability, formulate an attack hypothesis, and actually fire the exploit payloads, all while keeping you firmly in the driver’s seat.</p><p>If you are constantly switching contexts between your IDE, your terminal, and your proxy tools, you are losing valuable time. The industry is shifting away from isolated tools and moving toward autonomous, AI-driven workflows.</p><p>Today, we are bridging the gap between concept and execution. By combining <strong>Cline</strong> (an autonomous AI agent for VS Code) with the <strong>Model Context Protocol (MCP)</strong>, we can transform your code editor into a centralized AppSec engine.</p><p>Here is the step-by-step guide to setting up a technically accurate, highly effective AI AppSec workflow directly inside Visual Studio Code.</p><h3>The Architecture</h3><p>Before we build, let’s define our toolkit:</p><ol><li><strong>Visual Studio Code:</strong> Our operational base and single pane of glass.</li><li><strong>Cline:</strong> An open-source, agentic AI extension for VS Code. Unlike standard autocomplete tools, Cline can read your local file system, execute terminal commands, and interact with external APIs.</li><li><strong>Model Context Protocol (MCP):</strong> The open standard that allows AI models to securely connect to external tools. We will use it to wire Cline directly into our dynamic testing environment.</li><li><strong>Burp Suite:</strong> The industry-standard web proxy, armed with PortSwigger’s official MCP server extension.</li></ol><h3>Phase 1: The Setup</h3><h4>Step 1: Install Cline</h4><p>Cline acts as the hands and eyes of our operation.</p><ol><li>Open Visual Studio Code.</li><li>Go to the <strong>Extensions</strong> tab (Ctrl+Shift+X or Cmd+Shift+X).</li><li>Search for <strong>Cline</strong> and click Install.</li><li>Once installed, you will see a new robot icon in your sidebar. Click it to open the Cline interface.</li></ol><h4>Step 2: Empower the “Brain”</h4><p>Cline needs a reasoning engine to process vulnerabilities.</p><ol><li>In the Cline sidebar, click the settings gear.</li><li>Select your preferred API Provider. <em>(Note: you can get an API key from Gemini here).</em></li><li>Securely paste in your API key in Cline.</li></ol><h3>Phase 2: The Burp Suite MCP Integration</h3><p>Static analysis (SAST) tells us <em>where</em> a bug is, but dynamic testing (DAST) proves it. To allow Cline to dynamically test applications, we need to connect it to Burp Suite using the Model Context Protocol.</p><h4>Step 3: Install the MCP Server in Burp Suite</h4><p>PortSwigger provides an official MCP server extension that exposes Burp’s internal engine (like proxy history and request generation) to AI clients.</p><ol><li>Open Burp Suite and navigate to the <strong>Extensions</strong> -&gt; <strong>Installed</strong> tab.</li><li>Click the <strong>Add</strong> button.</li><li>Under <em>Extension Details</em>, set the Extension type to <strong>Java</strong>.</li><li>Click <strong>Select file…</strong> and select the Burp MCP Server .jar file (available via the BApp store or PortSwigger&#39;s releases).</li><li>Click <strong>Next</strong>. Burp will load the extension.</li><li>A new <strong>MCP</strong> tab will appear in Burp Suite’s top navigation menu. Navigate to it and check the <strong>Enabled</strong> box to turn the server on. By default, it binds to <a href="http://127.0.0.1:9876.">http://127.0.0.1:9876.</a></li></ol><p>p.s If you need more help with setting this up, check <a href="https://github.com/PortSwigger/mcp-server">here</a></p><h4>Step 4: Wire Burp to Cline</h4><p>Because Burp Suite is a constantly running desktop application, we connect our AI agent to it using <strong>Server-Sent Events (SSE)</strong>.</p><ol><li>Open VS Code and open the Cline sidebar.</li><li>Click the Settings icon and navigate to your <strong>MCP Servers</strong> configuration file. This will open cline_mcp_settings.json.</li><li>Add the Burp Suite SSE configuration, pointing it to your local Burp MCP instance:</li></ol><p>JSON</p><pre>{<br>  &quot;mcpServers&quot;: {<br>    &quot;burp&quot;: {<br>      &quot;url&quot;: &quot;http://127.0.0.1:9876/sse&quot;,<br>      &quot;disabled&quot;: false,<br>      &quot;autoApprove&quot;: []<br>    }<br>  }<br>}</pre><p>Save the file. Within seconds, Cline will successfully handshake with Burp Suite. If you click the “Tools” icon in Cline, you will suddenly see an arsenal of new AppSec capabilities populated directly from your proxy, including get_proxy_http_history_regex and send_http1_request.</p><h3>Phase 3: The Target Environment</h3><p>Before we unleash our autonomous agent, we need a battleground. To test this workflow safely, we must use a deliberately vulnerable application and generate the static analysis baseline that our AI will use for context.</p><blockquote><strong><em>⚠️ Critical Security Disclaimer:</em></strong><em> </em>Never run automated pentesting agents against infrastructure, applications, or APIs without explicit, written authorization. AI agents execute payloads rapidly and can cause unintended denial-of-service or data corruption. Always use safe, isolated, and legally cleared environments like VulnBank for testing.</blockquote><h4>Step 5: Provisioning the Target and Generating the SAST Baseline</h4><p>To properly demonstrate the SAST-to-DAST pipeline, we need an application’s raw source code, a static analysis report, and a live instance routed through Burp Suite. For this guide, we will use <strong>VulnBank</strong>, an intentionally vulnerable modern banking application designed specifically for benchmarking AppSec tools and AI agents.</p><p><strong>1. Clone the Target Codebase:</strong> Open your terminal and pull down the VulnBank repository into your workspace so Cline can read the source files.</p><pre>git clone https://github.com/Commando-X/vuln-bank.git<br>cd vuln-ban</pre><p><strong>2. Generate the SAST Report:</strong> We need to give Cline a roadmap of where the vulnerabilities live. We will use <strong>Semgrep</strong>, a fast, open-source static analysis tool, to scan the codebase and output the results in SARIF (Static Analysis Results Interchange Format) — the industry standard format that LLMs can easily parse.</p><p>If you don’t have Semgrep installed, install it via pip (pip install semgrep), and run the scan:</p><pre>semgrep scan --config auto --sarif -o results.sarif</pre><p>You now have a results.sarif file sitting in your directory. This is the first half of the AI&#39;s brain.</p><p><strong>3. Set Up the Live Target:</strong> Next, we need the dynamic environment. You have two choices with VulnBank:</p><ul><li><strong>Option A (Local Container):</strong> Spin it up safely on your own machine using Docker</li><li>docker-compose up --build</li><li><em>(The vulnerable API will run locally on </em><a href="http://localhost:5000)."><em>http://localhost:5000)</em>.</a></li><li><strong>Option B (Live Cloud Target):</strong> You can also test against the live instance hosted at <a href="https://vulnbank.org/">vulnbank.org</a>, which explicitly authorizes security engineers to practice and benchmark their AI agents.</li></ul><p><strong>4. Populate the Burp Suite Proxy History:</strong> Because Burp Suite only knows about the HTTP traffic it sees, we need to generate some baseline traffic for the MCP server to fetch.</p><ul><li>Ensure your browser or API testing tool (like Postman or curl) is configured to proxy traffic through Burp Suite (127.0.0.1:8080).</li><li>Navigate to your running VulnBank instance (either localhost:5000 or vulnbank.org) and click around. Register an account, try to transfer some funds, or send a few sample API requests to endpoints like /api/v1/login.</li></ul><p>Now, your Burp Suite HTTP history is populated with the correct baseline headers, session cookies, and routing information.</p><p>With the codebase loaded, the SARIF report generated, and the live application traffic captured in Burp, the stage is set. Let’s move to the execution phase.</p><h3>Phase 4: The Agentic Pentest Workflow</h3><p>Your IDE is now officially a weaponized, AI-driven penetration testing terminal. Here is how you execute an end-to-end triage workflow.</p><h4>Step 6: Contextualizing the Codebase (Ingesting SAST)</h4><p>Instead of manually hunting for sinks and sources, we point the agent directly at a SAST report or source code.</p><ul><li><strong>Your Prompt to Cline:</strong></li></ul><blockquote>“Please follow these steps sequentially: Review: Explain the findings in results.sarif.</blockquote><blockquote>Review the vulnerable codepath, the vulnerable endpoints, and what the code is doing wrong.</blockquote><blockquote>Contextualize: Query the Burp Suite MCP server to fetch recent HTTP history and find the live requests that correspond to the vulnerable endpoints you just identified.</blockquote><blockquote>Dynamic Exploitation: Using the context from the source code, craft a specialized exploit payload.<br> Use the Burp MCP to send this modified HTTP request to the target to validate if the vulnerability is dynamically exploitable. Report: Provide a final summary of whether the static finding was proven to be exploitable in the running environment.”</blockquote><ul><li><strong>The Action:</strong> Cline autonomously reads the SARIF file, navigates your workspace, reads the vulnerable Python file, and outputs a technical breakdown of the flaw. Though the Static analysis result tells us there is a vulnerability, Burp Suite speaks in HTTP so Cline executes the JSON-RPC command over the SSE stream to Burp Suite. It parses your proxy history and loads the exact baseline HTTP request into its context window. Cline, then formulates the payload (e.g., URL-encoding &#39; OR 1=1--), constructs the raw HTTP/1.1 request, and prepares to inject the payload into the baseline request.</li></ul><h4>Step 7: The Human-in-the-Loop (HITL) Gatekeeper</h4><p><strong>This is the most critical step.</strong> Agentic AI operates rapidly, and firing automated payloads at infrastructure requires strict oversight.</p><p>Before Cline executes the send_http1_request tool, it will <strong>pause and prompt you for explicit approval</strong>. You will see exactly what host, port, and raw HTTP string the AI is about to send over the wire.</p><ul><li><strong>You click:</strong> <em>Approve.</em></li></ul><p>Cline fires the payload through Burp Suite, reads the HTTP response streaming back through the MCP server, and evaluates the outcome. It will confidently report back whether the application returned a vulnerability indicator, threw an internal error, or blocked the request via a Web Application Firewall (WAF).</p><h3>The Future is Human-in-the-Loop</h3><p>The goal of AI in Application Security is <strong>not</strong> to replace the penetration tester; it is to eliminate the friction between discovery and exploitation.</p><p>By wiring Cline and utilizing the Model Context Protocol, the tedious mechanics of context-switching disappear. You no longer have to translate SAST findings into DAST payloads manually. The entire workflow, from static code review to payload generation to dynamic execution happens in one unified pane of glass.</p><p>You define the strategy. The AI executes the tactics.</p><p><strong>Call to Action:</strong> Have you experimented with MCP servers in your pentesting workflows yet? Drop your favorite local integrations in the comments below!</p><p><em>(Technical Note: Always ensure you have explicit authorization to test any infrastructure or codebase. AI agents execute commands rapidly; always utilize the Human-in-the-Loop approval features within Cline to review payloads before they hit the target.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d318ccc48c76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI-Assisted Security Engineering]]></title>
            <link>https://medium.com/@ayomikoya/ai-assisted-security-engineering-37b2ca7044e9?source=rss-c0dae941eea6------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b2ca7044e9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-assisted-coding]]></category>
            <dc:creator><![CDATA[Ayomide Odukoya]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 16:17:15 GMT</pubDate>
            <atom:updated>2026-03-22T17:55:01.241Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there, I’ll be keeping this short, so over the next couple of days or weeks, I will be releasing a few articles here to help guide anyone interested in AI-Assisted security engineering.</p><p>Personally, I learn stuff by stumbling through it a couple of times and I’ve been doing just that when it comes to AI-Assisted cyber stuff, I’m learning how LLMs work, how MCPs work, agents and all the shebang, how to connect them and automate some of the cool things I already do around pentesting, cloud security, devsecOps and other security engineering work.</p><p>It’s been great so far, I have been talking about it on my <a href="https://linkedin.com/in/ayomikoya">LinkedIn</a> however a few people have asked me to show them the what and how, so I decided to drop a few step by step articles to help.</p><p>To be honest, I’ve also been learning from others and I can just share the articles I learnt from. However, whenever I am doing a task I make sure to change something, make something unique about the work I’m doing. It could be as simple as changing the AI Model or as complex as changing the entire task and this is why I’ll be sharing these articles for those of us who like to learn by stumbling ourselves or through other people’s stumblings.</p><p>Finally, some of these articles might be AI-Assisted, this is just to help speed up the process as I do have other things to do like actually learning and stumbling. However, I would always mention when it is AI-Assisted.</p><p>So yeah, that’s it. <br><strong>Ẹ ṣe</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b2ca7044e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The role of Humans in an ever-increasing automated DevSecOps Pipeline]]></title>
            <link>https://medium.com/@ayomikoya/the-role-of-humans-in-an-ever-increasing-automated-devsecops-pipeline-dcf42e4fc549?source=rss-c0dae941eea6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf42e4fc549</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[engineer]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[devsecops]]></category>
            <dc:creator><![CDATA[Ayomide Odukoya]]></dc:creator>
            <pubDate>Thu, 09 Mar 2023 14:41:42 GMT</pubDate>
            <atom:updated>2023-03-09T16:06:26.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e46NhPCASDt0v251bqQR5Q.jpeg" /></figure><p>One question that I have encountered with a few security engineers, particularly those in the field of DevSecOps, is whether the increasing use of automated tools and AI in the security field will result in a reduction in the number of security engineers involved in a DevSecOps pipeline or process.</p><p>While there is a possibility that an increase in the use of DevSecOps tools may result in the reduction of security engineers, this is not necessarily the case. Rather, it not only enhances the abilities of security engineers but also provides them with more time to focus on more complex security issues. By building processes and experimenting with them, security engineers can reach a company-fit process that results in a faster and more secure DevSecOps pipeline.</p><p>Furthermore, security engineers play a crucial role in ensuring that security is not sacrificed for speed. In an automated DevSecOps pipeline, there is a risk that security can be deprioritized to ensure that software is delivered quickly. Humans can help ensure that security is not compromised, and that the software is delivered quickly and securely.</p><p>We all know automation is an essential aspect of a DevSecOps pipeline. Still, humans play a critical role in ensuring that the software is secure. Humans provide a unique perspective, expertise, and intuition that automated tools cannot replicate. Therefore, it is essential to strike a balance between automation and human intervention to ensure that software is delivered quickly and securely while minimizing potential risks to the organization.</p><p>This is an exciting time for the security industry as we continue to integrate the latest technology to improve our processes and protect our systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf42e4fc549" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get SOC2 certified in Nigeria]]></title>
            <link>https://medium.com/@ayomikoya/how-to-get-soc2-certified-in-nigeria-1ff89204ce2e?source=rss-c0dae941eea6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ff89204ce2e</guid>
            <category><![CDATA[nigeria]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[soc2]]></category>
            <category><![CDATA[startups-africa]]></category>
            <dc:creator><![CDATA[Ayomide Odukoya]]></dc:creator>
            <pubDate>Tue, 20 Dec 2022 21:16:23 GMT</pubDate>
            <atom:updated>2022-12-22T18:45:28.726Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jU_8trdZdhJzJuaRVqHL4w.jpeg" /></figure><p>In Nigeria, there are <a href="https://tracxn.com/explore/SaaS-Startups-in-Lagos">over 430 Startups</a> that have a SaaS product, and that number increases every year. As the number of SaaS (Software as a Service) startups increases, it is important for these companies to prioritize cybersecurity in order to protect their customers’ data and ensure the security of their systems. This is because SaaS companies often handle sensitive data, such as financial or personal information, and a security breach could have serious consequences for both the company and its customers.</p><p>Before we discuss Security, what are SaaS Products? SaaS (Software-as-a-Service) products are software applications that are delivered and accessed over the internet, rather than being installed on individual computers or servers. This delivery model has many benefits, including reduced costs and increased flexibility. The increase in SaaS startups highlights the importance of cybersecurity in the modern business landscape.</p><p>One way in which companies can prioritize their security is by undergoing the process of achieving security compliance certifications. Security compliance certifications often require companies to meet certain security standards and follow specific security practices. These standards and practices can help companies identify and address potential security vulnerabilities, improve their overall security posture, reduce the risk of a security breach, enhance the company’s reputation, assist with risk management, and help ensure legal and regulatory compliance.</p><p>SOC2 certification is a type of security certification from the AICPA (Association of International Certified Professional Accountants) that helps organizations ensure that they have strong controls in place to protect sensitive information. The audit assesses the controls and safeguards in place at an organization that relate to security, availability, processing integrity, confidentiality, and privacy. Achieving SOC2 certification would be beneficial for a SaaS startup however it can be a long and complex process if it is not properly prepared. The following steps help SaaS Startups get SOC2 certified in Nigeria quickly and effectively:</p><ol><li><strong>Determine what type of SOC2 certification you need.</strong> There are two types of SOC2 certification: <a href="https://www.strongdm.com/blog/what-is-soc-2-type-1">Type 1</a> and <a href="https://www.strongdm.com/blog/what-is-soc-2-type-2">Type 2</a>. Type 1 certification focuses on the design of your organization’s controls, while Type 2 certification focuses on the effectiveness of those controls over a specific period.</li><li><strong>Choose a certification body</strong>. In Nigeria, several organizations can help you get SOC2 certified, such as the International Association of Computer Science and Information Technology (IACSIT) or the Nigerian Computer Society (NCS).</li><li><strong>Prepare for the certification process:</strong> In preparing for your certification process, you will need to undergo the following steps.</li></ol><ul><li>Determine the scope of your Soc2 audit: You will need to decide which systems, processes, and controls you want to include in the audit. This will typically include any systems or processes that handle sensitive data or that are critical to your business operations.</li><li>Identify and document your controls: You will need to identify the controls and safeguards that you have in place to protect sensitive data and maintain the availability and integrity of your systems. You will need to document these controls in a formal control documentation document.</li><li>Test your controls: The auditor will need to test your controls to ensure that they are operating effectively. This may involve reviewing documentation, observing processes, and testing systems to ensure that they are functioning as intended.</li></ul><p><strong>Submit your application for certification</strong>. Once you have gathered all the necessary documentation and evidence, you can submit your application to the certification body. After submission, you will need to provide the auditor with access to your systems and documentation, as well as any other information they may need to conduct the audit. You should also be prepared to answer questions and provide additional information as needed. The auditor will conduct the audit, reviewing your controls and testing them to ensure that they are operating effectively. If the auditor identifies any deficiencies in your controls, you will need to address them and provide evidence that they have been corrected.</p><p><strong>Achieve certification.</strong> If the auditor determines that your controls meet the required standards, you will be awarded Soc2 certification. Once you have achieved SOC2 certification, you will need to maintain it by continuing to meet the required standards and undergoing regular audits.</p><p>The process of achieving SOC2 certification can now be automated which helps organizations save time and resources while improving efficiency and effectiveness. This can be done through the use of automated tools such as <a href="https://drata.com/">Drata</a>, <a href="https://www.vanta.com/">Vanta</a>, <a href="https://tugboatlogic.com/">Tugboat Logic</a>, etc. Automating the process can also reduce the risk of human error and ensure consistent maintenance and updates of security and compliance practices.</p><p>It’s important to note that getting SOC2 certified can be a complex and time-consuming process. It may require significant effort and resources from your organization, but the benefits of having strong controls in place to protect sensitive information can be well worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ff89204ce2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing your Crypto]]></title>
            <link>https://medium.com/@ayomikoya/securing-your-crypto-e6d38008789?source=rss-c0dae941eea6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6d38008789</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Ayomide Odukoya]]></dc:creator>
            <pubDate>Thu, 01 Dec 2022 00:31:25 GMT</pubDate>
            <atom:updated>2022-12-01T10:27:26.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUR8l6CBgb_a6Y4SdE_Bzw.jpeg" /></figure><p>This article was first published on <a href="https://breach.club/publications/crypto-security/securing-your-crypto">breach.club</a> by <a href="https://www.linkedin.com/in/ayomikoya?miniProfileUrn=urn%3Ali%3Afs_miniProfile%3AACoAACapwJ0Be3lod1Lk-U6XELGY0eFpmMXzLlI">Ayomide Odukoya</a>.</p><p><a href="https://www.cbsnews.com/news/cryptocurrency-theft-hacker-chainalysis-blockchain-crime/#:~:text=Hackers%20have%20stolen%20more%20than,to%20blockchain%20analytics%20firm%20Chainalysis."><strong>$3 Billion</strong></a>, that’s how much hackers have stolen this year in cryptocurrency as of October 2022.<strong> </strong><a href="https://www.jbs.cam.ac.uk/wp-content/uploads/2020/08/2017-04-20-global-cryptocurrency-benchmarking-study.pdf"><strong>30%</strong></a> of people surveyed by Cambridge University had experienced some form of crypto-related fraud. These are pretty significant numbers, and they are only likely to increase as more and more people get involved in the crypto world. How do these figures affect the average Alice and Bob, who are weekly crypto traders with their wallets in centralized Crypto exchanges? This is what I address in this article about securing your cryptocurrency and assets.</p><p>For starters, Alice and Bob are more likely to lose their digital assets not just as a result of their personal negligence, but also from the platforms where they exchange their cryptocurrencies for fiat or other cryptocurrencies. <a href="https://consensys.net/blog/news/decentralized-exchanges-overview-benefits-and-advantages-over-centralized-exchanges/"><strong>99%</strong></a> of cryptocurrency transactions take place on Centralized Exchanges (CEX), which are platforms that allow traders to buy, sell, and exchange cryptocurrencies for fiat currencies or other cryptocurrencies. Furthermore, <a href="https://www.jbs.cam.ac.uk/wp-content/uploads/2020/08/2017-04-20-global-cryptocurrency-benchmarking-study.pdf"><strong>70%</strong></a> of these CEX are custodians of their users’ assets, which is why hackers focus most of their attacks against these exchanges. What then should Alice and Bob do to protect themselves and their assets on these exchanges?</p><h3>Research, Research and Research!!!</h3><p>In the blockchain/crypto world, one thing that can never be over-emphasized is Research because of how new, vast and volatile the crypto world is. Therefore, Alice must first research the exchange she wants to use, she should check reviews about the exchange and verify if it adheres to the Cryptocurrency Security Standard (CCSS). Although, only a few CEX have published that they are CCSS compliant.</p><p>The CCSS is a set of security requirements for cryptocurrency systems which includes exchanges as well as mobile and web applications. This standard aids in the management and standardization of procedures and methods used to secure a specific system. It is a 10 Step Security standard broken into 3 levels of Increasing Security where a system that has achieved “first level security” has the ability to protect its crypto wallets with strong levels of security. This is quite important as <a href="https://www2.deloitte.com/mt/en/pages/technology/articles/mt-article-cryptocurrency-security-standard-CCSS.html">most of the systems that suffered a high-profile cryptocurrency breach were found to be non-compliant with CCSS Level 1.</a> After having proper knowledge about the exchange she wants to use, Alice can then make the decision accordingly.</p><h3>Store your assets using a Hybrid Strategy</h3><p>Most people store their assets in “hot wallets” which are cryptocurrency wallets that are always connected to the internet and cryptocurrency network. However, these wallets are very susceptible to attacks. Therefore, a hybrid strategy should be implemented whereby assets are stored primarily in <em>Cold wallets</em>*, then moved to hot wallets when a transaction is about to be made. This is safe because the cold wallet is stored on a platform that is not connected to the internet, shielding it from unauthorized access, cyber hacks, and other vulnerabilities that a hot wallet which is connected to the internet is susceptible to.</p><p><em>💡 Cold Wallets are devices or applications that store your private keys offline. They can be either be a device that look like USB thumb drives that stores your keys or applications on your device that do not connect to the internet.</em></p><h3>Test before you send</h3><p>Before you send cryptocurrency to a wallet address you’re not entirely sure is the right address, send a test amount to ensure that it is the right address and verify that the recipient received the test amount before moving the remaining. This helps in minimizing the amount of cryptocurrency lost due to mistakes made while transacting as Crypto-related transactions are irreversible.</p><h3>Remember your ABCs of Personal Digital Security</h3><p>Because of how intertwined our lives are with the Internet nowadays and our recent adoption of cryptocurrencies, protecting yourself online is critical in this day and age. In light of this, we should constantly exercise digital security practices, such as:</p><ul><li>Implement the use of strong passwords</li><li>Never share your wallet’s seed phrases with anyone</li><li>Enable Multi-factor Authentication (MFA)</li><li>Rotate passwords periodically</li><li>Beware of Phishing mails</li><li>Check sites such as <a href="https://haveibeenpwned.com/">Have I Been Pwned</a> to verify if your accounts linked to your crypto assets have been compromised.</li></ul><h3>Conclusion</h3><p>Cryptocurrency is often touted as being more secure than traditional forms of payment and might also be the future of money, but that doesn’t mean it’s immune to security risks. Keep the things above in mind, exercise caution while transacting and you can help protect yourself from fraud and theft.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6d38008789" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>