The No-Bullshit Guide to Pentest
Here's a few suggestions in no particular order.
> Learn python
> Learn assembly for at least x86
> Set up a test lab
> Put a small Windows domain in your lab and try to go from a regular user foothold to domain admin. Also try to go from a local administrator to domain admin. You can simulate that scenario by having a privileged account login to a workstation used by the local admin as if it were helpdesk troubleshooting a problem, then attack it as the stolen local admin account and use a tool like Mimikatz to get the privileged account and pivot from that workstation.
> Grab some intentionally vulnerable virtual machines and poke at them in your lab. Vulnhub has these for download and there's several other places too.
> If you're wanting to get into web app pentesting, learn javascript, learn how web servers work, learn how web browsers work, fire up wireshark and capture then analyze the traffic when you browse to a regular HTTP website, then again when you browse to HTTPS.
> Get good with Google.
> Hit up a training course for CEH (weak, but teaches some basic concepts) or PWK/OSCP (beast, and probably way out of your league as a beginner) and take everything you learn and apply it in your test lab. The knowledge is worthless unless you do something with it, so practice, practice, practice!
> Learn to hide. Find ways to hide your traffic in the normal background noise of a busy network. Learn to know what I mean by normal background noise of a network.
> Learn about the tools the blue teams will use to detect and stop you. Learn about next-gen firewalls, IPS devices, malware sandboxes, etc. Be too noisy and you get caught.
> And the most important one: never attack something without getting the owner's permission in writing first. CYA is a way of life
~ @H0N3YP07
Comments
Post a Comment