Who writes Liaison
LAST UPDATED 16 NOV 2026I’m Paul Bernabeu. I write every issue of Liaison, and I built this site, the signup and the weekly website check myself. I’m a student in Fontainebleau, France.
Liaison is for people who run a small business and have nobody whose job is security. Once a week it takes one real attack and says what happened, whether your business is exposed, and what to do about it.
Where each story comes from
- I start from attacks that are confirmed, not predicted: the US cyber agency’s list of flaws used in real attacks (CISA KEV), the vendors’ own security advisories, and published incident reports.
- I pick the one most likely to reach a small business: a website, an email account, a phone, a tool your team already uses.
- Every fix in an issue is the vendor’s own recommendation, and the advisory is linked next to it so you can check it yourself.
- I read the sources. I don’t test the flaws on anyone’s systems.
Corrections
If something in an issue is wrong, write to studio@liaison.vision. A person reads it. A confirmed mistake is corrected on the issue’s page in the archive.
What Liaison is not
It is free. It has no ads and no sponsored stories, and the emails carry no tracking pixels. It is information, not advice for your particular systems: the legal notice says who publishes it and the privacy page says what happens to your address.
Where to find me
On LinkedIn, where I post one attack a week between issues. Questions and story tips are welcome there or by email.
Subscribe to Liaison · Read the past issues · Check your website