About Me

Hello, I’m Dima and in the past few years I have become the AISecurityGuy (This means I am handling a lot of discussions with customers about securing their AI applications).

Welcome to my corner of the internet.

I am a Security Specialist and Architect by trade, currently working as a Security Solutions Architect at Google cloud.

While my day job involves helping organizations architect secure, scalable cloud solutions, my passion lies at the bleeding edge where Artificial Intelligence meets Cybersecurity. This blog is my dedicated space to explore that intersection—unfiltered and hands-on.

Why I Started This Blog #

We are living through a super exciting time.. AI is not just changing how we build software; it is fundamentally altering the threat landscape.

I started this journey because I realized that “best practices” for AI security are still being written. I didn’t want to just read about them; I wanted to test them, break them, and rebuild them.

Here, you won’t just find high-level theory. You will find my personal field notes, the vulnerabilities I’m researching, and the practical defense strategies I’m engineering in real-time.

What You Can Expect #

I write for security engineers, developers, and curious architects who want to go beyond the buzzwords. My focus includes:

• Adversarial AI: detailed research into how LLMs and AI agents can be manipulated—and how to stop it.
• The Blue Team Perspective: practical architectures for securing AI workloads on the cloud.
• From the Trenches: lessons learned from real-world successes (and the occasional frustrating failure).

Let’s Connect #

I am always looking to debate ideas or collaborate on research with fellow security professionals. If you want to chat about the latest prompt injection technique or discuss cloud security architecture, feel free to reach out via the social links on the homepage.

Disclaimer #

> Note: While I am a Google Cloud employee, the views, opinions, and code snippets expressed on the-ai-security-guy.com are strictly my own. They do not reflect the official policy, position, or roadmap of Google or Google Cloud.