Salesforce and Nvidia’s new reasoning model is everything the AI labs should fear
Salesforce and Nvidia launch Koa, Salesforce's first reasoning model, built on Nvidia's open-weight Nemotron and post-trained on synthetic sales and support data.
Salesforce announced Koa at Dreamforce, its first reasoning model, built on Nvidia's open-weight Nemotron and post-trained with synthetic data mimicking sales and customer-support scenarios rather than real customer data. Koa will be offered through the Agentforce platform's AI gateway as a cheaper, token-efficient alternative to closed frontier models like Claude and ChatGPT for enterprise tasks. Salesforce simultaneously announced a ClaudeForce partnership with Anthropic keeping customer data inside Salesforce's infrastructure.
‘Now We Can Know Everything and Do Anything,’ Jensen Huang Says at Dreamforce
Salesforce unveiled Koa, its first CRM reasoning model post-trained on NVIDIA Nemotron 3 Super, announced during Jensen Huang's Dreamforce keynote.
At Salesforce Dreamforce, NVIDIA CEO Jensen Huang joined Marc Benioff onstage as Salesforce announced Koa, its first CRM reasoning model, post-trained from NVIDIA Nemotron 3 Super using NeMo RL, NeMo Gym, and NeMo AutoModel. Koa was fine-tuned on a proprietary synthetic dataset drawn from nearly three decades of enterprise CRM deployments across 14+ industries, with no customer data used in training or inference. On Salesforce's CRM Bench of real-world tasks, Koa matches or exceeds leading model performance on CRM actions with 3x fewer errors. Koa already powers an employee agent in Slack, enters customer pilots in October with Formula 1, UChicago Medicine, Baxter Credit Union, 1-800Accountant, Engine, and Xero, and reaches general availability in Winter 2026 in U.S. regions.
AI is changing what Salesforce security needs to govern
WithSecure's Trust Mapping paper proposes a framework for governing trust relationships across Salesforce workflows, AI agents, integrations and connected SaaS systems.
WithSecure's paper 'Navigating Trust in the Modern Salesforce Ecosystem' introduces a Trust Mapping Framework spanning five domains: entities, information, connections, actions and system outcomes. It applies to Salesforce, Agentforce, Headless 360, third-party SaaS and AI-assisted workflows where users, AI agents, APIs and integrations form trust relationships. A Discovery step maps relationships, a Governance step assesses, restricts or retires them, and the paper defines 'trust drift' such as stale credentials, excessive access and unvalidated AI recommendations.
Who's governing your AI? A trust framework for enterprise agents and models
DigiCert pitches AI Trust framework using PKI, DNS policy records and workload identity to govern shadow AI agents across enterprises.
The Register-sponsored piece outlines DigiCert's AI Trust framework for governing AI agents, built on PKI, DNS, and attestation, citing IBM's 2026 Cost of a Data Breach report that 68% of organizations lack AI governance or shadow AI detection. The approach treats agent identity as workload identity aligned with IETF WIMSE, NIST CSF 2.0, and SPIFFE/SPIRE, using short-lived credentials instead of static API keys. DigiCert also proposes DMARC-style DNS agent policy records and an AI Agent Passport cryptographically binding agent identity to approved operations, with a unified kill switch.
One in four MCP servers opens AI agent security to code execution risk
Noma Security whitepaper finds most popular AI Skills and many MCP servers carry high-risk capabilities, with state changes most prevalent.
Noma Security analyzed hundreds of popular MCP servers and Skills across eight risk categories, finding most widely used Skills carry at least one risky characteristic and a typical enterprise runs well over a hundred high-risk agent tools, with arbitrary code execution common across MCP servers. The most prevalent risk is the ability to change state or data, and named toxic combinations include ContextCrush data leakage, ForcedLeak via poisoned Salesforce CRM records, DockerDash supply-chain compromise, the Replit production database deletion, and the hijacked Amazon Q VS Code extension. Building on OWASP LLM06:2025, the paper proposes the No Excessive CAP framework of capabilities, autonomy, and permissions, recommending allowlisting, MCP version pinning, approval gates on irreversible actions, and user-scoped expiring credentials.