Skip to content
WRITE-UPS ▸ 0 PUBLISHED STATUS ▸ FIRST ONE IN DRAFT

WRITE-UPS

Step-by-step write-ups of security challenges I've worked through: what I tried, what I found, and the detection I'd set up so it gets caught next time.

§01INDEX

  • CASE 001
    TryHackMe
    Title withheld until release Being written up now. Follow along to catch it when it's published.
    ● IN DRAFT
Follow on GitHub ↗ Follow on LinkedIn ↗

§02HOW EACH WRITE-UP IS STRUCTURED

hover the hidden lines to read them
  1. 00Summary
  2. 01Scope & setup
  3. 02Recon
  4. 03Findings
  5. 04Detection
  6. 05Lessons
PLATFORMDIFFICULTYTOOLS USED
The name of the challenge date · reading time · tools
00

Summary

Two or three sentences: what the target was, what I found, and the one thing a defender should take away.

01

Scope & setup

What I was allowed to test, and how my lab or virtual machine was set up.

02

Recon

What I looked at first and why, keeping only the output that mattered.

EXAMPLE COMMAND 
$ nmap -sC -sV -oN scan.txt <target>
03

Findings

Each step of the way in, the evidence for it, and the dead ends worth mentioning.

04

Detection

The log, Wazuh rule or Suricata signature that would have caught this.

EXAMPLE RULE 
alert http any any -> $HOME_NET any (msg:"<rule>"; sid:1000001;)
05

Lessons

What I would do differently, and what it taught me about the defender side.