Writing
IT posture, infrastructure fundamentals, and the patterns that keep showing up.
A place to collect thinking on IT posture, infrastructure fundamentals, and the kinds of problems that appear in practice across different organisations and sectors. Most of it is observational. Some of it is opinionated. None of it is sponsored.
Posts
-
Fable 5 is back, and so is the technique that got it pulled.
The US ordered two Anthropic models pulled worldwide for three weeks, over a jailbreak every major lab could already reproduce. A fabrication plant stays where you put it. A demonstrated technique does not, and the people left exposed are rarely the intended target.
-
Every vendor assumes they're the only vendor
Every vendor's setup guide assumes it's the only one editing your SPF record. Ten years of correct, unrelated five-minute changes can quietly cross a hard limit none of them mentioned, and it's already happened to one domain in four we scanned.
-
Not all cybercrime starts cyber
Two years of a previous tenant's mail landing at my address, a bank statement here, an ASIC pack there, today their Medicare cards, adds up to most of what someone would need to convincingly be them. No password was guessed.
-
The most expensive way to answer a simple question
I held the button, said a few search terms, and wanted the results page back. What I got was Gemini, thinking, then a paragraph answering a question I had not asked. That default is spreading.
-
The one email a wine club depends on, sitting in the one folder nobody checks.
A winery's club emails were landing in spam, failing for a share of members every cycle with nothing bounced and no one told. I scanned 124 wineries to see how common silent email authentication failure really is.
-
The first outage I caused.
The first real outage I caused wiped the NTFS permissions off every home folder in the company. What I remember most is the colleagues who stayed back and rebuilt it with me.
-
The cause is usually older than the trigger, and sometimes the cause is you.
A technically correct Group Policy change took months to surface as missing files and lost trust across dozens of profiles. The trigger is recent. The cause is older, and it was me.
-
Event Logs and the Story Behind Every Incident.
Most systems are already telling you what went wrong, quietly, in the event logs, long before anyone notices. Reading them well is less about event IDs than trusting how systems narrate their own behaviour.
Research
Sector scans of email authentication, run against public DNS and published with the data. The research hub pools every scan into one picture, and how the scans work sets out what is read and what each figure means.
-
Email authentication in Australian financial advisers
A scan of 66 advisers, July 2026
-
Email authentication in Australian real estate agencies
A national scan of 234 agencies, June 2026
-
Email authentication in Australian wineries
A scan of 124 independent wineries across five regions, June 2026
-
Email authentication in Australian law firms
A national scan of 252 independent firms, June 2026
The longer pieces and the research live here, on the site. Shorter observations go out more often on LinkedIn, but this is where the work and every figure it cites keeps its home.
Let's talk.
If you want to work together, book a call below. If you would rather write first, email me and I will get back to you.