<?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 Pentest Team @greenhats.com on Medium]]></title>
        <description><![CDATA[Stories by Pentest Team @greenhats.com on Medium]]></description>
        <link>https://medium.com/@greenhats?source=rss-df0a35f76334------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*a2MwOC8S2pHKLbv-lmlH-g.png</url>
            <title>Stories by Pentest Team @greenhats.com on Medium</title>
            <link>https://medium.com/@greenhats?source=rss-df0a35f76334------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:25:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@greenhats/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[OSAI / AI-300 Review by FLX]]></title>
            <link>https://greenhats.medium.com/osai-ai-300-review-by-flx-949efc74f2c9?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/949efc74f2c9</guid>
            <category><![CDATA[offsec]]></category>
            <category><![CDATA[osai]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 09:45:46 GMT</pubDate>
            <atom:updated>2026-10-01T09:45:46.944Z</atom:updated>
            <content:encoded><![CDATA[<p>A short story of prompts, costs and whatever I think about. Handwritten and grammar corrected by DeepL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*wLoh7wbdLvtAM_eEM4cVIw.png" /></figure><h3>The AI-300 Course</h3><p>The material is technically precise and well structured. I learned a few new tricks, for example, how to target RAG pipelines and reversing out information of these systems. That was nice! I had a goal. I wanted to complete the course by hand, set aside dedicated time for it, and do every exercise. Yeah, it’s not going very well. The 90 days course bundle was a bit optimistic for my schedule. The day to day job is very time consuming, and handling family, friends, hobbies, job, and the job after the job in conjunction with studying complete new things is not an easy task. So I bought a lab extension and always scheduled my learning blocks into the calendar — or better say, my wife scheduled them for me.</p><p>Overall, for the full course, I studied 32 hours spread across 7 days on the material and the labs. Have not done any challenge labs, only the one in the last chapter. It was so cool to see the shift. Until 50% of the course, I have done everything by hand, researched all the things manually, and tried to answer the questions by typing. After reaching the middle of the course, I noticed that the topics got extremely challenging because there are so much new info, so I decided to build up my agents to answer the lab questions. I converted the materials to an MCP server that my agents can search by category, buzzword, or chapter. This setup helped me with the course and the tasks, and, of course, the exam. Totally learned a lot from reading the answers of my agents. Sometimes the grading system was laggy, and the labs are not 100% stable. However, when you think about how to build such a system, you’ll realize that it comes with some challenges and side effects.</p><h3>The exam</h3><p>After scheduling the exam, I felt a bit nervous because I put not that much time I wanted into this project. But hey, failing exams or tasks is not a problem for me, it’s simply part of the journey, and you learn a lot more from failing than from success. I prepared a new skill set and MCP only for the exam with knowledge and a deep research about every blog post from OSAI exam reviews. Reading the reviews was a bit odd for me. So many different opinions how to tackle the exam, but there was a common thing in nearly every review. They mostly used flagship models. So I set a challenge for me. First, do not use a flagship model or provider. No OpenAI, Antropic, no Google or Grok. And route everything through Openrouter to exactly measure the costs and tokens. And of course, 100% coverage of the exam assignments. So, that is the result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZKqUQnnPkRXw2Yvs0AdFQ.png" /><figcaption>$8.46 in total, including help with writing the report using only Deepseek v4.1 Flash</figcaption></figure><p>No other model or provider. Also, the report is nearly handcrafted. Of course, AI assisted writing, but I prepared a skillset for my agents to save every evidence and output, document all the things, and completely build the report autonomously. That failed very hard! The report may contain all information and flags, but the task given by Offsec is clear. The report should be written in a way that an experienced human pentester can follow every step that I have taken to complete the challenge. And surprise, most of the LLMS completely fail with this task. The information may be complete, but ordering and structuring them logically within a 60 page document is something that I could not automate at the time of writing.</p><p>So I decided to do it on my own and pick the pieces and blocks and paste in the document with the right order and the design standards I would like to have in a professional report. Also, find a missing piece while doing that task by hand. Luckily, I was able to locate the correct output in my terminal history. I really encourage everyone to “write/pasting” the report by hand, follow every step in the terminal and take fresh screenshots. Because that is the part you will learn the most out of this course.</p><p>One final hint from me: As the exam guide says, there are two entry points to the exam environment. Choose one and follow that path. If it does not work, choose the other, but do not start with both at the same time. If you try to follow what the agents do and manually intercept, you will have too much on your plate. Two paths to follow will probably overwhelm you and double the amount of information the agents have to follow.</p><p>For anyone who is interested, how many tokens I spend and how the prices are calculated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*QLXP9D1XCd3OKP_CWdIWmQ.png" /><figcaption>Input $0.13/M tokens, Output $0.52/M tokens, Cache read $0.0026/M tokens</figcaption></figure><h3>FAQ for OSAI/AI-300/Pentesting</h3><p><strong>What flagship LLM / Provider / Model do I need for OSAI?<br></strong>GLM/Deepseek: Flash models will do the job with the right prompting, and without noticeable rail guards. At least, if you encounter someone, it’s an easy task to walk around.</p><p><strong>What about my local model?<br></strong>Depending on your hardware, the context window may not be large enough to display local models effectively. There is a lot of connected information, and, at the time of writing, a system with 12 GB of graphics memory will not be able to solve all machines, or even half of them, in an appropriate amount of time. Even with my current setup, the Minisforum S1 Max with 128 GB of unified memory, an AMD AI Max+ 395, and an uncensored QWEN 3.8 70b coder, you will hit a hard wall when it comes to the context window for such a large attack surface.</p><p><strong>What about AI Governance and Privacy?<br></strong>This topic is critical and gets almost completely ignored in the current hype. Dropping sensitive network structures, hashes, or custom code snippets into the web UI of a flagship model means you are directly feeding their training data. If you do that with real client data, you simply failed your job. For the lab environment, I solved this by routing everything through OpenRouter and strictly selecting providers that contractually guarantee Zero Data Retention. But let me be very clear. That is absolutely not an option for real engagements. The future of AI in pentesting is definitely local. Clients are currently asking tough questions about where their data is processed, and they are completely right to do so. It is simply not enough to host a model yourself in the cloud or at some provider. Even a dedicated infrastructure in your own datacenter is often off the table. We regularly sit on-site with clients, test air-gapped environments, or simply have zero internet access during the initial audit phase. The solution is as simple as it was before the AI era. The data never leaves the pentester’s system. How exactly we implement this with the necessary performance during real engagements is a story for another time.</p><p><strong>Someone solved the exam in 4h with GPT Sol/Terra/Whatever. Is it that easy and should I also use that?<br></strong>Nope! The most effective way to learn from the course is to use a fast and effective Reasoning LLM as your co-pilot in the exam environment. Stop at every major finding, and track the entire exploitation chain by hand. You will learn so much and take in new information from what you see, or even notice, some system you encountered in an earlier engagement. The course teaches you to use LLMs as a tool; letting the model do everything automatically doesn’t prove anything, and in real engagements, that isn’t an option either. When testing critical infrastructure, such as hospitals or the electricity industry, your autonomous agent will break things and forget about it. It’s your responsibility.</p><p><strong>After OSAI: How will pentesting looks like in 3 years? Do we even need manual testing?<br></strong>No one can even make any predictions how the next 6 months will go, so everyone claiming what will be in &gt; 1 year is talking BS. My personal opinion is definitely we need manual pentesting, but nearly everything is shifting. Scope, tooling, reporting. If we really want to answer this question, we have to step one step out. Of course, things change and keep changing, and we can talk about responsibility and having a copilot or let the LLM do all of the work, but let me be very specific. The real question is, what problem should a pentest solve, or what question should a pentest answer. If we can use LLMs to produce the same output from a one week engagement in one day: Good, do it and use the rest of the week for the customer to actually fix / harden the infrastructure. Lock the client’s sharpest admins in a room for a few days, order pizza, and tear through the report together. Don’t just send them a PDF — or, in our case, PDF+Markdown. Explain the mechanics, debate the fixes, and actually harden the network side-by-side. Writing a report isn’t the endgame; fixing the whole infrastructure is. Maybe they haven’t done some fancy hybrid AD configurations yet that your agent wrote in the report, and need some support of an experienced pentester who knows what can go wrong. Maybe they do not have the time in the daily work, so a meeting in person over days where they can fully focus on security is the only chance that you don`t get the same findings one year later. But please: Do not think that hyperboosting your skills with LLMs and creating a 300+ page report after 4 days of engagement will help the customer. It simply does not.</p><p>Cheers. FLX</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=949efc74f2c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 30-Hour Mistake: What the OSEE Taught Me About the Limits of AI and the Art of Persistence]]></title>
            <link>https://greenhats.medium.com/the-30-hour-mistake-what-the-osee-taught-me-about-the-limits-of-ai-and-the-art-of-persistence-3e46d1d1dee5?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e46d1d1dee5</guid>
            <category><![CDATA[osee]]></category>
            <category><![CDATA[exploit-development]]></category>
            <category><![CDATA[offsec]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 10:41:35 GMT</pubDate>
            <atom:updated>2026-01-13T20:01:30.796Z</atom:updated>
            <content:encoded><![CDATA[<p>A review of the <strong>Offensive Security Exploitation Expert</strong> exam, the trap of automation, and why manual mastery still reigns supreme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*QzP13plkFOVGS6exIjDRaQ.png" /></figure><blockquote>About me: Paul Werther | FLX, CTO greenhats, <a href="https://github.com/FLX-0x00">https://github.com/FLX-0x00</a></blockquote><p>Passing the OSEE (Offensive Security Exploitation Expert) has always been a major career milestone for me. It is widely regarded as one of the toughest exams in the cybersecurity world, and rightfully so. Now that I have received confirmation that I have passed, I would like to share my reflections. Not just about the technicalities, but about a hard-learned lesson on the current limitations of generative AI in high-end exploit development.</p><p>It started in May 2025 with a live course in the Netherlands. The course’s reputation alone was enough to make it feel intimidating. Is it justified? Yes and no. The sheer volume is overwhelming: over 700 pages of complex material skimmed in a week, coupled with sleepless nights. You are not just reviewing topics; you are fighting … especially for the Challenge Coin.</p><p>And … I wanted that coin. It’s not just for the collection, but also out of respect for the investment, the time away from my family / work and the sheer effort put into the course by the creators, <em>sickness</em> and <em>mschenk</em>. I know from my own experience building training environments how incredibly difficult it is to create robust, crash-proof labs that still teach complex concepts. The didactic quality and the “Try Harder” ethos they maintained deserve nothing less than 100% effort.</p><p><strong>The AI Trap: </strong>I needed two attempts to pass the exam. Why? Because I fell into a modern trap during my first attempt.</p><p>I wasted approximately 30 hours trying to automate the exploitation process or building solutions using generative AI. It was a calculated risk that failed spectacularly. I realized too late that while AI is excellent for repetitive coding or optimizing syntax, it hits a hard wall when precision is non-negotiable.</p><p>Exploit development at this level isn’t about probability; it’s about the precision of every single assembly instruction. The exam environment is custom, novel, and unforgiving. Generative models predict based on existing data; they cannot “solve” a puzzle they haven’t seen before. When I hit a dead end, despite the AI having all the same context I did, panic set in. I was left staring at a screen, realizing I had outsourced my thinking to a tool that couldn’t comprehend the problem.</p><p>That was the hardest lesson: You cannot automate understanding.</p><p><strong>Attempt Two: </strong>For the second attempt, I changed my strategy entirely. I adopted a “manual first” policy. For the first 10 hours, I wrote zero exploit code. I researched and developed a foundation of code that effectively communicates with the exam objectives. I mapped out the environment manually, relying on my own logic rather than a prompt.</p><p>I utilized tools like NotebookLM during preparation to create focused “learning snacks” and printed cheat sheets for mitigations, but in the exam, it was just me and the debugger. This approach prevented the rabbit holes I fell into previously.</p><p>The result? I solved 100% of the challenges. The satisfaction didn’t come from just getting a shell; it came from the “weaponization.” Taking a raw crash, bypassing custom constraints, and turning it into a stable exploit is a feeling of pure craft. It requires a level of creativity that, currently, no AI can replicate.</p><p><strong>The Reality of the OSEE</strong> People often ask me why I put myself through this. As a pentester, I rarely need to write custom kernel driver exploits or bypass advanced memory protections in my daily work. It is a massive time investment that rarely pays off in a standard engagement.</p><p>But that misses the point. It is about “Sportsgeist” (sportsmanship) and the necessity of deep understanding. In an age where fewer people understand how things work under the hood, possessing this low-level knowledge changes how you view high-level infrastructure. You stop seeing magic and start seeing logic.</p><p><strong>Advice for Future Candidates</strong> If you are aiming for the OSEE, here is my advice:</p><ol><li><strong>Don’t let the fear paralyze you.</strong> The topics are heavy, but it is not magic. It is assembly. Once you understand the principles, the “monster” becomes manageable. Like the course, the exam is all about exploiting and weaponizing vulnerabilities using pre-existing research.</li><li><strong>Master WinDbg.</strong> Routine is everything. You need to be fast with your debugger so you can spend your mental energy on the logic, not the tools.</li><li><strong>Map the Mitigations.</strong> Create a clear overview of every mitigation: when it applies, how to detect it, and conceptually how to bypass it. This saved me from missing the obvious.</li><li><strong>Respect the Report.</strong> My final report was 100 pages long. I treated it as a sign of respect to the graders. If they put the work into the exam, I will put the work into the documentation. Finally, good documentation helps you stay on top of your work, even after naps or exhaustive debugging sessions.</li><li><strong>As with every exam:</strong> Prepare your meals, take breaks, get enough sleep, and read the assignment and materials at least ten times.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FDYXT3FjeOuLY0km0nGk2Q.png" /></figure><p>The OSEE was painful, exhausting, and absolutely worth it. I’d like to express my gratitude to Offsec, and I’d especially like to thank mschenk and sickness for the incredible experience I had.</p><p>Cheers, FLX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e46d1d1dee5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Delete Fails: Weaponizing ISOs to Defeat EDR Remediation]]></title>
            <link>https://greenhats.medium.com/when-delete-fails-weaponizing-isos-to-defeat-edr-remediation-341a545d84b0?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/341a545d84b0</guid>
            <category><![CDATA[edr]]></category>
            <category><![CDATA[xdr]]></category>
            <category><![CDATA[exploitation]]></category>
            <category><![CDATA[byovd]]></category>
            <category><![CDATA[kernel-driver]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 13:22:16 GMT</pubDate>
            <atom:updated>2025-12-05T13:53:09.868Z</atom:updated>
            <content:encoded><![CDATA[<p>In the realm of advanced Windows exploitation and kernel interactions, the ‘Bring Your Own Vulnerable Driver’ (BYOVD) technique remains a staple in a Red Teamer’s arsenal. The premise is straightforward: leverage a legitimate, signed kernel driver with known vulnerabilities to execute privileged operations, such as terminating protected Endpoint Detection and Response (EDR) processes, from Ring 0.</p><p>However, the security landscape is adaptive. Modern EDR and XDR solutions, including Cynet and Trend Micro Vision One, have evolved beyond simple blocking. They often employ aggressive sanitization routines: upon detecting a known malicious driver hash (like the well known zam64.sys from Zemana AntiMalware), the EDR not only terminates the loading process but immediately quarantines or deletes the .sys file from the disk.</p><p>This destructive response creates a logistical challenge for the attacker. If the weaponization tool fails on the first attempt, the payload is gone, requiring a fresh drop which invariably triggers another alert. Yet, analysis of this behavior reveals a fundamental flaw: A reliance on file system write access to mitigate the threat. By introducing a read-only ISO container, this sanitization mechanism can be turned into a futile loop, allowing an attacker to exploit a race condition and successfully disable the EDR (with alerts but disabled).</p><h3>The Sanitization Loop and Race Conditions</h3><p>When a program attempts to register and load a vulnerable driver, EDR solutions utilizing file system mini-filters intercept the operation. Solutions like Trend Micro Vision One and Cynet typically follow a distinct pattern:</p><ol><li><strong>Detection:</strong> The driver write or load attempt matches a known bad signature.</li><li><strong>Intervention:</strong> The loading process is halted.</li><li><strong>Remediation:</strong> The driver file is deleted to prevent future attempts.</li></ol><p>Between the drop of the driver and its deletion, a race condition exists. It is a narrow window, often milliseconds. In a standard file system environment (NTFS), the EDR usually wins, or if it doesn’t, it successfully removes the file, preventing a second attempt. The attacker runs out of ammunition before they can force the door open.</p><h3>The ISO Anomaly: Immutable Ammunition</h3><p>The “Head First Through the Wall” strategy changes the environment to nullify the remediation step. Windows natively supports mounting ISO images, treating them as virtual optical drives. Crucially, these mounted volumes are read-only.</p><p>By packaging the compiled attack toolkit, specifically the loader (main.exe) and the vulnerable driver (Terminator.sys) into an ISO, we can observe a different behavior:</p><ol><li>The ISO is mounted (e.g., as Drive E:).</li><li>The loader (main.exe) is executed directly from the read-only volume.</li><li>It attempts to create the service and load the driver.</li><li>The EDR detects the threat and attempts to delete E:\Terminator.sys.</li><li>The operating system returns STATUS_MEDIA_WRITE_PROTECTED.</li><li>The EDR’s remediation routine fails, but the file remains intact.</li></ol><h3>Exploiting the Loop</h3><p>With the “ammunition” now indestructible, the limitation of a single attempt is removed. The EDR is forced into a loop of detection and failed remediation. This persistence allows the attacker to aggressively spam the load request.</p><p>Tests conducted against active Cynet and Trend Micro Vision One installations demonstrate that while the EDR is efficient, it is not infallible under high-frequency stress. By repeatedly executing main.exe in rapid succession, the race condition is eventually won. The EDR&#39;s processing overhead, analyzing the file, making the decision, attempting the deletion, and handling the error, creates brief gaps in coverage.</p><p>It typically takes between 5 to 8 rapid execution attempts. Eventually, the driver slips through the filter checks during a momentary lapse in the EDR’s enforcement cycle and successfully loads into the kernel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgSqbXHksO5KjvAEec_bbQ.png" /><figcaption>Successful disable Trend Micro EDR / XDR</figcaption></figure><h3>Impact and Persistence</h3><p>Once Terminator.sys is loaded, the game effectively ends for the EDR. The driver, originally part of Zemana AntiMalware, allows trusted processes to issue IOCTLs that can terminate any process ID (PID), regardless of its protection level (PPL).</p><p>As illustrated in the screenshot above, the tool successfully registers itself as trusted and systematically terminates the core processes of the EDR. While the UI agent might appear responsive or “ghosted,” the underlying sensors and enforcement drivers are severed.</p><p>The loader tool used (main.exe) is designed for operational efficiency. It checks for existing services before attempting a new load. If the driver is successfully loaded once, subsequent executions simply reuse the existing kernel service to terminate additional PIDs without re-triggering the initial race condition.</p><p>Full source code: <a href="https://github.com/FLX-0x00/BYOVD-Zemana">https://github.com/FLX-0x00/BYOVD-Zemana</a> (forked and modified)</p><h3>Conclusion</h3><p>The effectiveness of this technique highlights a critical distinction between “detecting a threat” and “neutralizing a threat.” Relying on file deletion as a primary mitigation strategy is insufficient when the environment (Read-Only File Systems) prevents modification.</p><p>For Blue Teams and security architects, this underscores the necessity of defense-in-depth strategies. Blocking known vulnerable drivers must occur at the API or integrity level, such as utilizing Microsoft’s Vulnerable Driver Blocklist or enforcing strict Windows Defender Application Control (WDAC) policies, rather than relying solely on reactive file scanning and deletion.</p><p>Cheers, FLX</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=341a545d84b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implement soft-delete in Rails with Avo + Discard]]></title>
            <link>https://greenhats.medium.com/implement-soft-delete-in-rails-with-avo-discard-bc33d1e84e79?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc33d1e84e79</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[avo]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Fri, 16 May 2025 20:15:28 GMT</pubDate>
            <atom:updated>2025-07-14T08:22:34.860Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>A step-by-step guide (with copy-pastable code) to add a </em>recycle-bin<em> to any Rails app using Avo’s admin panel and the Discard gem.</em></blockquote><h3>Why soft-delete?</h3><ul><li><strong>Safety first</strong> — deleting the wrong record in production is costly; with soft-delete you can undo mistakes.</li><li><strong>Auditability</strong> — a “deleted” record is still queryable for investigations, analytics, refunds, GDPR export, etc.</li><li><strong>User experience</strong> — customer-facing features (for example, “reactivate account”) are trivial once the data still exists.</li><li><strong>Ops peace-of-mind</strong> — bulk deletes now become two steps: <em>discard</em> (immediately invisible) and <strong>later</strong> hard-delete by cron/job.</li><li><strong>Admin productivity</strong> — surfacing discarded records in the back-office lets support teams restore data without touching the console.</li></ul><p>Soft-delete is therefore a <em>must</em> for most serious web apps. Below is a complete recipe to add it in minutes with a nice interface. Of course, this is only a proof of concept. However, you can easily extend its functionality. For example, you could use the audited gem to display the user who deleted the record.</p><h3>Prerequisites</h3><h3>1 — Avo</h3><p><a href="https://avohq.io/">Avo</a> is a Rails admin-panel / CMS that turns plain models into polished CRUD UIs in minutes. It is highly customizable, integrates with Pundit/CanCanCan, works with Hotwire, and <strong>ships a resource DSL</strong> that we’ll leverage for our recycle-bin. Installing this gem is beyond the scope of this blog post. Please refer to the documentation.</p><h3>2 — Discard</h3><p><a href="https://github.com/jhawthorn/discard">Discard</a> adds minimal, default-scoped soft-delete to ActiveRecord. It uses a single discarded_at column plus helper scopes (kept, discarded) and callbacks.</p><pre>gem &quot;discard&quot;, &quot;~&gt; 1.4&quot;</pre><pre>bundle install</pre><h3>1. Make a model discardable</h3><p>We’ll use <strong>Account</strong> as the example, but the pattern works for <em>every</em> model.</p><pre># app/models/account.rb<br>class Account &lt; ApplicationRecord<br>  include Discard::Model<br>  # Hide discarded records from normal queries<br>  default_scope -&gt; { kept }<br>  # Custom business rule: never allow admins to be discarded<br>  def discardable?<br>    return false if discarded? || has_role?(:admin)<br>    true<br>  end<br>  # ...<br>end</pre><p><strong>What happens?</strong></p><ul><li>include Discard::Model injects discard, undiscard, discarded?, scopes, and callbacks.</li><li>default_scope -&gt; { kept } silently excludes discarded rows from <em>all</em> default ActiveRecord and Avo queries.</li><li>discardable? is our custom guard-rail, used later by the discard action to prevent deleting protected records. This is optional and uses the rolify gem.</li></ul><h3>Add the column</h3><pre>bin/rails g migration add_discarded_at_to_accounts discarded_at:datetime:index<br>bin/rails db:migrate</pre><h3>2. Avo recycle-bin — the universal DiscardedRecord resource</h3><p>Because discarded rows can live in multiple tables, we’ll build a <strong>virtual</strong> resource backed by an <strong>array</strong>, not an ActiveRecord model.</p><pre>bin/rails generate avo:resource DiscardedRecord --array</pre><p>Replace the generated file with:</p><pre># app/avo/resources/discarded_record.rb<br>class Avo::Resources::DiscardedRecord &lt; Avo::Resources::ArrayResource<br>  self.description = &quot;Shows all soft-deleted items across the application&quot;<br>  self.title       = :id<br><br>  self.index_controls = -&gt; {<br>    action Avo::Actions::Undiscard,<br>           style:  :primary,<br>           color:  :primary,<br>           icon:   &quot;heroicons/solid/arrow-uturn-left&quot;<br>  }<br>  # Row-level controls<br>  self.row_controls = -&gt; do<br>    show_button<br>    action Avo::Actions::Undiscard,<br>           title: &quot;Undiscard&quot;,<br>           icon:  &quot;heroicons/solid/arrow-uturn-left&quot;,<br>           style: :icon<br>  end<br>  # ----------------------------------<br>  #   DATA SOURCE<br>  # ----------------------------------<br>  def records<br>    Rails.application.eager_load! # ensure all models are loaded<br>    discarded_records = []<br>    ActiveRecord::Base.descendants.each do |model|<br>      next if model.abstract_class?<br>      next unless model.included_modules.include?(Discard::Model)<br>      model.unscoped do  # ignore each model&#39;s default_scope<br>        model.discarded.find_each.with_index do |record, id|<br>          discarded_records &lt;&lt; {<br>            id:            id,<br>            model_type:    model.name,<br>            record:        record,<br>            discarded_at:  record.discarded_at<br>          }<br>        end<br>      end<br>    end<br>    # newest first<br>    discarded_records.sort_by { |r| r[:discarded_at] }.reverse<br>  end<br>  # ----------------------------------<br>  #   UI FIELDS<br>  # ----------------------------------<br>  def fields<br>    field :preview,      as: :preview<br>    field :model_type,   as: :text<br>    field :record,       as: :record_link<br>    field :object,       as: :text, hide_on: :index, show_on: :preview do<br>      &quot;&lt;pre style=&#39;white-space:pre-wrap&#39;&gt;&quot; \<br>      &quot;#{CGI.escapeHTML(JSON.pretty_generate(JSON.parse(record.record.to_json)))}&quot; \<br>      &quot;&lt;/pre&gt;&quot;.html_safe<br>    end<br>    field :discarded_at, as: :text<br>  end<br>  # ----------------------------------<br>  #   ACTIONS<br>  # ----------------------------------<br>  def actions<br>    action Avo::Actions::Undiscard, icon: &quot;heroicons/solid/arrow-uturn-left&quot;<br>  end<br>end</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SsJPJiHF-ELqLgds69mJkQ.png" /></figure><p><strong>Highlights</strong></p><ul><li><strong>Dynamic model list</strong> — the resource loops over every loaded model that include Discard::Model.</li><li><strong>unscoped { … discarded }</strong> – bypasses each model’s default_scope to fetch <strong>all</strong> discarded rows.</li><li><strong>JSON preview</strong>— Pretty render the full record to json and display them in the preview</li></ul><h3>3. Pundit policy</h3><p>Keep it simple for now — only admins (rolify) can see the recycle-bin:</p><pre># app/policies/avo/discarded_record_policy.rb<br>class Avo::DiscardedRecordPolicy &lt; ApplicationPolicy<br>  class Scope &lt; ApplicationPolicy::Scope<br>    def resolve; end # empty because no needed for array resources<br>  end<br><br>  def index?<br>    user.has_any_role? :admin<br>  end<br><br>  def show?<br>    index?<br>  end<br><br>  def preview?<br>    index?<br>  end<br><br>  def act_on?<br>    user.has_any_role? :admin<br>  end<br>end</pre><h3>4. Actions — soft-delete &amp; undo</h3><h3>4.1 Discard action (mass-delete on any resource)</h3><pre># app/avo/actions/discard.rb<br>class Avo::Actions::Discard &lt; Avo::BaseAction<br>  self.name = &#39;Soft Delete&#39;<br>  self.message = &#39;This will mark the selected records as deleted. The records will not be visible in the application anymore but can be restored for 30 days. After 30 days, the account and all associated data will be automatically deleted.&#39;<br>  self.visible = -&gt; do<br>    view.index? || view.show?<br>  end<br>  self.authorize = -&gt; do<br>    current_user.has_any_role? :admin<br>  end<br><br>  def handle(query:, fields:, current_user:, resource:, **args)<br>    succeed_count = 0<br>    error_count = 0<br>    query.each do |record|<br>      if record.respond_to?(:discardable?)<br>        if record.discardable?<br>          record.discard<br>          succeed_count += 1<br>        else<br>          error_count += 1<br>        end<br>      elsif record.undiscarded?<br>        record.discard<br>        succeed_count += 1<br>      else<br>        error_count += 1<br>      end<br>    end<br><br>    error &quot;Could not discard #{error_count} #{&#39;record&#39;.pluralize(error_count)}. Please check the logs for more information.&quot; if error_count.positive?<br>    succeed &quot;Successfully discarded #{succeed_count} #{&#39;record&#39;.pluralize(succeed_count)}.&quot; if succeed_count.positive?<br>  end<br>end</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*mduhZxhanl7rVkpxI3fG0g.png" /></figure><h3>4.2 Undiscard action (restore from recycle-bin)</h3><pre># app/avo/actions/undiscard.rb<br>class Avo::Actions::Undiscard &lt; Avo::BaseAction<br>  self.name = &#39;Restore&#39;<br>  self.message = &#39;Are you sure you want to restore the selected records?&#39;<br>  self.visible = -&gt; do<br>    view.index? || view.show?<br>  end<br>  self.authorize = -&gt; do<br>    current_user.has_any_role? :admin<br>  end<br><br>  def handle(query:, fields:, current_user:, resource:, **args)<br>    succeed_count = 0<br>    error_count = 0<br>    query.map(&amp;:record).each do |record|<br>      if record.discarded?<br>        record.undiscard<br>        succeed_count += 1<br>      else<br>        error_count += 1<br>      end<br>    end<br>    error &quot;Could not undiscard #{error_count} #{&#39;record&#39;.pluralize(error_count)}. Please check the logs for more information.&quot; if error_count.positive?<br>    succeed &quot;Successfully undiscarded #{succeed_count} #{&#39;record&#39;.pluralize(succeed_count)}.&quot; if succeed_count.positive?<br>  end<br>end</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*5fEG5n1fxFcAvnTL-mBj2w.png" /></figure><blockquote><strong><em>Note</em></strong><em>: we map </em><em>query to </em><em>record because the recycle-bin rows wrap the </em>real<em> object in the </em><em>:record key.</em></blockquote><h3>5. Menu entry</h3><pre># config/initializers/avo.rb<br># ...<br>resource :discarded_records, visible: -&gt; { current_user.has_any_role? :admin }, label: &#39;Recycle bin&#39;<br># ...</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*uHIxFWzxW_89K37JMPoYoA.png" /></figure><p>Now any admin can browse <strong>/avo/discarded_records</strong>, check discarded items, preview the JSON payload, and restore them with one click.</p><h3>6. The account resource</h3><p>Use row controls and the actions to add the discard button directly to the account resource.</p><pre># app/avo/resources/account.rb<br>class Avo::Resources::Account &lt; Avo::BaseResource<br># ...<br>  self.row_controls = -&gt; do<br>    show_button<br>    edit_button<br>    delete_button<br>    action Avo::Actions::Discard, title: &#39;Discard&#39;, icon: &#39;heroicons/outline/user-minus&#39;, style: :icon if current_user.has_any_role?(:admin) &amp;&amp; record.undiscarded?<br>  end<br><br>  def actions<br>    action Avo::Actions::Discard<br>  end<br># ...</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*gUVj1vWTtrmWNGFXtlUiOQ.png" /></figure><p>Now any admin can browse <strong>/avo/discarded_records</strong>, check discarded items, preview the object as JSON , and restore them with one click.</p><h3>7. House-keeping — permanent deletion</h3><p>Soft-delete is half the story; remember to <em>really</em> delete after the legal/business grace period:</p><pre># lib/tasks/hard_delete.rake<br>namespace :maintenance do<br>  desc &quot;Permanently remove records discarded more than 30 days ago&quot;<br>  task hard_delete: :environment do<br>    days = (ENV[&quot;DAYS&quot;] || 30).to_i<br>    cutoff = days.days.ago<br>    ActiveRecord::Base.descendants.each do |model|<br>      next unless model.included_modules.include?(Discard::Model)<br>      model.discarded.where(model.arel_table[:discarded_at].lt(cutoff)).find_each(&amp;:destroy)<br>    end<br>  end<br>end</pre><p>Run from cron or Sidekiq-Cron:</p><pre>bin/rails maintenance:hard_delete            # default 30 days<br>bin/rails maintenance:hard_delete DAYS=7     # override</pre><h3>Conclusion</h3><p>With a few lines of code you now have:</p><ul><li>Per-resource <em>Soft Delete</em> baked directly in the Avo interface.</li><li>A <strong>Recycle bin</strong> that aggregates discarded rows from <em>all</em> models.</li><li>One-click restore</li><li>Automatic data retention by combining Discard with a nightly task.</li></ul><p>Happy shipping — and enjoy the peace-of-mind that comes with reversible deletes!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc33d1e84e79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EN: Interview — 11 years of OSCP — A personal review]]></title>
            <link>https://greenhats.medium.com/en-interview-11-years-of-oscp-a-personal-review-c2a881d15744?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a881d15744</guid>
            <category><![CDATA[oscp-preparation]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[offsec]]></category>
            <category><![CDATA[oscp]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Wed, 25 Dec 2024 15:59:23 GMT</pubDate>
            <atom:updated>2026-01-19T14:23:59.530Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*AnJkF3ZHthyVdWxT_i3Rxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*gQ1eIreePBdYKMp-hRi0aA.png" /></figure><p><em>Hardly any other industry is developing as dynamically as IT security. The constant development of technologies not only brings new opportunities, but also new challenges — and requires specialists to always be one step ahead. Cybersecurity certifications such as the OSCP play a central role in this. Pierre Herget, Managing Director of INS Systems GmbH, talks to Paul Werther, CTO of greenhats GmbH, about his personal career in the field of cybersecurity specialist certification.</em></p><p>Pierre: Hey Paul, welcome to our interview 11 years of OSCP! Let’s jump straight in. First of all — for anyone who has never heard the term OSCP before: What’s behind it?</p><p>Paul: Hey Pierre — So the Offensive Security Certified Professional, or OSCP for short, is one of the best-known pentesting certifications around. It requires complete, practical hacking skills — not a multiple-choice test, but a real attack simulation in a fictitious company’s infrastructure. It really doesn’t get any more practical than this.</p><p>Pierre: I see — how exactly does such an exam work and why do many people talk about two days of constant stress?</p><p>Paul: The exam is roughly divided into 24 hours of hacking and then 24 hours of documentation. During the first part, you are largely isolated, constantly monitored via a webcam and screen sharing and have to rely completely on your own skills. In the end, the only thing that counts is whether you manage to achieve the objectives in the tasks set and document all the steps correctly, comprehensibly and exactly as prescribed — points are not published, but at the end it is simply a case of pass or fail.</p><p>Pierre: Okay, that’s amazing — you took your OSCP back in 2013 and have therefore held a lifelong certification for over a decade. At the same time, you have also passed several significantly higher OffSec certifications. Nevertheless, you have now deliberately opted for the new OSCP+, even though it is the same certificate that you passed eleven years ago, but which expires after a certain period of time. Why don’t you start by telling us how your journey with OffSec originally began and what particularly fascinated you back then?</p><p>Paul: Yes, my enthusiasm for security and hacking goes back to my youth. Back then, it was much more difficult to gain in-depth knowledge. There were hardly any high-quality, purpose-built infrastructures or playgrounds like there are today (e.g. TryHackMe or Hack The Box), and YouTube videos or e-books were often rather patchy. As a result, you had to make a lot of things up yourself, which took time and patience. When I was able to afford the OSCP, I bought it straight away. The idea of learning directly from the makers of BackTrack (now Kali Linux) was simply irresistible. And so I signed up to Offsec in 2013 and passed my first certification in the field — the OSCP — in the same year. Offsec itself was not only the creator of one of the most well-known hacker operating systems in the world, but even then it was the world’s leading provider of training in this area.</p><h3>Personal background &amp; motivation</h3><p>Pierre: You’ve been with Offsec for 11 years and now have several certifications under your belt. What motivates you to keep taking new exams and developing yourself further?</p><p>Paul: The subject area is incredibly diverse. You can quickly get lost in one specialization — which I wanted to avoid. The various exams at OffSec help me to cover a broad spectrum and thus become really fit in many areas instead of just being an absolute crack in one specialty. I’m also driven by exploring new topics.</p><p>Pierre: You mentioned the “Try Harder” mantra several times before the interview. What significance does this have in your professional and personal environment?</p><p>Paul: For me, “Try Harder” means above all: keep at it! Continuous development and not taking any shortcuts. If you want to get really good at pentesting, you have to internalize the mantra and integrate it into your everyday life. It also teaches me to trust myself and master things independently. If I fail, it’s often because I’m still missing the basics — that doesn’t mean I can never do it. This mindset has taken me a long way professionally and made me the pentester I am today.</p><h3>Changes at OffSec &amp; social impact</h3><p>Pierre: OffSec has evolved over the years. What do you see as the most important changes, both at company and course/exam level?</p><p>Paul: Firstly, OffSec has improved the quality of the teaching material. It has always been on top, but you can tell that they are living their own “Try Harder” mantra and constantly improving it. The whole company seems more professional today; at the same time, contact with the students has become more accessible. In 2013, it was all still quite distant, you had to browse forums and find out for yourself when you were ready for the exam, for example. The courses are now much more structured, which is particularly beneficial for IT professionals who want to get into the hacking scene.</p><p>Pierre: How do you perceive the social impact of OffSec, especially with regard to the “Try Harder” mantra and the demanding certifications?</p><p>Paul: Certifications such as the OSCP are highly valued — both in the industry and in individual teams. Passing alone creates an incredibly positive feeling; you are proud to have achieved something so challenging. Even failing can help you move forward because you learn a lot and are better prepared for the next attempt.</p><p>Pierre: The proctored exams are a big topic at OffSec. To what extent do you see this as a step towards more professionalism and seriousness?</p><p>Paul: The video and screen monitoring makes the certificate even more credible. Fraud is made much more difficult, which increases the value of the certification. In our company, we even use such certificates as a recruitment criterion. Of course, there are still loopholes, but OffSec is making an important contribution to protecting the integrity of its certificates and thus making the entire industry a great deal more professional.</p><h3>The new OSCP+ exam</h3><p>Pierre: Let’s move on to the new OSCP+. What was your first impression of it compared to your old OSCP exam from 2013?</p><p>Paul: After more than ten years, a lot has changed! The content has been modernized, for example Active Directory topics or a breached account scenario in which you receive valid access data for the fictitious company network in advance — similar to what is already done in many pentest scenarios. At the same time, other classic things such as the buffer overflow part have been removed from the exam. That was also one of the reasons why I wanted to take the exam again — to reinforce current content and to see how OffSec has adapted the format to modern times. I also work as an internal instructor and wanted to see for myself what the process is like nowadays in order to be able to help junior pentesters in the best possible way.</p><p>Pierre: And how would you rate the level of difficulty from a personal perspective? After all, you are now at a completely different level professionally.</p><p>Paul: As a senior pentester, you might expect to pass the exam without any problems. But OffSec likes to surprise you! I only took a few days to go through the new material and practise in the challenge labs. The exam itself took me around 18 hours, partly because I’m very meticulous with my documentation. Of course it was solvable for me, but some of the tasks were really nerve-wracking. Nevertheless, the learning effect was great. I recommend anyone who has already collected dust on their OSCP certificate on the wall to take a look at the new OSCP+.</p><p>Pierre: What aspects of the new format surprised you in a particularly positive way?</p><p>Paul: The AD environment was really cool. It was a bit smaller than I had initially expected, but the new breached account scenario — i.e. starting the race with an existing user/pass — has a nice twist. It saves you the often very frustrating start when you have to start completely without a clue. This allows beginners in particular to concentrate on the actual topic. For me, it was also a welcome opportunity to test new tools in the exam — these are my personal challenges that I create for myself. For example, I tried out “ligolo-ng” (<a href="https://github.com/nicocha30/ligolo-ng">https://github.com/nicocha30/ligolo-ng</a>) for tunneling and found it extremely useful.</p><p>Pierre: In the new OSCP+, but also before that, there is a clear requirement not to use AI tools such as ChatGPT. How do you assess this ban, especially in light of the fact that such technologies are used in practice?</p><p>Paul: I see that as quite controversial and a very exciting question. On the one hand, of course, you want to reflect real-life scenarios and allow modern technologies, because AI can actually help in many areas. On the other hand, however, the test should reflect personal performance, not that of a language model. I understand that OffSec wants to play it safe here, so that “the AI” doesn’t just spit out a solution. Nevertheless, a the trade-off between using and banning would perhaps make sense — for example, limited use of AI for research purposes, but no automated actions, or perhaps a time limit. There are already special regulations for special software in the exam anyway. Offsec also has its own AI learning assistant, which is of course not permitted in the exam. It is possible that this is a tool that could be adapted accordingly in order to allow it for the exam and thus make the research more efficient. After all, AI-based solutions have long been part of everyday life in many companies today — including here at greenhats, of course — and I think it would make more sense to train people to use them responsibly rather than banning them outright. But this is an extremely complex topic that cannot be solved so easily — so please take the statements as loosely unstructured thoughts for now.</p><h3>Personal experience &amp; further development</h3><p>Pierre: During the preparations for the interview, you liked to draw parallels with martial arts. How would you describe the similarities?</p><p>Paul: In martial arts, a black belt is often just the beginning of a much longer journey. You may be a “master”, but the development never stops. I feel the same way about the OSCP: once you’ve passed the exam, you can be proud — but that’s when it really starts. Your self-confidence grows and at the same time you learn to constantly challenge yourself. For me, an exam is always an ideal environment to apply new knowledge and develop myself further.</p><p>Pierre: What does “not resting on one’s laurels” actually mean in your more than ten-year career as a pentester?</p><p>Paul: The field is developing rapidly! New vulnerabilities, leaks, tools and tactics emerge every day. It’s impossible to pick up on everything immediately, but it’s important to keep updated with latest tools. OffSec courses offer a solid basis that is up-to-date and relevant to practice. I think certifications are a good incentive to get to grips with a topic in depth. But regardless of this, you should approach new tools with curiosity and not rely on what you have already learned.</p><p>Pierre: Although you already have seven certificates, including OSEE and OSCE3, you decided to take the OSCP again. What was the main reason?</p><p>Paul: I now have the OSCP+ — seven certificates, if you’ve been counting ;) — Joking aside. Of course, I can prove with the certificate that I’m also constantly training and have current topics on my radar. In fact, my most important reason was my role as an instructor. I want to give my junior pentesters an impression of the current examination process that is as close to reality as possible. This is only possible if I know myself how things currently work at OffSec. Of course, there is also a certain amount of personal motivation: I like exams because I learn best in such stressful situations.</p><p>Pierre: Okay, that’s a whole new perspective. How did you prepare yourself mentally and physically for the test, which lasted several days?</p><p>Paul: I would say I’m pretty used to the stress of exams. Nevertheless, you can still feel the strain after many hours of concentrated work. The most important thing for me is sleep! A short power nap can work wonders if you’re stuck in one place. And of course a solid meal is part of it. My wife always cooks a big pot of goulash in advance, which I spread out over the exam days — tradition is a must!</p><h3>Tips &amp; Tricks</h3><p>Pierre: Do you have any general strategies or approaches for future candidates to prepare themselves optimally?</p><p>Paul: As I said: eat, drink and, above all, sleep enough! I’ve seen for myself that after a long period of frustration and a short break, you can suddenly crack a task in 20 minutes that you previously failed at for six hours. Mental freshness is therefore essential. I also recommend getting to know different tools instead of just relying on the ones mentioned in the course. A newer tool is often more efficient or provides better error messages. For example, I currently use “legba” (<a href="https://github.com/evilsocket/legba">https://github.com/evilsocket/legba</a>) instead of “hydra” for brute force attacks on network protocols, simply because it is much more intuitive to use.</p><p>Pierre: On the subject of perseverance and “try harder”: do you have any mental tricks to cope with the rollercoaster ride in the exam?</p><p>Paul: Rituals help. Whether it’s the same meal, a sports session or a certain drink — that’s how you stabilize yourself a bit and create consistency in the highs and lows. As far as the content is concerned, the official material covers all the essentials, but OffSec places great emphasis on your own thinking. You have to think outside the box and not expect every attack technique to work one-to-one like in the textbook.</p><p>Pierre: Are there any specific platforms or books that you recommend to complement the OffSec materials?</p><p>Paul: I always find it useful to look at newer tools, because the OffSec materials naturally can’t always be completely up to date. Examples: “netexec” is a good successor to crackmapexec, ‘legba’ for Bruteforce or even ‘ligolo-ng’ for tunneling. It simply makes sense not to have just one tool for one task, especially if an attack attempt does not work as planned. It’s often the most trivial things that get in the way, such as a tool that is not up to date or is too new, so that new unexpected errors occur that are not yet sufficiently documented.</p><h3>Conclusion &amp; outlook</h3><p>Pierre: Despite all your certificates, you still want to learn new things. What fascinates you most about it?</p><p>Paul: I see it as a never-ending journey. Every exam gives me the opportunity to discover something new or to see things differently. The IT security world is so dynamic that there is always something that makes me curious.</p><p>Pierre: Where do you see the greatest added value in the fact that the OSCP certification (now OSCP+) is constantly being further developed?</p><p>Paul: On the one hand, it allows you to keep pace with modern systems, tools and tactics. On the other hand, the candidates become aware that there is no “forever valid” solution. Finally, an expiring certificate has more value to government agencies and large enterprises. Customers appreciate it when certificates are not valid for life because it underlines the topicality of the knowledge.</p><p>Pierre: What final statement would you like to pass on to the community and future candidates?</p><p>Paul: Much of what we use in cyber security today is based on the dedication and work of individuals or small teams that drive open source projects forward. I think it’s important to give something back — be it through your own tools, features, documentation or simply constructive bug reports. Every contribution counts. And with this in mind: Try harder! Never stop developing yourselves.</p><h3>Personal Insides</h3><p>Pierre: Okay, we could actually stop there — but let’s go into a few more points. Was there a moment during your learning phases or exams that had a particular impact on you?</p><p>Paul: Definitely. The feeling when you finally break through after hours of failure and find a solution is unique. In the same way, failing can be completely frustrating. The important thing is not to be discouraged by it, but to learn from it and try again.</p><p>Pierre: And how important is the exchange with the community or other OffSec students for you?</p><p>Paul: For me personally, it has never played a major role. I usually do my own thing. But I see in forums and on Discord how much support people give each other. That’s great and can definitely help.</p><p>Pierre: Do you have any highlights or anecdotes from your experiences at Offsec?</p><p>Paul: I had a ticket open with OffSec a few months before the official launch of the OSCP+, asking about the possibility of redoing the OSCP — but there was no option at the time, even after weeks of discussion. Then, at some point, the news came that OffSec was actually customizing the flagship product. Certainly a coincidence, but nevertheless funny that it then became OSCP+ of all things, with which they make exactly that possible. Respect to OffSec for daring to do something so big — tweaking the OSCP is really brave!</p><p>Pierre: What is your final personal opinion on the OSCP+?</p><p>Paul: OffSec has proven itself once again with the OSCP+: They are moving with the times, integrating new technologies into their course material, and placing even more emphasis on professionalism. For longtime pentesters, it’s worth taking on such a demanding challenge again-if only to stay on the ball and keep growing. Those who take on the challenge should internalize the “Try Harder” mantra: Perseverance, creativity, structured work and, last but not least, a good dose of tenacity are required. Of course, the OSCP is a certificate for life and no matter when you pass it, it is an incredible achievement. But … after all, it’s &quot;Try Harder,&quot; not &quot;Tried Harder.&quot; — so keep up!</p><p>Pierre: Thank you very much for the exciting insight! Finally: What’s next for you personally? Have you already set your sights on new goals or certifications?</p><p>Paul: Definitely. My next big project is the OSEE, which is considered by OffSec to be one of the toughest certifications of all. This course is about kernel exploit development at a level that goes much deeper into the operating system level than is normally required in the day-to-day work of a pentester. That’s what I find so fascinating and daunting at the same time: you get to know the computer from the inside out, so to speak, but I rarely use this hardcore knowledge in my day-to-day pentesting job. Nevertheless, I don’t want to miss out on this opportunity and want to prepare for it soon.</p><p>Pierre: That sounds like a good resolution for 2025. In any case, I wish you every success and thank you for your personal insight into the world of pentest certifications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a881d15744" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DE: Interview — 11 Jahre OSCP — Ein persönlicher Rückblick]]></title>
            <link>https://greenhats.medium.com/de-interview-11-jahre-oscp-ein-pers%C3%B6nlicher-r%C3%BCckblick-9de8c2b21732?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/9de8c2b21732</guid>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[oscp-certification]]></category>
            <category><![CDATA[offsec]]></category>
            <category><![CDATA[oscp-preparation]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Wed, 25 Dec 2024 15:49:20 GMT</pubDate>
            <atom:updated>2026-01-19T14:25:01.508Z</atom:updated>
            <content:encoded><![CDATA[<h3>DE: Interview — 11 Jahre OSCP — Ein persönlicher Rückblick</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*gQ1eIreePBdYKMp-hRi0aA.png" /></figure><p><em>Kaum eine Branche entwickelt sich so dynamisch wie die IT-Sicherheit. Die ständige Weiterentwicklung von Technologien bringt nicht nur neue Möglichkeiten, sondern auch neue Herausforderungen mit sich — und erfordert von Fachkräften, immer einen Schritt voraus zu sein. Cybersecurity-Zertifizierungen wie der OSCP spielen dabei eine zentrale Rolle. Pierre Herget, Geschäftsführer der INS Systems GmbH, spricht heute mit Paul Werther, CTO der greenhats GmbH, über seinen persönlichen Werdegang im Bereich der Zertifizierung von Cybersecurity-Spezialisten.</em></p><p><strong>Pierre</strong>: Hey Paul, willkommen zu unserem Interview 11 Jahre OSCP! Wir steigen direkt ein. Vorab — für alle, die den Begriff OSCP noch nie gehört haben: Was verbirgt sich dahinter?</p><p><strong>Paul</strong>: Hey Pierre — Also der Offensive Security Certified Professional oder kurz OSCP ist eine der bekanntesten Pentesting-Zertifizierungen überhaupt. Sie setzt vollständiges, praktisches Hacking-Können voraus — also kein Multiple-Choice-Test, sondern eine echte Angriffssimulation in einer Infrastruktur eines fiktiven Unternehmens. Praxisnaher geht es wirklich nicht.</p><p><strong>Pierre</strong>: Verstehe — Wie genau läuft so eine Prüfung ab und warum sprechen viele von zwei Tagen Dauerstress?</p><p><strong>Paul</strong>: Das Examen teilt sich grob auf in 24 Stunden Hacking und anschließend 24 Stunden für die Dokumentation. Man ist im ersten Teil weitestgehend isoliert, wird permanent über eine Webcam und Screensharing überwacht und muss sich komplett auf das eigene Können verlassen. Am Ende zählt nur, ob man es schafft, die Ziele in den gestellten Aufgaben zu erreichen und sämtliche Schritte korrekt, nachvollziehbar und genau nach Vorschrift zu dokumentieren — Punkte werden nicht veröffentlicht, sondern es heißt am Schluss schlicht: bestanden oder nicht bestanden.</p><p><strong>Pierre</strong>: Okay, krass — du hast bereits 2013 deinen OSCP gemacht und hältst somit seit über einem Jahrzehnt eine lebenslang gültige Zertifizierung. Gleichzeitig hast du inzwischen auch mehrere deutlich höhere OffSec-Zertifizierungen abgelegt. Trotzdem hast du dich jetzt ganz bewusst für den neuen OSCP+ entschieden, obwohl es ja das gleiche Zertifikat ist, was du vor elf Jahren bestanden hast, was aber nach einer gewissen Zeit abläuft. Erzähl uns doch zu Beginn, wie deine Reise mit OffSec ursprünglich begonnen hat und was dich damals besonders fasziniert hat.</p><p><strong>Paul</strong>: Ja, meine Begeisterung für Security und Hacking reicht zurück bis in meine Jugend. Damals war es erheblich schwieriger, an fundiertes Wissen zu gelangen. Es gab kaum hochwertige und genau dafür gebaute Infrastrukturen oder Spielwiesen wie heute (z. B. TryHackMe oder Hack The Box), und YouTube-Videos oder E-Books waren oft eher lückenhaft. Entsprechend musste man sich vieles selbst zusammenreimen, was Zeit und Geduld gekostet hat. Als ich mir dann den OSCP leisten konnte, habe ich sofort zugeschlagen. Der Gedanke, direkt von den Machern von BackTrack (heute Kali Linux) zu lernen, war einfach unwiderstehlich. Und so habe ich 2013 mich bei Offsec angemeldet und noch im selben Jahr meine erste Zertifizierung in dem Bereich — den OSCP — bestanden. Offsec selbst war nicht nur der Schöpfer eines der bekanntesten Hacker-Betriebssysteme der Welt, sondern schon damals der weltweit führende Anbieter von Schulungen in diesem Bereich.</p><h3>Persönlicher Werdegang &amp; Motivation</h3><p>Pierre: Du bist seit 11 Jahren dabei und hast mittlerweile mehrere Zertifizierungen in der Tasche. Was motiviert dich immer wieder, neue Prüfungen abzulegen und dich weiterzuentwickeln?</p><p><strong>Paul</strong>: Das Themengebiet ist unheimlich vielfältig. Man kann sich schnell in einer Spezialisierung verlieren — was ich vermeiden wollte. Die verschiedenen Prüfungen bei OffSec helfen mir, ein breites Spektrum abzudecken, und so in vielen Bereichen wirklich fit zu werden, anstatt nur in einem Spezialgebiet der absolute Crack zu sein. Außerdem treibt mich das Erforschen neuer Themen an.</p><p><strong>Pierre</strong>: Du hast bereits vor dem Interview mehrfach das „Try Harder“-Mantra angesprochen. Welche Bedeutung hat das in deinem beruflichen und persönlichen Umfeld?</p><p>Paul: „Try Harder“ heißt für mich vor allem: <em>dranbleiben</em>! Sich stetig weiterentwickeln und keine Abkürzungen nehmen. Wer im Pentesting richtig gut werden will, muss das Mantra verinnerlichen und in den Alltag integrieren. Es vermittelt mir auch, mir selbst zu vertrauen und Dinge eigenständig zu meistern. Wenn ich scheitere, liegt es oft daran, dass mir noch Grundlagen fehlen — das heißt nicht, dass ich es niemals schaffen kann. Dieses Mindset hat mich beruflich sehr weit gebracht und mich zu dem Pentester gemacht, der ich heute bin.</p><h3>Veränderungen bei OffSec &amp; gesellschaftlicher Impact</h3><p><strong>Pierre</strong>: Im Laufe der Jahre hat sich OffSec weiterentwickelt. Was sind aus deiner Sicht die wichtigsten Veränderungen, sowohl auf Unternehmens- als auch auf Kurs-/Prüfungsebene?</p><p><strong>Paul</strong>: Zum einen hat OffSec die Qualität des Lehrmaterials nochmal gesteigert. Es war schon immer on top, aber man merkt, dass sie ihr eigenes „Try Harder“-Mantra leben und ständig verbessern. Die gesamte Firma wirkt heute professioneller; gleichzeitig ist der Kontakt zu den Studenten zugänglicher geworden. 2013 war das alles noch recht distanziert, man musste in Foren stöbern und selbst herausfinden, wann man z. B. zur Prüfung bereit ist. Inzwischen sind die Kurse viel stärker strukturiert, was insbesondere IT-Profis die in die Hacking-Szene einsteigen wollen sehr zugute kommt.</p><p><strong>Pierre</strong>: Wie nimmst du den gesellschaftlichen Einfluss von OffSec wahr, insbesondere im Hinblick auf das „Try Harder“-Mantra und die anspruchsvollen Zertifizierungen?</p><p><strong>Paul</strong>: Zertifizierungen wie der OSCP haben einen hohen Stellenwert — sowohl in der Branche als auch in einzelnen Teams. Allein das Bestehen erzeugt ein unglaublich positives Gefühl; man ist stolz darauf, etwas so Forderndes geschafft zu haben. Selbst ein Nichtbestehen kann einen voranbringen, weil man viel lernt und beim nächsten Versuch besser vorbereitet ist.</p><p><strong>Pierre</strong>: Die neuen überwachten Prüfungen sind ein großes Thema bei OffSec. Inwiefern siehst du darin einen Schritt zu mehr Professionalität und Seriosität?</p><p><strong>Paul</strong>: Die Video- und Bildschirmüberwachung macht das Zertifikat noch glaubwürdiger. Betrug wird deutlich erschwert, was den Wert der Zertifizierung steigert. In unserer Firma nutzen wir solche Zertifikate sogar als Einstellungskriterium. Natürlich gibt es immer noch Schlupflöcher, aber OffSec leistet hier einen wichtigen Beitrag, um die Integrität ihrer Zertifikate zu schützen und so die ganze Branche ein großes Stück professioneller zu machen.</p><h3>Das neue OSCP+ Examen</h3><p><strong>Pierre</strong>: Kommen wir zum neuen OSCP+. Was war dein erster Eindruck davon im Vergleich zu deiner alten OSCP-Prüfung von 2013?</p><p><strong>Paul</strong>: Nach mehr als zehn Jahren hat sich viel geändert! Die Inhalte sind modernisiert, zum Beispiel Active-Directory-Themen oder ein Breached-Account-Szenario, bei dem man gültige Zugangsdaten für das fiktive Unternehmensnetz vorab erhält — also ähnlich wie es bei vielen Pentest-Szenarien auch schon gemacht wird. Gleichzeitig sind andere klassische Dinge wie der Buffer-Overflow-Part entfernt worden. Das war auch einer der Gründe, warum ich die Prüfung erneut machen wollte — um aktuelle Inhalte zu festigen und zu sehen, wie OffSec das Format an die heutige Zeit angepasst hat. Außerdem bin ich als interner Ausbilder tätig und wollte selbst erleben, wie der Ablauf heutzutage ist, um Nachwuchspentestern optimal helfen zu können.</p><p><strong>Pierre</strong>: Und wie würdest du den Schwierigkeitsgrad aus persönlicher Sicht einordnen? Immerhin bist du mittlerweile fachlich auf einem komplett anderen Level.</p><p><strong>Paul</strong>: Als Senior Pentester erwartet man vielleicht, das Examen ohne Probleme zu meistern. Aber OffSec sorgt gern für Überraschungen! Ich hatte mir nur ein paar Tage Zeit genommen, das neue Material durchzugehen und in den Challenge-Labs zu üben. Beim Examen selbst habe ich schließlich rund 18 Stunden gebraucht, auch weil ich sehr akribisch dokumentiere. Klar war es für mich lösbar, aber manche Aufgaben haben echt Nerven gekostet. Der Lerneffekt war dennoch großartig. Ich empfehle jedem, bei dem sich schon Staub auf dem OSCP Zertifikat an der Wand angesammelt hat, sich mal den neuen OSCP+ anzuschauen.</p><p><strong>Pierre</strong>: Welche Aspekte des neuen Formats haben dich besonders positiv überrascht?</p><p><strong>Paul</strong>: Die AD-Umgebung war wirklich cool. Zwar etwas kleiner, als ich zunächst erwartet hatte, aber das neue Breached-Account-Szenario — sprich, mit einem bereits vorhandenen User/Pass ins Rennen zu starten — hat einen netten Twist. Es erspart den oft sehr frustrierenden Einstieg, wenn man komplett ohne Anhaltspunkt loslegen muss. So können sich gerade Einsteiger auf das <em>eigentliche</em> Thema konzentrieren. Für mich war es außerdem eine willkommene Gelegenheit, im Examen neue Tools zu testen — das sind dann meine persönlichen Herausforderungen, die ich mir zusätzlich schaffe. Zum Beispiel habe ich „ligolo-ng“ (https://github.com/nicocha30/ligolo-ng) für Tunneling ausprobiert und fand das extrem nützlich.</p><p><strong>Pierre</strong>: Im neuen OSCP+, aber auch davor schon, gibt es die klare Vorgabe, keine KI-Tools wie ChatGPT einzusetzen. Wie bewertest du dieses Verbot, gerade vor dem Hintergrund, dass solche Technologien in der Praxis durchaus genutzt werden?</p><p><strong>Paul</strong>: Das sehe ich ziemlich kontrovers und ist eine sehr spannende Frage. Auf der einen Seite möchte man natürlich reale Szenarien abbilden und moderne Techniken zulassen, denn KI kann in vielen Bereichen tatsächlich helfen. Auf der anderen Seite soll die Prüfung aber die <em>persönliche</em> Leistung widerspiegeln, nicht die eines Sprachmodells. Ich verstehe, dass OffSec hier auf Nummer sicher gehen möchte, damit nicht einfach „die KI“ eine Lösung ausspuckt. Trotzdem wäre ein besserer Mittelweg vielleicht sinnvoll — beispielsweise eine begrenzte Nutzung von KI zu Recherchezwecken, aber keine automatisierten Handlungen, oder vielleicht eine zeitliche Begrenzung. Sonderregelungen gibt es ja im Examen ohnehin für spezielle Software schon. Außerdem hat Offsec ja einen eigenen KI Lernassistenten, der im Examen natürlich nicht erlaubt ist. Möglicherweise ist das ja ein Werkzeug, was entsprechend angepasst werden könnte, um es für die Prüfung zuzulassen und die Recherche somit effizienter zu machen. Immerhin gehören KI-basierte Lösungen heute in vielen Unternehmen längst zum Alltag — natürlich auch bei uns bei greenhats, und für mich wäre es sinnvoller, den Umgang damit verantwortungsvoll zu trainieren, anstatt sie pauschal zu verbieten. Aber das ist ein extrem komplexes Thema, was man keinesfalls so einfach lösen kann — daher bitte die Aussagen jetzt erst mal als lose unstrukturierte Gedanken werten.</p><h3>Persönliche Erfahrungen &amp; Weiterentwicklung</h3><p><strong>Pierre</strong>: Im Rahmen der Vorbereitungen für das Interview hast du gern Parallelen zum Kampfsport gezogen. Wie würdest du die Gemeinsamkeiten beschreiben?</p><p><strong>Paul</strong>: Im Kampfsport ist ein schwarzer Gürtel oft nur der Anfang einer viel längeren Reise. Man ist zwar „Meister“, aber die Entwicklung hört nie auf. Genauso empfinde ich das beim OSCP: Hat man die Prüfung bestanden, kann man stolz sein — aber dann geht es erst richtig los. Das eigene Selbstvertrauen wächst, und man lernt gleichzeitig, sich ständig neu zu challengen. Für mich ist ein Examen immer eine optimale Umgebung, um neues Wissen anzuwenden und mich weiterzuentwickeln.</p><p><strong>Pierre</strong>: Was bedeutet „nicht auf seinen Lorbeeren ausruhen“ konkret in deiner über zehnjährigen Pentester-Karriere?</p><p><strong>Paul</strong>: Der Bereich entwickelt sich rasant! Täglich tauchen neue Schwachstellen, Leaks, Tools und Taktiken auf. Man kann unmöglich alles sofort aufnehmen, aber es ist wichtig, am Ball zu bleiben. OffSec-Kurse bieten da eine solide Basis, die aktuell und praxisrelevant ist. Ich finde, Zertifizierungen sind dabei ein guter Anreiz, sich intensiv mit einem Thema auseinanderzusetzen. Aber auch unabhängig davon sollte man mit Neugier an neue Tools herangehen und sich nicht auf das bereits Erlernte verlassen.</p><p><strong>Pierre</strong>: Obwohl du schon sieben Zertifikate, inklusive OSEE und OSCE3, hast, hast du dich nochmal für das OSCP entschieden. Was war der Hauptgrund?</p><p><strong>Paul</strong>: Inzwischen darf ich mich über das OSCP+ freuen — also sieben Zertifikate, wer’s mitgezählt hat ;) — Spaß beiseite. Natürlich kann ich selbst mit dem Zertifikat nachweisen, dass ich mich ebenso permanent weiterbilde und aktuelle Themen auf dem Schirm habe. Tatsächlich war mein wichtigster Grund meine Rolle als Ausbilder. Ich will meinen Nachwuchspentestern einen möglichst realitätsnahen Eindruck vom aktuellen Prüfungsablauf geben. Das geht nur, wenn ich selbst weiß, wie es derzeit bei OffSec abläuft. Natürlich kommt auch ein gewisser persönlicher Antrieb dazu: Ich mag Prüfungen, denn ich lerne in solchen Stresssituationen am allerbesten.</p><p><strong>Pierre</strong>: Okay, das ist mal eine ganz neue Perspektive. Wie hast du dich mental und körperlich auf die mehrtägige Dauer der Prüfung vorbereitet?</p><p><strong>Paul</strong>: Ich würde sagen, ich bin den Prüfungsstress schon ziemlich gewohnt. Trotzdem spürt man die Belastung nach vielen Stunden konzentrierter Arbeit. Am wichtigsten ist für mich Schlaf! Ein kurzer Powernap kann Wunder wirken, wenn man an einer Stelle festhängt. Und natürlich gehört eine solide Mahlzeit dazu. Meine Frau kocht immer einen großen Topf Gulasch vor, den ich über die Prüfungstage verteile — Tradition muss sein!</p><h3>Tipps &amp; Tricks</h3><p><strong>Pierre</strong>: Hast du allgemeine Strategien oder Herangehensweisen für künftige Prüflinge, um sich optimal vorzubereiten?</p><p><strong>Paul</strong>: Wie gesagt: ausreichend Essen, Trinken und vor allem Schlafen! Ich habe es selbst erlebt, dass man nach einer längeren Frustrationsphase und einer kurzen Ruhepause plötzlich in 20 Minuten eine Aufgabe knackt, an der man vorher sechs Stunden lang gescheitert ist. Mentale Frische ist also essenziell. Zusätzlich empfehle ich, verschiedene Tools kennenzulernen, anstatt sich nur auf die im Kurs erwähnten zu verlassen. Oft ist ein neueres Tool effizienter oder liefert bessere Fehlermeldungen. Beispielsweise habe nutze ich für Brute-Force Angriffe auf Netzwerkprotokolle aktuell “legba” (<a href="https://github.com/evilsocket/legba">https://github.com/evilsocket/legba</a>) statt “hydra”, einfach weil die Handhabung deutlich intuitiver ist.</p><p><strong>Pierre</strong>: Thema Durchhaltevermögen und „Try Harder“: Hast du mentale Tricks, um die Achterbahnfahrt in der Prüfung zu bewältigen?</p><p><strong>Paul</strong>: Rituale helfen. Egal ob es das gleiche Essen ist, eine Sporteinheit oder ein bestimmtes Getränk — so stabilisiert man sich ein bisschen und schafft Konstanz in den Hochs und Tiefs. Was die Inhalte angeht: Das offizielle Material deckt alles Wesentliche ab, aber OffSec legt großen Wert auf das eigene Denken. Man muss um die Ecke denken und darf nicht erwarten, dass jede Angriffstechnik eins zu eins so klappt wie im Lehrbuch.</p><p><strong>Pierre</strong>: Gibt es bestimmte Plattformen oder Bücher, die du ergänzend zu den OffSec-Materialien empfiehlst?</p><p><strong>Paul</strong>: Ich finde es immer sinnvoll, sich mit neueren Tools auseinanderzusetzen, weil die OffSec-Materialien naturgemäß nicht immer <em>ganz</em> up to date sein können. Beispiele: „netexec“ ist ein guter Nachfolger für crackmapexec, „legba“ für Bruteforce oder eben „ligolo-ng“ zum Tunneln. Es ist einfach sinnvoll, nicht nur <em>ein</em> Werkzeug für eine Aufgabe zu haben, gerade, wenn mal ein Angriffsversuch nicht klappt wie geplant. Oft sind es die trivialsten Sachen, an denen man sich aufhält wie ein Tool, was nicht up to date ist oder zu neu, sodass neue unerwartete Fehler passieren, die noch nicht ausreichend dokumentiert sind.</p><h3>Fazit &amp; Ausblick</h3><p><strong>Pierre</strong>: Trotz all deiner Zertifikate hast du immer noch Lust, Neues zu lernen. Was fasziniert dich daran besonders?</p><p><strong>Paul</strong>: Ich betrachte das als nie endende Reise. Jede Prüfung gibt mir Gelegenheit, Neues zu entdecken oder Bekanntes anders zu sehen. Die IT-Security-Welt ist so dynamisch, da findet sich immer wieder etwas, das mich neugierig macht.</p><p><strong>Pierre</strong>: Wo siehst du den größten Mehrwert darin, dass die OSCP-Zertifizierung (jetzt OSCP+) ständig weiterentwickelt wird?</p><p><strong>Paul</strong>: Zum einen hält man so Schritt mit modernen Systemen, Tools und Taktiken. Zum anderen entsteht bei den Prüflingen ein Bewusstsein dafür, dass es keine „ewig gültige“ Lösung gibt. Und nicht zuletzt sind ablaufende Zertifikate auch in Behörden und großen Unternehmen ein Thema. Kunden schätzen es, wenn Zertifikate <em>nicht</em> auf Lebenszeit gelten, weil es die Aktualität des Wissens unterstreicht.</p><p><strong>Pierre</strong>: Was möchtest du als abschließendes Statement an die Community und zukünftige Prüflinge weitergeben?</p><p><strong>Paul</strong>: Ein Großteil dessen, was wir heute in der Cyber-Security nutzen, basiert auf der Hingabe und Arbeit einzelner Menschen oder kleiner Teams, die Open-Source-Projekte voranbringen. Ich finde es wichtig, etwas zurückzugeben — sei es durch eigene Tools, Features, Dokumentation oder einfach konstruktive Bug-Reports. Jeder Beitrag zählt. Und in diesem Sinne: <em>Try Harder</em>! Hört nie auf, euch weiterzuentwickeln.</p><h3>Persönliche Insides</h3><p><strong>Pierre</strong>: Okay, eigentlich könnte man auch damit aufhören — aber lass uns noch kurz ein paar Punkte vertiefen. Gab es einen Moment während deiner Lernphasen oder Prüfungen, der dich besonders geprägt hat?</p><p><strong>Paul</strong>: Auf jeden Fall. Das Gefühl, wenn man nach stundenlangem Scheitern endlich durchbricht und eine Lösung findet, ist einmalig. Genauso kann ein Nichtbestehen komplett frustrieren. Wichtig ist, sich davon nicht entmutigen zu lassen, sondern daraus zu lernen und es neu zu versuchen.</p><p><strong>Pierre</strong>: Und wie wichtig ist für dich der Austausch mit der Community oder anderen OffSec-Studenten?</p><p><strong>Paul</strong>: Für mich persönlich hat das nie eine große Rolle gespielt. Ich ziehe mein Ding meist allein durch. Aber ich sehe in Foren und auf Discord, wie viel Unterstützung sich die Leute gegenseitig geben. Das ist großartig und kann definitiv weiterhelfen.</p><p><strong>Pierre</strong>: Hast du noch irgendein Highlight oder eine Anekdote, aus deinen Erfahrungen bei Offsec?</p><p><strong>Paul</strong>: Ich hatte einige Monate vor dem offiziellen Launch des OSCP+ ein Ticket bei OffSec offen, in dem ich nach einer Möglichkeit fragte, den OSCP erneut zu machen — damals gab es allerdings noch keine Option — auch nicht nach wochenlangen Diskussionen. Dann kam irgendwann die Neuigkeit, dass OffSec das Flaggschiff-Produkt tatsächlich anpasst. Sicher Zufall, aber trotzdem lustig, dass es dann ausgerechnet zum OSCP+ geworden ist, mit dem sie genau das ermöglichen. Respekt an OffSec, dass sie sich so etwas Großes trauen — am OSCP zu schrauben ist schon mutig!</p><p><strong>Pierre</strong>: Was ist deine abschließende persönliche Meinung zum OSCP+?</p><p><strong>Paul</strong>: Mit dem OSCP+ hat sich OffSec ein weiteres Mal bewiesen: Sie gehen mit der Zeit, integrieren neue Technologien in ihr Kursmaterial und legen noch mehr Wert auf Professionalität. Für langjährige Pentester lohnt sich der Schritt, sich erneut einer so anspruchsvollen Challenge zu stellen — allein schon, um „am Ball zu bleiben“ und sich selbst weiterzuentwickeln. Wer sich darauf einlässt, sollte das „Try Harder“-Mantra verinnerlichen: Ausdauer, Kreativität, strukturiertes Arbeiten und nicht zuletzt eine gute Portion Hartnäckigkeit sind gefragt. Klar, der OSCP ist ein Zertifikat auf Lebenszeit und egal wann man ihn bestanden hat, eine unfassbar große Leistung. Das kleine Aber sehe ich dennoch. Es heißt ja “Try Harder” und nicht “Tried Harder”.</p><p><strong>Pierre</strong>: Vielen Dank für den spannenden Einblick! Zum Schluss: Wie geht es für dich persönlich weiter? Hast du schon neue Ziele oder Zertifizierungen ins Auge gefasst?</p><p><strong>Paul</strong>: Auf jeden Fall. Mein nächstes großes Vorhaben ist der OSEE, die von OffSec als eine der härtesten Zertifizierungen überhaupt gilt. In diesem Kurs geht es um Kernel Exploit Development auf einem Level, das viel tiefer in die Betriebssystemebene hineinreicht, als man es im Alltag eines Pentesters normalerweise braucht. Genau das finde ich so faszinierend und zugleich abschreckend: Man lernt den Computer quasi von innen heraus kennen, doch in meinem täglichen Pentesting-Job nutze ich diese Hardcore-Kenntnisse eher selten. Dennoch möchte ich mir diese Gelegenheit nicht entgehen lassen und mich bald darauf vorbereiten.</p><p><strong>Pierre</strong>: Das klingt doch mal nach einem guten Vorsatz für 2025. Ich wünsche dir auf jeden Fall viel Erfolg und bedanke mich für deinen persönlichen Einblick in die Welt der Pentest — Zertifizierungen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9de8c2b21732" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pentesters choice: Useful links / software for daily work in IT]]></title>
            <link>https://greenhats.medium.com/useful-links-software-for-daily-work-in-it-6231a45b63c0?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/6231a45b63c0</guid>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[links]]></category>
            <category><![CDATA[it-security]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 07:43:11 GMT</pubDate>
            <atom:updated>2026-06-01T10:37:28.742Z</atom:updated>
            <content:encoded><![CDATA[<p>Here you will find a current selection of useful websites or open source software that can make everyday life in the IT department easier. This is not a compilation, but a very selective choice collected by our pentest team.</p><h3>Mail Tester</h3><p>DMARC, SPF, DKIM, Spam Check, Blacklist Check<br><a href="https://www.mailgenius.com/">https://www.mailgenius.com/</a></p><h3>DNS</h3><p>DNS History, Reverse Search, Find hosts sharing the same IP<br><a href="https://dnsdumpster.com/">https://dnsdumpster.com/</a></p><h3>Tunneling</h3><p><a href="https://ngrok.io/">https://ngrok.io/</a></p><h3>SIEM / XDR (Open Source)</h3><p><a href="https://wazuh.com/">https://wazuh.com/</a></p><h3>Open Source all-in one PaaS</h3><p>Coolify is an all-in one PaaS that helps you to self-host your own applications, databases or services (like Wordpress, Plausible Analytics, Ghost) without managing your servers and all the complexity that comes with it, it is also known as an open-source &amp; self-hostable Heroku / Netlify / Vercel alternative.<a href="https://coolify.io/"><br>https://coolify.io/</a></p><h3>Uptime Monitoring</h3><p><a href="https://github.com/louislam/uptime-kuma">https://github.com/louislam/uptime-kuma</a><br><a href="https://evait.medium.com/uptime-and-network-monitoring-while-pentesting-ensuring-service-continuity-and-early-detection-80aef8b5c13b">https://evait.medium.com/uptime-and-network-monitoring-while-pentesting-ensuring-service-continuity-and-early-detection-80aef8b5c13b</a></p><h3>Translation &amp; Grammar</h3><p>AI-supported translation of texts into different languages<br><a href="https://www.deepl.com/">https://www.deepl.com/</a></p><p>Grammar, style and spelling checker<br><a href="https://www.deepl.com/write">https://www.deepl.com/write</a></p><h3>E-Mail finder and verification tool</h3><p><a href="https://hunter.io/">https://hunter.io/</a></p><h3>Remote Desktop</h3><p>Open source alternative to Teamviewer and Anydesk, cross-platform incl. free STUN / TURN servers<br><a href="https://rustdesk.com/">https://rustdesk.com</a></p><h3>Document Signing</h3><p>Open Source Alternative to DocuSign, PandaDoc and more.<br><a href="https://www.docuseal.com/">https://www.docuseal.com/</a></p><h3>Online Asset finder</h3><p><a href="https://www.shodan.io/">https://www.shodan.io/</a><br><a href="https://censys.io/">https://censys.io/</a></p><h3>Community based learning</h3><p>roadmap.sh is a community effort to create roadmaps, guides and other educational content to help guide developers in picking up a path and guide their learnings.<br><a href="https://roadmap.sh/">https://roadmap.sh/</a><br><a href="https://roadmap.sh/cyber-security">https://roadmap.sh/cyber-security</a></p><h3>“Open Source” images &amp; vectors / free licence</h3><p><a href="https://pixabay.com/">https://pixabay.com/</a><br><a href="https://www.pexels.com/">https://www.pexels.com/<br></a><a href="https://www.freepik.com/">https://www.freepik.com/</a></p><h3>Online Photo / Vector</h3><p>Avnac is an open canvas for layouts, posters, and graphics. <a href="https://avnac.design/"><br>https://avnac.design/</a></p><p>Image compression, resizing, converting (client side / no server)<br><a href="https://squoosh.app/">https://squoosh.app/</a></p><p>Avnac is an open canvas for layouts, posters, and graphics. <a href="https://avnac.design/"><br>https://avnac.design/</a> (<a href="https://github.com/akinloluwami/avnac">https://github.com/akinloluwami/avnac</a>)</p><h3>File-Share</h3><p>Fast &amp; secure transmission of data (end-to-end via WebRTC) (can be blocked by firewall)<br><a href="https://www.sharedrop.io/">https://www.sharedrop.io/</a></p><p>Same as sharedrop but for LAN only (local file sharing in your browser. Inspired by Apple’s Airdrop.)<br><a href="https://snapdrop.net/">https://snapdrop.net/</a></p><p>P2P + E2EE: Syncthing<br><a href="https://syncthing.net/">https://syncthing.net/</a></p><h3>VPN Connect Server (Wireguard)</h3><p>NetBird creates a peer-to-peer overlay network that automatically connects your servers, containers, cloud, and remote teams over an encrypted tunnel. WireGuard®-based.<br><a href="https://netbird.io/">https://netbird.io/</a><br><a href="https://docs.netbird.io/selfhosted/selfhosted-quickstart">https://docs.netbird.io/selfhosted/selfhosted-quickstart</a></p><h3>Process automation</h3><p><a href="https://n8n.io/">https://n8n.io/</a> (Community Edition)</p><h3>Standalone Modern E-Mail Server</h3><p>Stalwart is a scalable, secure and robust open-source mail server software written in Rust designed for the 21st century.<br><a href="https://stalw.art/">https://stalw.art/</a></p><h3>Bookmark Manager</h3><p><a href="https://github.com/linkwarden">https://github.com/linkwarden</a></p><h3>Devops</h3><p><a href="https://www.rundeck.com/">https://www.rundeck.com/</a> (Community Edition)</p><h3>Ticketsystem</h3><p><a href="https://zammad.org/">https://zammad.org/</a> (Community Edition)</p><h3>Mobile Development</h3><p>Create / convert image resource packages for iOS &amp; Android<br><a href="https://appicon.co/">https://appicon.co/</a></p><h3>Screenshots on Windows, Mac &amp; Linux</h3><p>Direct editing, blur areas, insert texts, open source<br><a href="https://github.com/flameshot-org/flameshot">https://github.com/flameshot-org/flameshot</a></p><p>Demonstration of the most important functions in a GIF<br><a href="https://raw.githubusercontent.com/flameshot-org/flameshot/master/data/img/preview/animatedUsage.gif">https://raw.githubusercontent.com/flameshot-org/flameshot/master/data/img/preview/animatedUsage.gif</a></p><h3>Active Directory Self Audit (Windows Domäne)</h3><p><a href="https://www.pingcastle.com/">www.pingcastle.com</a></p><p><a href="https://www.semperis.com/purple-knight/">https://www.semperis.com/purple-knight/</a></p><h3>Backups</h3><p>Borg: Deduplicated, compressed, encrypted backups<br><a href="https://www.borgbackup.org/">https://www.borgbackup.org/</a> + <a href="https://torsion.org/borgmatic/">https://torsion.org/borgmatic/</a></p><p>Storage: <a href="https://www.borgbase.com/">https://www.borgbase.com/</a><br>GUI: <a href="https://vorta.borgbase.com/">https://vorta.borgbase.com/</a></p><p>Alternative (For specific files / folders)<br><a href="https://restic.net/">https://restic.net/</a></p><h3>Website Change Notifier</h3><p>Monitors changes on websites and Sken.io notifies via e-mail when a change occurs.<br><a href="https://sken.io/">https://sken.io</a></p><p>Open Source Self-hosted change monitoring of web pages<br><a href="https://github.com/dgtlmoon/changedetection.io">https://github.com/dgtlmoon/changedetection.io</a></p><h3>Password Manager</h3><p>Cloud:<br><a href="https://bitwarden.com/">https://bitwarden.com/</a></p><p>Self hosted:<br><a href="https://github.com/dani-garcia/vaultwarden">https://github.com/dani-garcia/vaultwarden</a></p><h3>RAID Calculator</h3><p><a href="https://www.omnicalculator.com/other/raid">https://www.omnicalculator.com/other/raid</a></p><h3>Microsoft 365 Licensing Overview</h3><p><a href="https://m365maps.com/">https://m365maps.com/</a></p><h3>Local Wiki / Documentation (Markdown)</h3><p><a href="https://obsidian.md/">https://obsidian.md</a> (Desktop)<br><a href="https://obsidian.md/mobile">https://obsidian.md/mobile</a> (Mobile)</p><p>Self hosted:<br><a href="https://js.wiki/">https://js.wiki/</a></p><h3>List of other exciting open source projects</h3><p><a href="https://github.com/awesome-selfhosted/awesome-selfhosted">https://github.com/awesome-selfhosted/awesome-selfhosted</a></p><h3>LDAP Monitor</h3><p><a href="https://github.com/p0dalirius/LDAPmonitor">https://github.com/p0dalirius/LDAPmonitor</a><br><a href="https://evait.medium.com/ldap-monitor-live-%C3%BCberwachung-f%C3%BCr-ver%C3%A4nderungen-an-ldap-objekten-31e4f7d9f7b7">https://evait.medium.com/ldap-monitor-live-%C3%BCberwachung-f%C3%BCr-ver%C3%A4nderungen-an-ldap-objekten-31e4f7d9f7b7</a></p><h3>Decoder &amp; Encoder</h3><p>Complex concatenation of encryption and coding<br><a href="https://gchq.github.io/CyberChef/">https://gchq.github.io/CyberChef/</a></p><h3>Collection of almost all important pentest topics (offensive)</h3><p><a href="https://book.hacktricks.xyz/">https://book.hacktricks.xyz/</a></p><h3>Overview Application Security Testing</h3><p><a href="https://appsecmap.com/">https://appsecmap.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6231a45b63c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing accessed_at to ActiveStorage Blob in Ruby on Rails]]></title>
            <link>https://greenhats.medium.com/implementing-accessed-at-to-activestorage-blob-in-ruby-on-rails-b8ad00d9944f?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8ad00d9944f</guid>
            <category><![CDATA[avo]]></category>
            <category><![CDATA[active-storage]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Sat, 09 Sep 2023 07:10:07 GMT</pubDate>
            <atom:updated>2023-09-10T19:44:51.996Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implementing accessed_at to ActiveStorage Blob / Attachment in Ruby on Rails</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*DH__ZDltuQmZxbTS3bfh7g.png" /><figcaption>Overwriting ActiveStorage::Blobs::RedirectController</figcaption></figure><p>Ruby on Rails (RoR) is a powerful web application framework known for its simplicity and productivity. In this technical blog post, we’ll explore how to enhance your RoR application by adding an accessed_at column to ActiveStorage Blobs and customizing the ActiveStorage::Blobs::RedirectController. This will allow you to track when someone accesses a specific blob or file, such as through a download action.</p><p><strong>Adding the accessed_at column</strong></p><p><em>Make sure that Active Storage is properly installed and initialized.</em></p><p>To start, we need to add an accessed_at column to the active_storage_attachments table. We can achieve this using a Rails migration:</p><pre>bin/rails generate migration AddAccessedAtToActiveStorageAttachments accessed_at:datetime</pre><p>Which results in the following code</p><pre>class AddAccessedAtToActiveStorageAttachments &lt; ActiveRecord::Migration[7.0]<br>  def change<br>    add_column :active_storage_attachments, :accessed_at, :datetime<br>  end<br>end</pre><p>This migration adds the necessary column to store the access timestamps.</p><p><strong>Customizing the RedirectController</strong></p><p>Next, we’ll customize the ActiveStorage::Blobs::RedirectController to update the accessed_at timestamp whenever someone accesses / downloads a file. We do this by calling the touch method on the corresponding Attachment record. First create a file that overwrites the internal Rails controller:</p><p><strong><em>app/controllers/active_storage/blobs/redirect_controller.rb</em></strong></p><p>Then we have to add our code (some parts are copied from the original source code of this controller)</p><pre>class ActiveStorage::Blobs::RedirectController &lt; ActiveStorage::BaseController<br>  include ActiveStorage::SetBlob<br>  before_action :authenticate # Optional: Add authentication to any active storage blob<br><br>  def show<br>    # Begin accessed_at modification<br>    attachment = ActiveStorage::Attachment.find_by(blob_id: @blob.id)<br>    attachment.touch(:accessed_at) if attachment<br>    # End accessed_at modification<br><br>    expires_in ActiveStorage.service_urls_expire_in<br>    redirect_to @blob.url(/service/disposition: params[:disposition]), allow_other_host: true<br>  end<br><br>  private<br><br>  def authenticate<br>    # Implement your authentication logic here (in our example we use rodauth)<br>    rodauth.require_account<br>  end<br>end</pre><p>With this code, we ensure that the accessed_at timestamp is updated whenever someone accesses a file. Additionally, we&#39;ve added an optional authentication step using Rodauth to restrict access to authenticated users. Adjust the authenticate method to your authentication requirements.</p><p><strong>Displaying the accessed_at Column</strong></p><p>To display the accessed_at metadata in a user-friendly way, we utilized the Avo gem — an absolute must have in your RoR project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k5f0c71Ju1RLQ0yv.png" /><figcaption>Check out on <a href="https://avohq.io/">https://avohq.io/</a></figcaption></figure><p>Lets have a look at the default file list view:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFxsaSYd2diQ4qrcnFltkA.png" /></figure><p>This view contains the filename and the file size. Now we need to add our metadata. Specifically, we ejected the view for the File List component with the following command:</p><pre>bin/rails g avo:eject --component Avo::Fields::Common::Files::ViewType::ListComponent</pre><p>This command extracts the view files into your Rails application’s directory under app/components/avo/fields/common/files/view_type/</p><ul><li>list_component.rb</li><li>list_component.html.erb</li></ul><p>In the list_component.html.erb file, we made a simple modification to display the accessed_at timestamp alongside the file name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*thuOTpLQWkrhmQ5N8zdrIw.png" /></figure><p>Just replace the &lt;%= file.filename %&gt; part with:</p><pre>&lt;div class=&quot;flex flex-col&quot;&gt;<br>  &lt;p&gt;&lt;%= file.filename %&gt;&lt;/p&gt;<br>  &lt;p class=&quot;text-xs text-gray-400&quot;&gt;&lt;%= file.created_at %&gt;&lt;%= &quot; (Last access: #{file.accessed_at})&quot; if file.accessed_at? %&gt;&lt;/p&gt;<br>&lt;/div&gt;</pre><p>This modification ensures that the creation date is also displayed along with the last access date (if available) in parentheses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*2zz5irU2OjY4IK7L21RRAw.png" /></figure><p>After clicking on the download button of the first file the result is as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*smipAKe3617PUtxJwziMqQ.png" /></figure><p><strong>Software used</strong></p><ul><li>Ruby on Rails: 7.0.7.2</li><li>Ruby: 3.2.0</li><li>Rodauth: 2.31.0</li><li>Avo: 3.0.1.beta8</li></ul><p>By implementing these steps, you can enhance your RoR application’s functionality by tracking when users access specific files while maintaining optional authentication control. Additionally, you can provide a more informative user interface by displaying relevant metadata. Taking it a step further, you can use the overridden Rails controller to update only specific files or file types.</p><p>So, go ahead, rock your RoR projects, and let your code leave a lasting impression! 🚀💎</p><p>Thanks for reading,</p><p>FLX</p><p><a href="https://github.com/FLX-0x00">https://github.com/FLX-0x00</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8ad00d9944f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uptime and Network Monitoring While Pentesting: Ensuring Service Continuity and Early Detection]]></title>
            <link>https://greenhats.medium.com/uptime-and-network-monitoring-while-pentesting-ensuring-service-continuity-and-early-detection-80aef8b5c13b?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/80aef8b5c13b</guid>
            <category><![CDATA[uptime-monitoring]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[pentest]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 10:04:34 GMT</pubDate>
            <atom:updated>2024-09-03T16:26:46.100Z</atom:updated>
            <content:encoded><![CDATA[<p>In the realm of penetration testing, it is essential to maintain an overview of the target environment while conducting simulated attacks. Ensuring that critical services of the client remain unaffected during the testing process is crucial for a successful and comprehensive assessment. Network monitoring, specifically uptime monitoring, plays a pivotal role in achieving this objective. By monitoring specific targets, a pentester can detect potential service disruptions early on and respond swiftly to any unforeseen issues.</p><p><strong>The Importance of Uptime Monitoring in Pentesting</strong></p><p>Uptime monitoring serves as a vital safeguard during penetration testing engagements. It enables the pentester to observe the availability and stability of essential services on the client’s network infrastructure continually. This monitoring approach provides several key advantages:</p><ol><li>Service Continuity: Penetration testing, by its nature, involves simulating attacks and probing various systems and services. However, it is crucial to avoid any significant disruption to business operations during this process. Uptime monitoring helps to ensure that critical services remain up and running, minimizing the impact on the client’s daily operations by providing quick feedback on any interference attempts.</li><li>Early Detection of Service Failures: During the penetration testing process, certain actions might inadvertently trigger service failures, such as hitting a blocking firewall rule. With uptime monitoring, the pentester can promptly identify any service interruptions, enabling them to adjust their tactics and minimize any potential downtime.</li><li>Network Connectivity Awareness: Apart from monitoring services, uptime monitoring also assists in keeping track of the pentester’s network connectivity. This monitoring ensures that the pentester is instantly alerted if their network connection is interrupted or blocked, allowing them to address the issue promptly.</li></ol><p><strong>Uptime Kuma: An Efficient Monitoring Tool</strong></p><p><a href="https://github.com/louislam/uptime-kuma">https://github.com/louislam/uptime-kuma</a></p><p>At evait security, we rely on the tool to fulfill our uptime monitoring needs during penetration testing engagements. This powerful tool is deployed using Docker, requiring just one command to set up. After creating an account, the local instance becomes readily accessible, simplifying the monitoring process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YWyj0awTKvXgXnduj2ZdhQ.png" /><figcaption>Uptime Kuma in action: Monitors the internal DC with ping, an internal http service and the internet connection via google.com</figcaption></figure><pre>docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma</pre><p><strong>Monitoring Multiple Services Simultaneously</strong></p><p>Uptime Kuma supports various monitoring options, including HTTP, TCP, DNS, and Ping, allowing the pentester to monitor multiple services simultaneously. By configuring short intervals for monitoring, the pentester can obtain real-time insights into service availability.</p><p><strong>Timely Notifications for Proactive Response</strong></p><p>When a service becomes unreachable, Uptime Kuma provides timely notifications through a wide range of communication channels. These notifications can be sent via popular messaging platforms, push or email services, or even as local alerts. Such proactive alerts allow the pentester to respond swiftly, mitigating potential issues before they escalate.</p><p><strong>Interpreting Network Disruptions</strong></p><p>In cases where all monitored services become inaccessible simultaneously, this may indicate a larger network issue. It could be due to the intervention of a firewall solution or a direct disruption from a network switch. Uptime monitoring helps in quickly pinpointing such disruptions, enabling the pentester to focus on identifying the root cause and rectifying the problem.</p><p><strong>Conclusion</strong></p><p>Uptime and network monitoring are invaluable tools in the arsenal of a penetration tester. Maintaining service continuity and being aware of network disruptions are crucial aspects of ethical hacking engagements. With the open source solution Uptime Kuma, pentesters can efficiently monitor multiple services and receive real-time notifications, empowering them to respond proactively to any service interruptions. By employing such monitoring practices, pentesters can ensure a comprehensive assessment while minimizing the risk of causing disruptions to their clients’ critical systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80aef8b5c13b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovery of a reflective XSS vulnerability in ARP Guard software (CVE-2023–39575)]]></title>
            <link>https://greenhats.medium.com/discovery-of-a-reflective-xss-vulnerability-in-arp-guard-software-1734b5113e1c?source=rss-df0a35f76334------2</link>
            <guid isPermaLink="false">https://medium.com/p/1734b5113e1c</guid>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[xss-vulnerability]]></category>
            <category><![CDATA[cve]]></category>
            <dc:creator><![CDATA[Pentest Team @greenhats.com]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 07:24:04 GMT</pubDate>
            <atom:updated>2023-10-12T15:40:29.041Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong><br>We recently executed an internal security assessment for a customer. During this engagement we discovered a vulnerability in the ARP Guard software. This vulnerability allowed us to inject HTML or JavaScript code into the application’s pages using a manipulated URL parameter, even without prior authentication. In this article, we provide a detailed technical description of the vulnerability and its potential impact.</p><p><strong>Technical Description</strong><br>The Reflective Cross-Site Scripting (XSS) vulnerability in ARP Guard is due to inadequate input validation and sanitization mechanisms. By manipulating a specific URL parameter, an attacker can inject arbitrary code that is executed within the victim’s browser, often leading to malicious actions or information theft. In our case, we were able to exploit the fact that the cookie named “S” is not marked as html only and can be stolen by abusing XSS. It has not been tested whether the parameter is used for authentication purposes.</p><p>We identified a vulnerable URL parameter “url_str” that was likely used to perform relative redirects after successful authentication. Insufficient input validation on the server side allowed us to inject malicious scripts into a hidden input field via this parameter.</p><figure><img alt="Typical GET request on the login page" src="https://cdn-images-1.medium.com/max/1024/1*c7PpSTN_he9Ot__G-5tgAQ.png" /><figcaption>Typical GET request on the login page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QYcxU4oLVX70NK-Tw3Z07w.png" /><figcaption>The string is injected into the hidden field after the type declaration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FTtYUz2KipSTOr6eDXxNhw.png" /><figcaption>It is also worth noting that the parameter name is injectible as well — here an example of changing the url_str to test’</figcaption></figure><p>In the context of exploiting XSS vulnerabilities, hidden HTML inputs present an interesting challenge. Hidden inputs are elements within an HTML form that are not displayed on the web page, but still contain values that can be used when the form is submitted. While XSS attacks primarily rely on injecting malicious code into visible fields, hidden inputs can also be potential targets for exploitation but the immediate impact of an XSS attack is limited in this case. A great article on this topic is provided by Portswigger: <a href="https://portswigger.net/research/xss-in-hidden-input-fields">https://portswigger.net/research/xss-in-hidden-input-fields</a></p><p>Because the injection point is positioned right after the field type declaration, it is impossible to change the type of the field using this attack. However, we can abuse the accesskey method to demonstrate a successful attack chain. But the impact is very limited because the user has to press a key combination to execute the injected js code.</p><p>Using the following simple payload, we are able to exploit the bug in the latest version of ARP Guard.</p><blockquote>https://REDACTED/login/?url_str=/management/admin/index%27%20onclick=%22alert(document.cookie)%22%20accesskey=%22C%22</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cvJL5bWil4n-pZgn6GaQUw.png" /><figcaption>After pressing CTRL+ALT+C the payload will be executed in the context of the visitor</figcaption></figure><p><strong>Conclusion</strong></p><p>The discovery of a Reflective XSS vulnerability in ARP Guard software highlights the importance of tough security testing and ongoing awareness. At evait security / greenhats, we remain committed to helping organizations identify and mitigate such vulnerabilities to improve their overall security structure. By remaining proactive and implementing the recommended fixes, organizations can strengthen their defenses against potential attacks, protect their sensitive data, and maintain the trust of their users.</p><p><strong>Mitigation</strong></p><p>If you are using this software, please ensure that you have updated to the latest version, or at least 4.0.4–1, to protect your environment from this vulnerability.</p><p><strong>Timeline</strong></p><p>20.06.2023 — Bug discovery and internal review</p><p>21.06.2023 — Vendor informed via E-Mail about this bug and providing additional information</p><p>10.07.2023 — Reminder via E-Mail (vendor has not yet responded)</p><p>11.07.2023 — Initial response from the vendor</p><p>25.07.2023 — Initial CVE request (Mitre)</p><p>04.08.2023 — Vendor deployed a fix in version 4.0.4–1, online instances will need two more weeks to fix</p><p>28.08.2023 — Mitre reserved CVE-2023–39575 for this vulnerability</p><p>10.09.2023 — Reminder via E-Mail (no response from vendor since 04.08.2023)</p><p>14.09.2023 — Still no response from vendor; inform about upcoming public disclosure as fixed version is availabe</p><p>18.09.2023 — Publicly disclose, notify Mitre team, wait for CVE to become public</p><p>20.09.2023 — Publicly disclosure of CVE</p><p>Author: FLX | <a href="https://github.com/FLX-0x00">https://github.com/FLX-0x00</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1734b5113e1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>