Blog

Test notes.

What we found, how it worked and how to fix it. Written by the testers, with client names taken out.

One new note a month

Tester crouched at an open network cabinet, a laptop cabled to a firewall appliance

The host nobody remembers is still the easiest way in

Old test servers and retired gateways rarely appear on an asset list. How we find them in the first day, and how to find them first.
Read the note
Tester's hands at a keyboard, a dark log console and a hardware key on the desk

Five settings that slow us down the most

Small Active Directory changes that turned a one-day path to domain admin into a week of noise.
Read the note
Hands on a keyboard under a network graph on a dark screen, a security key on the desk

Change one number, read another customer’s data

Broken object-level checks are simple to test by hand. Here is the routine we run on every API.
Read the note
Two testers reviewing a dark wall console together

Why a retest catches half-finished fixes

A patched host behind an unchanged rule is still open. What we check on day 38.
Read the note
Tester wearing a call headset at a steel bench in a dark test lab

What a phone test teaches a front desk

Nobody gets named and nobody gets blamed. How to turn the results into one simple call-back rule.
Read the note
Tester at a dark desk reading an attack path on a laptop

What the person who signs a red team should ask

Objectives, stop rules and who else knows. Six questions for the only person in the secret.
Read the note
Portrait of Jun Tanaka, a man in his thirties in glasses, lit by a dark terminal

The cloud role that outlived its project

Build pipelines collect permissions over time. A short review that removes most of them.
Read the note
1 2
Monthly test notes

One short email.

What we found and how to fix it. No sales mail.