About

WHAT

This site is a pentesting and offensive security reference: checklists, service-specific notes, exploitation steps, and tool cheatsheets Content follows a rough engagement flow from pre-engagement through reporting with a “Notes” section for standalone tool pages (think mini-manuals) and some other, complex distilled material.

Although less of a priority, there are likely still lab notes (those are generally very rough) and maybe old versions of my former cheatsheets as I migrate that information into this main web. The “Docs” section is likely to be of greatest use for anyone else.

WHY

This site is MY personal reference first for reference, practice, and cybersecurity exams (e.g. HTB’s CPTS). Often times, it is difficult to remember command syntax or the exact complexities of a technique or tool. This is written for me and my utility first, though it could be a useful reference for others (though there are better sites that I try to include as References near the top of the pages).

Although it lives within my own private devices, I have it public for easy reference wherever I might be in case I don’t have said devices. Sometimes the live version will lag a little behind my local source.

Disclaimer

All pages are first written by me manually and then sometimes structured or formatted with AI like putting info into tables or trying to match the general “style” of the whole website. Only a minority were mostly generated by distilling messy notes into something usable (and those should be noted on their respective pages). This is not “AI slop” per se, but AI was used – expect a mix of human voice and maybe tool-assisted editing quirks, and most importantly, always verify commands and logic in your own environment.

Quirk of the Sometimes Missing Table of Contents

Because this site uses Hugo to generate a static pages from Markdown sources, only the bottom-level pages (at its lowest level) will have a Table of Contents and its respective button appear at the top left of the navigation bar to find the page sections. This is a Hugo limitation that I may or may not fix since there are already multiple means of navigation and searching:

  • search function via:
    • built-in website (site-wide)
    • CTRL+F browser (within whatever smaller context you are currently viewing)
  • navigation via:
    • a single, “megapage” of all the content nested into it or smaller “metapages” of categorical sections
    • the navigation section on the left
    • individual pages for the specific tool, technique, or procedure
    • table of contents for those individual pages

For instance, if want to navigate a very large page like the Active Directory one, you must navigate directly to that page at its lowest level (not the other higher-level pages that nest its content) in order to use the TOC.

This website was birth from the idea of a single page cheatsheet, but it later became obvious after a few versions that that idea was unmaintable and difficult to use for reference or search due to size and egregiously long TOCs:

  • what if… I want to only search the mimikatz commands in the context of Active Directory – well, I can go the Active Directory page and easily CTRL+F it
  • what if… I want to find all references ever, even in my labs, of that one-off command I used only once, but I don’t remember where… use the built-in website search
  • what if… I want to follow a general, chronological process to an engagement… well the built-in navigation bars gives a rough progression overall and the individual page TOCs are normally ordered from start to finish of an idea (references -> enumeration -> technique execution -> more complex things -> etc.)