@bobface16

@bobface16

Words of Wisdom

---

"Audited codebases"

Regarding bug bounties, almost all codebases have been previously audited, often by leading security firms.

Don’t let that fool you into thinking they are bug-free. Some of my biggest bounties have been in projects that have been audited extensively and yet still were vulnerable.

Approach each codebase as if it came fresh from the developers.

"Be prepared to negotiate"

Identifying a bug, writing up a PoC, and reporting it is only the first half.

The second half commonly involves quite a bit of discussion and negotiation.

Learn how to express complex technical situations, how to present a well-founded case, and how to professionally negotiate.

"When to stop searching"

At which point do you stop searching a codebase for bugs?

Try to understand the system to the point where you could reimplement it from scratch without looking at the original codebase. Not from remembering the code, but from having understood what the application is supposed to do.

If you have examined a project that far and have not found a bug, the chances of finding one by continuing is low. On the other hand, if there was a bug in there, you would have most likely found it.

"How to improve your skills"

Theoretical knowledge is important, but nothing trumps practical experience.

Develop your own projects and observe areas of security concern, participate in CTFs, and build PoCs for past exploits.