<?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 Storm on Medium]]></title>
        <description><![CDATA[Stories by Storm on Medium]]></description>
        <link>https://medium.com/@MrJakobStorm?source=rss-93b0fb2df52c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*IakQ_PFBgdJwRIp4.jpeg</url>
            <title>Stories by Storm on Medium</title>
            <link>https://medium.com/@MrJakobStorm?source=rss-93b0fb2df52c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:17:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MrJakobStorm/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[Enhancements to our Pentest as a Service platform empower agile development teams]]></title>
            <link>https://medium.com/@MrJakobStorm/enhancements-to-our-pentest-as-a-service-platform-empower-agile-development-teams-5535460e2fb6?source=rss-93b0fb2df52c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5535460e2fb6</guid>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[platform]]></category>
            <dc:creator><![CDATA[Storm]]></dc:creator>
            <pubDate>Thu, 05 Mar 2020 15:16:49 GMT</pubDate>
            <atom:updated>2020-03-05T15:20:09.343Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past two years, we’ve had the pleasure of hosting a Customer Advisory Board, where we bring together some of our top customers from around the world to gain advanced insight into our platform as well as input on future development. It’s one of my favorite events of the year because it allows us to use real problems that you’re facing to inform which solutions we choose to tackle and how we choose to tackle them.</p><p>As Chief Product Architect at Cobalt, hearing how our platform can make your lives easier is what encourages us to work hard every day. Today, we’re excited to share that we’ve listened to your feedback and have launched significant enhancements to our Pentest as a Service (PtaaS) platform, delivering the first of its kind find-to-fix workflow to remediate security vulnerabilities.</p><p>Below is a snapshot of what’s new and how it’s giving modern agile development teams like yours the ability to do fast and frequent pentests and enhancing development and security operations.</p><p><strong>Cobalt Credits</strong> — the first delivery model that standardizes cost with unit of work for flexible, cost-effective pentest consumption.</p><ul><li>Instead of being tied to a traditional all-in-scope assessment, estimate the amount of pentesting you anticipate across a contractual year and assign Credits as needed for specific use cases.</li><li>With Credits, security teams can start a pentest in 24 hours, saving agile teams time by eliminating scheduling and onboarding back and forth with a vendor with each new feature release.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElSnXf31nenKEg-587A1dQ.png" /></figure><p><strong>Pentest Wizard</strong> — a self-starter guide that helps you select your assets, set your pentest objectives, specify details, and finalize the testing timeline.</p><ul><li>Complete critical steps autonomously to create a thorough pentest brief in a simple and efficient manner.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4EIRwmq7iS46KNGIMNS-A.png" /></figure><p><strong>Vulnerability taxonomy</strong> — more granular categorization of vulnerability findings, with 25 high-level categories and 135 sub-categories.</p><ul><li>Pentesters spend more time finding vulnerabilities and less time writing about them, while customers receive more detailed reports that make it easier to assign and remediate risk.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXRMwn_B5EKH3ok941db8A.png" /></figure><p><strong>JIRA bi-directional integration</strong><em> (available June 2020) </em>— the ability for security and development teams to communicate back-and-forth online and in-platform through JIRA.</p><ul><li>Instead of manually uploading findings into JIRA, this two-way communication creates operational efficiencies and expedites the remediation process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jgpMOb1zGqpjLFuC0_vAYg.png" /></figure><p>Thank you to our customers who invest your time to help us continuously improve for the next generation of tech-driven companies!</p><p>Interested in learning more about Cobalt’s Pentest as a Service Platform? <a href="https://cobalt.io/schedule-demo-penetration-test">Schedule a call with our team today!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5535460e2fb6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cobalt’s PTaaS Platform has a powerful new feature: Assets]]></title>
            <link>https://medium.com/@MrJakobStorm/cobalts-ptaas-platform-has-a-powerful-new-feature-assets-36133e02e045?source=rss-93b0fb2df52c------2</link>
            <guid isPermaLink="false">https://medium.com/p/36133e02e045</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <dc:creator><![CDATA[Storm]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 15:51:00 GMT</pubDate>
            <atom:updated>2020-10-09T15:47:55.381Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cobalt’s PtaaS platform has a powerful new feature: Assets</h3><p>We are excited to introduce — Assets.</p><p>In Cobalt terminology, an Asset is the highest level under which you can group your testing efforts by their scope — such as a Web Application, a Mobile App, an API, an External or Internal network, or a Cloud instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SalhKmXbtuHjPQaRmabNZQ.png" /><figcaption>An <strong>Asset</strong> enables your testing efforts to be grouped by their scope</figcaption></figure><p>Here are the benefits you can start taking advantage of once your pentests are grouped under assets:</p><ul><li><strong>Improved management and efficiency for consecutive rounds of pentesting</strong></li></ul><p>An asset allows you to group all the important documentation and collateral that pentesters will need; including user model overviews, API documents, and video walk-throughs. Before starting a new pentest, you can easily review the asset to ensure all this information is up to date, ensuring new teams have a complete overview. There’s no need to submit the same information over again.</p><ul><li><strong>Ease in tracking your pentesting progress</strong></li></ul><p>You can easily see and track the progress of each pentest for an asset all on one page. This is especially helpful when you need to do multiple rounds of pentesting concurrently and need to easily see how many vulnerabilities were found.</p><ul><li><strong>Improved quality of time spent on pentesting</strong></li></ul><p>We know it’s not always possible for security and development teams to have all the vulnerability findings fixed before the next round of pentesting. By grouping all your pentests under an asset, you can now easily see which findings should be carried over to the next round of pentesting. Assets also provide valuable information to the researcher team on what vulnerabilities were previously found. This ensures that all relevant findings are consolidated on the latest pentest.</p><p>And last, but not least, Assets will enable you to take advantage of another new feature — <strong>Cobalt Insights</strong>! With Insights, you can now <strong>track and compare</strong> your pentest findings by <em>criticality, status</em>, and<em> the type</em> — helping you effectively act upon the most critical vulnerabilities by knowing where you need to prioritize your remediation efforts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IIuU4izSc5yyYlkvszMwlQ.png" /><figcaption>Track and compare your pentest findings by <em>criticality, status</em>, and<em> the type</em></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36133e02e045" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Tips for Making the Most of a Pen Test Report]]></title>
            <link>https://medium.com/@MrJakobStorm/4-tips-for-making-the-most-of-a-pen-test-report-6ef3fb8d1bfc?source=rss-93b0fb2df52c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ef3fb8d1bfc</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[modern-pen-testing]]></category>
            <category><![CDATA[industry-insights]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Storm]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 15:33:39 GMT</pubDate>
            <atom:updated>2021-06-10T18:07:58.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*K47Zpjt5PwDqu5MKA9T7Ag.png" /></figure><p>In traditional pen testing models, the final report consists of a pdf summary of the findings emailed to you at the end of a testing period. All communication around individual vulnerabilities usually happens in a one-hour readout call, then you’re on your own. This old-fashioned way of reporting works for compliance purposes, but for the developers who actually need to fix the findings, it’s not the best delivery method.</p><p>With <a href="https://cobalt.io/">Cobalt’s Pen Testing as a Service model</a>, reporting is an interactive and ongoing process. Individual findings are posted on the <a href="https://cobalt.io/platform">platform</a> as they are found, and at the end of a test the pen test lead reviews all the findings and produces a final summary report. Once complete, the lead passes it on to the customer. The final report that is sent over at the end of a test isn’t static, it’s a living document and reflects the changes and input made. For example, when vulnerabilities are marked ready for re-test on the platform, the researcher will verify the fix and update the state which is then automatically reflected on the full report.</p><p>Here are 4 tips to get the most out of a pen test report:</p><h4>1. Get Involved in the Risk Assessment</h4><p>The <a href="https://cobalt.io/talent">Cobalt researchers</a> are experts in pen testing and have strong experience in assessing risk from a technical standpoint — but they don’t know your business as well as you, and sometimes it can be challenging for a third party to assess the actual business impact of a vulnerability. The pen test lead will always have the final say in the risk assessment, but relevant information is key for good decisions. Therefore, we encourage business teams to get involved in the risk assessment process by providing business related insights to the pen test lead so the assigned risk is aligned with the real world. You can do this by providing comments directly in the platform for each individual finding as it is reported.</p><h4>2. Show Progress to Stakeholders</h4><p>During a pen test there are many stakeholders that may be interested in the findings and success of a test. This may be members of your security team, engineering, product, etc. You want to show stakeholders that the test was successful, that you are fixing vulnerabilities, and that you are more secure. You can do this by providing them with most up-to-date information. With traditional pen testing this would mean you are updating the final report you were given. With Cobalt, the status of findings are automatically updated as they are fixed. This gives you the ability to download the most up-to-date report at anytime. The pen testing is a point in time, but the final report is a living document that shows the fixes overall.</p><h4>3. Use Different Report Views</h4><p>After testing is done, you want to be able to share the results with key stakeholders. However, the amount of information you want to share with each individual can differ. This is where having different versions of you full report can help summarize only certain information to different stakeholders. With Cobalt, we make this easy by offering three different levels: Attestation, Full Report, and Full Report + Findings Details. No need to go in cut, copy, and paste. Have it ready with a click of a button.</p><h4>4. Facilitate Direct Communication with Developers</h4><p>While a full pen test summary report is great for compliance and stakeholder management, reporting to the developers needs to be more detailed. It’s important that the communication channel between security and Development teams is as seamless as possible. The easier it is to communicate, the more likely it is that findings will get fixed. Traditionally, this finding communication is done via email, but with Cobalt this can be done by either inviting the developers into the platform for direct communication and/or setting up integrations enabling you to push the findings over to your JIRA or GitHub project with the click of a button.</p><p>Hope these tips offer some guidance as you manage your pen test reports. Feel free to comment or reach out with feedback or additional tips.</p><p>In case you missed the previous step in the pen testing process. Here are <a href="https://blog.cobalt.io/4-tips-for-keeping-a-pen-test-methodology-successful-dbbb585d3778">4 Tips for Keeping a Pen Test Methodology Successful</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ef3fb8d1bfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Tips for Preparing for a Pen Test]]></title>
            <link>https://medium.com/@MrJakobStorm/3-tips-for-preparing-for-a-pen-test-a150f2c22bf1?source=rss-93b0fb2df52c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a150f2c22bf1</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[industry-insights]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Storm]]></dc:creator>
            <pubDate>Tue, 24 Oct 2017 16:37:28 GMT</pubDate>
            <atom:updated>2021-02-12T19:21:57.862Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lessons learned from over 300 pen tests</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*SHDMrVmfSnCWqZ20gJCR3Q.png" /></figure><p>I’m the Chief Operations Officer at <a href="https://cobalt.io/">Cobalt</a>, a <a href="https://cobalt.io/services/pentest-service">Pen Testing as a Service</a> company that has performed over 300 pen tests to-date. It’s my job to make sure that each and every one of our pen test programs is up and running properly. A large part of that deals with preparing organizations and pen testers for the pen test engagement. If you know that you are going to be running a <a href="https://cobalt.io/pentest">pen test</a>, internal or external, then you need to get your ducks in a row and prepare for it.</p><p>Often times there is a negative connotation associated with pen testing preparation; that it’s this agonizing, irritating, and time-consuming task. However, this doesn’t have to be the case. <a href="https://resource.cobalt.io/analyst-research-roi-of-pen-testing-as-a-service">Our customers tell us that their teams overall spend is about 3 hours preparing for a Cobalt pen test</a>. Though these 3 hours of work are not done all at once, and are not necessarily completed by the same individual.</p><p>These three tips will help make preparing for a pen test much easier:</p><h4>1. Drop the Silos — Align security and development teams</h4><p>To effectively find and fix application security issues there needs to be collaboration and communication between the security, product, and development teams. Organizations can use pen testing to facilitate this conversation. Pen test findings serve as a great feedback loop for this conversation, and it gives developers an opportunity to understand the real-world implications of writing insecure code.</p><p>However, security organizations often focus on defect discovery instead of focusing on process and cross-functional relationships that are required to get issues fixed. By involving and coordinating with dev teams in the beginning of the pen testing preparation process then they will be more committed to fix the issues found. Developers should have an understanding around what is happening. Security teams will get better responses from dev, and dev will not feel like they are getting pushed around from security.</p><p><em>Note to security teams: Remember to deliver the good news about securely built modules etc. — this creates positive reinforcement and a nice work climate.</em></p><p>If you prepare the teams and align them on what will be tested. You can better facilitate a more open and positive line of communication during the pen test.</p><h4>2. Focus on the Important — Clear and impactful scope</h4><p>One common mistake with preparing for a pen test is that the security team feels that they need to provide the pen tester with every single nitty-gritty detail about their application. Although including every detail can add a little value it is often a lot of unnecessary work. What is more important is to provide the tester with the critical workflows, key features, and data flows. Give them the important information, and that’s it. Too much information can make the important details get lost in the dust, as well as, take away from everyone’s valuable time.</p><p>The best way to think about it is, “what can I provide that gives the tester the information needed to perform the test, and that doesn’t take away too much of my/his/her time.” Maybe that is creating a short screen sharing video of common workflows, or providing a checklist of key features. That is up to you to decide, but just remember it’s not about just about quantity, quality plays a larger role.</p><h4>3. Work with Experts — Obtain the right pen testers</h4><p>It’s a no-brainer that you want to have highly skilled and qualified pen testers looking into your application, but it’s also just as important to have those tester’s skills match the scope of what you want tested. Skills matching is a critical component to achieving quality results in any penetration test. The benefit of a pen test shouldn’t just be in discovering vulnerabilities, but using that knowledge to reduce the risk associated with the application. The more important attributes of any penetration tester are skill set, experience, and performance. When choosing your testers, this could be internally or externally with pen test providers, you need match their skills to your tech stack. You want the tester to be familiar with what they are testing.</p><p>If you have the right workflows set in place, preparing for a pen test can be easy. Know what you’re testing, communicate this to the right teams, and have the best individuals, given your scope, perform the testing.</p><p>Hope these tips offer some guidance in preparing your pen test program. This blog was the first in a series about the pen testing process. Look out for the next blog post in this series that will dive into tips for kicking off your pen test.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a150f2c22bf1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hybrid Vigor of Security Testing]]></title>
            <link>https://medium.com/@MrJakobStorm/the-hybrid-vigor-of-security-testing-b78caf6d4d59?source=rss-93b0fb2df52c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78caf6d4d59</guid>
            <category><![CDATA[industry-insights]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Storm]]></dc:creator>
            <pubDate>Mon, 24 Oct 2016 19:11:30 GMT</pubDate>
            <atom:updated>2016-10-25T20:09:41.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pbaSFDuLCP0TlI3IIUS_8w.png" /></figure><p>Cobalt has been on the forefront of the wave of bug bounty programs. We have been running public, curated, and private versions of these for businesses over the years. What we have noticed is that businesses are constantly juggling the trade-off between noise vs. exposure/coverage.</p><p>Through our experience in these programs we have learned two valuable concepts. The most obvious learning is that nothing beats human logic — both in introducing vulnerabilities, <em>and </em>in identifying them — the automatic scanners out there only scratch the surface. In addition, we’ve learned that one size does not fit all. Each application is different, and its security should accommodate those differences.</p><p>It’s been an extremely interesting process — turning the different knobs to find a balance that makes sense depending on an applications security maturity level, team size, security drivers (e.g. compliance or internal security standards), and more. And we’ve learned a lot!</p><p>There is no doubt in my mind that a bug bounty program is a powerful tool — a lot of issues will surface from them. But, and there is a but, it’s a big job to manage it effectively, too big for most companies out there. I won’t dive deep into these hidden cost today, but feel free to check out one of our <a href="https://blog.cobalt.io/deconstructing-and-rewiring-bug-bounty-programs-f76c2b72dd11#.mtpvapppw">previous blog posts</a> for a closer look.</p><p>One way to counter the issues of bug bounties programs is through traditional application vulnerability assessments — it’s a tried and true concept. You get structured and guaranteed coverage that is often set at a predictable cost. So it is easy to budget with and you can document the work to your stakeholders. However, too often the actual human testing is done by junior researchers, poorly incentivized working on an hourly pay. Or they may even substitute the human logic and ingenuity for a generic scanner.</p><p>Now I come back to the headline of this post, hybrid vigor. The improved functioning of any biological quality in a hybrid offspring. What if we took the elements that make bug bounties awesome — incentives, a qualified and diverse talent pool — and mix it with virtues from the traditional assessment world — structure, coverage, quality assurance, and fixed costs. Furthermore, powering this hybrid with technology that enables integration, communication, and collaboration. Making it a breeze to start and run an application security assessment, as well as making it easy for the DevOps teams to access issues, ask questions if needed, and finally fix them — which is the ultimate goal.</p><p>What would we call that cross between bug bounties and vulnerability assessments you may be asking? We call that hybrid offspring the <strong>Cobalt Pen Test</strong>. We assemble the best team for your company and applications based on the application size and tech stack. This handpicked security team will then deliver guaranteed coverage and actionable issue reports — including a top level executive summary that can easily be shared with relevant stakeholders.</p><p>With a security solution like this there are a number of advantages that come to mind: #Humanlogic, #tools_assisted, #great_talent, #feedback_cycles, #ratings, #collaboration, #agile, #integrated.</p><p>Feel free to tweet at us with some of the hashtags at <a href="https://twitter.com/cobalt_io">@Cobalt.io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78caf6d4d59" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>