OECD.AI Wonk · July 16, 2026

HAIP is transforming transparency from a compliance burden to a competitive advantage

Why it matters

Salesforce’s Paula Goldman argues on the OECD.AI blog that the Hiroshima AI Process Reporting Framework can give organizations a common language for public AI-risk disclosures across jurisdictions and the expanding agentic-AI value chain.

My takeaway: This is an industry viewpoint rather than an OECD policy position. The practical value is a reusable reporting taxonomy: map each public commitment to an owner, evidence source, model or agent scope, update cadence, and jurisdiction-specific obligation.
Keep exploring

More curated notes connected through AI Compliance and Agent Security.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.

OWASP GenAI Security Project · tool

FinBot CTF Is Live: A Hands-On Companion to the OWASP GenAI Security Project

OWASP FinBot is a hands-on agentic-security CTF built around a simulated multi-agent financial-services platform with real tool access. Its challenges cover prompt injection, tool misuse, policy bypass, data exfiltration, privilege escalation, remote code execution, shared context, and compromised MCP servers.

NVIDIA AI Red Team · analysis

Mitigating Indirect AGENTS.md Injection Attacks in Agentic Environments

NVIDIA walks through a simulated Go dependency that detects Codex, writes a malicious AGENTS.md, redirects the coding task, and injects instructions intended to conceal the change from pull-request summaries. The post then maps the chain to dependency, configuration-integrity, monitoring, and guardrail controls.