<?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 Omar Tamer on Medium]]></title>
        <description><![CDATA[Stories by Omar Tamer on Medium]]></description>
        <link>https://medium.com/@OmarTamer0?source=rss-a5b84c4de62e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*osYKNMzLU-NL1Y7EYKWHxg.jpeg</url>
            <title>Stories by Omar Tamer on Medium</title>
            <link>https://medium.com/@OmarTamer0?source=rss-a5b84c4de62e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:26:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@OmarTamer0/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[How I Found an Unauthenticated GraphQL API Leaking User Data]]></title>
            <link>https://infosecwriteups.com/how-i-found-an-unauthenticated-graphql-api-leaking-user-data-eeec3d54fe74?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeec3d54fe74</guid>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 20:10:55 GMT</pubDate>
            <atom:updated>2026-10-11T20:10:55.262Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmpNzylbXAAq2zRKlAGmFA.png" /></figure><h3>GraphQL shifts a lot of power to the client. One endpoint, one POST request, and the caller decides exactly which objects and fields come back. That flexibility is the feature. It is also why a single missing authorization check does not leak one record, it leaks the graph.</h3><p>This article is based on one of my own bug bounty findings: an unauthenticated GraphQL API that exposed user data at scale. The company stays unnamed and identifying details are generalized, but the methodology is exactly what I used: fingerprinting, schema discovery, locating the missing-authorization bug, proving impact at scale, and writing it up so the severity is undeniable.</p><h3>Why GraphQL fails differently</h3><p>In REST, each resource sits behind its own route, and authorization is usually checked route by route. In GraphQL, a single endpoint resolves an arbitrary tree of fields. Authorization has to be enforced at the <strong>resolver</strong> level, on every field, for every object. Teams frequently authenticate the <em>endpoint</em> (“you need a token to call /graphql”) but forget to authorize the <em>resolvers</em> (“should this token see this specific object’s email field?”).</p><p>The result is two recurring bug classes:</p><ul><li><strong>Missing authentication</strong>: the endpoint answers sensitive queries with no credentials at all.</li><li><strong>Broken object-level authorization (BOLA)</strong>: you are authenticated, but you can request objects that are not yours by supplying their identifiers.</li></ul><p>Both come from the same root cause: the server was built to answer questions without deciding <em>who is allowed to ask them</em>.</p><h3>Step 1: Confirm and fingerprint the endpoint</h3><p>During recon I came across an endpoint that looked like GraphQL. Before anything else, I confirmed it with a minimal valid query:</p><pre>POST /graphql HTTP/1.1<br>Content-Type: application/json</pre><pre>{&quot;query&quot;:&quot;{__typename}&quot;}</pre><p>It answered with {&quot;data&quot;:{&quot;__typename&quot;:&quot;Query&quot;}}, confirming a live GraphQL API.</p><p>Next, I fingerprinted the implementation, because the engine determines how it leaks. Different servers behave differently under malformed input: some echo distinctive error strings, some expose a specific set of default fields, some enable introspection or field suggestions by default and others do not. Sending a deliberately invalid query and studying the exact shape and wording of the error told me which discovery technique would pay off before I spent time on it.</p><h3>Step 2: Map the schema with introspection</h3><p>Introspection is GraphQL’s built-in self-description, and it is the first thing I check. When it is on, the server hands you the entire schema:</p><pre>{&quot;query&quot;:&quot;query{__schema{types{name kind fields{name args{name} type{name kind ofType{name}}}}}}&quot;}</pre><p>That response is a map: every type, every query and mutation, every field and argument. Loading it into a visualizer shows how the types connect, and from that point you are no longer guessing. The target has documented its own attack surface for you.</p><h3>Step 3: When introspection is disabled</h3><p>Disabling introspection is the usual first hardening step, and it is not a dead end. The schema can often be rebuilt indirectly:</p><ul><li><strong>Field suggestions.</strong> Many engines, even with introspection off, still respond to a wrong field with “Did you mean email?” Each hint reveals a real field name. Tooling automates this into a near-complete schema reconstruction.</li><li><strong>Client-side artifacts.</strong> Front-end bundles, mobile apps, and documented operations contain real queries. Captured traffic shows the field names and arguments the application itself uses.</li><li><strong>Error-driven enumeration.</strong> Type mismatches and argument errors leak structure one message at a time.</li></ul><p>Introspection being off reduces convenience, not exposure.</p><h3>Step 4: Find the query with no guard</h3><p>With the schema mapped, the real work begins: for each query and mutation that returns something sensitive, test whether authorization is actually enforced.</p><p>The method is systematic. I took the query that returns user data and sent it with every credential stripped: no Authorization header, no session cookie, nothing that identifies a user.</p><pre>POST /graphql HTTP/1.1<br>Content-Type: application/json</pre><pre>{&quot;query&quot;:&quot;{ users { id username name createdAt } }&quot;}</pre><p>It returned data. No token, no session, and the response contained user records: internal IDs, usernames, full names, and account creation dates. The finding was binary and undeniable: personal data, no authentication. When an endpoint does require a session, the next move is BOLA: authenticate as a low-privilege user and request objects by identifiers that should not belong to you.</p><pre>{&quot;query&quot;:&quot;{ user(id: 1337) { id email role } }&quot;}</pre><p>The highest-value gap is often the difference between what the UI renders and what the resolver returns. An interface may only show a display name, while the underlying type still exposes email, role, internal flags, or tokens to anyone who asks for those fields.</p><h3>Step 5: Prove scale</h3><p>A single leaked record is a finding. The entire user base is a severity multiplier. The vulnerable query supported cursor-based pagination, so proving scale took nothing more than following the cursor:</p><pre>{&quot;query&quot;:&quot;{ users(first: 100, after: \&quot;&lt;cursor&gt;\&quot;) { edges { node { id email } } pageInfo { endCursor hasNextPage } } }&quot;}</pre><p>Walking the cursor page by page showed that every user record was reachable in bulk. The query also accepted a search parameter, which meant an attacker could look up specific people by name instead of only dumping everything. Documenting “this query returns the full set, paginated, with no authentication” is what turns a shrug into a critical.</p><h3>Step 6: Extend the impact</h3><p>Before writing it up, I checked the adjacent issues that frequently accompany the core bug:</p><ul><li><strong>Mutations without authorization.</strong> Write operations outrank reads. A mutation that changes state unauthenticated is a far higher-impact finding than a read.</li><li><strong>Query batching.</strong> Some servers accept an array of operations in one request. Where they do, per-request rate limits on sensitive actions can be bypassed by batching many attempts into a single call.</li><li><strong>Depth and complexity.</strong> Deeply nested, recursive selections with no depth or cost limit can exhaust server resources, a denial-of-service vector distinct from data exposure.</li><li><strong>Verbose errors.</strong> Stack traces and internal paths in error responses leak implementation detail useful for further attacks.</li></ul><h3>Step 7: Write it up so the severity is undeniable</h3><p>The technical work is only half the job; a strong report is what gets a finding resolved instead of dismissed. I anchor every GraphQL exposure report on four points:</p><ol><li><strong>No authentication required</strong>: the full request, with every credential removed, so there is no ambiguity.</li><li><strong>Exactly what is exposed</strong>: the specific fields and why they matter (PII, internal identifiers, authentication material).</li><li><strong>Scale</strong>: the pagination proof showing how much data is reachable, not just a sample.</li><li><strong>A realistic attacker scenario</strong>: who can do this (anyone on the internet) and what they walk away with.</li></ol><p>Then I include remediation, because demonstrating you understand the fix elevates the report:</p><ul><li>Enforce authentication and <strong>object-level authorization at the resolver</strong>, on every field, not only at the gateway.</li><li>Disable introspection and field suggestions in production.</li><li>Apply query depth and complexity limits, and rate-limit batched operations.</li><li>Return only the fields each role is entitled to, and never rely on the UI to conceal data the API still serves.</li></ul><h3>The pattern underneath</h3><p>Across every GraphQL exposure I have looked at, the flaw is not an exotic exploit. It is a design decision that was never consciously made: the API was built to answer questions, and no one decided which questions, from whom. As teams ship more code faster, that gap keeps widening, and the recon-to-impact path above keeps working.</p><p>The bug I found did not need a clever chain or an exotic payload. It only needed someone to ask the API a question that nobody had decided it should refuse.</p><h3>About the author</h3><p>I’m Omar Tamer, an offensive security specialist and penetration tester based in Cairo. I hold OSCP+, CPENT, LPT Master and CEH Master, and I serve on EC-Council’s CPENT Scheme Committee, helping shape the exam that tests real-world penetration testing skills.</p><p>This finding is the kind of work those certifications are meant to prove: methodical recon, understanding how an application is built, and turning a technical flaw into clear, provable impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeec3d54fe74" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-i-found-an-unauthenticated-graphql-api-leaking-user-data-eeec3d54fe74">How I Found an Unauthenticated GraphQL API Leaking User Data</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CPENT and LPT Master: My Full Experience, Prep Strategy and Everything You Need to Know]]></title>
            <link>https://medium.com/@OmarTamer0/cpent-and-lpt-master-my-full-experience-prep-strategy-and-everything-you-need-to-know-387be9fefad0?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/387be9fefad0</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cpent]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[ec-council]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Sat, 27 Jun 2026 23:30:36 GMT</pubDate>
            <atom:updated>2026-06-29T17:58:06.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Y2dp-ciHxl9DNURgBt4m6A.jpeg" /><figcaption><strong>CPENT Certification</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*_uYnk5OIeKdK0-inpcL5eg.jpeg" /><figcaption><strong>LPT Master Certification</strong></figcaption></figure><h3>Who Am I?</h3><p>I’m Omar Tamer, a 22-year-old offensive security specialist based in Egypt. I hold <strong>OSCP+, CPENT, </strong>and <strong>LPT Master,</strong> E<strong>C-Council’s highest penetration testing credential</strong>, and serve as a<strong> CPENT Scheme Committee Member (2026–2029)</strong> and <strong>EC-Council Exam Item Writer.</strong></p><p>On the platform side: #4 Worldwide on CyberTalents, Top 1% on TryHackMe, and Pro Hacker on Hack The Box with all 11 HTB Pro Labs completed, including 5 ultra-rare tracks.</p><h3>Why I’m Writing This</h3><p><strong>CPENT </strong>is one of the most valuable hands-on certifications in offensive security today. It is respected by employers, rigorous in its design, and increasingly recognized as a true differentiator for penetration testers. But there are almost no quality writeups out there. Most of what you’ll find is either vague, outdated, or written by someone who barely passed. I want to change that. Whether you’re considering <strong>CPENT</strong>, currently studying, or about to sit the exam, this is the guide I wish I had.</p><h3>What Is CPENT?</h3><p>The <strong>Certified Penetration Testing Professional (CPENT)</strong> is EC-Council’s advanced, fully hands-on penetration testing certification. It tests your ability to perform real-world penetration tests across complex, multi-layered enterprise network environments. No theory-only questions, no multiple-choice tricks.</p><p><strong>Exam Structure at a Glance:</strong></p><p>The exam takes place inside a live, multi-segment enterprise network environment. You are given a set of targets across isolated network ranges and your job is to enumerate, exploit, pivot, and document everything like a real penetration tester would on a professional engagement. The environment includes:</p><ul><li>Multiple network segments that require pivoting to access</li><li>Windows and Linux machines with varying levels of hardness</li><li>Active Directory components</li><li>Targets that require double pivoting to reach deeper network zones</li><li>Reverse engineering challenges</li><li>A full professional penetration test report as part of your final deliverable</li></ul><p>Your score is based on the machines you compromise, the flags you capture, and the quality of your report. The report is not optional; it is graded. Once your exam time ends, you have <strong>one full week</strong> to complete and submit your penetration test report, which gives you enough time to write a polished, professional document rather than rushing it at the end of your session.</p><p>If you score <strong>70% or above</strong>, you earn the <strong>CPENT </strong>certification. If you score <strong>90% or above</strong>, you automatically earn the <strong>LPT Master</strong>, EC-Council’s highest penetration testing credential.</p><p>That’s the target. And it’s absolutely achievable with the right preparation.</p><h3>The Exam Format: 24 Hours or 2x12 Hours?</h3><p>CPENT gives you two options:</p><blockquote>One continuous 24-hour attempt</blockquote><blockquote>Two separate 12-hour sessions</blockquote><p>I chose the <strong>2x12-hour split</strong>, and it was the best decision I made.</p><p>Here’s my honest take: 24 hours straight is brutal on the mind and body. You lose cognitive sharpness after hour 10 or 12, and in an exam that demands precision, especially in report writing and complex pivoting, that matters enormously.</p><p>The split gave me a chance to step back after Day 1, sleep, process what I had found, come back fresh for the next 12 hr split and finish strong. If you’re someone who performs better with rest (and most people do), go with the 2x12 split. Don’t let anyone tell you it’s the “easier” option. It’s the smarter one.</p><h3>Preparation: What Actually Works</h3><p>This is the most important section of this article. I’ll be blunt: there’s a lot of noise about CPENT prep. Here’s what actually moved the needle for me.</p><h3>1. EC-Council iLabs: Your Number One Resource</h3><p>If you do nothing else, <strong>do iLabs</strong>. Cover every single lab in the curriculum. Don’t skip, don’t rush, don’t just read the solution. Hands-on practice in <strong>iLabs </strong>is the closest thing you’ll get to the actual exam environment.</p><p>The <strong>CPENT </strong>exam is practical. The machines, the network structure, the types of vulnerabilities, iLabs primes you for all of it. I cannot overstate this enough.</p><h3>2. The CPENT Practice Range: Your Secret Weapon</h3><p>The second most impactful resource I used was the <strong>CPENT Practice Range</strong>. This is a dedicated environment specifically designed to simulate the exam. If you focus on both iLabs and the Practice Range, you are setting yourself up for a full mark and for LPT Master.</p><p>This combination is your formula:</p><blockquote><strong><em>iLabs + Practice Range = CPENT + LPT Master</em></strong></blockquote><p>I’m not guessing. That’s what happened for me, and I believe it’s repeatable.</p><h3>3. Prior Certifications as a Foundation</h3><p>When I sat for CPENT, the only certification I had was the <strong>CEH (Certified Ethical Hacker)</strong>. That was my entire foundation going in. So if you’re thinking you need a long list of credentials before attempting CPENT, you don’t. What you need is solid hands-on practice, which is exactly what iLabs and the Practice Range give you.</p><p>After CPENT I continued building my stack, but the point is that CEH gave me enough theoretical grounding and CPENT rewarded the practical effort I put in on top of it.</p><h3>The Technical Domains: What to Focus On</h3><p>CPENT covers a wide range of domains and all of them matter. Here is the order I worked through them during the exam and my honest take on each one.</p><h3>1. Active Directory</h3><p>Active Directory was the first domain I tackled and rightfully so. AD attacks are central to any enterprise penetration test and CPENT reflects that. You need to be comfortable with enumeration, privilege escalation paths, lateral movement, and common attack techniques like Kerberoasting and Pass-the-Hash. Get your AD fundamentals solid before exam day because this is where a lot of your early points come from.</p><h3>2. Reverse Engineering: It’s Broad, So Be Systematic</h3><p>Reverse engineering topics in CPENT are extensive. There’s a lot of ground to cover and it can feel overwhelming. My advice: don’t try to master everything. Focus on understanding the core concepts and common patterns. Know your tools (Ghidra, x64dbg, etc.), understand how to identify what a binary is doing, and practice reading disassembled code logically.</p><p>The exam won’t expect you to be a malware analyst. It expects you to apply reversing skills in a pentest context.</p><h3>3. IoT and OT</h3><p>This domain surprised me in a good way. <strong>CPENT includes IoT and OT targets which sets it apart from most other penetration testing certifications</strong>. You don’t need to be a hardware specialist but you do need to understand the protocols, the attack surface, and how these devices differ from traditional network targets. iLabs covers this well so don’t skip those exercises.</p><h3>4. Web Application</h3><p>Web application testing is a domain most pentesters are already somewhat comfortable with and CPENT is no different. You’ll be looking at common vulnerabilities, authentication issues, and chaining findings for impact. Approach it methodically and don’t rush through it just because it feels familiar.</p><h3>5. Pivoting and Double Pivoting: Understand It Deeply</h3><p>Pivoting and double pivoting were the most challenging areas for me personally. The concept of pivoting through multiple machines to reach isolated network segments requires solid mental mapping of network topology. You need to be comfortable with:</p><ul><li>SSH tunneling and dynamic port forwarding</li><li>Proxychains configuration</li><li>Chaining pivots across multiple hops</li><li>Keeping track of your routes under time pressure</li></ul><p><strong>Golden tip:</strong> Don’t try to master every pivoting tool out there. Instead, pick two and go deep; I recommend <strong>ligolo-ng</strong> and <strong>sshuttle</strong> as your primary tools, with <strong>ProxyChains</strong> as your fallback. <strong>Ligolo-ng</strong> especially is a game changer for multi-hop scenarios; once you understand how it handles routing, double pivoting becomes significantly less stressful. If you can set up a two-hop pivot with these tools without referencing documentation, you’re exam-ready.</p><p>Practice this until it’s muscle memory. A confused pivot mid-exam costs you enormous time. Double pivoting specifically is where a lot of candidates struggle, so make sure you’ve practiced chaining at least two hops in your lab environment before sitting the exam.</p><h3>Report Writing: Don’t Sleep on This</h3><p>This was actually one of my favorite parts of the exam, and it surprised me. <strong>It was my first time writing a professional penetration test report, and I genuinely enjoyed the process.</strong></p><p><strong>EC-Council</strong> evaluates your report as part of your score. This isn’t an afterthought; it’s a significant component. A professional report should include:</p><ul><li>Executive Summary (for non-technical stakeholders)</li><li>Findings with clear risk ratings (Critical/High/Medium/Low)</li><li>Proof of concept with screenshots</li><li>Business impact per finding</li><li>Remediation recommendations</li></ul><p>Start practicing report writing early. Don’t wait until you’re done exploiting to think about documentation. Take notes as you work.</p><h3>During the Exam: My Approach</h3><p>Here’s how I structured my time across the two sessions:</p><p><strong>Session 1 (12 hours):</strong></p><ul><li>Reconnaissance and enumeration first. Map everything before touching anything.</li><li>Prioritize lower-hanging fruit to secure base points.</li><li>Document findings in real time. Don’t rely on memory.</li><li>Leave the hardest challenges for Session 2 when I’m refreshed.</li></ul><p><strong>Session 2 (12 hours):</strong></p><ul><li>Revisit anything I couldn’t complete on Day 1 with a fresh perspective.</li><li>Focus on pivoting challenges and deeper exploitation.</li><li>Reserve the last 1.5 to 2 hours exclusively for report writing and polish.</li></ul><p><strong>Golden rules during the exam:</strong></p><ul><li>Take screenshots of everything, even things you don’t end up using.</li><li>Don’t get tunnel-visioned on one machine for too long. Move on and come back.</li><li>Manage your time ruthlessly.</li><li>Stay hydrated, eat properly, and take short breaks.</li></ul><h3>The Outcome: LPT Master</h3><p>I cleared <strong>CPENT </strong>with a score that earned me the <strong>LPT Master</strong> designation, EC-Council’s pinnacle credential for penetration testers.</p><p>If you’re aiming for <strong>LPT Master</strong> (and you should be), you need 90%+. That bar is achievable. It requires:</p><ul><li>Solid preparation through iLabs and the Practice Range</li><li>Strong technical execution on the exam</li><li>A polished, professional report</li></ul><p>It’s not handed to you, but it’s absolutely within reach.</p><h3>Should You Pursue CPENT?</h3><p>Here’s my honest assessment:</p><p><strong>CPENT </strong>is worth it if you’re serious about offensive security and want a certification that holds up in a technical interview. It proves you can operate inside a real enterprise environment, not just answer multiple-choice questions. If you’re targeting red team roles, penetration testing consultancies, or any market where certifications are a hard requirement for client-facing roles, <strong>CPENT plus LPT Master is a strong combination.</strong></p><p>It’s not the right first step if you have no hands-on foundation. The exam will expose gaps fast. Get comfortable with<strong> CEH Practical</strong> or a platform like <strong>HTB </strong>and <strong>TryHackMe </strong>first, then come back to <strong>CPENT </strong>when you can enumerate and pivot without second-guessing yourself.</p><p>Final Words <strong>CPENT </strong>is one of the most respected practical penetration testing certifications available today, and it’s only getting more relevant as organizations demand certified professionals who can actually hack, not just talk about hacking.</p><blockquote>The path to <strong>CPENT + LPT Master</strong> is clear: iLabs, Practice Range, understand your pivoting cold, take report writing seriously, and choose the 2x12 split.</blockquote><p>If you have questions about <strong>CPENT</strong>, preparation strategy, or offensive security in general, feel free to reach out on <strong>LinkedIn</strong>. I respond to genuine questions.</p><p><strong>LinkedIn</strong>: <a href="http://www.linkedin.com/in/omar-tamer-1a986b2a7">Omar Tamer</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=387be9fefad0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HorusEye: I Built an AI-Assisted Active Directory Attack Platform After 1000+ CTF Rooms]]></title>
            <link>https://medium.com/@OmarTamer0/horuseye-i-built-an-ai-assisted-active-directory-attack-platform-after-1000-ctf-rooms-7f0ace21895c?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f0ace21895c</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[active-directory]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 03:25:26 GMT</pubDate>
            <atom:updated>2026-03-11T03:25:26.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thIb2EPSgUHgSlAloK1sLQ.png" /></figure><p>I have solved over 1000 rooms and machines across <strong>HackTheBox</strong>, <strong>TryHackMe</strong>, and <strong>OffSec</strong>. These are the three biggest hands-on cybersecurity platforms in the world, and together they have put me through every corner of offensive security, from basic Linux privilege escalation all the way to full Active Directory domain compromises in complex multi-machine environments.</p><p>After all of that, one thing became very clear to me. The gap between knowing how an attack works and executing it efficiently in a real environment is not a knowledge problem. It is a tooling problem.</p><p>This is the story of how I went from a 200-line wordlist script to building <strong>HorusEye</strong>, a full Active Directory attack platform, and how I built it with Claude.</p><blockquote><strong>GitHub</strong>: <a href="https://github.com/omar-tamerr/HorusEye">https://github.com/omar-tamerr/HorusEye</a></blockquote><h3>The Problem With the Current AD Toolchain</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*xtz7C1BeGnH8xfntTGouvA.png" /></figure><p>If you have done any serious Active Directory penetration testing, you already know the workflow.</p><p>You run SharpHound on the target. You load the output into BloodHound. You stare at the graph. BloodHound shows you attack paths and gives you generic exploitation steps, but when you are in a real environment with 400 users, 12 service accounts, and nested group memberships three levels deep, those generic steps leave you connecting the dots yourself. Then you open Certipy to check ADCS misconfigurations. You run impacket for execution. You run CrackMapExec to map the network. You run hashcat in a separate terminal. You keep notes in a fifth window trying to remember which account has which privilege and which path is actually worth pursuing first.</p><p>That context switching is expensive. In a timed exam it costs you hours. In a CTF tournament it costs your team flags. In a professional engagement it costs the client money.</p><p>That fragmentation is exactly what <strong>HorusEye </strong>was built to fix.</p><h3>How It Started: One Script, One Feature</h3><p>The first version was embarrassingly small. A single Python script that read BloodHound JSON and generated username wordlists in every common format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*r3s_1VmfY__teR8u90e6IA.png" /></figure><p>Given a list of AD users like john.smith and sarah.jones, it would produce every format that real IT departments actually use across 18 different patterns. That was it. No analysis, no detection, no exploitation.</p><p>But it saved me real time on every machine. Every AD engagement starts with username enumeration and password spraying. Instead of manually creating variations of every name I found in BloodHound, the script did it in seconds from data I already had.</p><p>Then I started asking myself what else I was doing manually that followed a predictable enough pattern to automate. And the list got long very quickly.</p><h3><strong>Building With Claude: Being Transparent About It</strong></h3><p>I want to be direct about this before going further. I built HorusEye with Claude. Not just for debugging or looking up syntax, but building it feature by feature, iterating on the architecture, and expanding the tool over multiple sessions together.</p><p>The security knowledge is mine. Understanding why ADCS ESC1 matters, how to chain ACL abuse into DCSync, which Kerberoastable accounts are worth targeting in what order, how to avoid lockout detection during password spraying. That comes from 1000+ machines across HTB, TryHackMe, and OffSec. Claude handled a significant portion of the implementation complexity, especially the multi-threaded network scanner, the hashcat integration layer, and the team collaboration socket server.</p><p>What I found is that this division worked extremely well. I could describe what I wanted in security terms and Claude would implement it correctly. I would test it against a real lab, find edge cases, bring those back, and iterate. The result is a tool I fully understand and can extend, but that I would have taken three times as long to build alone.</p><h3>What HorusEye Does</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xcd_hN7X24pgaJ4yMphXHA.png" /></figure><p>HorusEye ingests output from BloodHound, Certipy, ldapdomaindump, and CrackMapExec simultaneously, then handles the analysis and prioritization layer you would normally do manually. Here is a full walkthrough of every major feature.</p><h3>Attack Path Detection</h3><p>The detection engine processes your input data and identifies 13 attack path types. Each finding is scored 0 to 100 by exploitability and sorted so the fastest path to Domain Admin appears first.</p><p><strong>Kerberoasting</strong> identifies service accounts with SPNs and prioritizes any that are members of privileged groups. If svc-sql is both Kerberoastable and a Domain Admin member, that is your first target.</p><p><strong>AS-REP Roasting</strong> finds accounts with DONT_REQUIRE_PREAUTH set. No credentials are needed for this attack, which makes it extremely valuable early in an engagement before you have any foothold.</p><p><strong>DCSync</strong> detects accounts with Replicating Directory Changes rights. This is the direct path to dumping every password hash in the domain.</p><p><strong>ACL Abuse</strong> flags GenericAll, WriteDacl, WriteOwner, ForceChangePassword, and AddMember misconfigurations on high-value targets like Domain Admins and privileged groups.</p><p><strong>ADCS ESC1 through ESC8</strong> covers all eight Certipy vulnerability classes with exploitation commands specific to the templates it found in your environment.</p><p>The remaining types include Unconstrained Delegation, Constrained Delegation, GPO Abuse, Pass-the-Hash, Domain Trusts, Privileged Sessions, Weak Password Policy, and Stale Admin Accounts.</p><p>The key difference from running these tools manually: the output includes the exact impacket or tool command tailored to the account names and configurations it actually found. Not a textbook example. The real command for your real environment.</p><h3>Hash Cracking Engine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*slj9vwSA1blHLPAk5O5iQw.png" /></figure><p>Three rounds designed specifically for corporate Active Directory environments.</p><p><strong>Round 1</strong> generates AD-specific password candidates based on your target domain name. Patterns like Corp2024!, Corp@2025, Welcome2024!, Summer2024!, Password2024!. These hit in round 1 far more often than you would expect. Corporate environments where password policies technically exist but users find ways to comply while remaining predictable produce these patterns constantly across labs and real engagements.</p><p><strong>Round 2</strong> runs remaining hashes through rockyou with hashcat rule mutations. Best64, dive, or d3ad0ne depending on your time budget.</p><p><strong>Round 3</strong> runs hybrid mask attacks on anything still uncracked, appending year and number suffixes to wordlist words.</p><p>All cracked credentials are written to valid_credentials.txt immediately on discovery. Supported hash types: Kerberoast TGS-RC4 (13100), AS-REP (18200), NTLM (1000), NetNTLMv2 (5600), MS-Cache v2 (2100).</p><h3>Password Spraying</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*ccO-r64vMlf34CLcYxwRHQ.png" /></figure><p>Multi-threaded sprayer with automatic lockout detection. Primary authentication via SMB with LDAP fallback. Safe mode stops the entire operation the moment it detects lockout behavior, preventing you from accidentally locking out accounts during a real engagement. All valid credentials are saved immediately on discovery and broadcast to any connected team members in real time.</p><h3>Lateral Movement Engine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*JuVMVSJ4d5vFoSeILJFWxQ.png" /></figure><p>After you have credentials, this engine scans your target network range, tests credentials on every live host, confirms admin access by probing ADMIN$, and enumerates accessible shares. It flags interesting ones like SYSVOL, C$, backup folders, and data shares.</p><p>Output is a clear table of every reachable host with protocol support (SMB, WinRM, RDP, LDAP, MSSQL), admin status clearly marked, and ready-to-run next-step commands for each admin host.</p><h3>Attack Timeline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*1LMsGs0AioUUyrslEo1mnQ.png" /></figure><p>Takes your findings and builds a visual timeline from your current position to Domain Admin with time estimates for each step and the exact command to run at every phase. Useful both for planning your approach before execution and for writing up the attack chain afterward.</p><h3>LSASS Dump Automation</h3><p>Detects which AV or EDR is running on the target and automatically selects the appropriate dump method. CrowdStrike or SentinelOne detected means nanodump. Windows Defender means comsvcs via rundll32. Nothing detected defaults to comsvcs. Fallback is procdump. You do not have to think about this, it picks the right method for the environment automatically.</p><h3>Domain Takeover Checklist</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*5TMkelJa7njReCX4de3wlw.png" /></figure><p>A 25-item interactive checklist covering every phase of a domain takeover from initial foothold through to persistence and reporting. Items auto-check based on what HorusEye has already found and executed. Covers FOOTHOLD, RECON, CRED, LATERAL, ESCALATION, DA, PERSIST, and REPORT phases. Very useful for making sure you have not missed anything before finishing a lab or a real engagement.</p><h3>Team Collaboration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*2U0Eon2gEtys73F6slfiQA.png" /></figure><p>This feature came directly from frustration during CTF team events. Two operators share a live session over TCP. The server broadcasts every finding, cracked hash, and discovered credential to all connected operators in real time. Someone joining late gets a full state sync of everything found so far.</p><p>One person runs BloodHound analysis, another runs password spraying, another does lateral movement. Every time any of them finds a valid credential or cracks a hash, everyone sees it immediately without copying anything over Discord.</p><h3>Credentials Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*IBdw4-z-CvD_wxz6gxlZrQ.png" /></figure><p>Every credential found by any module funnels through a central manager with automatic deduplication. Spray hits, Kerberoast cracks, AS-REP results, DCSync output, lateral movement finds. All of it written to valid_credentials.txt for human use and valid_credentials.json for integration with other tools or pipelines.</p><h3>Claude AI Integration</h3><p>If you configure an Anthropic API key, HorusEye sends your findings to Claude and gets back a narrative analysis specific to your environment. Not generic descriptions but analysis like: “svc-sql TGS can be cracked offline and this account is a direct member of Domain Admins. Kerberoast then DCSync is a two-step path to full compromise.” The tool works completely without this. Every other feature runs fine without an API key. But the narrative layer is genuinely useful when you are in an unfamiliar environment and want a second opinion on what you are looking at.</p><h3>A Real CTF Workflow With HorusEye</h3><pre># Step 1: Collect with SharpHound on the Windows target<br>SharpHound.exe -c All --zipfilename bh.zip<br><br># Step 2: ADCS enumeration if a CA is present<br>certipy find -u user@corp.local -p pass -dc-ip 10.10.10.5 -json<br><br># Step 3: Run HorusEye with everything<br>python3 horuseye.py \<br>    --bloodhound ./bh/ \<br>    --certipy certipy.json \<br>    --domain corp.local \<br>    --dc 10.10.10.5 \<br>    --timeline \<br>    --da-checklist \<br>    --report report.html<br><br># Step 4: If Kerberoastable accounts found, run the auto-chain<br>python3 horuseye.py --auto-chain \<br>    --domain corp.local --dc 10.10.10.5 \<br>    -u user -p pass<br><br># Step 5: After valid creds, map the network<br>python3 horuseye.py --pivot \<br>    --target-network 10.10.10.0/24 \<br>    -u svc-sql -p &#39;ServicePass2024!&#39; \<br>    --domain corp.local --dc 10.10.10.5</pre><p>Within a few minutes you have a ranked list of attack paths, a visual timeline to Domain Admin, a network map with admin access marked, and all cracked hashes saved to file.</p><h3><strong>What 1000+ Rooms Taught Me About Building This</strong></h3><p>After solving machines across HackTheBox, TryHackMe, and OffSec, the top three platforms for hands-on security training, a few patterns became clear enough that they ended up directly in the tool.</p><p><strong>Corporate password patterns are embarrassingly predictable.</strong> The round 1 AD pattern generator hits in a meaningful percentage of real lab environments. Password policies that enforce complexity but not actual randomness produce Corp2024! over and over across different organizations and different labs.</p><p><strong>The fastest path to DA is usually the most boring one.</strong> The sophisticated attacks get written about more but in practice, weak password policy plus one Kerberoastable service account with elevated group membership is how most domains fall. HorusEye scores findings by exploitability for this reason.</p><p><strong>Tool fragmentation is the real time sink.</strong> The actual exploitation steps take minutes once you know what to do. The time goes to switching between tools, reformatting output, and holding mental state about which account has which access. Reducing that context switching was the core design goal.</p><p><strong>Team collaboration in CTFs is underrated.</strong> The coordination overhead of syncing findings manually over Discord during a team CTF is surprisingly large. A shared live state that updates automatically removes an entire category of work.</p><p>I am putting all of that experience into this tool and I will keep adding features to make it better. The road map includes OPSEC mode with traffic randomization to avoid SIEM detection, a Telegram bot that notifies your phone when credentials are found or DA is achieved, and an attack surface scoring system that grades the domain 0 to 100 for client reporting.</p><h3>Getting Started</h3><pre>git clone https://github.com/omar-tamerr/HorusEye<br>cd HorusEye<br>pip3 install -r requirements.txt --break-system-packages<br>python3 horuseye.py --help</pre><p>Test without any BloodHound output:</p><pre>python3 horuseye.py --manual --domain corp.local --no-ai</pre><p>Full documentation, all CLI flags, and usage examples are in the README.</p><blockquote><strong>GitHub</strong>: <a href="https://github.com/omar-tamerr/HorusEye">https://github.com/omar-tamerr/HorusEye</a></blockquote><h3>Final Thought</h3><p>I built HorusEye because after 1000+ machines across HTB, TryHackMe, and OffSec I wanted a tool that treated me like I already understood Active Directory. Not a tool that explains what Kerberoasting is, but one that tells me which specific account to Kerberoast in my current environment and what exact command to run against it.</p><p>Whether you use it directly or take ideas from it for your own tooling, I hope it is useful. The code is open source, feedback is welcome, and I am always reachable on LinkedIn.</p><p><strong>Omar Tamer</strong> Penetration Tester, Egypt</p><blockquote><strong>LinkedIn</strong>: <a href="https://www.linkedin.com/in/omar-tamer-1a986b2a7/">https://www.linkedin.com/in/omar-tamer-1a986b2a7/</a></blockquote><blockquote><strong>Medium</strong>: <a href="https://medium.com/@OmarTamer0">https://medium.com/@OmarTamer0</a></blockquote><blockquote><strong>Portfolio</strong>: <a href="https://omar-tamerr.github.io/">https://omar-tamerr.github.io/</a></blockquote><blockquote><strong>GitHub</strong>: <a href="https://github.com/omar-tamerr/HorusEye">https://github.com/omar-tamerr/HorusEye</a></blockquote><p>I think that is a legitimate way to build things, and being transparent about it is more useful to the community than pretending otherwise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f0ace21895c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Doubt to OSCP: My 5-Month Journey, First Failure, and Final Win]]></title>
            <link>https://medium.com/@OmarTamer0/from-doubt-to-oscp-my-5-month-journey-first-failure-and-final-win-c20304eef6dc?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20304eef6dc</guid>
            <category><![CDATA[oscp-certification]]></category>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Wed, 18 Feb 2026 19:16:08 GMT</pubDate>
            <atom:updated>2026-02-18T19:16:08.081Z</atom:updated>
            <content:encoded><![CDATA[<p>The email with “Congratulations” in the subject line is something I’ll never forget.<br>After months of preparation, one failed attempt, and a lot of pressure, I finally passed the OSCP with <strong>80/100</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gWzR3A-PNq1dbPsGCwyX8w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-Iav3h7Y2NISB7mg0cMbQ.jpeg" /></figure><p>This article is my real journey: what I did, what went wrong, and what actually helped me pass.</p><h3>My Background</h3><p>Before starting OSCP, I was already deep into offensive security.<br>👉 <a href="https://omar-tamerr.github.io/">My Portfolio</a></p><p>I hold multiple certifications and roles in the field, including:</p><ul><li>LPT Master</li><li>CPENT</li><li>CEH Master</li><li>eJPT</li><li>PCEP</li><li><strong>EC-Council</strong> Exam Item Writer</li><li>CyberTalk Speaker for<strong> EC-Council University</strong></li></ul><p>Even with this background, <strong>OSCP </strong>felt different.<br>It’s globally recognized and known for being one of the most practical penetration testing certifications. I wanted something that would truly test my methodology, mindset, and ability to perform under pressure.</p><h3>Why I Chose OSCP</h3><p>I didn’t want another theoretical certification.<br>I wanted something hands-on that reflects real penetration testing work.</p><p><strong>OSCP </strong>has that reputation worldwide, and after going through it, I can confirm it absolutely lives up to it.</p><h3>My Preparation Strategy (September → December 2025)</h3><p>I started preparing in <strong>September 2025</strong> and followed a structured plan instead of jumping randomly between platforms.</p><h3>Starting with the TJ Null List on Hack The Box</h3><p>I began with machines from the TJ Null OSCP-like list on Hack The Box.</p><p>My order was:</p><ul><li>Active Directory machines first</li><li>Easy → Medium → Hard difficulty</li><li>Then Windows machines</li><li>Then Linux machines</li></ul><p>I intentionally started with <strong>Hack The Box</strong> because I believe HTB machines are more technical and sometimes harder than other platforms.</p><p>My mindset was simple:</p><blockquote><strong><em>If I can solve HTB machines, everything else will feel easier.</em></strong></blockquote><p>This helped me build strong enumeration habits early.</p><h3>TryHackMe (Light Reinforcement)</h3><p>After <strong>HTB</strong>, I used <strong>TryHackMe </strong>for a small number of labs.<br>It wasn’t my main platform, but it helped reinforce concepts and fill gaps in certain areas.</p><h3>OffSec Proving Grounds</h3><p>Then I moved to <strong>Proving Grounds Practice and Play</strong>.</p><p>I finished all of them using the same strategy:</p><ul><li>Start simple</li><li>Enumerate deeply</li><li>Don’t rush exploitation</li><li>Build a repeatable methodology</li></ul><p>By this stage, I had spent <strong>three straight months locked in</strong>, solving machines daily.</p><h3>Buying the Exam Voucher</h3><p>I purchased the <strong>exam voucher only</strong>, without the training material, which gave me <strong>two attempts</strong>.</p><p>I felt confident.</p><p>I thought I was ready.</p><p>I wasn’t.</p><h3>OSCP Exam Structure</h3><p>For anyone curious about how the OSCP exam is structured, here’s a simplified breakdown.</p><h4>Duration</h4><ul><li><strong>23 hours and 45 minutes</strong> to complete the exam</li><li><strong>24 hours</strong> afterward to submit the final report</li></ul><h4>Machines Layout</h4><p>The OSCP exam environment typically contains:</p><p><strong>3 Stand-Alone Machines: 60 Points Total</strong></p><ul><li>20 points per machine</li><li>10 points for initial access</li><li>10 points for privilege escalation</li></ul><p><strong>1 Active Directory Set (3 Machines): 40 Points Total</strong></p><ul><li>Learners are provided with a username and password, simulating a breach scenario</li><li>10 points for machine #1</li><li>10 points for machine #2</li><li>20 points for machine #3</li></ul><h4>Passing Score</h4><p>You need <strong>70 out of 100 points</strong> to pass.</p><p>Some example ways to pass include:</p><ul><li>40 points from AD + 3 local flags (70 points)</li><li>40 points from AD + 2 local flags + 1 proof flag (70 points)</li><li>20 points from AD + 3 local flags + 2 proof flags (70 points)</li><li>10 points from AD + 3 fully completed stand-alone machines (70 points)</li></ul><p>The exam tests not only exploitation skills but also time management, reporting, and the ability to stay calm under pressure for nearly a full day.</p><h3>First Attempt: December 2025 (Failure)</h3><p>I failed my first attempt.</p><p>The reason wasn’t lack of knowledge; it was mindset, time management, and one technical issue that threw me off.</p><h3>The Active Directory Problem</h3><p>During the AD section, I spent a huge amount of time on the very first machine, the entry point into the domain.</p><p>Something just wasn’t working as expected.</p><p>I tried everything:</p><ul><li>Re-enumerating multiple times</li><li>Testing different attack paths</li><li>Double-checking tools and commands</li></ul><p>At some point, it starts affecting your confidence. You begin questioning yourself:</p><blockquote><strong><em>“Did I actually prepare well enough for this?”</em></strong></blockquote><p>After the exam, I realized what really happened.</p><p>The machine needed a revert, and the solution required just <strong>one simple step after resetting it</strong>.</p><p>That was it.</p><p>But during the exam, I burned a huge amount of time trying to “fix” the situation instead of stepping back sooner.</p><p>Because of that, I didn’t give myself enough time to properly work on the standalone machines.</p><h3>The Mindset Mistake</h3><p>I also went into the exam believing:</p><blockquote><strong><em>“This exam is famous for being hard, so nothing will be simple.”</em></strong></blockquote><p>So whenever I saw something that looked basic, like a potential SQL injection or straightforward misconfiguration, I assumed it <em>must</em> be more complex.</p><p>I skipped obvious paths.<br>I overthought things.<br>I chased complexity instead of checking fundamentals.</p><p>After reviewing my notes later, I realized:</p><p><strong><em>Most of what I needed was right in front of me.</em></strong></p><p>It was frustrating after three months of preparation, but it became the biggest lesson of my journey.</p><h3>The Comeback Phase (December → February)</h3><p>After two days of frustration, I reset and went back to work.</p><p>This time, my focus wasn’t just practice; it was rebuilding confidence.</p><h3>HTB Pro Labs</h3><p>I bought several <strong>Hack The Box Pro Labs</strong> like:</p><ul><li>Dante</li><li>Zephyr</li><li>and others</li></ul><p>These labs helped me massively, especially with sharpening my Active Directory attack flow.</p><p>I already trusted my standalone skills.<br>My goal now was simple:</p><p><strong>Secure AD points fast in the next attempt.</strong></p><h3>Second Attempt: February (The One That Worked)</h3><p>This time, I entered the exam with a completely different mindset:</p><p><strong>Start simple. Trust enumeration. Don’t assume complexity.</strong></p><h3>First 30 Minutes</h3><p>Within the first 30 minutes, I captured <strong>two AD flags</strong>.</p><p>That instantly boosted my confidence.</p><p>Later, I struggled with the Domain Controller, so instead of forcing it, I made a strategic decision to switch targets.</p><h3>The Key Difference This Time</h3><p>On the standalone machines, I did something I didn’t do before:</p><p>I tried the <strong>basic things first</strong>.</p><p>Good enumeration.<br>Checking common paths.<br>No overthinking.</p><p>And it worked.</p><p>I fully exploited all <strong>three standalone machines</strong>, and I still had time left.</p><p>I could have pushed harder for the DC, but I made a smart choice:</p><p>I stopped and focused on the report.</p><h3>Small Note on Tools &amp; Community Help</h3><p>One thing that made a real difference in my second attempt was discovering the <strong>Penelope</strong> tool.</p><p>During my first try, I didn’t know about it at all. Between attempts, I came across discussions about it on Reddit in the OSCP community, and I’m honestly thankful for that.</p><p>Learning how to use Penelope helped streamline parts of my workflow and made my interaction with shells and sessions much smoother during the exam.</p><p>So credit where it’s due: the OSCP Reddit community helped me more than they probably realize.</p><h3>The Report Phase (The Real Final Boss)</h3><p>I barely slept, maybe two hours.</p><p>I couldn’t stop thinking about the report.<br>It was the last step before the certification I had wanted for so long.</p><p>I finished the report the next night and submitted it.</p><p>Then came the waiting.</p><h3>The Email</h3><p>The next evening, my email buzzed.</p><p>“Congratulations.”</p><p>I passed with <strong>80/100</strong>.<br>The passing score was <strong>70</strong>.</p><p>It was honestly one of the best days of my life.</p><h3>Side Note: My Secret Weapon 🎧</h3><p>I played music during the entire exam.</p><p>I created a Spotify playlist with my favorite songs and kept it running the whole time.</p><p>It helped me stay calm, focused, and in rhythm while solving.</p><p>That playlist was my personal “cheat code.”</p><h3>My Advice for Future OSCP Candidates</h3><p>You’ve probably heard these before, but trust me, they are real:</p><ul><li>Don’t panic</li><li>Don’t assume things are complex</li><li>Start with the basics</li><li>Enumerate deeply</li><li>Trust your process</li><li>Manage your time carefully</li></ul><p>If you stay consistent and calm, you <strong>can</strong> pass.</p><h3>Final Thoughts</h3><p><strong>OSCP </strong>is tough. The pressure is real.<br>But what you learn from it is huge.</p><p>I recommend it to anyone serious about becoming a penetration tester.</p><p>If you need advice, feel free to reach out to me on <strong>LinkedIn</strong>:<br>👉 <a href="https://www.linkedin.com/in/omar-tamer-1a986b2a7/">Linkedin Profile</a></p><p>Good luck to everyone preparing; you’ve got this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20304eef6dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Built OTSec: Offensive Security in OT/IoT Environments]]></title>
            <link>https://medium.com/@OmarTamer0/why-i-built-otsec-offensive-security-in-ot-iot-environments-afeeb28c34bb?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/afeeb28c34bb</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[iot-security]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[operational-technology]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 16:25:48 GMT</pubDate>
            <atom:updated>2025-08-29T16:25:48.489Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Omar Tamer, </em>Penetration Tester | EC-Council LPT Master | CPENT | CEH Master | eJPT | PCEP | Top Ranked on Hack The Box, TryHackMe &amp; CyberTalents</p><h3>What Are OT and IoT, and Why Do They Matter?</h3><p>When most people hear <em>penetration testing</em>, they think of <strong>web apps, APIs, cloud platforms, or corporate networks</strong>. These are important, but they aren’t the only systems that matter.</p><blockquote><strong>Operational Technology (OT):</strong><br> OT refers to the hardware and software systems that control <strong>physical processes</strong>. Think power plants, water facilities, oil pipelines, and factories running on PLCs (Programmable Logic Controllers) and SCADA systems.<br> ⚡ If these systems fail, the result isn’t just downtime; it could mean blackouts, halted production, or even risks to human safety.</blockquote><blockquote><strong>Internet of Things (IoT):</strong><br> IoT covers billions of <strong>connected smart devices</strong>, from home cameras and medical devices to enterprise HVAC systems, access controls, and industrial sensors.<br> 📡 These devices are everywhere, and most are deployed quickly with little to no rigorous security testing.</blockquote><p>👉 In short:</p><ul><li><strong>OT keeps critical infrastructure alive.</strong></li><li><strong>IoT connects our modern world.</strong></li></ul><p>Both are essential, and both are potential targets if left unprotected.</p><h3>🌍 The Gap in OT/IoT Security</h3><p>Despite their importance, OT and IoT security lag behind traditional IT security in several ways:</p><blockquote><strong>Critical Infrastructure Exposure</strong> → OT often relies on <strong>legacy protocols</strong> (Modbus, DNP3, and BACnet) designed for reliability, not security. They rarely include encryption or authentication.</blockquote><blockquote><strong>IoT Everywhere, Insecure</strong> → Billions of IoT devices are rushed to market, often shipping with <strong>default passwords, weak firmware, or no patch lifecycle</strong>.</blockquote><blockquote><strong>Fragmented Tooling</strong> → A few OT/ICS tools exist, but they’re often outdated, protocol-specific, or difficult for new researchers to use.</blockquote><blockquote><strong>Defender Privilege </strong>→ Most OT research focuses on <strong>defensive monitoring</strong> (detecting attacks) instead of <strong>offensive simulation</strong> (actually testing resilience like a red team would).</blockquote><blockquote><strong>Skill Shortage</strong> → Thousands of juniors grind web hacking and AD exploitation, but very few touch OT/IoT, leaving a gap in both talent and tooling.</blockquote><p>⚠️ This creates a dangerous imbalance: attackers experimenting with OT/IoT vectors often face <strong>less resistance</strong> than in mature IT networks, while security testers lack the right tools to simulate realistic attacks.</p><p>That’s the <strong>gap I set out to address</strong>.</p><h3>🚀 Introducing OTSec</h3><p>I built <strong>OTSec (Offensive OT/IoT Security Toolkit)</strong> as a lightweight, modular Python framework to help <strong>red teamers, penetration testers, and security researchers</strong> explore OT and IoT environments.</p><h3>🔑 Key Features</h3><ul><li>✅ OT/IoT device discovery</li><li>✅ Modbus protocol manipulation (read &amp; inject)</li><li>✅ Banner analysis with CVE matching</li><li>✅ Vulnerability detection via YAML-based database</li><li>✅ Interactive command shell for chaining modules</li><li>✅ Clean, extensible CLI design</li></ul><p>📦 <strong>Install via PyPI:</strong></p><pre>pip install otsec <br><br>otsec shell</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vx9cALNMUzhYinzYm2IxUA.png" /><figcaption><a href="https://github.com/Omar-tamerr/OTSec">OTSec Tool</a></figcaption></figure><h3>🎯 My Goals with OTSec</h3><p>OTSec is not meant to compete with massive frameworks; instead, it’s designed to be:</p><ol><li><strong>Accessible</strong> → Easy to install, easy to extend, and approachable for both students and professionals.</li><li><strong>Practical</strong> → Focused on real-world red team tasks like Modbus traffic manipulation and quick vulnerability checks.</li><li><strong>Community-driven</strong> → With a YAML-based database, anyone can add new CVEs or modules, growing the toolkit together.</li></ol><p>In short, I wanted to <strong>bridge the gap between CTF-style learning and real-world OT/IoT red teaming</strong>.</p><h3>👥 Who Can Benefit From OTSec?</h3><p>When I built OTSec, I wanted it to be useful across different parts of the security community, not just for niche researchers. Here’s who can gain value from it:</p><blockquote><strong>🔴 Red Teamers</strong> → Simulate attacks against OT/IoT environments during assessments and demonstrate real-world impact.</blockquote><blockquote><strong>🔬 Security Researchers</strong> → Analyze and experiment with OT/IoT protocols, discover new attack vectors, and contribute modules to the database.</blockquote><blockquote><strong>🎓 Students &amp; CTF Players</strong> → Move beyond web hacking or AD exploitation and practice offensive techniques in OT/IoT, a domain very few juniors touch.</blockquote><blockquote><strong>🏭 ICS/SCADA Testers</strong> → Quickly scan and test Modbus/OT devices in lab environments for misconfigurations or known vulnerabilities.</blockquote><p>👉 In short: whether you’re learning, testing, or simulating, OTSec is designed to give you a starting point in the offensive OT/IoT space.</p><h3>📖 Lessons Learned</h3><p>Building <strong>OTSec </strong>taught me a lot:</p><ul><li>OT/IoT protocols behave very differently from typical IT protocols.</li><li>Red teams <strong>must start preparing for OT environments now;</strong> adversaries already are.</li><li>Tool-building is more than coding; it’s how you <strong>turn knowledge into something tangible that others can use</strong>.</li></ul><h3>🔮 What’s Next</h3><p><strong>OTSec </strong>is only the beginning. I plan to:</p><blockquote>Add support for additional protocols (e.g., DNP3, MQTT).</blockquote><blockquote>Expand the YAML vulnerability database.</blockquote><blockquote>Improve Windows compatibility (readline/Npcap support).</blockquote><blockquote>Invite the community to contribute and shape the toolkit.</blockquote><h3>🙌 Final Thoughts</h3><p>At 21, I know I’m early in my journey, but I believe <strong>age shouldn’t stop anyone from building tools that matter</strong>.</p><p>OTSec is my contribution to the security community and a reminder that the future of offensive security isn’t just about <strong>web apps or Active Directory;</strong> it’s about <strong>OT and IoT too</strong>.</p><p>🔗 <strong>GitHub</strong>: <a href="https://github.com/Omar-tamerr/OTSec">OTSec</a><br> 📦 <strong>PyPI</strong>: <a href="https://pypi.org/project/otsec/">otsec</a><br>💼 <strong>LinkedIn</strong>: <a href="https://www.linkedin.com/in/omar-tamer-1a986b2a7/">Omar Tamer</a></p><p>💡 I’d love your feedback, ideas, and contributions. Let’s make OT/IoT red teaming stronger, together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afeeb28c34bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Became a CEH Master at 21; The Beginning of My Offensive Security Path]]></title>
            <link>https://medium.com/@OmarTamer0/how-i-became-a-ceh-master-at-21-the-beginning-of-my-offensive-security-path-1fd7c7199b62?source=rss-a5b84c4de62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fd7c7199b62</guid>
            <category><![CDATA[ceh-master]]></category>
            <category><![CDATA[ceh-certification]]></category>
            <category><![CDATA[ceh-practical]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[ec-council]]></category>
            <dc:creator><![CDATA[Omar Tamer]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 15:32:12 GMT</pubDate>
            <atom:updated>2025-08-19T15:32:12.956Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How I Became a CEH Master at 21: The Beginning of My Offensive Security Path</strong></h3><p>Cybersecurity has always been more than just a career choice for me; it’s a passion, a challenge, and a field where curiosity pays off every single day. At just <strong>21 years old</strong>, I’ve been fortunate to achieve milestones that shaped me into the professional I am today.</p><p>I’ve ranked in the <strong>Top 1% worldwide on TryHackMe</strong>, completing <strong>894 rooms</strong> with a global rank of <strong>#158. </strong>earned a <strong>Top 50 spot in HackTheBox Egypt and</strong> reached <strong>Top 5 in CyberTalents Egypt</strong>. Along the way, I’ve competed in CTFs, worked on red team engagements, and earned multiple certifications, including <strong>EC-Council’s CEH Master, CPENT, and LPT Master,</strong> as well as the <strong>eJPT from INE Security</strong> and <strong>PCEP from the Python Institute</strong>.</p><p>But if I look back, there was one certification that truly started it all: <strong>CEH (Certified Ethical Hacker)</strong>.</p><h3>What is CEH?</h3><p>The <strong>Certified Ethical Hacker (CEH)</strong>, offered by <strong>EC-Council</strong>, is one of the most recognized entry-level certifications in cybersecurity. It introduces professionals to the <strong>mindset of a hacker</strong>, but with the goal of defending against attacks.</p><p>The program is structured into <strong>20 comprehensive modules</strong>, each focusing on a different area of ethical hacking. Together, they cover the entire lifecycle of an attack and defense strategy, giving learners both theory and hands-on skills.</p><p>Some of the key chapters include</p><ul><li><strong>Introduction to Ethical Hacking:</strong> building the foundation and understanding the attacker’s mindset</li><li><strong>Footprinting and reconnaissance:</strong> gathering intelligence on targets</li><li><strong>Scanning Networks:</strong> identifying live hosts, open ports, and services</li><li><strong>Enumeration:</strong> digging deeper into network services for useful details</li><li><strong>Vulnerability Analysis:</strong> identifying weaknesses in systems</li><li><strong>System Hacking:</strong> techniques for gaining and escalating access</li><li><strong>Malware Threats:</strong> understanding viruses, trojans, and backdoors</li><li><strong>Sniffing &amp; Social Engineering:</strong> capturing traffic and exploiting human behavior</li><li><strong>Denial-of-Service &amp; Session Hijacking:</strong> disrupting services and exploiting sessions</li><li><strong>Web Applications, SQL Injection, and Wireless Attacks:</strong> exploiting common real-world targets</li><li><strong>Evading IDS, Firewalls, and Honeypots</strong>; bypassing defensive technologies</li><li><strong>Cloud Computing, IoT, and Cryptography:</strong> addressing modern attack surfaces</li></ul><p>Each module comes with both theory and practical labs, which make the concepts more real and easier to apply.</p><p>For anyone starting out in cybersecurity, CEH’s <strong>20 chapters</strong> make it an excellent foundation. It doesn’t just list tools; it gives you structured knowledge across multiple areas, helping you understand how attacks work so you can better defend against them.</p><h3>The Two Sides of CEH</h3><p>When people talk about the <strong>Certified Ethical Hacker</strong>, they usually mean the theoretical exam, the multiple-choice version that tests your knowledge across all domains of ethical hacking. But CEH actually has <strong>two parts,</strong> and both play an important role.</p><h3>1️⃣ The CEH (Theoretical Exam)</h3><p>This is the traditional version: a <strong>knowledge-based, multiple-choice exam</strong>. It’s designed to test your understanding of ethical hacking concepts, tools, and security practices across all domains.</p><p>From my experience, if you want to pass this part with a strong score, the key is preparation and discipline:</p><ul><li><strong>Solve all the chapter questions</strong> in the official training material. Don’t skip them, because they sharpen your understanding of each domain.</li><li>Focus on the <strong>two official test exams</strong> EC-Council provides. They are very close to the real thing and give you the confidence you need.</li><li><strong>Stay calm</strong> and focus on understanding <em>why</em> an answer is correct, not just memorizing it.</li></ul><p>For me, passing CEH at a young age wasn’t just about checking off a box; it was about proving to myself that I could commit to the process and master the foundations of ethical hacking.</p><h3>2️⃣ The CEH (Practical Exam)</h3><p>Then there’s the <strong>Certified Ethical Hacker (Practical),</strong> a completely different challenge. Instead of testing your memory, it tests your <strong>ability to apply your knowledge</strong> in a live environment.</p><p>This is a <strong>six-hour exam</strong> with <strong>20 practical challenges</strong>, delivered through EC-Council’s browser-based iLabs. You’ll be given access to Parrot OS and Windows machines and expected to perform penetration testing activities in a corporate-style network.</p><p><strong>Key Details of CEH Practical:</strong></p><ul><li><strong>Duration:</strong> 6 hours (with a short break)</li><li><strong>Challenges:</strong> 20; realistic and hands-on</li><li><strong>Passing Score:</strong> 70% (14 out of 20)</li><li><strong>Environment:</strong> iLabs; no need to run your own VMs</li><li><strong>Proctoring:</strong> Fully monitored with webcam, mic, and screen sharing</li></ul><p>It’s also <strong>open book,</strong> which sounds easy but actually tests how resourceful you are under time pressure. Google and notes are your friends, but at the end of the day, it’s your calmness and problem-solving process that matter.</p><p>From my experience, I strongly recommend anyone planning for CEH Practical to buy the <strong>EC-Council official labs</strong>. They helped me a lot because they mirror the actual style of the exam and let you practice in the same environment.</p><p>And here’s my <strong>golden tip:</strong> learn how to <strong>transfer files between systems</strong>. It might sound like a small thing, but in real-world penetration testing (and in practical exams), it can make or break your workflow.</p><h3>Why CEH Was the Right Start for Me</h3><p>Looking back, CEH was the perfect <strong>launchpad</strong> into my career because it:</p><ul><li>Gave me a globally recognized foundation in ethical hacking.</li><li>Helped me understand both the attacker and defender perspectives.</li><li>Taught me that cybersecurity isn’t about memorizing tools; it’s about solving problems creatively.</li></ul><p>Most importantly, CEH gave me the confidence to aim higher. Instead of stopping at one milestone, I used it as the <strong>first step toward CPENT and eventually LPT Master</strong>.</p><h3>Final Thoughts</h3><p>The CEH isn’t the hardest certification in cybersecurity, but it’s one of the most important <strong>first steps</strong>. If you treat it as more than “just an exam,” if you use it to build discipline, technical foundations, and professional habits, it will open the door to everything that comes next.</p><p>And here’s something many people don’t realize: once you pass <strong>both the CEH (theoretical)</strong> and the <strong>CEH Practical</strong>, you officially earn the title <strong>CEH Master</strong>. That’s why I proudly call this my <strong>CEH Master Journey</strong>; it represents mastering both the knowledge and the hands-on application.</p><p>For me, CEH was never the finish line. It was the foundation that shaped the rest of my journey. At just <strong>21 years old</strong>, I can proudly look back and say, If I could achieve CEH Master this early, you can too; it’s all about focus, consistency, and the willingness to learn.</p><p>At the end of this write-up, I’m sharing photos of my three certifications; <strong>CEH</strong>, <strong>CEH Practical</strong>, and <strong>CEH Master</strong>; not just as proof but as a reminder that persistence and discipline can turn goals into achievements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsdnTq1umMZwxi1GwDnfAQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-RrFNVgMbpm9mBfDJRTDQA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEmBui7UWpgJCzLAKP5qoA.jpeg" /></figure><p>If you’d like me to share my journey with <strong>CPENT</strong> and <strong>LPT Master</strong>, let me know in the comments; I’d be happy to write about it</p><p>📌 Connect with me:</p><ul><li><a href="https://www.linkedin.com/in/omar-tamer-1a986b2a7/">LinkedIn</a></li><li><a href="https://github.com/Omar-tamerr">GitHub</a></li><li><a href="https://omar-tamerr.github.io/">Portfolio Website</a></li><li><a href="https://tryhackme.com/p/OmarTamer0">Tryhackme</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fd7c7199b62" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>