Currently work as a software security consultant, pentest of web and mobile app, secure code review and training activities With the job and the channels don’t have much time for bug bounty, but I’m planning to do more of it in the future, and of course I will bring related material to the channel
Sir I will be very helpful if you reply your opinion on one of my concern (Asking this because I have been learning cybersec, Specially web application penetration testing for now 2 years but I am not able to see myself at even a intermediate level in order to get started with bug bounty) Basically I have a tendency to spend a lot of time understanding how vulnerabilities work under the hood. I don't feel comfortable moving on until I have a crystal-clear understanding of why something happens and what causes it. For example, I recently spent two days thoroughly understanding the CVE related to jQuery's deparam function and how it leads to prototype pollution. While I feel this depth of understanding helps me avoid being a script kiddie who just copies and pastes payloads without understanding them, it also slows me down significantly. I worry that if I continue this approach, I’ll spend so much time on each topic that I won’t be able to cover the breadth of knowledge required to start my bug bounty journey. How can I strike a balance between diving deep into topics and abstracting things so that I can move on to learn other new things as well in order to start my bug bounty journey? How can I determine how much time and effort to invest in understanding a specific vulnerability?
Ok, I'll try to answer your question, hope it is somewhat useful. First of all, I would not wait until all the knowledge has been acquired before proceeding to do bug bounty. Truth is, you can start now. Yes, with limited knowledge, and maybe that won't be enough. However, do not fall into the trap of "over-preparation", which is another form of perfectionism. Truth is, not all knowledge is required to get something. Just something is required to get something. Hope that is not confusing. Invest of course maybe not the whole day to it. But you can start small, feel the experience itself, and you will have more understanding on what you need to improve on. As to what to focus on, I would say: start with low hanging fruits. What are these? These are vulnerabilities which are not too difficult to understand or to exploit. Yes, they are also very popular. Key here is to develop good automations to speed up the discovery of such vulnerabilities. In general, try to have a very focused approach, where you don't just study everything because it could be important, but you focus specifically on a technological stack. Like, idk, IDOR authz byass. Or WAF bypass to inject XSS payloads. Focus on 1-2-3 areas like this, and yeah, you can do deep dives in these areas, but with a very well defined focus. What i'm trying to say is: define precise goals. They can be hard, but they must be precise. Do not over-prepare and learn by doing, failing, and doing it again!
This exactly that we need ! Thank you so much!
Excellent content
This is awesome ! Are you going to upload the Windows course as a long video like the linux one too ?
Yah, working on the timestamps and everything
Great content ❤
more web exploration stuff pleaseeeeee
its coming!
Are the syllabus of oscp and oscp+ same , and also like toughness level etc
Yes, consider them the same exam/study material. When u obtain the exam u get oscp+, then after 3 months it becomes a normal oscp
@hexdump1337 thank you for providing us this level of valuable content. And after 3 years it become normal oscp ✅️
oh yeah sorry, it was 3 years xD
3 months would’ve been crazy short
Thanks u so much
Sir are you into bug bounty?
Currently work as a software security consultant, pentest of web and mobile app, secure code review and training activities
With the job and the channels don’t have much time for bug bounty, but I’m planning to do more of it in the future, and of course I will bring related material to the channel
Sir I will be very helpful if you reply your opinion on one of my concern (Asking this because I have been learning cybersec, Specially web application penetration testing for now 2 years but I am not able to see myself at even a intermediate level in order to get started with bug bounty)
Basically I have a tendency to spend a lot of time understanding how vulnerabilities work under the hood. I don't feel comfortable moving on until I have a crystal-clear understanding of why something happens and what causes it. For example, I recently spent two days thoroughly understanding the CVE related to jQuery's deparam function and how it leads to prototype pollution.
While I feel this depth of understanding helps me avoid being a script kiddie who just copies and pastes payloads without understanding them, it also slows me down significantly. I worry that if I continue this approach, I’ll spend so much time on each topic that I won’t be able to cover the breadth of knowledge required to start my bug bounty journey.
How can I strike a balance between diving deep into topics and abstracting things so that I can move on to learn other new things as well in order to start my bug bounty journey? How can I determine how much time and effort to invest in understanding a specific vulnerability?
Thats a very precious question, thanks for asking.
I’m gonna think about it for a while before answering, but no worries, I am thinking about it!
No worries sir I am glad that you took out some time from your busy schedule in order to read it out and reply me 🙏🏻😇
Ok, I'll try to answer your question, hope it is somewhat useful.
First of all, I would not wait until all the knowledge has been acquired before proceeding to do bug bounty. Truth is, you can start now. Yes, with limited knowledge, and maybe that won't be enough. However, do not fall into the trap of "over-preparation", which is another form of perfectionism. Truth is, not all knowledge is required to get something. Just something is required to get something. Hope that is not confusing. Invest of course maybe not the whole day to it. But you can start small, feel the experience itself, and you will have more understanding on what you need to improve on.
As to what to focus on, I would say: start with low hanging fruits. What are these? These are vulnerabilities which are not too difficult to understand or to exploit. Yes, they are also very popular. Key here is to develop good automations to speed up the discovery of such vulnerabilities.
In general, try to have a very focused approach, where you don't just study everything because it could be important, but you focus specifically on a technological stack. Like, idk, IDOR authz byass. Or WAF bypass to inject XSS payloads. Focus on 1-2-3 areas like this, and yeah, you can do deep dives in these areas, but with a very well defined focus.
What i'm trying to say is: define precise goals.
They can be hard, but they must be precise.
Do not over-prepare and learn by doing, failing, and doing it again!
First comment ❤