<?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 Luis Abreu from Cyver on Medium]]></title>
        <description><![CDATA[Stories by Luis Abreu from Cyver on Medium]]></description>
        <link>https://medium.com/@cyver?source=rss-724b38146c40------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I4V2A4iy4Ajy5ymStkNHBg.png</url>
            <title>Stories by Luis Abreu from Cyver on Medium</title>
            <link>https://medium.com/@cyver?source=rss-724b38146c40------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:47:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cyver/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[Why Changing Findings Between Retests Cost Pentest Teams More Than They Think]]></title>
            <link>https://medium.com/@cyver/why-changing-findings-between-retests-cost-pentest-teams-more-than-they-think-766047779eca?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/766047779eca</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[pentest]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 12:47:03 GMT</pubDate>
            <atom:updated>2026-11-21T12:47:03.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MnJwoZGwQUdJ5BFjjV8SlA.png" /></figure><p>Findings that change between retests usually mean the process is working. A vulnerability gets fixed, a severity is revised after new evidence, or a confirmed issue turns out to be a false positive, which saves the client from remediating something that was never a risk. All of this is normal, and it shows a team that keeps refining its results.</p><p>The problem is what each change does to the reporting workflow. A single engagement already involves many moving parts: discovering and documenting findings, validating fixes, and communicating outcomes. Every change between the first test and the retest adds another state to track. When nothing tracks it systematically, the cost is spread out and hard to notice.</p><p><strong>Keeping one finding’s history intact</strong></p><p>When a finding looks different at retest, the team has to work out what it is looking at. It could be the same issue with updated details, a resolved issue, or a new one that happens to look similar.</p><p>Without a consistent way to link findings across assessments, context gets lost: earlier evidence, how the risk score changed, notes from the original tester. Teams then spend time rebuilding what changed instead of confirming whether the risk was actually addressed. The client pays for that time too, in slower answers and less clarity.</p><p><strong>Comparing reports by hand</strong></p><p>Comparing the initial report with the retest report should be a quick check of what was fixed. In practice, it often means reading versions side by side to confirm that two entries describe the same thing.</p><p>This gets harder when several testers, assessments or report formats are involved. Small differences in wording can hide whether real progress was made, and a single missed detail weakens trust in the whole report.</p><p><strong>The effect on confidence</strong></p><p>Clients rely on pentest reports to make remediation decisions, so accuracy and consistency are what they are paying for. A report is only as trustworthy as the process behind it.</p><p>If the team has to reconcile changes manually, it cannot be fully confident that nothing was missed. That uncertainty grows with the number of engagements, and clients feel it eventually.</p><p><strong>Part of a larger problem</strong></p><p>Changing findings are one symptom of something broader. Duplicated findings, incomplete documentation and remediation that can’t be traced back all come from the same source: workflows that weren’t built to keep findings connected over time. As engagements involve more tools, more findings and more testing methods, these gaps widen.</p><p>The fix is structural. When findings live in one system from discovery through remediation and retest, each vulnerability keeps a single, continuous record. Consultants can see at a glance whether an issue was updated, resolved or needs more work, and a standardized workflow means every engagement is reported the same way. This is the approach behind <a href="https://core.cyver.io/">Cyver Core</a>.</p><p><strong>Conclusion</strong></p><p>Changed findings rarely look like a problem, which is why their cost stays hidden. The impact shows up later as rework, reconciliation and small inconsistencies that weaken a report.</p><p>For many teams, these errors trace back to process, not technical skill. Keeping findings connected and reporting consistent is what lets a pentest practice scale without losing accuracy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=766047779eca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exposure Is Not Risk: Why Pentest Findings Need Exploitability Context]]></title>
            <link>https://medium.com/@cyver/exposure-is-not-risk-why-pentest-findings-need-exploitability-context-bc551c987ad9?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc551c987ad9</guid>
            <category><![CDATA[red-teaming]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 12:45:58 GMT</pubDate>
            <atom:updated>2026-11-21T12:45:58.481Z</atom:updated>
            <content:encoded><![CDATA[<p>Exposure Is Not Risk: Why Pentest Findings Need Exploitability Context</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzqINLwBONz3M7nOG-dUBQ.png" /></figure><p>A pentest is meant to show how an attacker could compromise an environment. Telling a client that something is exposed is part of that, but on its own it rarely tells them what to fix first. Findings without exploitability context make a report longer without making remediation any clearer.</p><p><strong>What exposure validation does</strong></p><p>Exposure validation confirms that a potential attack surface is actually reachable: an open port, a misconfigured service, an internet-facing application. Instead of relying on scanner output or assumptions, the testing team checks that the asset exists and can be accessed.</p><p>This step matters. You cannot reduce risk you haven’t located, and validating exposure removes false positives before they reach the report.</p><p>But it answers only one question: what can an attacker see or reach?</p><p><strong>What exploitability context adds</strong></p><p>The second question is: what can an attacker do with it?</p><p>Exposure means a weakness is present. Exploitability describes whether it can realistically be used, under what conditions, and with what outcome. When reports skip this step, every exposed asset carries roughly the same weight, and prioritization turns into guesswork.</p><p>Two examples show the difference.</p><p><em>High exposure, low exploitability.</em> A publicly accessible web application runs a version with a known vulnerability. As an exposure finding, it is valid. Further testing shows that exploiting it requires administrator credentials the tester could not obtain, and other controls restrict access further. The issue is real, but it belongs lower on the remediation list than the first finding suggests.</p><p><em>Low individual severity, high combined risk.</em> A low-privilege user account looks minor in isolation. Combined with a privilege escalation path, such as a misconfigured access control or an unpatched local vulnerability, it gives an attacker administrative access. Two manageable issues become one realistic attack path. You only see this when findings are assessed together, with context.</p><p><strong>What happens when context is missing</strong></p><p>Findings without context produce long lists where everything looks equally urgent. The usual result is misallocated effort:</p><ul><li>Teams fix low-impact items first and leave serious ones open longer.</li><li>Resources go to exposures that may not be practically exploitable at all.</li><li>Critical attack paths get buried among dozens of similar-looking entries.</li></ul><p>The value of a pentest, whether it’s a one-off engagement or an ongoing service, comes less from how much exposure it surfaces and more from showing which exposures matter.</p><p><strong>Context only helps if it is structured</strong></p><p>Having exploitability data is not enough. If it reaches the client as loose notes, it becomes one more thing for them to interpret.</p><p>Useful reporting makes three things explicit:</p><ul><li><strong>Exposure:</strong> what is reachable</li><li><strong>Technique:</strong> how it could be used, alone or chained with other weaknesses</li><li><strong>Outcome:</strong> what an attacker would gain</li></ul><p>This depends on how the testing team works internally. If findings, evidence and attack paths are scattered across tools and documents during the engagement, the report will be fragmented too. Teams that manage findings in one structured, central system are better placed to deliver context that is consistent and actionable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc551c987ad9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Attack Chain Is the Deliverable, So Why Do Most Red Team Reports Lose It?]]></title>
            <link>https://medium.com/@cyver/the-attack-chain-is-the-deliverable-so-why-do-most-red-team-reports-lose-it-cfc6b3937e15?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfc6b3937e15</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[red-teaming]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[pentester]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 06:34:49 GMT</pubDate>
            <atom:updated>2026-09-20T06:34:49.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1V5aankeofdOu7_ewNl-A.png" /></figure><p>A red team engagement doesn’t fail because the operators couldn’t get in. It fails, as a communication exercise, when the client can see every individual finding but can’t reconstruct how those findings connected into a working attack path. That distinction gets lost constantly, and it’s worth separating out: a finding tells you a door was unlocked. The attack chain tells you why that door mattered, what it led to, and what should have stopped it before it did.</p><h3>How progression usually gets tracked</h3><p>Most teams reconstruct the chain after the fact, from three sources: operator notes, screenshots and log evidence, and a mapping pass against MITRE ATT&amp;CK or the Cyber Kill Chain. Each piece answers a narrow question what technique was used, what was accessed, what the outcome was. None of them, on their own, answers the question the client actually cares about: how did step 4 depend on evidence collected in step 1, and would the engagement have gone differently if that dependency had been caught earlier.</p><h3>The real challenge is fragmentation</h3><p>Engagements aren’t linear, so the record of them shouldn’t be treated as if it were. Operators pivot, back out of dead ends, and combine techniques from unrelated phases into a single working exploit. A credential harvested in phase one might only become relevant three phases later, in a context nobody was tracking when it was first collected. When the record of that credential lives in a different note, tool, or screenshot folder than the record of where it eventually got used, reconstructing the dependency becomes a manual reassembly job done under deadline, at the end of the engagement, by whoever’s writing the report. That reassembly cost scales worse than the engagements do. Cloud infrastructure, remote-access tooling, and API surface area have pushed even smaller red team objectives into multi-path territory, where a single engagement can touch several independent attack paths in parallel. More paths means more cross-references to hold in your head while writing the report, and disconnected evidence stores don’t hold state for you.</p><h3>What actually gets lost when this breaks down</h3><p>The individual finding survives a fragmented process a compromised credential or a successful phishing attempt still makes it into the report. What doesn’t reliably survive is the causal link between findings: why one weakness was exploitable because of a decision made two steps earlier, and where in that chain a defensive control should have interrupted it. A client reading a list of findings can patch each one individually. A client reading a reconstructed attack path can see which control, if fixed, would have broken three findings at once. That’s a materially different, and more useful, piece of intelligence and it’s the piece most reporting workflows aren’t structured to preserve.</p><h3>What a structured record changes</h3><p>The fix isn’t more thorough note-taking. It’s keeping attack-chain data techniques, evidence, ATT&amp;CK mapping, and outcomes in one connected workflow instead of scattered across notes and screenshots, so the dependencies between steps are visible while the engagement is still running, not reconstructed from memory afterward. This is the same problem Cyver Core’s red teaming workflow is built around: attack-chain visualization mapped to MITRE ATT&amp;CK and the Cyber Kill Chain, centralized evidence and findings, and reporting that’s assembled from that structure rather than stitched together at the end. Better tooling here doesn’t make the report more polished. It makes the causal story accurate which is the part of red team reporting that’s actually hard to fake and the easiest part to lose.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfc6b3937e15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Pentest Report to Closed Ticket: What Happens to a Vulnerability After It’s Found]]></title>
            <link>https://medium.com/@cyver/from-pentest-report-to-closed-ticket-what-happens-to-a-vulnerability-after-its-found-9942ae0fd777?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/9942ae0fd777</guid>
            <category><![CDATA[pentester]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[red-teaming]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 08:02:30 GMT</pubDate>
            <atom:updated>2026-08-17T08:02:30.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z0EKcrYT8sQ80NZXUShpZg.png" /></figure><p>A pentest engagement follows a fairly predictable arc: scope the assets, run the assessment (automated tooling plus manual testing), and document what turns up. Each finding gets a severity rating, a proof-of-concept, and a remediation recommendation, and then it moves into the development backlog.</p><p>That handoff is usually where the visibility ends. The report gets delivered, the engagement is marked complete, and what happens to the finding afterward, how it gets triaged, who picks it up, how long it sits , depends entirely on how the receiving organization handles security work internally.</p><h3>Not every backlog treats findings the same way</h3><p>Some organizations have no real process for this at all. A finding lands in the backlog next to feature requests and bug reports, with nothing to flag it as security-relevant or time-sensitive, and it can sit there for months. Nobody owns it, so nobody’s accountable for it slipping.</p><p>Others have a defined handling path: findings get triaged, ownership gets assigned, progress gets tracked, and the security team eventually confirms the fix actually works. When that path exists, it tends to break down into the same handful of stages.</p><h3>Triage: not every finding is equally urgent</h3><p>The first stage is deciding what matters most. A critical remote code execution finding and a low-severity misconfiguration are not the same kind of problem, even if they arrived in the same report. Triage means weighing severity and exploitability together with what the finding would actually cost the business if someone exploited it before it’s fixed.</p><h3>Assignment: someone has to actually own it</h3><p>Once findings are ranked, they need an owner, a specific developer, the team responsible for the affected service, or (for anything crossing system boundaries) a cross-functional group that can coordinate a fix across teams.</p><p>The ownership itself matters less than making sure it’s unambiguous. A finding with no clear owner tends to get deprioritized by default, not by decision. Assignment should also carry context with it: the proof-of-concept, links to the affected code or asset, and a remediation suggestion. The less a developer has to go digging or ask the security team to re-explain what they meant, the faster the fix moves, which is largely what platforms like ours are built to automate and make visible end to end.</p><h3>Tracking: making progress visible to everyone, not just the assignee</h3><p>Ownership without visibility just relocates the problem. Teams need a shared view of when a vulnerability was found, who’s responsible for it, and where it currently sits in the remediation lifecycle, otherwise a finding can be “in progress” indefinitely with no one able to say what that actually means.</p><p>This is where dashboards and integrations with tools like <a href="https://newwavesolution.com/what-is-jira-software/">Jira</a> do real work: they keep security findings in the same field of view as everything else competing for a developer’s attention, instead of living in a separate report that only gets opened once.</p><h3>Why fixes stall</h3><p>Even organizations with a defined process hit friction. The common causes tend to repeat:</p><p><strong>Cross-team dependencies.</strong> Some findings can’t be fixed by one team alone, infrastructure, API, and security groups all need to be in sync, particularly when <a href="https://core.cyver.io/how-to-standardise-security-test-reports-across-a-distributed-team/">testing spans a distributed team</a>.</p><p><strong>Competing priorities.</strong> Developers are already balancing feature work and other bugs; security fixes lose that competition more often than they should.</p><p><strong>Missing expertise.</strong> Some vulnerability classes need specialized knowledge that isn’t always on hand.</p><p><strong>Vague remediation guidance.</strong> A finding without a clear proof-of-concept or fix suggestion creates back-and-forth instead of forward progress.</p><p><strong>Thin reporting.</strong> Missing context is the quiet version of the above, it doesn’t block the fix outright, it just makes it slower and less precise.</p><p>None of these are unusual on their own. The risk is that they compound quietly, a backlog doesn’t fail all at once, it degrades one deprioritized finding at a time. Catching that requires regular backlog grooming (reviewing, reprioritizing, and clarifying what’s still outstanding), paired with <a href="https://asana.com/resources/team-communication">better communication habits across teams</a> and, where manual tracking is itself the bottleneck, more automation.</p><h3>Closure isn’t the same as “marked done”</h3><p>The last stage is verification. A fix isn’t actually resolved until the security team retests it and confirms the vulnerability is no longer exploitable, updating the severity if needed. That step is what closes the loop between security and development, without it, “done” just means someone stopped looking at the ticket, not that the risk is gone.</p><h3>The gap between what should happen and what does</h3><p>This is the process as it’s meant to work. In practice, plenty of security teams find vulnerabilities without a structured way to hand them off, and plenty of developers receive findings with no context or priority attached, which is usually where the process above breaks down first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9942ae0fd777" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Red Teaming Makes Attack Chains Visible]]></title>
            <link>https://medium.com/@cyver/why-red-teaming-makes-attack-chains-visible-7c9f65ef0ef3?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c9f65ef0ef3</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Mon, 06 Oct 2025 20:46:39 GMT</pubDate>
            <atom:updated>2025-10-06T20:46:39.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyChZ9fW1LaUk3zihK2OTA.png" /></figure><p>Attackers rarely use one big exploit. They take small steps that connect. A weak password, a cloud misconfiguration, or an exposed endpoint can link together and give access to sensitive systems.</p><p>That sequence of steps is called an <strong>attack chain</strong>. It shows how different parts of your environment interact and how real attacks unfold. Red teaming helps you see that path clearly, before someone else does.</p><h3>From Issues to Attack Paths</h3><p>Traditional penetration tests help identify security issues. They give you a list of vulnerabilities, a severity rating, and recommendations. That’s useful, but it doesn’t always explain how those findings work together.</p><p>Red teams go deeper. They simulate how an attacker would actually move through your environment using the weaknesses already there. The goal is to understand what can happen when several small risks align — not just to confirm that they exist.</p><h3>Why the Full Chain Matters</h3><p>Every red team exercise follows a story. It starts with reconnaissance and initial access, then continues with lateral movement, privilege escalation, and persistence. Each stage reveals how systems, identities, and policies connect.</p><p>The more complex your infrastructure, the more hidden paths appear. Those paths often matter more than individual vulnerabilities. If you only test isolated issues, you don’t see the real picture of how an attack could spread.</p><h3>Measure Real-World Response</h3><p>Red team exercises also show how well your organization detects and reacts to threats.</p><p>Can your SOC recognize suspicious privilege changes? Does your EDR notice when someone moves across systems? Does your team report a phishing email before credentials are stolen?</p><p>These tests measure readiness in real conditions. They show how your tools and people perform together when facing an actual scenario.</p><h3>Turn Findings Into Action</h3><p>Red teamers often spend weeks documenting every step of an attack simulation. The result is detailed, but sometimes difficult for internal teams to act on.</p><p>That’s where <strong>Cyver Core</strong> comes in. We built it to make those stories clear and practical. The platform visualizes attack paths, connects vulnerabilities with identities and assets, and adds context to each step.</p><p>Instead of reading through pages of data, teams can follow a mapped chain, understand priorities, and plan the right response.</p><h3>Break the Chain Before It Breaks You</h3><p>When you understand your attack chain, you can focus your efforts where they matter most. Sometimes that means patching a service. Sometimes it means improving identity management or monitoring. Often, it’s a combination.</p><p>Red teams uncover the chain. Cyver Core helps you analyze and act on it. Seeing how attacks could connect makes it easier to prevent them.</p><p><strong>Want to see how Cyver Core helps visualize attack chains?</strong><br>Start a test project and explore how your red team findings turn into clear, actionable insight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c9f65ef0ef3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retesting Vulnerabilities: Why Security Doesn’t End at the Patch]]></title>
            <link>https://medium.com/@cyver/retesting-vulnerabilities-why-security-doesnt-end-at-the-patch-3806b215d950?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/3806b215d950</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[pentester]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 07:17:13 GMT</pubDate>
            <atom:updated>2025-09-30T07:17:13.199Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zp5_5FiBWRkR4hkOdSYGA.png" /></figure><p>I’ve spent years building tools for pentesters and security teams, and one thing has become clear: fixing vulnerabilities isn’t the finish line — it’s just another checkpoint.</p><p>Here’s the truth most teams don’t like to hear: patching without retesting leaves you exposed. On paper, the CVE might be closed. In practice, you may have shifted the risk somewhere else. And in 2025, where AI is amplifying how attackers discover and chain weaknesses, that’s a risk you can’t afford.</p><h3>Patching Alone Creates a False Sense of Security</h3><p>Most organizations measure themselves by patch speed. That’s logical — it reduces exposure time. But I’ve seen too many cases where “fast patching” actually masked a deeper issue:</p><ul><li>Was the fix applied consistently across environments?</li><li>Did staging and production both get updated?</li><li>Did the change introduce new misconfigurations or IAM drift?</li><li>Did it solve the root cause, or just silence the immediate symptom?</li></ul><p>These blind spots aren’t hypothetical. Attackers don’t care about your SLA; they care about whether the door is really locked. And with AI-driven reconnaissance, they’ll find the smallest crack.</p><h3>Why AI Changes the Equation</h3><p>Attackers today aren’t limited by time or human fatigue. They’re running LLM-powered tools that can:</p><ul><li>Generate tailored payloads</li></ul><p>Reason across multiple service interactions</p><ul><li>Probe for lateral movement opportunities you never anticipated</li></ul><p>This isn’t brute force. It’s intelligent, adaptive hunting. And if your remediation isn’t validated through retesting, AI will find the gaps before you do.</p><h3>Retesting Is Reenactment, Not a Checkbox</h3><p>Retesting doesn’t mean rerunning a scan. It means replaying the original exploit chain, in the real environment, after the fix. It means checking the context: IAM roles, adjacent services, network exposure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7KtXmk4wSTWeqDx2.png" /></figure><p>This mindset aligns with Continuous Threat Exposure Management (CTEM). Instead of “find, patch, and hope,” CTEM is about <strong>simulate, validate, and close the loop — continuously.</strong> Retesting is the heartbeat of that loop. It turns fixes into measurable assurance, not theoretical compliance.</p><h3>How We Built Retesting Into Cyver</h3><p>When I started Cyver, I wanted to break away from the old pentesting cycle: find → report → fix → forget. That’s why retesting is core to our approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UYgkb3IURpBN1RCQ.png" /></figure><p>On Cyver Core, security teams and pentesters can:</p><ul><li>Re-execute test cases immediately after a fix</li><li>Track attack paths across remediation stages</li><li>Document whether an issue is still exploitable or resolved — with evidence</li></ul><p>And because we built it for scalability, teams can standardize validation across clients and environments. Less human error, faster turnaround, stronger assurance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6OAa3OQ8GM23r_Lt.png" /></figure><h3>From Reactive to Proactive Security</h3><p>The attackers have already gone proactive. AI has given them reach and creativity at scale. If defenders stick to reactive patch-and-move-on cycles, they’ll always be a step behind.</p><p>Retesting is how we catch up. It’s how we verify fixes in real-world conditions, not just in Jira tickets. It’s how security teams move from “we think it’s fixed” to “we know it’s closed.”</p><p>And that’s what gives me confidence in the work we do at Cyver — helping teams prove their security, not just assume it.</p><p>Because in the end, attackers don’t read your reports. They test your systems. And you should too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3806b215d950" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why cloud-native pentest platforms are changing the game]]></title>
            <link>https://medium.com/@cyver/why-cloud-native-pentest-platforms-are-changing-the-game-f491c2527b2f?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/f491c2527b2f</guid>
            <category><![CDATA[pentester]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 13:17:42 GMT</pubDate>
            <atom:updated>2025-09-21T13:17:42.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6ENlMJoTps3KCLbnl5mXg.png" /></figure><p>When I first started working in pentesting, reporting always felt like the bottleneck. Collecting screenshots, formatting endless Word docs, and emailing versions back and forth with clients took up more time than the actual testing. That approach worked when projects were occasional and expectations were lower. But today, security work looks very different.</p><p>Engagements are continuous, environments are complex, and clients want answers yesterday. Static reports just don’t cut it anymore. That’s why I believe cloud-native pentest platforms are no longer optional — they’re essential for keeping pace with modern security needs.</p><h3>Why on-prem still feels “safe” (but rarely is efficient)</h3><p>Many teams still lean on on-premise systems because they feel more secure. You keep everything behind the firewall, you’re in control, and nothing leaves your infrastructure. But that control comes at a cost: constant patching, downtime for updates, manual report exports, and version chaos across multiple files.</p><p>The truth is, the more projects you handle, the heavier that burden becomes. Instead of focusing on security, teams end up managing infrastructure. And while that might feel safe, it’s not the most effective use of limited time and resources.</p><h3>Cloud-native is a workflow shift</h3><p>The real difference with a cloud-native approach is how it changes the entire pentest lifecycle. Findings aren’t locked away until the final report. They’re added as the engagement progresses, so clients can already act on them. Communication happens in the same platform, not in messy email threads. Reports pull directly from live data instead of static snapshots.</p><p>This shift makes collaboration natural. Clients see progress, confirm fixes, and provide feedback along the way. Meanwhile, testers don’t waste energy duplicating work. Everything — scopes, evidence, vulnerabilities, and exports — lives in one place.</p><p>That’s the vision behind Cyver Core: make pentesting smoother for both sides without adding overhead.</p><h3>Addressing security concerns head-on</h3><p>I get why security professionals hesitate with the cloud. But in 2025, “cloud-native” no longer means sacrificing control. On the contrary, it often means stronger protections.</p><p>At Cyver, we built on top of mature cloud infrastructure with encryption in transit and at rest, role-based access, full audit logs, and single sign-on. Automatic updates ensure patches are applied without anyone having to open a ticket or schedule downtime. Instead of manually maintaining a system, your team gets the assurance that the platform is secure and always up to date.</p><h3>Speed without sacrificing accuracy</h3><p>The challenge with reporting has always been balancing speed and accuracy. Deliver too fast, and details slip through the cracks. Take too long, and the findings lose relevance.</p><p>With a centralized cloud-native system, that tension eases. Reports update in real time. Validation, remediation, and status tracking all happen in one place. Instead of chasing down the latest version, everyone works from a single source of truth. The result: faster delivery without sacrificing quality.</p><h3>Where on-prem still makes sense</h3><p>Of course, there are cases where on-premise is the only option — regulated industries, certain government contracts, or organizations with strict policies. In those cases, cloud might not be viable.</p><p>But for most teams handling dynamic scopes, multiple clients, or fast-paced projects, the overhead of running everything internally is too high. Cloud-native simply scales better.</p><p>Pentesting has evolved. It’s not only about identifying vulnerabilities — it’s about enabling clients to remediate faster and reduce risk in real time. That’s why the way we report matters.</p><p>A cloud-native platform doesn’t just modernize infrastructure. It transforms delivery. It gives teams clarity, speed, and collaboration without the extra friction.</p><p>That’s what we’ve built with Cyver Core, and it’s what I believe will define the next era of pentesting. If your reporting process still depends on PDFs and email chains, it might be time to rethink the workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f491c2527b2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Threat Exposure Management: Why It Matters and How to Make It Real]]></title>
            <link>https://medium.com/@cyver/continuous-threat-exposure-management-why-it-matters-and-how-to-make-it-real-b91efd554ce0?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/b91efd554ce0</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Mon, 08 Sep 2025 10:50:42 GMT</pubDate>
            <atom:updated>2025-09-08T10:50:42.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MIhHRsSgjj0kK3AF-wvukQ.png" /></figure><p>Cybersecurity is shifting under our feet. Attack surfaces don’t sit still anymore — they expand with every SaaS tool, every cloud instance, every new line of code. Running a scan every quarter — or even every month — just doesn’t cut it when attackers are automating exploits within hours of a new CVE being published.</p><p>That’s why Continuous Threat Exposure Management (CTEM) has started to gain real traction. And let me be clear: CTEM isn’t another shiny acronym. It’s a mindset shift. It’s about moving away from “finding vulnerabilities” as a static task and instead treating exposure as something alive, dynamic, and tied to business reality.</p><h3>What CTEM Actually Is</h3><p>Gartner coined the term, but the principle is straightforward: CTEM is a structured, ongoing process where you <strong>discover, validate, and reduce exposures continuously</strong>, not on a schedule.</p><p>Here’s the way I see it:</p><ul><li><strong>Scope</strong>: Decide what matters most — your core assets, your critical infrastructure, your business-driving applications.</li><li><strong>Discover</strong>: Keep your eyes open. Constant monitoring across infrastructure, apps, and integrations.</li><li><strong>Prioritize</strong>: Context is everything. A “critical” CVSS score is meaningless unless you know how it touches your business.</li><li><strong>Validate</strong>: Test whether vulnerabilities are <em>actually</em> exploitable, not just flagged by a scanner.</li><li><strong>Mobilize</strong>: Fix fast, document the response, and close the loop.</li></ul><p>It’s not a product you buy. It’s a loop you run, refine, and repeat as your environment — and the threat landscape — keeps changing.</p><h3>Why Companies Are Turning to CTEM</h3><p>The problem with legacy vulnerability management is timing. A scan gives you a snapshot, but by the time you act, the picture is already outdated. Meanwhile, your environment has shifted, and so have the attackers.</p><p>Modern organizations need near-real-time awareness. With CTEM, you’re not waiting for the next audit cycle — you’re operating in a <strong>continuous feedback loop</strong> where:</p><ul><li>High-risk exposures get caught and addressed faster.</li><li>Risks are prioritized using live threat intelligence and business impact, not just raw severity scores.</li><li>Fixes are validated, so you’re not just closing tickets — you’re closing risk.</li><li>Security starts syncing with IT and leadership instead of living in its own silo.</li></ul><p>This is where the real value lies: <strong>better decisions, made faster, with fewer blind spots.</strong></p><h3>The Hard Part: Making CTEM Work</h3><p>Adopting CTEM isn’t just about buying more scanners. In fact, most companies already have plenty of tools. The real challenge is operational.</p><ul><li><strong>Fragmentation</strong>: Data is spread across scanners, spreadsheets, and ticketing systems. Making CTEM work means stitching it together into something coherent.</li><li><strong>Prioritization</strong>: When you’re flooded with new vulnerabilities daily, what gets fixed first? Without a strong risk model, teams drown in noise.</li><li><strong>Validation</strong>: Verifying exposures and confirming fixes takes time and discipline. Skip this, and you risk patching the wrong things — or thinking you fixed an issue that’s still wide open.</li><li><strong>Collaboration</strong>: CTEM forces security, IT, and development to align. Otherwise, discoveries don’t translate into meaningful change.</li></ul><p>In short, CTEM is as much about culture and workflows as it is about technology.</p><h3>Building Your CTEM Foundation</h3><p>If you’re serious about implementing CTEM, start simple:</p><ol><li><strong>Map what matters.</strong> Know your critical assets and the business functions tied to them.</li><li><strong>Make visibility routine.</strong> Stop tying it to audits — make it daily.</li><li><strong>Demand validation.</strong> Don’t trust fixes until they’re proven.</li><li><strong>Centralize exposure data.</strong> If information is fragmented across static reports, you can’t manage it continuously.</li></ol><p>CTEM isn’t about reacting faster to alerts. It’s about <strong>always knowing your true exposure surface</strong> and reducing it in a structured, ongoing way.</p><h3>Where Cyver Fits In</h3><p>When we built <strong>Cyver Core</strong>, our goal was exactly this: to make continuous exposure management practical.</p><p>Instead of juggling spreadsheets and static PDFs, you get a single platform where vulnerabilities are dynamic records — linked to assets, scopes, and business objectives. Retesting, validation, and reporting all happen inside the same workflow. And because everything runs on live data, reports are always current, never stale snapshots.</p><p>CTEM only works when discovery, prioritization, validation, and remediation talk to each other. That’s what we designed Cyver Core for.</p><p>If you’re ready to move beyond reactive security and actually implement CTEM in a scalable way, we’d love to show you how.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b91efd554ce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud-Native or Containerized? What Really Works for Pentest Delivery]]></title>
            <link>https://medium.com/@cyver/cloud-native-or-containerized-what-really-works-for-pentest-delivery-ffeeb23991b3?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffeeb23991b3</guid>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentester]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 01:24:34 GMT</pubDate>
            <atom:updated>2025-09-01T01:24:34.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uxIDDZCDR6ho__fKO3RWlw.png" /></figure><p>Every now and then, I’ll be on a call with a prospect and the question comes up:<br>“Can we just run the platform in containers and manage it ourselves?”</p><p>It’s a fair question. Containers are everywhere. They promise flexibility, portability, and control — you spin up your own services, run them where you want, and manage everything in-house. For infrastructure teams, that’s gold.</p><p>But when we shift the conversation from <em>hosting software</em> to <em>delivering pentests</em>, the tradeoffs get real. Running a pentest management platform isn’t just about keeping an app alive. It’s about how you deliver work to clients: managing projects, collaborating in real time, reporting vulnerabilities, and proving fixes. And for that, infrastructure choices matter more than people realize.</p><h3>Control Sounds Good — Until You Own All of It</h3><p>Containers give you control, sure. You get to decide where the platform lives, how it scales, what it integrates with. But along with control comes responsibility.</p><p>If you deploy a pentest reporting platform in containers, suddenly you’re on the hook for:</p><ul><li>Uptime and monitoring</li><li>Patching and version management</li><li>Backups and disaster recovery</li><li>Security hardening and compliance audits</li><li>Logging, data handling, and everything in between</li></ul><p>That’s operating a SaaS business inside your own team. And unless infrastructure is your core mission, you risk spending more time firefighting environments than delivering pentests.</p><h3>Why Cloud-Native Works Better for Pentest Delivery</h3><p>Pentesting isn’t about servers or Kubernetes clusters. It’s about helping clients reduce risk — which means reporting vulnerabilities fast, validating fixes, and keeping everyone aligned.</p><p>Cloud-native platforms are designed around that outcome. You log in, open a project, and start working. The infrastructure is already there — elastic, secure, and maintained. Reports pull from live data, not exports. Clients get dashboards instead of long email threads. Collaboration happens in real time, inside the platform itself.</p><p>In other words: the cloud becomes the <em>delivery layer</em>, not just a hosting option.</p><h3>Security Isn’t About Where It Runs — It’s About How</h3><p>A lot of teams still assume: “If we host it ourselves, it’ll be more secure.” But that’s only true if you have a DevOps team applying patches, monitoring logs, and hardening the stack 24/7.</p><p>With a mature cloud-native platform like Cyver Core, security is built in:</p><ul><li>Encryption at rest and in transit</li><li>Role-based access and SSO</li><li>Continuous patching and monitoring</li><li>Audit trails and compliance-ready features</li></ul><p>Updates roll out automatically. Vulnerabilities get patched before disclosure. The security baseline improves constantly without extra effort on your side. For smaller consultancies and lean teams, that’s a massive advantage.</p><h3>Flexibility vs. Focus</h3><p>Yes, containers let you customize endlessly. You can integrate legacy systems, tweak routing, and control every dependency. But flexibility has a price: testing, compatibility checks, dependency management, and performance tuning.</p><p>Cloud-native SaaS flips that equation. Instead of worrying about environments, you focus on engagements. Reporting is instant, delivery is smoother, and your team can scale without adding DevOps overhead. For most pentest teams, that tradeoff isn’t even a tradeoff — it’s a clear win.</p><h3>When Containers Still Make Sense</h3><p>There are still cases where self-hosting is unavoidable. Government agencies, highly regulated industries, or air-gapped environments often require local deployments, no matter how efficient the cloud may be. In those cases, containerization provides a workable alternative.</p><p>But those situations are the exception. As cloud infrastructure matures and compliance standards are baked into SaaS platforms, more teams are realizing they don’t gain much by managing environments themselves.</p><h3>Ask the Better Question</h3><p>So when someone asks me, “Can we just run it in containers?”, I usually push back with:<br>“Do you really need to?”</p><p>If your priority is faster pentest delivery, better client collaboration, and less time wasted on reporting, then the cloud already gives you what you’re trying to build in containers — without the overhead.</p><p>Because security isn’t about architecture diagrams. It’s about impact. And the more you automate, standardize, and simplify the operational side of pentesting, the more time you have for the work that matters: keeping clients secure.</p><p>— <br><em>Luis, Founder @ Cyver</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffeeb23991b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make CTEM Work: How We Built a Pentest Reporting Platform to Keep Up With Real-World Risk]]></title>
            <link>https://medium.com/@cyver/make-ctem-work-how-we-built-a-pentest-reporting-platform-to-keep-up-with-real-world-risk-794dce805dcf?source=rss-724b38146c40------2</link>
            <guid isPermaLink="false">https://medium.com/p/794dce805dcf</guid>
            <category><![CDATA[pentester]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <dc:creator><![CDATA[Luis Abreu from Cyver]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 13:48:23 GMT</pubDate>
            <atom:updated>2025-06-10T13:48:23.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*goqIB-aDFh09m24RybZuEg.png" /></figure><p>Staying ahead of security threats used to mean scanning once a quarter and crossing your fingers. Not anymore. The pace of today’s environments demands something better — constant visibility, faster feedback loops, and a smarter way to prioritize risk. It’s no longer enough to treat these as separate tasks — they have to work as part of a single, continuous process.</p><p>That’s exactly why Continuous Threat Exposure Management (CTEM) exists. But while the concept makes sense, putting it into practice is where most teams struggle. It’s not just about spotting issues — it’s about building a system that connects discovery, validation, and remediation into a workflow that’s fast, flexible, and always on.</p><p>That’s what drove us to create Cyver Core.</p><h3>Why We Built Cyver Core for CTEM</h3><p>We designed Cyver Core to close the gap between theory and reality in exposure management. Instead of bouncing between spreadsheets, emails, and reports, we wanted everything to live in one platform. A place where vulnerabilities are tracked, validated, and resolved as part of day-to-day operations — not as an afterthought.</p><p>The goal: Make CTEM not just possible, but practical.</p><h3>Start With Structure, Not Just Scans</h3><p>Real CTEM doesn’t start with a list of findings — it starts with context. That’s why, in Cyver Core, every engagement begins with a defined scope. Assets, environments, and business objectives are linked from the beginning. This lets you trace every vulnerability back to something that actually matters.</p><p>It also means you’re not scrambling later to figure out where something fits. The structure is already there, reducing noise and helping teams stay focused on what counts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eW3lAK1wAbApfr4kawDQQQ.png" /></figure><h3>From Static Reports to Live Discovery</h3><p>Traditional vulnerability management treats findings like paperwork: you collect them, write them down, and hope someone reads the report.</p><p>We flipped that. In Cyver Core, findings are live from the start. As vulnerabilities are discovered, they’re linked to specific assets, automatically scored, validated, and updated. No waiting for someone to “finish the report” — you’re always working with real-time exposure data.</p><p>Validation outcomes, retest results, and remediation status all stay in sync — so your team can move quickly and confidently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0nXyeJsqIvq0IUe_LXw_A.png" /></figure><h3>Real Risk, Not Just High Scores</h3><p>CTEM isn’t about fixing everything. It’s about fixing the right things.</p><p>With Cyver Core, prioritization is built in. You can sort and filter findings not just by CVSS score, but by asset importance and business impact. This helps security teams avoid wasting time on low-priority noise and focus on what genuinely reduces risk.</p><p>Prioritization isn’t something you bolt on at the end — it’s woven into how vulnerabilities are tracked from the moment they’re discovered.</p><h3>Validation Without the Guesswork</h3><p>We’ve all seen it: a vulnerability gets marked as fixed, but no one’s really sure if it was. That’s where many workflows break.</p><p>In Cyver Core, validation is part of the process. Fixes are retested, and everything — from evidence to proof-of-concept — is logged directly in the platform. You don’t need extra documents or scattered notes. Just clear, trackable steps from detection to resolution.</p><p>When something’s closed, there’s no ambiguity — just confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gB19hlz89BoilZyYDFoyGA.png" /></figure><h3>Reports That Don’t Go Out of Date</h3><p>Too often, security reports are outdated the moment they’re shared. That’s a problem when decisions need to be made fast.</p><p>We solved that by generating reports directly from live exposure data. As validation happens and statuses change, the reports update automatically. No double entry. No rework. Just accurate, professional reports that reflect what’s happening right now.</p><p>It saves time — and helps everyone from security teams to execs stay aligned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sH7O2sGO_xERuHn5m0k1FQ.png" /></figure><h3>Built for Collaboration, Not Silos</h3><p>Exposure management is never just one person’s job. It involves pentesters, security leads, IT, and business stakeholders. So we built Cyver Core for collaboration from day one.</p><p>You get role-based access, in-platform comments, task assignments, and real-time status updates. Everyone sees what’s happening, who’s responsible, and what still needs work — without relying on endless email threads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ywig32n01zVoXda1BKUfeg.png" /></figure><h3>What Makes CTEM Actually Work</h3><p>At its core, CTEM is about integration. Discovery, validation, prioritization, and reporting can’t live in silos — they have to work together.</p><p>That’s what Cyver Core delivers. It keeps your exposure management connected, dynamic, and rooted in real business impact. No more disconnected tools or reactive reporting. Just one platform built to keep your team ahead of risk.</p><p>If you’re ready to bring CTEM into your daily operations, let’s talk.<br>We built Cyver Core to help security teams work smarter — not just harder.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=794dce805dcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>