Andoreatta Pentesting Notes and Methodology

Personal field notes for penetration testing, with an OSCP study track. The goal is practical recall: exact commands, prerequisites, and the edge cases that decide whether a technique works in a lab or on a real engagement.

How to use these notes

Each section card below says what the section covers and how many pages it holds. Use it to choose a track before you start reading.

• Studying a topic? Start with the section map below: Active Directory, Linux or Windows privilege escalation, Web Applications, or Protocols and Services.
• Need a command fast? Use the Command Checklist — phase-by-phase, copy-paste templates with placeholders.
• Stuck on a box? Use the Lab Field Manual — per-machine edge cases, a pattern library, and a machine index.
• Planning an engagement or the exam? Start with the Pentesting Methodology.
• Enumerating? The Information Gathering page covers the first pass; the Enumerating Attack Vectors pages are checklists.
• Looking for a term or command? Use the search in the header. It indexes the full text of every note; the tag index groups pages by topic.

Commands use placeholders such as <IP>, <USER>, and $TARGET. Replace them; never paste a placeholder into a live target.

Conventions

• $TARGET / <IP> — target address; $ATTACKER / <LHOST> — your attacker address.
• Commands are shown for Linux; adapt paths and package names on other distributions.
• “Exam note” callouts highlight behaviour that commonly differs between lab boxes and the exam (timeouts, lockouts, egress filtering, AV).
• Hashcat modes and tool names are checked against current tool releases (NetExec replaces CrackMapExec; Impacket scripts use the impacket- prefix).

Legal

These notes are a study aid, not an authorization. You are responsible for staying within the scope of your engagement, lab, or exam. The notes are published in English only.