Build, secure, defend.
Almost everything I do revolves around those three verbs. My background is in cloud deployment and systems administration, so I first learned to build infrastructure (microservice architectures on AWS and Azure, databases, caching, orchestration with Kubernetes) and to automate it with CI/CD pipelines on GitHub and GitLab.
Specialising in cybersecurity took that practice towards a DevSecOps approach: embedding controls into the development cycle itself, with code analysis, dependency scanning and container review before anything reaches production.
Then I learned to defend what I had built.
I have built complete Blue Team environments: SIEM with Wazuh and its detection rules, response automation through SOAR, OPNsense firewalls, EDR and VPN, plus honeypots exposed to the internet. Coming from systems administration gives me an edge here: once you know what a healthy machine looks like, you spot what falls outside the norm much sooner.
But what really hooks me is what happens after the attack.
My honeypot takes real intrusion attempts every day, and each one leaves a trail to reconstruct: where it got in, which commands it ran, what it downloaded and how far it went. For that I rely on memory analysis and the MITRE ATT&CK framework, which lets me classify every move by known tactics and techniques.
And what comes out of it doesn't stay in the lab: I report the attacking IP addresses and upload the malware samples to public threat intelligence platforms, including several binaries no antivirus engine had recorded before.
In fact...
Latest trainingAdvanced Vocational Training Specialization Course on Cybersecurity in Information Technology Environments (EQF 5C)
Prior trainingHigher Technician in Computer Network Systems Management (EQF 5)
FocusDFIR, SOC, Secure infrastructure
LanguagesSpanish nativeBulgarian nativeEnglish C1-C2French A1Russian A1