A peer told me recently that AI governance is bullshit. I’ve heard this before. It’s a common misconception when our industry believes that governance is about policy. It is not. It's about continuous control and evidence from beginning to the end, while building resilience.
Part that builds resilience isn’t the model itself, it’s the entire harness including tools and infrastructure around it. Driving 417 kmh on the German highway isn’t illegal and not a problem, if you have continuous governance and proactive resilience built within and around your car including the driver and the infrastructure. It’s easier said than done.
Continuous AI execution is easy. Continuous AI governance is extremely hard. That doesn’t make it unnecessary. It makes it an even more important problem worth solving.
While plenty of governance people assume security will sort itself out on its own, and plenty of security experts believe AI governance is bs, both are wrong.
This last week made the cost of that argument obvious in so many ways I can't keep track of, including the US govt. yanking Fable 5 to “allow it to be released again.”
But here are some more highlights that prove we need AI governance and controls: a GitHub repo whose only crime was a helpful error message that handed a stranger a developer's credentials without a single line of malicious code, a Munich court made Google personally liable for a lie its own AI told about a real company, and a drone maker calmly confirmed that ten machines sent toward Bakhmut had no way to be called back.
None of that is a checkbox problem.
Assume chaos. Build resilience. I have said it before and I’ll say it again:
In the world of agentic AI, it means three key things:
- Assume chaos
- Verify across agentic AI lifecycle
- Build elements of resilience
Governance that's checkbox failed long before agentic AI came into the picture. You are definitely not going to succeed with the checkbox approach now.
True AI governance is about the evidence, or lack of it, that someone was still in control when the system broke and that control was enforced.
It is about observability of how your AI behaves under different scenarios and what you control when it drifts.
It is about the sovereignty and who actually owns your data.
It is about the reskilling bet that needs to be made more often, faster.
It is about who is liable when your AI is the one that lied or went horribly wrong.
It’s about many more questions that can’t be answered with either policy or technology alone.
This edition is what that AI governance control looks like in five different rooms this month, and what it costs the people who assumed they already had it.

Welcome to The Predictability Factor by Monica Talks Cyber, a deep dive and POV at the intersection of AI, Security, Privacy and Tech, written by a hacker and CISO, to help you Go From Chaos to Resilience in The World of AI.
Today’s edition of The Predictability Factor by Monica Talks Cyber, covers:
If you haven’t already, do me a favour, subscribe and help me make an even bigger impact. Let’s dig in!

Quick Updates
🫣 I know, I’ve been away. I went completely off-grid to enjoy the UK summer, since we moved here around 2 years ago. Best time to do it is when it’s scorching hot I guess.
As I came back, I went straight to the AI panel I was invited to speak at on AI governance and resilience in cybersecurity, hosted by Elevata VC and NinetyOne UK. Here are the three key things I talked about:
Data governance and sovereignty - I cover a part of it in this week’s edition
Assume chaos and build resilience - This is the no. 1 advise I give to enterprises
Human in the loop vs. human oversight - They are not the same. Human-in-the-loop is not scalable. More on it later.

Pic from the AI and Cyber Event in London, where I spoke on the panel
My opening keynote from the biggest tech and cyber conference in Bratislava is coming out soon on my YouTube channel. Feel free to subscribe if you don’t want to miss it.

The next LIVE cohort of my AI Governance and Security Accelerator starts next week. It’s a 6-week cohort will real-world examples, practical and hands-on learning you need in your role, if you are at all working with AI governance, security, risk, or compliance. Last few seats left. Enroll now to join. If you aren’t going off-grid and want to use this quiet summer time to skill up, this is your opportunity.
P.S. If you’ve already enrolled, you’ll receive emails in the next days with further details.

No Bug, Just Bait
Data Governance | Strategy & Leadership | Culture & Literacy | GRC | Controls & Engineering
Researchers at Mozilla's 0DIN lab did not write a single line of malicious code. Yet the attack succeeded.
So here’s what happened. In a proof of concept published in June 2026, Mozilla’s research lab built a completely ordinary looking GitHub repository. A complete clean README with standard setup instructions. A Python package that behaves exactly like every package you have ever installed, including the part where it fails on the first run, throws an error and is kind enough to tell you exactly how to fix that failure.
You clone the repo.
Ask the AI agent to set it up.
The setup looks completely normal.
The agent installs the requirements, runs the setup.sh
It sees and fixes the one error it throws and you're done.
While all that happens the attacker has a reverse shell into your machine, along with your credentials.
That error message itself is the attack. Your agent, Claude Code, being so helpful fixes that error and in doing so, it resolves the DNS TXT record and executes whatever comes back, which is exactly what hands over a reverse shell to the attacker. The error that your Claude Code was being so helpful to fix for you, is exactly where things go wrong. The repo never had the malicious command. It was in the DNS entry, the thing that hands your credentials, your keys and your machine to a remote attacker along with a complete reverse shell.
You cannot fix this at a model layer. The agent did exactly what it was supposed to.
That’s why AI governance and implementation matters. No status analysis tool would have caught this. That is the part about agentic AI that should worry you more than the exploit itself.
That fix is the damn attack that opens a reverse shell on the attacker's machine.
From there, the attacker owns everything that user owns: API keys, cloud credentials, SSH access, whatever secrets lived in that environment.
Agentic coding tools have access to everything they need for this: private data, including environment variables, credentials, API keys, and local configuration files.
The malicious code never touched the repository. Not the README, not the package, not a single commit. It lived in a DNS record, fetched at runtime, invisible to code review, invisible to static scanners, invisible to the coding agent's own pre execution checks.
Your regular supply chain controls won’t even detect this issue, let alone respond to it. Indirect prompt injections like these are harder to detect. Every untrusted data, no matter where it sits, is a potential attack vector for your agent.
As I've said it always and I'll say it again, preventative controls were never enough pre agentic AI era, they are definitely not going to be enough now.
Reduce the blast radius, but even that’s not enough.
Add detection and response, because eventually things will go wrong even beyond your control.
Build resilience and add observability and predictability in advance as a proactive measure.

The Moat Nobody Owns
Data Governance | Strategy & Leadership | Culture & Literacy | GRC | Controls & Engineering
Alex Karp went on CNBC on July 1st and said the enterprise AI industry has gone "completely wrong."
Karp's argument: the model was never the moat. Control over your compute, your data stack, your alpha, that's the moat. He is exactly right. He's also using that exact argument to sell you Palantir's new sovereign AI engine, built with NVIDIA, the same week as this interview. The man warning you not to trust an AI vendor with your data is asking you to trust him with it instead. Hypocrisy? Maybe. But that's the whole game right now, especially after the Trump administration pulled the plug on Fable 5 before releasing it again.
I have watched companies misunderstand sovereignty for decades.
Just because T-systems builds a Microsoft datacenter in Germany doesn't make German companies, using it, sovereign. With AI, the mistake is deeper, and it is no longer just a regulated-industry problem.
Upgrade to Continue Reading
Become a paying subscriber of The Predictability Factor to get access to this post and other premium-only content including bonuses
Upgrade NowAlready a subscriber? Sign in
A subscription gets you:
- Free access to premium content
- The Ultimate Enterprise AI Governance and Security Maturity Playbook
- My 7-Step enterprise AI roadmap with 50+ real-world examples, actionable insights, 5 key pillars for governance and security, and more







