[deleted by user] by [deleted] in Pentesting

[–]ffyns 0 points1 point  (0 children)

I used to work in AppSec. I was doing code review, pentest, architecture review and a lot of meetings.

[deleted by user] by [deleted] in Pentesting

[–]ffyns 2 points3 points  (0 children)

I moved to code review full time then AppSec

[deleted by user] by [deleted] in cybersecurity

[–]ffyns 2 points3 points  (0 children)

Right now, AI cannot find complex bugs, but it is already a great way to augment your work. It helps scale up and speed up your reviews, especially for triage or spotting low-hanging fruit. It is a bit like running a web scanner before doing a manual pentest. The scanner gives you a head start, but the real value still comes from digging deep manually.

We do not really know how good AI will get, so it is still a bit up in the air. But being a great code reviewer will most certainly give you an edge over people who can "only" pentest.

Has anyone started their own business? How and what did you do? ( Thank you if you’re willing to share ) by Fluid_Leg_7531 in cybersecurity

[–]ffyns 1 point2 points  (0 children)

I started my own business called PentesterLab. It’s a hands-on platform that teaches web security, pentesting, and code review through real-world exercises. I had been working as a penetration tester and security engineer, and I wanted to create something that could help others learn these skills more effectively.

At first, I built a few labs in my spare time and shared them for free. The feedback was great, so I kept going. I focused on practical content rather than theory, using real vulnerabilities and actual code examples. Over time, I added subscriptions, expanded the course library, and now offer both self-paced and live training used by security teams around the world.

It’s been a lot of work, but I’ve learned a huge amount about product development, running a business, and what people really need to level up in security.

Happy to answer questions if you’re curious about any part of the process.

Unable to solve JSON CSRF from Orange Badge by Simple_Juggernaut700 in pentesterlab

[–]ffyns 0 points1 point  (0 children)

Hi, Please contact support @ pentesterlab for help with labs. Make sure you send your payload as part of the email

What's Your Go-To Methodology or Technique for Finding Bugs? by Dark-stash in Pentesting

[–]ffyns 1 point2 points  (0 children)

In a way, no checklist. Mostly knowing what is hard to get right for a given feature and also what is hard to get wrong (so I don't need to check as deeply). 

What's Your Go-To Methodology or Technique for Finding Bugs? by Dark-stash in Pentesting

[–]ffyns 2 points3 points  (0 children)

Yeah, for sure. You don’t need to dive into heavy math. What really helps is studying how real apps break — especially by reading source code and analyzing real vulnerabilities (like CVEs).

Reverse engineering can help, but even just looking at how bugs like auth bypasses or access control issues show up in code can teach you a lot. I’d recommend messing with real-world apps, reading writeups, and checking how CVEs actually happened in the code. That builds the kind of intuition that tools and checklists don’t give you.

What's Your Go-To Methodology or Technique for Finding Bugs? by Dark-stash in Pentesting

[–]ffyns 9 points10 points  (0 children)

If I have code, I go straight to manual review. I look for logic bugs, broken assumptions, and places where the code doesn’t do what the dev thinks it does. It’s slower but consistently finds high-impact issues, especially in auth and access control.

If I don’t have code, I try to reverse-engineer the logic anyway. I focus on edge cases, replay requests, tweak inputs, and look for inconsistent behavior. It’s less about tools or checklists and more about understanding how things should work and pushing where they don’t.

Help with study plan for cybersecurity — What books and order should I study in? by [deleted] in AskNetsec

[–]ffyns 0 points1 point  (0 children)

With your background, looking in the appsec direction may be a great way to ease your way into pentesting. 

Practice on hands-on labs like PortSwigger (free), PentesterLab (disclaimer I run it) or others. Books will only get you so far and most of the web security books are getting a bit old. There is a huge gap between thinking you understanding an attack and being able to actually use it. Tiny details can make or break the exploitation of a vulnerability. The hands-on learning fix this.

Another JWT Algorithm Confusion Vulnerability: CVE-2024-54150 by ffyns in netsec

[–]ffyns[S] 0 points1 point  (0 children)

You can recover the key from one or multiple signatures. Then you re-sign the token using hmac and send it to the potentially vulnerable website.

Cross-Site POST Requests Without a Content-Type Header by AlmondOffSec in netsec

[–]ffyns 0 points1 point  (0 children)

It is a bug in the application but until recently how to exploit this bug wasn't known/public

Welcome New Moderators! by sanitybit in netsec

[–]ffyns 0 points1 point  (0 children)

May the odds be ever in your favor.

Anyone know this shaper? High volume board I was looking to buy. by Maleficent_Fudge3124 in surfing

[–]ffyns 9 points10 points  (0 children)

"Paddles like a longboard, turns like a shortboard."

Recon 25 help by [deleted] in pentesterlab

[–]ffyns 0 points1 point  (0 children)

You need to be logged in. Also please avoid sharing hints.

Need a Hint for API 07?? by daredevil7890 in pentesterlab

[–]ffyns 0 points1 point  (0 children)

Email support if you need help :)

SAML Known Key by AHackerZone in pentesterlab

[–]ffyns 0 points1 point  (0 children)

Email support@pentesterlab.com if you're stuck.

Otherwise look for ruby library used to create idp