OSCP only proves you can handle 20% of a pentest.

The remaining 80%:

• Scoping the engagement
• Understanding the design
• Estimating the effort
• Presenting your findings

All done when your Kali VM is off.

And people still wonder why OSCP can't land them their first pentesting job.

Instead:

• Get a job that teaches you even if it pays less, OR
• Learn from people who do this for a living

Because 80% > 20%, no matter how you slice it.

OSCP only proves you can handle 20% of a pentest. | William Chu | 83 comments

OSCP only proves you can handle 20% of a pentest. The remaining 80%: - Scoping the engagement - Understanding the design - Estimating the effort - Presenting your findings All done when your Kali VM is off. And people still wonder why OSCP can’t land them their first pentesting job. Instead: - Get a job that teaches you even if it pays less, OR - Learn from people who do this for a living Because 80% > 20%, no matter how you slice it. P.S. Posting my framework to do that 80% on https://sechurity.com in a few days, subscribe so you won’t miss! | 83 comments on LinkedIn

LinkedInWilliam Chu

Follow up post

The only guide you need to handle a pentest

(From pre-engagement to reporting, and beyond)

Disclaimer: I did not write this piece of art
It's from GovTech Singapore: https://docs.developer.tech.gov.sg/docs/security-testing-guidelines/penetration-test?id=_233-lifecycle

"I've read it. What's next?"

I recommend doing these 3 things if you really want to excel at this (less-appealing) 80% of a pentest:

1. Chat more with clients
   → Best way to get in-depth knowledge about the system before the test
   (Sometimes they turn into friends)

2. Work somewhere you can practice
   → Get your repetition and learn to deal with exceptions

3. Standardize the process
   → Checklists and forms saves everyone's time and minimize errors

Honestly, I hate doing these instead of the actual pentest.
But doing them correctly saves everyone from headaches in the long run.
(Do you really want to crash your client's server on a Friday?)

So the next best thing we can do is to make the knowledge accessible.

Do you think that's enough? Let me know your thoughts in the comments.

The only guide you need to handle a pentest | William Chu

The only guide you need to handle a pentest (From pre-engagement to reporting, and beyond) Disclaimer: I did not write this piece of art It’s from GovTech Singapore: https://lnkd.in/dC67r7qc “I’ve read it. What’s next?” I recommend doing these 3 things if you really want to excel at this (less-appealing) 80% of a pentest: 1. Chat more with clients → Best way to get in-depth knowledge about the system before the test (Sometimes they turn into friends) 2. Work somewhere you can practice → Get your repetition and learn to deal with exceptions 3. Standardize the process → Checklists and forms saves everyone’s time and minimize errors Honestly, I hate doing these instead of the actual pentest. But doing them correctly saves everyone from headaches in the long run. (Do you really want to crash your client’s server on a Friday?) So the next best thing we can do is to make the knowledge accessible. Do you think that’s enough? Let me know your thoughts in the comments. P.S. I’m back. Resigned recently so I finally feel like myself again.

LinkedInWilliam Chu