Pentest
External and internal perimeter. Scanning, recon, attack chains — with a report, not just "found a hole".
22/tcpopen
80/tcpopen
443/tcpopen
3306/tcpfiltered
...scanning
Networks that hold up. And those that don't.
Pentest and infrastructure. I test perimeters, map topologies, and build systems that stay up — while finding what shouldn't be there.
› whoami
pentester · network builder
› hostname -f
lab.finn.meme
› ▊
01
about
Just a card — not an agency, not a ten-page resume. I work in security and networks: finding gaps, testing perimeters, wiring infrastructure so it doesn't fall apart on Monday morning.
VLANs, firewalls, VPN, monitoring, homelabs — that's the terrain.
pentest
recon · exploitation · reporting
netops
topology · routing · hardening
linux
servers · containers · automation
02
focus
Networks
Design and build: segmentation, routing, VPN, DNS. Traffic goes where it should.
Hardening
Close what's open, set policies, logging and monitoring. Better to find issues yourself than wait for an incident.
ALLOW 10.0.0.0/8 → 443
ALLOW vpn → internal
DENY * → *
policy: default deny
03
stack
› ls ./offensive/
nmapmasscanburp metasploitsqlmapnikto
› ls ./network/
wiresharkiptablesnginx bindopenvpnansible
› cat os
Debian · Arch · anything with a penguin
Map first
Understand topology and attack surface before touching anything.
Document it
Diagrams, configs, reports — so it still makes sense six months later.
Lab it
Test on benches, not on prod on a Friday night.
04