This blog is where I document what I have learned securing networks, investigating cybercrime and studying security at graduate level, written so that practitioners can reuse it and decision-makers can act on it.
Why I write
I spent fifteen years on both sides of the security problem. As a helpdesk technician and later head of a network and sysadmin team at a Belgian federal agency, I was responsible for keeping systems patched, accounts tidy and users aware of phishing. As a Chief Detective at the Belgian Federal Computer Crime Unit, I saw what happens when those basics fail: dark-web markets, crypto-asset fraud and the forensic work needed to reconstruct an attack after the fact.
That experience taught me that most incidents are not exotic. They come from misconfigurations, missing updates, weak identity controls and unclear processes. Good documentation prevents a surprising share of them, which is why this blog exists.
What you will find here
- Network and systems hardening — practical configurations and checklists for Windows, Linux and network devices.
- Cloud networking and identity — Azure architecture, hybrid identity and access management, and the controls that matter most.
- Automation — using Python, Ansible and containers to make secure configurations repeatable.
- Investigations and forensics — lessons from real-world casework, explained without disclosing sensitive details.
- Research and trends — my graduate work at the University of Central Florida, including AI-assisted threat modeling, and analysis of current security news.
Principles
- Accuracy first. I test what I publish where I can, cite my sources and correct mistakes openly.
- Responsible disclosure. I do not publish exploit code or details that could harm people or organisations, and I never share information from investigations.
- Useful to two audiences. Each article aims to give engineers something they can apply and managers something they can decide on, a balance shaped by my Global Executive MBA at Paris 1 Panthéon-Sorbonne.
If a topic would help your team, or you would like to discuss a role, get in touch.