<?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 Tunahan TEKEOGLU on Medium]]></title>
        <description><![CDATA[Stories by Tunahan TEKEOGLU on Medium]]></description>
        <link>https://medium.com/@tun4hunt?source=rss-ed536e0ac16a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dyMx7TfxeZcKHN3fXJewBQ.jpeg</url>
            <title>Stories by Tunahan TEKEOGLU on Medium</title>
            <link>https://medium.com/@tun4hunt?source=rss-ed536e0ac16a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:03:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tun4hunt/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[Active Directory Is a Trust System. Do You Understand Who Controls It?]]></title>
            <link>https://tun4hunt.medium.com/active-directory-is-a-trust-system-do-you-understand-who-controls-it-89c0a355a046?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/89c0a355a046</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[privilege-escalation]]></category>
            <category><![CDATA[active-directory]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 19:16:40 GMT</pubDate>
            <atom:updated>2026-11-12T19:16:40.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvbIcxNgPM7iuWpyw1nuKQ.png" /></figure><p>Imagine a help-desk account that can change the membership of a group used to grant administrative access to an application server.</p><p>The account isn’t a member of that group. It isn’t a Domain Admin. Administering that server isn’t supposed to be part of the help desk’s job.</p><p>But it can decide who gets added.</p><p>Before I care which tool can abuse that, I want to understand why the account has that permission, and which systems will act on the change.</p><p>From the directory’s point of view, adding a member may be a perfectly valid operation. The problem is that an identity has been allowed to make a decision outside its intended responsibilities.</p><p>This is the part of Active Directory I want people to understand before they start collecting attack names.</p><h3>Start with an ordinary access decision</h3><p>I’m talking about Active Directory Domain Services here, and using “trust” in a broader architectural sense than a configured domain or forest trust. I mean the authorities, identities and permissions that systems rely on when they accept a request.</p><p>Take something boring: a user opening a file on a Windows file server.</p><p>In a Kerberos-authenticated connection, the client obtains a service ticket from the domain controller’s Key Distribution Center. The service validates that ticket using its own key. The client doesn’t need to know the service account’s password to present a ticket the service can accept. <a href="https://learn.microsoft.com/en-us/windows/win32/secauthn/session-tickets">Microsoft’s explanation of session tickets</a> describes this exchange.</p><p>That establishes part of the picture. It doesn’t give the user permission to read every file.</p><p>Windows represents the authenticated identity and its group memberships in a security context. For resource access, the user’s access token is checked against the relevant permissions. A successful authentication can still end in “Access denied.”</p><p><a href="https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-principals">Authentication and access control are different decisions.</a></p><p>That distinction matters when you’re testing an environment. Did you establish an identity? Did the target accept it? Did that identity actually have the permission needed for the operation?</p><p>Those are separate questions. A tool reporting success at one stage doesn’t answer all three.</p><h3>The account does not need to hold the access today</h3><p>Now go back to the help-desk example.</p><p>There are two relationships to examine. The server grants administrative rights to members of a group. A different permission allows the help-desk account to modify that group’s membership.</p><p>The second relationship can change the first.</p><p>Directory objects have their own access controls, including permissions to modify individual properties. In this example, the relevant control is the effective ability to change the group’s member attribute. You don&#39;t discover that simply by checking which groups the help-desk account belongs to. <a href="https://learn.microsoft.com/en-us/windows/win32/ad/how-access-control-works-in-active-directory-domain-services">Microsoft documents these object and property permissions here.</a></p><p>After a membership change, the affected account needs an appropriate security context reflecting its new membership. Existing tokens don’t instantly rewrite themselves because someone edited a group. The resulting access also depends on what permissions that group actually has.</p><p>The <a href="https://bloodhound.specterops.io/resources/edges/add-member">AddMember relationship</a> is a useful example of how BloodHound models this control.</p><p>Delegating group management isn’t inherently a vulnerability. Someone has to administer access. The issue in our example is the mismatch between the help desk’s intended role and the authority it has been given.</p><p>This is why “the account isn’t a Domain Admin” is an incomplete security assessment.</p><p>I want to ask two questions:</p><p><strong>What can this identity access, and what can it change about who gets access next?</strong></p><p>The first tells me about its current position. The second tells me how much that position can change.</p><p>It also changes how I read a finding. “User can modify group membership” is a description of a permission. “A help-desk identity can grant administrative rights on a server it isn’t responsible for” explains why that permission matters.</p><h3>Kerberoasting makes more sense after Kerberos</h3><p>Kerberoasting is a good example of what gets lost when the attack is taught before the normal behaviour.</p><p>A user requests a service ticket. Part of that ticket is encrypted with a key belonging to the account running the service. For a password-based service account, that key is derived from its password.</p><p>The client is supposed to be able to obtain the ticket without knowing that password. That is normal Kerberos behaviour.</p><p>The attack uses the encrypted material to test password guesses offline. Whether those guesses succeed depends on factors including the password’s strength and the encryption type. Getting the material is not the same as recovering the password.</p><p><a href="https://www.microsoft.com/en-us/security/blog/2024/10/11/microsofts-guidance-to-help-mitigate-kerberoasting/">Microsoft’s Kerberoasting guidance</a> makes that distinction important to the mitigation as well: AES doesn’t rescue a weak password.</p><p>If a lab deliberately gives a service account a predictable password, cracking it demonstrates the attack under that condition. It doesn’t establish that every account with a Service Principal Name is one command away from compromise.</p><p>I’d want the learner to repeat the exercise with a strong, randomly generated password and explain what changed. The ticket request may still work. The practical route to recovering the credential may not.</p><p>Where supported, a group Managed Service Account helps by using a long, randomly generated password managed by Windows. It still needs appropriate permissions. Better credential management doesn’t make unnecessary administrative access harmless. <a href="https://learn.microsoft.com/en-us/entra/architecture/service-accounts-group-managed">Microsoft’s gMSA guidance</a> explicitly treats those as separate concerns.</p><p>This is also why “AD attacks are just misconfigurations” is too convenient an explanation. Overbroad delegation and a guessable service account password are different problems. A software vulnerability is different again. The fix has to address the mechanism involved.</p><h3>Read the relationship behind the BloodHound edge</h3><p>BloodHound is useful because a relationship that is difficult to spot across directory objects becomes much easier to examine in a graph.</p><p>But an edge label is still something you need to understand.</p><p>An AddMember relationship isn’t the same thing as existing membership. Permission to reset an account’s password isn’t the same thing as knowing its current password. And not every relationship shown in the graph represents a directly abusable step.</p><p>BloodHound distinguishes <a href="https://bloodhound.specterops.io/resources/edges/traversable-edges">traversable and non-traversable edges</a>, including relationships that become meaningful when combined.</p><p>When I look at a potential path, I want to be able to describe each step in ordinary language:</p><p>Which identity do I need to control? What does that identity have permission to do? What changes if I exercise that permission? What does the next step rely on?</p><p>Then I want to check whether those conditions still hold.</p><p>That’s how I would use the graph in an assessment. Collection data and a plausible path give me something specific to investigate. They don’t justify writing that I compromised a system I never reached.</p><p>You can report a dangerous configuration without exploiting it. Just be clear about what the evidence establishes.</p><h3>A useful AD lab should include the legitimate use case</h3><p>If I were teaching the group-management example, I wouldn’t start by telling the student which attack to run.</p><p>I’d start with a small environment and an explicit requirement: the help desk should manage membership of an ordinary application-access group, but shouldn’t be able to grant server administration.</p><p>First, show that legitimate access works. Show an action that should be denied, too.</p><p>Then introduce an incorrectly scoped delegation and ask the learner to identify what it allows. Before changing anything, have them predict which access decision could be affected and why.</p><p>Only then test the prediction in the lab.</p><p>The important part comes afterwards. Correct the delegation, verify that the unintended change is denied, and confirm that the help desk can still perform its legitimate work.</p><p>That last check matters. Removing every delegated permission may make the attack fail, but it can also make the environment unusable. It doesn’t prove that you understood the boundary you were supposed to enforce.</p><p>I’d also change the names and layout in a second version of the exercise. Keep the underlying relationship, but remove the familiar account names and the obvious target group.</p><p>Can the learner still find it?</p><p>That tells me more than whether they remember the command from the first version.</p><h3>Remediation should follow the same reasoning</h3><p>Return to our original help-desk account one last time.</p><p>If it has been compromised, resetting its credentials may be necessary. But a password reset doesn’t remove its permission to manage the privileged group.</p><p>Removing an unauthorised member addresses that membership. It doesn’t stop an identity with the same excessive delegation from adding another one.</p><p>For this scenario, remediation means reviewing who can manage the group and whether that authority matches the group’s role. Then it means checking that the intended access still works and the unintended control no longer does.</p><p>The offensive explanation and the defensive explanation should agree.</p><p>If I can explain exactly why an operation was accepted, I should be able to identify the permission or prerequisite that made it possible. If I recommend changing that permission, I should be able to explain what legitimate activity the change might affect.</p><p>Otherwise, I’ve described a technique without fully understanding the environment it operates in.</p><h3>What I want an AD learner to take away</h3><p>Knowing the attack names is useful. So is knowing the tools. I don’t expect someone to manually reproduce every protocol exchange before they can do meaningful work.</p><p>I do expect them to explain why the environment accepted the operation they performed.</p><p>Which identity was involved? Who was authorised to change the relevant object? Which service relied on the result? Where did the observed behaviour exceed the intended access?</p><p>Those questions connect an attack to the system underneath it. They also remain useful when the tool changes, the lab looks different, or the first attempt fails.</p><p>That’s what I mean when I say Active Directory is a trust system.</p><p>The question I want to hear after “it worked” is: <strong>“Why was this identity allowed to make that happen?”</strong></p><p><em>If you’re working through AD fundamentals, you can also find free AD learning material on </em><a href="https://hacker.directory/"><em>hacker.directory</em></a><em>, my community project. Try applying these questions to each technique you study.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89c0a355a046" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is cybersecurity training still worth paying for as we head into 2027?]]></title>
            <link>https://infosecwriteups.com/is-cybersecurity-training-still-worth-paying-for-as-we-head-into-2027-07739382dcfb?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/07739382dcfb</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 14:03:06 GMT</pubDate>
            <atom:updated>2026-11-05T14:03:06.102Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HYg4vwY0ovQiXA12SS-1CQ.png" /><figcaption>Is cybersecurity training still worth paying for as we head into 2027?</figcaption></figure><p>Imagine you’ve just finished a lab. You followed the video, sent the requests and got the expected result. You read the walkthrough, and it all makes sense.</p><p>Then you open another application. This time, the lab title doesn’t tell you which vulnerability to look for. Nobody points out the parameter you should change.</p><p>Do you know where to start?</p><p>When I pay for cybersecurity training, I’m interested in what I can do in that second application. That’s also why my answer to the question in the title is still yes.</p><p><strong>I’ll pay for training that helps me move from following a walkthrough to planning and running my own tests.</strong></p><p>In my previous <a href="https://medium.com/@tun4hunt">course and exam reviews</a>, I’ve looked at the depth of the material, the labs and what the assessments actually measure. As we head into 2027, we also need to consider the free resources and AI tools available to someone trying to learn.</p><h3>A paid course needs to justify its price</h3><p>We don’t need a new course for every gap in our knowledge.</p><p>You might need to understand one particular topic. You read some good documentation, examine an example and try it in your own environment. Sometimes, that’s enough.</p><p>Free resources can also go well beyond the basics. <a href="https://portswigger.net/web-security">PortSwigger Web Security Academy</a>, for example, provides learning material alongside free interactive labs. A resource’s price doesn’t tell us how much depth it has.</p><p>AI can be useful for examining a piece of code, discussing a mechanism through different examples or looking for gaps in your own explanation.</p><p>With these options available, I want to understand why a particular course would help me. A long syllabus or a large number of video hours doesn’t answer that on its own.</p><p>A clear explanation, a carefully chosen sequence of examples and a lab environment that would take time to build myself all have value. I also want to know what they help me learn to do, and how the course helps me when I get stuck.</p><h3>What happens when you remove the lab title?</h3><p>Consider a simple authorization example.</p><p>Alice and Bob each have a private document that only its owner should be able to read. While logged in as Alice, you change the document ID in a request and gain access to Bob’s document. That’s an example you might use when teaching <a href="https://portswigger.net/web-security/access-control/idor">IDOR</a>.</p><p>For an introductory lesson, I think it’s useful to walk through this step by step. Explain what the request does, which account is being used and which access should be denied.</p><p>In the next application, though, there are questions I’d want the learner to answer themselves:</p><ul><li>Which records should this user be able to access?</li><li>What did I change during the test, and what did I keep the same?</li><li>Does the response actually contain another user’s private data?</li><li>Does my evidence support the authorization flaw I’m claiming to have found?</li></ul><p><strong>A </strong><strong>200 OK response alone isn’t enough.</strong> We need to examine the response body before claiming that we’ve accessed Bob’s private document.</p><p>A title like “IDOR Lab” is useful when you’re first learning the concept. As the course progresses, I also want exercises where I have to decide what to investigate.</p><p>A different application might have different roles, ownership rules, sharing features or request structures. I should be able to work out the expected behavior in that application and build my test around it.</p><h3>Knowing when to reduce the guidance</h3><p>This is where I think a lot of the work in course design happens.</p><p>In the first example, the instructor explains how each decision is made. In the next, the learner chooses some of the steps. In another scenario, the conditions change, and the learner has to work out which parts of the previous approach still apply.</p><p>I want that progression to be deliberate. Dropping a beginner into a difficult environment without explanation doesn’t, by itself, teach them how to research a problem. Showing every step in advance leaves little room for them to make their own decisions.</p><p>I have the same expectation for Active Directory training. If a command doesn’t produce the result I expected, I should be able to investigate which identity I’m using, which service I’m interacting with and what my current permissions allow. The course should help me connect those pieces.</p><p>Difficulty also needs a purpose.</p><p>Testing an incorrect assumption, getting an unexpected result and investigating why can be valuable. If I’m spending hours dealing with incomplete instructions or a broken service, I’d want to understand what that is supposed to teach me. If troubleshooting is the learning objective, it should be designed deliberately.</p><p>The help available when I get stuck matters, too. Sometimes a small hint is enough. Sometimes I need a prerequisite explained again. When I read a walkthrough, I want to understand why a particular command was the next thing to try.</p><p>If Kerberos doesn’t click after the first diagram, that’s fine. :) The course should help me work out what I’m missing and keep going.</p><h3>Working with AI also means checking its answers</h3><p>I think working with AI belongs in the learning process. A course should consider how learners can use these tools thoughtfully.</p><p>Imagine asking AI for a test idea. The suggestion might assume that a particular role or sharing feature exists in the application. If that condition isn’t present in your environment, a plausible explanation won’t make the test relevant.</p><p>The same applies to a finding written with AI assistance. Does the result you obtained support the impact described in the report? Did you demonstrate access to another user’s data, or did you simply receive a different response?</p><p>I’d find it useful for a course to ask me to explain the result in my own words and check my evidence. Changing one condition and asking me to predict how the outcome should change would also be a useful exercise.</p><p>Working independently still involves consulting documentation, using tools and learning from other people’s experience. We need to be able to adapt that help to our own problem and check the result.</p><h3>What I look for before paying</h3><p>I want to see a sample lesson and, ideally, try an exercise. These are the questions I’d ask:</p><ul><li><strong>Are the level and objectives clear?</strong> What should I know before starting, and what should I be able to do by the end?</li><li><strong>Does the explanation help me during practice?</strong> Does understanding the mechanism help me explain the decisions I make in the lab?</li><li><strong>Is there room to work independently?</strong> After the guided example, can I attempt a scenario without the solution in front of me?</li><li><strong>Can I learn from my mistakes?</strong> Does the feedback help me understand what I got wrong and how to approach another attempt?</li><li><strong>Does the assessment measure the skill being taught?</strong> Am I expected to carry out the task, explain the result and provide evidence where needed?</li></ul><p>I don’t expect an introductory course to produce advanced expertise. I do expect it to answer those questions consistently at the level it promises.</p><p>I look at certifications in the same way. A certification can be meaningful when it represents skills demonstrated within a defined scope. The level, assessment conditions and method should be clear.</p><p>If a course provides that experience, fits what I need and helps me notice things I would miss while studying alone, I still consider it worth investing time and money in.</p><h3>If you’d like to start with free material</h3><p>If you want to get started or strengthen your fundamentals, you can take a look at <a href="https://hacker.directory/">hacker.directory</a>, my community project. The web and Active Directory material is free.</p><p>The web content explores the journey of an HTTP request and how browsers behave. The AD content looks at identity, permissions and trust relationships, using visual explanations and short practical exercises. For me, “Understand what you hack” starts with understanding how a system normally works and questioning the assumptions it relies on.</p><p><strong>As we head into 2027, good cybersecurity training is still worth paying for.</strong></p><p>I want to see that value the next time I’m working with an unfamiliar system. If I have a clearer idea of what to investigate, why I’m investigating it and how to verify what I find, that course has been worth paying for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07739382dcfb" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/is-cybersecurity-training-still-worth-paying-for-as-we-head-into-2027-07739382dcfb">Is cybersecurity training still worth paying for as we head into 2027?</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[Certified Web Application Exploiter (CWAE) Exam Review 2026]]></title>
            <link>https://infosecwriteups.com/certified-web-application-exploiter-cwae-exam-review-2026-3bd286b6d7cb?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bd286b6d7cb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 11:14:51 GMT</pubDate>
            <atom:updated>2026-08-18T11:14:51.130Z</atom:updated>
            <content:encoded><![CDATA[<h3>My experience with CyberExam’s practical white-box web security certification, from source-code auditing to AI-graded reporting.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SjI8m4ooKU-ufp8UhAelCw.png" /><figcaption>My CWAE Certificate Final Score : 99/101 (%98)</figcaption></figure><h3>Introduction</h3><p>Hello everyone! I am Tunahan Tekeoğlu.</p><p>After writing reviews about certifications such as OSCP, OSCC, CAPenX, C-AI/MLPen and ASCP, I recently had the opportunity to take a look at another practical cybersecurity certification: <strong>Certified Web Application Exploiter (CWAE)</strong> by CyberExam.</p><p>And as usual, before I forget my experiences, I decided to write a review about it. :)</p><p>CWAE was interesting to me for one simple reason.</p><p>Most practical web security exams place an application in front of you and ask you to attack it from the outside. You enumerate the application, manipulate requests, understand its behaviour and eventually try to find a way in.</p><p>CWAE changes the perspective a little.</p><p>You have the application <strong>and its source code</strong>.</p><p>So the question is no longer only:</p><blockquote><em>“Can you exploit this application?”</em></blockquote><p>There is another question behind it:</p><blockquote><em>“Can you understand why this application is vulnerable in the first place?”</em></blockquote><p>For someone working in application security, I think that difference is important.</p><p>The exam mixes source-code review, practical exploitation, different technology stacks and technical reporting into a relatively compact experience.</p><p>Was everything perfect?</p><p>No.</p><p>I had some issues with the lab and VNC experience, and there were moments where the platform itself created more confusion than the technical challenge.</p><p>But I also saw several ideas that I genuinely liked, especially the reporting side.</p><p>I completed CWAE with a final score of <strong>99/101–98%</strong>.</p><p>So let’s talk about what the certification actually offers, what I liked, what I think still needs improvement and, most importantly, who should consider taking it.</p><p>Are you ready?</p><p>Let’s get started!</p><h3>A Small Disclosure Before We Continue</h3><p>CyberExam provided me with complimentary reviewer access to CWAE.</p><p>Since my purpose was not only to complete the certification but also to evaluate the technical structure and candidate experience, I was also given access to the intended solution material.</p><p>For that reason, this was <strong>not a completely blind attempt</strong>, and it would not be fair for me to present my completion time or score as if I entered the exam without knowing anything about the expected technical paths.</p><p>I still reviewed the code, reproduced the vulnerabilities against the live applications, completed the practical tasks and went through the reporting process.</p><p>CyberExam did not pay me for this review and did not ask to approve what I would write.</p><p>I think being clear about this is important.</p><p>If you have read my previous certification reviews, you probably already know that I prefer explaining what I actually experienced rather than writing another “everything was amazing” article.</p><h3>What Is CWAE?</h3><p>CWAE is essentially a <strong>practical white-box web application security exam</strong>.</p><p>Instead of staying within a single technology, the assessment moves between applications written in:</p><ul><li><strong>PHP</strong></li><li><strong>Node.js</strong></li><li><strong>Python</strong></li><li><strong>Java</strong></li></ul><p>You are provided with source code and access to live applications through a browser-based attacker environment.</p><p>The exam then expects you to understand how the application works, locate potentially dangerous data flows and prove whether those weaknesses are actually exploitable.</p><p>This part is important.</p><p>Seeing something like exec(), unserialize() or a dangerous deserialization function inside source code does not automatically make it a valid finding.</p><p>You still need to understand questions such as:</p><p>Where does the input come from?</p><p>Can an attacker control it?</p><p>What happens to it before it reaches the dangerous function?</p><p>Is that code path actually reachable?</p><p>Does it require authentication?</p><p>Is there another security control in between?</p><p>And if the issue is real, what can an attacker actually achieve?</p><p>That is closer to how I expect a professional source-code review to work.</p><h3>Exam Overview</h3><ul><li><strong>Certification:</strong> Certified Web Application Exploiter</li><li><strong>Provider:</strong> CyberExam</li><li><strong>Exam Window:</strong> 5 hours</li><li><strong>Format:</strong> Practical white-box web application security assessment</li><li><strong>Technology Stacks:</strong> PHP, Node.js, Python and Java</li><li><strong>Environment:</strong> Browser-based attacker environment</li><li><strong>Main Focus:</strong> Source-code analysis, exploitability validation, vulnerability chaining and reporting</li><li><strong>My Final Score:</strong> 99/101–98%</li></ul><p>One thing I liked here is that CWAE does not try to turn the exam into a huge artificial enterprise application.</p><p>The applications are relatively small and focused.</p><p>That obviously makes the assessment more manageable within five hours, but it also means you can spend more time understanding the vulnerability itself instead of trying to navigate hundreds of thousands of lines of unrelated code.</p><h3>Source Code Changes the Way You Think</h3><p>People sometimes assume that giving the candidate source code automatically makes an exam easy.</p><p>I do not completely agree.</p><p>Yes, some things become easier.</p><p>You do not need to spend forty minutes guessing whether a hidden endpoint exists when you can simply inspect the routes.</p><p>You can see which libraries are being used.</p><p>You can understand how authentication works.</p><p>You can follow what happens to a parameter after the request reaches the backend.</p><p>But having the source also creates another problem:</p><p><strong>Now you need to understand it.</strong></p><p>And that is where source-to-sink thinking becomes important.</p><p>A basic approach during a white-box assessment is usually something like this:</p><p>Understand the application entry points.</p><p>Find attacker-controlled input.</p><p>Follow the data.</p><p>Identify dangerous operations.</p><p>Check the security controls in between.</p><p>Confirm whether exploitation is actually possible.</p><p>That sounds obvious when written like this, but it is something I see being missed quite often.</p><p>Anyone can run:</p><p>grep -R &quot;exec&quot;</p><p>The interesting part starts after you find it.</p><p>Can a user actually control the argument?</p><p>Can that route be reached?</p><p>Is the value constrained?</p><p>What privilege does the application have?</p><p>Does exploitation create useful impact?</p><p>CWAE pushes the candidate toward answering those questions rather than simply recognizing vulnerability names.</p><p>That was probably my favourite technical aspect of the certification.</p><h3>What Does the Exam Cover?</h3><p>I intentionally do not want to describe the exact attack chains here.</p><p>There is no point in writing an exam review if the review becomes a solution guide for the next candidate.</p><p>What I can say is that the practical sections touch several familiar areas of modern web application security.</p><p>You will encounter concepts around injection, authentication and session handling, unsafe server-side operations, object behaviour, file handling, authorization decisions and insecure data reconstruction.</p><p>The important part is not whether you have seen the vulnerability name before.</p><p>Most experienced web pentesters probably have.</p><p>The challenge is understanding how that particular weakness appears in <strong>that particular language and application</strong>.</p><p>A security mistake in a Node.js application does not always look like the same mistake in PHP.</p><p>A Python framework may introduce a completely different trust model.</p><p>Java has its own very special ways of reminding us why object deserialization has traumatized security engineers for years. :)</p><p>And yes, after not touching some of these things for a long time, seeing them again was a nice little trip back in time.</p><h3>It Is About Chaining, Not Only Finding</h3><p>Another thing I liked was that the practical side is not designed entirely around unrelated vulnerabilities.</p><p>In several places, understanding one weakness gives you the context or access required to continue investigating another part of the application.</p><p>I will deliberately stop there because saying more would start giving away the exam.</p><p>But this design is much closer to reality than:</p><blockquote><em>Find vulnerability A → get flag → forget everything → move to completely unrelated vulnerability B.</em></blockquote><p>Real compromises often do not work like that.</p><p>An information disclosure may initially look medium severity.</p><p>Then you realize that the disclosed information influences authentication.</p><p>That access may expose another administrative function.</p><p>And suddenly several individually understandable mistakes become one serious attack path.</p><p>Thinking in terms of chains is important both for offensive security and for security architecture.</p><p>CWAE understands this.</p><h3>Is This Another OSWE?</h3><p>No.</p><p>And I do not think it needs to be.</p><p>Whenever a certification includes source-code review, people immediately start comparing it with OSWE.</p><p>I think that comparison needs some context.</p><p>CWAE is much more compact.</p><p>The applications are smaller.</p><p>The tasks provide more guidance.</p><p>The expected attack surface is narrower.</p><p>You are not dropped into a large application and expected to spend days eliminating false positives and building an exploit chain almost completely independently.</p><p>So if you enter CWAE expecting an OSWE-style code-audit marathon, that is not what you are going to get.</p><p>But I do not see this as a problem.</p><p>There is a very large gap between:</p><blockquote><em>“I know how to use Burp Suite and test a web application.”</em></blockquote><p>and:</p><blockquote><em>“Give me an unfamiliar codebase and I can audit it professionally.”</em></blockquote><p>Not everyone needs to jump directly from one end to the other.</p><p>I think CWAE fits somewhere in the middle.</p><p>It gives web pentesters a practical reason to start reading code without immediately throwing them into an extremely large and open-ended assessment.</p><p>That is actually a useful position for a certification.</p><h3>The Part I Did Not Expect to Like This Much: Reporting</h3><p>Now we come to probably the most interesting part of the exam for me.</p><p>The final practical section does not finish when you reach the technical objective.</p><p>You also need to prepare several parts of an engagement report.</p><p>The exam asks for sections such as an Executive Summary, Root Cause, References, Timeline, Reproduction Steps, Remediation and Impact.</p><p>This immediately caught my attention.</p><p>Because finding a vulnerability is only half of a professional penetration test.</p><p>You also need to explain it.</p><p>A developer needs to understand why the code is vulnerable.</p><p>A security engineer needs to understand how the attack path works.</p><p>A CISO needs to understand the risk.</p><p>A CIO or CTO probably does not want to read three pages explaining how a Java object was reconstructed.</p><p>:)</p><p>Being able to communicate the same finding to different audiences is part of the job.</p><p>I liked seeing that included directly in the certification.</p><h3>AI-Graded Reporting</h3><p>Here things became more interesting.</p><p>The report sections are evaluated using an AI-based grading mechanism.</p><p>When you submit a section, the platform evaluates it and provides feedback almost immediately.</p><p>My first reaction was honestly:</p><blockquote><em>“Let’s see if this just rewards security buzzwords.”</em></blockquote><p>Because we all know how easy it is to write something that sounds professional without really saying anything.</p><p>“Critical risk.”</p><p>“Defense in depth.”</p><p>“Zero Trust.”</p><p>“Validate user input.”</p><p>“Follow OWASP best practices.”</p><p>Perfect consulting report. :D</p><p>But the result was better than I expected.</p><p>For example, I submitted a timeline based on the actual sequence of my assessment.</p><p>The grader gave the section full points and specifically mentioned that the timeline was grounded in the correct technical chain and did not contain meaningful gaps.</p><p>That part was nice.</p><p>I have taken quite a few practical certifications over the years, and I had not personally seen reporting handled exactly like this before.</p><p>Normally you either:</p><p>Find the flags and finish the exam.</p><p>Or write a PDF and wait for someone to review it.</p><p>Here, you write a relatively focused section and receive immediate feedback about whether the answer actually contains what the grader expects.</p><p>It makes the report feel like part of the assessment rather than paperwork you do after the interesting part is finished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iH8E0tn4Ez8B0n0dToDNuQ.png" /><figcaption><em>The AI grader evaluating one of my engagement-report sections. The immediate, context-aware feedback was one of the most interesting parts of the exam</em></figcaption></figure><p>There is one limitation I would like to see improved in the future.</p><p>Once some report sections are submitted and graded, they become locked.</p><p>I understand the reason behind this from an exam-integrity perspective.</p><p>However, AI is still AI.</p><p>If a technically correct answer is interpreted incorrectly, there should ideally be a manual review or appeal option.</p><p>I did not personally have a problem with the grader, but having that fallback would make the system much stronger.</p><h3>My VNC / Lab Experience</h3><p>Now we come to the part where my experience was not completely smooth.</p><p>The exam environment is delivered through a browser-based remote desktop.</p><p>Conceptually, I like this approach.</p><p>You do not need to prepare your own attacker machine, configure a VPN, or spend the first part of the exam troubleshooting local dependencies. The required tools and source code are already available inside the environment.</p><p>That is the good part.</p><p>During my review, I did experience a few operational rough edges around provisioning and service accessibility, and there were moments where target addressing could have been clearer.</p><p>At one point, I was not completely sure whether I was debugging my exploit or debugging the lab environment.</p><p>And that is never a great feeling during an exam. :)</p><p>However, there is another side to this experience that I think is worth mentioning.</p><p>While reviewing one of the challenge flows, I shared some technical feedback based on my own experience as someone who works professionally in offensive security and application security.</p><p>What impressed me was how quickly that feedback was acted on.</p><p>Rather than simply acknowledging the comment and leaving it for a future release, Besim reviewed the point almost immediately, made an adjustment to the challenge, and asked me to test the revised version while I was still inside the environment.</p><p>From a reviewer perspective, I actually appreciated this a lot.</p><p>It showed that the platform was not treating the review as a marketing exercise. The feedback was being taken seriously and translated directly into improvements.</p><p>Naturally, making changes that quickly can temporarily create small differences between existing material and the updated live environment, which is something that should be carefully controlled in production exam sessions.</p><p>But in my case, this happened specifically as part of an active reviewer feedback loop, not because challenges were being changed unpredictably for normal candidates.</p><p>So while I still think the VNC and lab-delivery experience can become more polished, I came away with a positive impression of how CyberExam responds to technical feedback.</p><p>For a young platform, that willingness to listen, react quickly, and improve the product in real time is something I genuinely value.</p><h3>The Support Experience Was a Different Story</h3><p>Although the lab experience had rough edges, the support experience was very good.</p><p>Whenever I reported an issue, <strong>Besim Altınok</strong>, founder of CyberExam, responded very quickly and actually looked into the technical problem.</p><p>There was no endless ticket chain.</p><p>No copy-paste support response.</p><p>No:</p><blockquote><em>“Could you please clear your browser cache and try again tomorrow?”</em></blockquote><p>:)</p><p>If something needed investigation, he investigated it.</p><p>If something needed adjustment, it was adjusted.</p><p>I also shared a few platform-side observations related to the examination workflow and environment privately.</p><p>I obviously will not publish technical details that could affect the integrity of the certification.</p><p>What matters here is that the feedback was taken seriously.</p><p>I always appreciate this in new security products.</p><p>Problems can happen.</p><p>Especially in a young platform.</p><p>The more important question is sometimes:</p><blockquote><em>What happens after you report the problem?</em></blockquote><p>In my experience, the response was fast and constructive.</p><p>Of course, the long-term goal should be that candidates do not need direct intervention from the founder during an exam.</p><p>But the attitude toward feedback was definitely one of the positive sides of my experience.</p><h3>How Difficult Is CWAE?</h3><p>This is slightly difficult for me to score because, as I explained earlier, I had access to the intended solution material as part of the reviewer process.</p><p>So I am not going to say:</p><blockquote><em>“I went completely blind and CWAE is exactly 7.43/10 difficulty.”</em></blockquote><p>That would not be honest.</p><p>Instead, I can evaluate the underlying technical level.</p><p>If you are already an experienced web penetration tester or AppSec engineer and regularly read source code, many of the individual vulnerability concepts will probably look familiar.</p><p>The challenge will be moving quickly between different languages and understanding how the same security principles appear differently across frameworks.</p><p>If you are an intermediate black-box pentester, I think the exam becomes more interesting.</p><p>You may already know how to exploit many of the vulnerability classes, but source-code tracing will force you to approach them differently.</p><p>For a junior candidate, I would consider CWAE relatively difficult.</p><p>This is not where I would start learning web application security from zero.</p><p>You should already understand HTTP, sessions, authentication, common web vulnerabilities, Linux basics and enough programming to follow an unfamiliar function without immediately closing the editor. :)</p><p>Overall, based on the technical content rather than my reviewer completion experience, I would place CWAE around <strong>7/10</strong> for its intended audience.</p><p>Challenging enough to require preparation.</p><p>Not an OSWE-level marathon.</p><p>And I think that is a fair place for it.</p><h3>How Would I Prepare for CWAE?</h3><p>I would not spend the entire preparation period memorizing payloads.</p><p>That is probably the biggest mistake.</p><p>Instead, take vulnerable applications and practise asking:</p><p>Where does this value come from?</p><p>Where does it go?</p><p>What security decision depends on it?</p><p>What happens before it reaches the dangerous function?</p><p>Can the attacker actually control the full path?</p><p>That mindset is much more useful than remembering another fifty-character payload from a cheat sheet.</p><p>You should also be reasonably comfortable reading PHP, JavaScript, Python and Java.</p><p>You do not need to professionally develop applications in all four languages.</p><p>But classes, functions, request parameters, object properties, route handlers and authentication logic should not look completely foreign.</p><p>Finally, practise reporting.</p><p>Take one vulnerability you already know and try to explain it three times:</p><p>First to a developer.</p><p>Then to a CISO.</p><p>Then to a CIO.</p><p>If all three explanations are identical, you probably need more reporting practice.</p><p>:)</p><h3>Who Should Take CWAE?</h3><p>I think the best candidate for CWAE is someone who already understands traditional web penetration testing and wants to move one step closer to <strong>AppSec and white-box auditing</strong>.</p><p>A web pentester who spends most of the day inside Burp Suite but wants to become more comfortable reading backend code would probably get value from it.</p><p>The same applies to bug bounty hunters who want to move toward more structured application-security work, junior or intermediate AppSec engineers, and offensive security professionals who regularly encounter custom applications.</p><p>I would not recommend it as someone’s first cybersecurity certification.</p><p>And I definitely would not recommend taking it simply because the word “Exploiter” sounds cool on LinkedIn.</p><p>The value is in the methodology behind the certificate.</p><h3>What I Liked</h3><p>The strongest part of CWAE for me was the <strong>white-box mindset</strong>.</p><p>The exam does not completely separate code review from exploitation.</p><p>You are expected to understand both.</p><p>I also liked the multi-language approach.</p><p>Using PHP, Node.js, Python and Java prevents the entire assessment from becoming a single-framework exercise.</p><p>The chained nature of the practical tasks also makes sense.</p><p>You are encouraged to think about how weaknesses interact rather than evaluating every vulnerability in isolation.</p><p>And finally, the reporting system genuinely surprised me.</p><p>The AI grader was something I initially expected to treat as a gimmick.</p><p>Instead, it became one of the parts I remembered most clearly after finishing the assessment.</p><p>That does not happen very often.</p><h3>What Could Be Better?</h3><p>The biggest improvement area is the lab experience.</p><p>Source code, live targets and task descriptions should always represent the same challenge version.</p><p>Target addressing should be completely clear.</p><p>The environment should be fully ready before the candidate starts spending meaningful exam time.</p><p>These things sound small, but they matter.</p><p>When you are working through an exploit, you should be thinking:</p><blockquote><em>“What am I missing in the application?”</em></blockquote><p>Not:</p><blockquote><em>“Is this service actually running where I think it is?”</em></blockquote><p>I would also like future versions to include slightly more ambiguity in the code.</p><p>The current exam has good breadth, but some tasks are naturally more guided because of the five-hour format.</p><p>Larger applications, more false-positive sinks and multiple possible paths could make future versions even stronger.</p><p>Finally, as I mentioned earlier, I think AI grading should eventually have a manual review fallback.</p><p>These are improvements rather than reasons to dismiss the certification.</p><p>The core idea is already good.</p><p>The platform just needs to become as mature as the concept behind it.</p><h3>Does “Certified Web Application Exploiter” Live Up to the Name?</h3><p>I think this is probably the most important question in the entire review.</p><p>My answer is:</p><p><strong>Mostly, yes.</strong></p><p>CWAE expects you to read source code.</p><p>Understand data flow.</p><p>Identify security-sensitive behaviour.</p><p>Validate exploitability.</p><p>Work across multiple application stacks.</p><p>Think about vulnerability chains.</p><p>And explain your findings professionally.</p><p>Those are all relevant skills for someone working in offensive web application security.</p><p>Would I say that someone who passes CWAE can immediately audit a massive enterprise application alone at senior AppSec level?</p><p>Of course not.</p><p>That would be a ridiculous expectation from any five-hour certification.</p><p>But does CWAE demonstrate more than the ability to copy a payload from PayloadsAllTheThings and collect a flag?</p><p>Yes.</p><p>I think it does.</p><p>And that is why I believe the certification has a legitimate place.</p><h3>Is CWAE Worth It?</h3><p>For the right candidate, yes.</p><p>Especially if your current experience is mostly black-box web penetration testing and you want a structured introduction to source-oriented application security.</p><p>The exam gives you exposure to multiple languages, different implementation mistakes, chained exploitation and professional reporting in one package.</p><p>At the same time, I would personally like to see the VNC and lab-delivery experience become more polished as the platform grows.</p><p>The content is already pointing in the right direction.</p><p>Now the delivery needs to catch up.</p><h3>My Final Rating = 8/10</h3><p>CWAE is not perfect.</p><p>But it is interesting.</p><p>And I would much rather review a certification that tries something different and still has a few rough edges than another exam built entirely around memorizing theoretical questions.</p><p>The strongest parts are the white-box methodology, vulnerability chaining and reporting approach.</p><p>The weakest part of my experience was clearly the lab/VNC side.</p><p>The support, however, was excellent.</p><p>With some additional maturity around provisioning, environment consistency and examination workflow, I think CWAE can become a very solid certification for people transitioning from traditional web penetration testing into application security.</p><h3>Final Thoughts</h3><p>When I look back at CWAE, the thing I remember most is not a particular payload or vulnerability.</p><p>It is the way the exam tries to connect <strong>code, exploitation and reporting</strong>.</p><p>I think that combination matters.</p><p>A good pentester should not only be able to say:</p><blockquote><em>“I sent this payload and got RCE.”</em></blockquote><p>They should also be able to explain:</p><p>Why did the application allow it?</p><p>Which security assumption failed?</p><p>How did the input reach the dangerous operation?</p><p>What can an attacker actually achieve?</p><p>And what should the engineering team change so the vulnerability does not come back six months later?</p><p>That is where penetration testing starts becoming application security.</p><p>CWAE is not OSWE.</p><p>It does not need to be.</p><p>It is shorter, more guided and more accessible.</p><p>But it also pushes candidates slightly beyond pure black-box testing, and I think there is real value in that.</p><p>My VNC experience was not perfect.</p><p>I encountered some issues and shared quite a lot of feedback during the assessment.</p><p>But I also saw how quickly those problems were addressed.</p><p>For a young certification platform, that willingness to listen and improve is important.</p><p>The technical foundation is there.</p><p>The reporting idea is genuinely interesting.</p><p>And if CyberExam continues improving the platform around those ideas, I think CWAE has good potential.</p><p>Would this certification alone make someone a senior application security engineer?</p><p>No.</p><p>No certification does that.</p><p>But if CWAE makes a web pentester stop asking only:</p><blockquote><em>“Which payload works?”</em></blockquote><p>and start asking:</p><blockquote><em>“Why was this payload able to work?”</em></blockquote><p>then I think it has already achieved something useful.</p><p>Special thanks to <strong>CyberExam | Certification</strong> and <strong>Besim Altınok</strong> for providing reviewer access, being open to technical feedback and responding quickly throughout the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*5Jcsae5fUzVI64zc.gif" /></figure><p>Thank you for reading!</p><p>As always, feel free to connect with me on <a href="https://www.linkedin.com/in/tunahantekeoglu/">LinkedIn</a> and share your experience if you decide to take the exam.</p><p>See you in the next review.</p><p>Maybe I have another surprise coming soon. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bd286b6d7cb" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/certified-web-application-exploiter-cwae-exam-review-2026-3bd286b6d7cb">Certified Web Application Exploiter (CWAE) Exam Review 2026</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[MCP Security for Enterprise Part 2: The Red Team Playbook]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://tun4hunt.medium.com/mcp-security-for-enterprise-part-2-the-red-team-playbook-0611abe8d806?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/1400/0*z6YyflZzYKFoaBfJ.png" width="1400"></a></p><p class="medium-feed-snippet">I Stole Your SSH Keys with a Calculator App.</p><p class="medium-feed-link"><a href="https://tun4hunt.medium.com/mcp-security-for-enterprise-part-2-the-red-team-playbook-0611abe8d806?source=rss-ed536e0ac16a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://tun4hunt.medium.com/mcp-security-for-enterprise-part-2-the-red-team-playbook-0611abe8d806?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0611abe8d806</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 20:18:42 GMT</pubDate>
            <atom:updated>2026-04-07T20:18:42.367Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[MCP Security for Enterprise: When LLMs Stop Talking and Start Acting]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://tun4hunt.medium.com/mcp-security-for-enterprise-when-llms-stop-talking-and-start-acting-ff4f6e6cafd4?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/2600/1*H_izkWjS73fjaBQ-VB_Z_w.png" width="2752"></a></p><p class="medium-feed-snippet">Architecture-Level Threat Modeling, Abuse Scenarios &amp; Hardening Principles</p><p class="medium-feed-link"><a href="https://tun4hunt.medium.com/mcp-security-for-enterprise-when-llms-stop-talking-and-start-acting-ff4f6e6cafd4?source=rss-ed536e0ac16a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://tun4hunt.medium.com/mcp-security-for-enterprise-when-llms-stop-talking-and-start-acting-ff4f6e6cafd4?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff4f6e6cafd4</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 12:39:09 GMT</pubDate>
            <atom:updated>2025-12-16T12:39:09.425Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[API Security Certified Professional (ASCP) Exam Review]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/api-security-certified-professional-ascp-exam-review-f221920a57f2?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/2600/1*BVSnRbUlCgZmXBaibuMHYA.jpeg" width="3300"></a></p><p class="medium-feed-snippet">Is ASCP worth it? My review covers the 12-hour hands-on exam, key vulnerabilities, and strategies to capture all flags.</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/api-security-certified-professional-ascp-exam-review-f221920a57f2?source=rss-ed536e0ac16a------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/api-security-certified-professional-ascp-exam-review-f221920a57f2?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f221920a57f2</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 25 Nov 2025 11:27:03 GMT</pubDate>
            <atom:updated>2025-12-15T08:15:06.680Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Certified AI/ML Pentester (C-AI/MLPen) Exam Review 2025]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/certified-ai-ml-pentester-c-ai-mlpen-exam-review-2025-9142bc97f373?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/1926/1*h5d_2tyEGK7EuWi0L4ODTQ.png" width="1926"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/certified-ai-ml-pentester-c-ai-mlpen-exam-review-2025-9142bc97f373?source=rss-ed536e0ac16a------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/certified-ai-ml-pentester-c-ai-mlpen-exam-review-2025-9142bc97f373?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9142bc97f373</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[prompt]]></category>
            <category><![CDATA[appsec]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 12:34:33 GMT</pubDate>
            <atom:updated>2025-07-28T06:01:17.138Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Offensive Security SEC-100 & OSCC Certification: Course and Exam Review]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/offensive-security-sec-100-oscc-certification-course-and-exam-review-aec9016326ce?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/1264/1*3s15-JPmpnu6ZcaOU5ZGag.png" width="1264"></a></p><p class="medium-feed-snippet">A comprehensive review of OffSec&#x2019;s newest entry-level training and certification program</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/offensive-security-sec-100-oscc-certification-course-and-exam-review-aec9016326ce?source=rss-ed536e0ac16a------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/offensive-security-sec-100-oscc-certification-course-and-exam-review-aec9016326ce?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aec9016326ce</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Thu, 10 Apr 2025 14:58:46 GMT</pubDate>
            <atom:updated>2026-01-25T14:07:08.697Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CAPenX Exam Review 2025]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/capenx-exam-review-2025-dfead0bb29a9?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/1796/1*oPeh6vIAsX4kEyZ6ZmLvzA.png" width="1796"></a></p><p class="medium-feed-snippet">Hello everyone! I&#x2019;m Tunahan Tekeo&#x11F;lu</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/capenx-exam-review-2025-dfead0bb29a9?source=rss-ed536e0ac16a------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/capenx-exam-review-2025-dfead0bb29a9?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfead0bb29a9</guid>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[capenx]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Wed, 12 Mar 2025 09:02:37 GMT</pubDate>
            <atom:updated>2025-03-12T09:20:38.888Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The World’s First OSCP+ Exam Review]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/the-worlds-first-oscp-exam-review-317950db3267?source=rss-ed536e0ac16a------2"><img src="https://cdn-images-1.medium.com/max/1272/1*zk-wLbxvDqjOLO95AkBIVg.png" width="1272"></a></p><p class="medium-feed-snippet">Hello everyone! I&#x2019;m Tunahan TEKEOGLU. After the articles I wrote about CEH and EWPTXv2 received much more attention than I expected, along&#x2026;</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/the-worlds-first-oscp-exam-review-317950db3267?source=rss-ed536e0ac16a------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/the-worlds-first-oscp-exam-review-317950db3267?source=rss-ed536e0ac16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/317950db3267</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[oscp-preparation]]></category>
            <dc:creator><![CDATA[Tunahan TEKEOGLU]]></dc:creator>
            <pubDate>Tue, 26 Nov 2024 15:45:11 GMT</pubDate>
            <atom:updated>2024-11-26T15:45:11.024Z</atom:updated>
        </item>
    </channel>
</rss>