customcrypto

Security, systems,
and the occasional
tool.

A place for writing on security engineering, infrastructure, and the tools that fall out of it. Long-form posts live at blog.customcrypto.com; everything else is a repository and a few notes on how things actually work.

01

What lives here

Three things, loosely related: things learned, things broken, things built.

This site is a notebook. Some of it is long-form writing — postmortems, design notes, and explanations of how a piece of infrastructure or a protocol actually works. Some of it is tooling that grew out of a problem and turned into a repository. And some of it is reference material: commands, configs, and defaults.

The blog lives at blog.customcrypto.com. The code behind it changes language as the work demands — Python for glue, C when it needs to sit close to the metal, V because it's fun, and whatever else earns its place. The source for everything else is on GitHub.

02

Areas of Expertise

i.e. how I make a living

Program governance

  • CIS Controls
  • NIST CSF
  • NIST SP 800-61
  • SOC 2
  • ISO 27001

Offensive

  • Penetration testing
  • Web application testing
  • Purple teaming
  • Adversary emulation
  • Threat modeling

Defensive

  • SIEM & log pipelines
  • Incident response
  • Vulnerability management
  • Threat intelligence
  • Forensics & investigation

Cloud & infrastructure

  • Microsoft Azure
  • Amazon AWS
  • Windows & RedHat
  • Debian / Ubuntu / Kali
  • Networking

Identity & endpoint

  • PKI
  • MDM
  • IAM (Okta, Entra ID)
  • SSO & SCIM
  • OAuth 2.0
  • EDR

Software & AI

  • DevSecOps
  • Secure code review
  • Scripting: Bash, Python, PowerShell
  • AI risk management
  • Model & data governance
03

Writing

Long-form posts on security engineering, systems work, and the tools that came out of them.

Blog

blog.customcrypto.com

Postmortems, design notes, and explanations of how the infrastructure underneath actually works — the kind of thing that is easier to write down than to remember.

Read the blog Security · Systems · Tooling

On the docket

  • Postmortems — what broke and what the fix actually changed
  • Design notes — how the log pipeline got built
  • Tooling — small programs that solve real problems
  • Field notes — ICS/OT, identity, and the unglamorous middle
04

Code

Public repositories, mostly tooling. Some useful, some only useful to me.

Browse all repositories python, c, and shell — plus whatever else fits
05

Both sides

"If you know the enemy and know yourself, you need not fear the result of a hundred battles."

Blue

The Shield

  • Detection engineering and log pipeline design
  • Incident response and recovery
  • Identity, PKI, and endpoint hardening
  • Cloud and network auditing
  • Monitoring and detection

Red

The Sword

  • Web application and network penetration testing
  • Adversary emulation and C2 tradecraft
  • Purple team exercises and detection validation
  • Application security and code analysis
  • Thinking like the person on the other side
06

Off hours

The parts of the practice that never made it into a report.

Locks and lockpicking

Physical security is the oldest kind of security, and the locks still teach things about threat modeling that software rarely does.

Breaking things

HackTheBox labs, CTFs, and the particular satisfaction of a working exploit that nobody expected to work.

New languages

Opinions change fast. The curiosity doesn’t — I pick up whatever looks worth learning and drop it when it stops paying.