OSCP-Exam-Report-Template
alacarte
OSCP-Exam-Report-Template | alacarte | |
---|---|---|
9 | 2 | |
913 | 20 | |
- | - | |
0.0 | 0.0 | |
almost 3 years ago | almost 4 years ago | |
Shell | ||
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OSCP-Exam-Report-Template
-
Passing the OSCP in 8 hours(as a high school student)
I had never done any formal pentesting reports like this one, so I kind of learned it on the fly. The whoisflynn template came in clutch for me, since I just had to follow the instructions laid out and copy paste whatever I needed to. Don’t underestimate this part of the exam, and do some planning beforehand to make sure you’re comfortable and have enough time. There isn’t an upper limit to detail in the report, and I was sure I was very detailed in my writeups.
- 22 Hours Later
-
Really bad exam experience, don't wanna take it again?
Was easy to be honest. The way I work was to create reports for all boxes I did in the PWK, proving grounds and HTB as if they were real engagements. I used a template in Joplin I found here https://github.com/whoisflynn/OSCP-Exam-Report-Template. During my practice I would document my findings as I went through and edited out things I didn't need.
-
Passed second try, my thoughts
As for the report, I used this template, and removed most sections such as remediation, and added another section for common tools that I used that needs to leave a link to (i.e. Nishang's repo, Feroxbuster, AutoRecon, etc.)
- Une petite demande concernant les spécialistes en cybersécurité
- I passed OSCP, and here is how you should(nt) do it
-
everything i need to know :3
I used https://github.com/whoisflynn/OSCP-Exam-Report-Template for my report
- Report format for OSCP
-
OSCP report
I had the same thing, the template looks very differently from what I would've done on my own. In the end I decided to follow the template (or more specifically, this version, since it made more sense to me) as closely as possible, only diverging when I had to, for instance when there were certain vulnerabilities I had to exploit before I could do the actual exploit that I used to obtain a shell, but that didn't allow me to obtain a shell themselves directly. In those cases I put those explanations in the initial description.
alacarte
-
Enumeration Playbook?
You might find this tool useful: https://github.com/4ut0m4t0n/alacarte
- I passed OSCP, and here is how you should(nt) do it
What are some alternatives?
OSCP-Exam-Report-Template-Markdown - :orange_book: Markdown Templates for Offensive Security OSCP, OSWE, OSCE, OSEE, OSWP exam report
nmapAutomator - A script that you can run in the background!
AutoRecon - AutoRecon is a multi-threaded network reconnaissance tool which performs automated enumeration of services.
CTF-Difficulty - This cheasheet is aimed at the CTF Players and Beginners to help them sort the CTF Challenges on the basis of Difficulties.
EZEA - EZEA (EaZy Enum Automator), made for OSCP. This tool uses bash to automate most of the enumeration proces
SUDO_KILLER - A tool designed to exploit a privilege escalation vulnerability in the sudo program on Unix-like systems. It takes advantage of a specific misconfiguration or flaw in sudo to gain elevated privileges on the system, essentially allowing a regular user to execute commands as the root user.
awesome-oscp - A curated list of awesome OSCP resources