welcome to techical journaling
Why I'm keeping a public technical journal — and what topics it'll cover.
This is the first post in what I expect to be a long-running public working journal. The premise is simple: I write things down so I can search them later.
The point isn’t authority — it’s record-keeping.
Why a public journal
Most of what makes cloud security work — the actual production reality — lives in private Slack threads, post-mortem docs, and that one teammate’s notebook. None of it is searchable, none of it is shared, and most of it gets lost the moment someone changes teams.
This is my attempt to put some of it on the open web. Field-tested notes on:
- CNAPP operations — CSPM, CWPP, CIEM tooling (Prisma Cloud / Cortex Cloud)
- IAM drift — entitlement reviews, layered policy drafts, the gaps between what we think is set and what actually is
- CVE triage — how alerts flow into Layer-1 drafts and become enforceable rules
- Incident post-mortems — short, technical write-ups after bad days
- Multi-cloud posture — AWS + Azure, what works, what doesn’t
- Dev workflow + tooling — the small things that compound
What you’ll find here
Note
This is not a tutorial series. Posts are written fast and published as soon as they’re useful — usually unpolished. I optimize for grep, not readability.
Typical post formats:
- Field note from a real investigation (with redacted screenshots)
- A small tool or script that saved me an hour
- An incident retrospective (with the actually-useful parts)
- A short opinion on a CVE or policy change
Practical stuff
RSS — there’s an RSS feed at /rss.xml for anyone who wants to
follow along without checking the site.
Contact — desktop_onsite@aol.com if something’s worth saying in
private. Replies may be slow.
Hosting — the site itself is a static build deployed to Cloudflare
Pages. Total cost so far: $0. The whole write-up of how I set that up
is the second post.
That’s it for the intro. Next post: the full story of how this very site ended up deployed for free.