Direct
- Email: matias@zapf.dev — the best way to reach me, and the one I actually read.
- LinkedIn: linkedin.com/in/zapf
- GitHub: github.com/MatiasZapf — issues and pull requests on any of my repositories are welcome and usually get a faster response than email.
- X: @MatiasZapf
I read everything that arrives. I answer most of it, though not always quickly — I work on this site and its projects around a Cyberdefense degree, so replies come in bursts rather than on a schedule.
What I am glad to hear about
- Corrections. If something on this site is wrong — a misread CVE, a technique mapped to the wrong ATT&CK ID, a detection rule that would not fire — please tell me. Corrections are the most useful mail I get, and they are welcome bluntly.
- Questions about something I wrote. If a post or an atlas node left you stuck, the gap is probably in my explanation rather than in your reading, and I would like to know where.
- Work and collaboration in security engineering, detection, or data — especially anything where the interesting part is making a system reliable rather than making a demo.
About errors on this site
Everything here is written while learning in public. Posts and atlas nodes get corrected in place when I get something wrong, and the change is visible in the repository rather than quietly overwritten.
Comments on blog posts run on GitHub Discussions via Giscus, so a public correction on a post is also welcome and stays attached to it.
Automated clients
If you are an agent or a crawler rather than a person, start at /llms.txt: it indexes every page
on the site, and any page is available as clean markdown by appending .md to its URL. The
usage policy for AI systems is in the privacy page and declared
machine-readably in robots.txt.