I have spent years in cybersecurity. I know the past, I see the present, and I am convinced the future holds a revolution in how we think about security itself.
But before the numbers, a word about where I come from, because the argument I am making is not abstract to me. It is the conclusion of five-plus years spent in the trenches across web hosting, telecom, and surveillance technology, and through work that took me to multiple countries on international assignments. I did not arrive at this position from a whiteboard. I arrived at it from customer tickets, incident rooms, and code.
Where I come from
My path started at the bottom of the stack, in the place where security is most real: customer support. Support teaches you something a research paper cannot. You learn where things actually break, and how ordinary people get hurt by systems that were designed to be convenient rather than safe.
From there, the work moved outward and deeper:
- 2021–2023: Loopia, web hosting Technical support and security recommendations for customers and internal staff. The role covered both the physical side (routines, access control, incident handling) and the digital side: account security, web application protection, DNS and domain security.
- 2022–2024: Huawei, HarmonyOS and Huawei Mobile Services A research program focused on security analysis of mobile ecosystems, auditing API surfaces, and identifying vulnerability classes. It ran in parallel with my Loopia role through 2022 and 2023 and finished in 2024.
- 2024–2025: Dahua Technology, cloud security Work on the civilian product line: security review of cloud services, access control, and protection of user data in distributed environments.
Every stop on that road pointed at the same conclusion. The industry keeps bolting layers onto systems that were never built to be safe, and then wonders why the pile keeps growing.
I want to kill the antivirus
I want to kill it and replace it with a revolutionary kind of system: one that defends itself.
In other words, the hacker has to invest more than the victim stands to lose. For the attacker, there is then no reason to bother.
What is the difference? Traditional operating systems were designed in the sixties and seventies. Not the code itself, but the architecture and the founding ideas. Security was never embedded in them, simply because no one required it. So you get the operating system layer, applications on top, and security, in the form of antivirus, bolted onto the very top.
Where Boot2Desk fits
Boot2Desk is my own entry in this direction. It is a temporary, security-focused desktop built on Debian 13, designed so that an intruder has as little room to work with as possible. Read the full Boot2Desk article.
It follows the same logic as everything above. Security is not a layer on top; it is part of the construction. Six independent security layers protect the environment:
- Wayland isolation and desktop portals Limit how applications interact with the desktop and reach the user’s resources.
- Firejail sandboxes Applications such as Firefox ESR and Remmina run sandboxed.
- AppArmor Limits what each process may reach.
- seccomp Filters the system calls each process may make.
- nftables firewall, default-deny Blocks everything not explicitly allowed.
The system runs entirely from RAM. The whole environment is copied into memory at boot, the medium can then be removed, and nothing is written to the host’s disk. That means very little code and state for an attacker to exploit, and if one component is compromised, the others do not automatically fall with it.
That is the fortress, not the house of cards, at the scale of a single endpoint. And it is built from public Debian sources, so the security rules are decided and reviewable before anything is assembled. This is security in practice, not on paper.
The mission
I have built this competence the way most real competence is built: through practical work with security review, incident handling, and system development, complemented by continuous study in fields that move fast. Boot2Desk itself is ongoing education, theory turned into practice, where every security layer has to be defended against real attack scenarios.
I report vulnerabilities as I find them, and the goal never changes: make it harder for attackers by shrinking the attack surface, not by adding more layers on top of an insecure system.
I believe the cyber world of the future will be built on systems that defend themselves. That is the mission: to change the world, and to help the world build its future on that foundation, on machines that are too costly to break rather than machines that are patched forever.
Thank you for reading.