<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cortex-Agents on Kevin Keller</title><link>https://kevinkeller.org/tags/cortex-agents/</link><description>Recent content in Cortex-Agents on Kevin Keller</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>kellerkev@gmail.com (Kevin Keller)</managingEditor><webMaster>kellerkev@gmail.com (Kevin Keller)</webMaster><copyright>© 2026 Kevin Keller</copyright><lastBuildDate>Fri, 13 Nov 2026 11:30:00 +0000</lastBuildDate><atom:link href="https://kevinkeller.org/tags/cortex-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Snowflake XDR: A Fully Automated SIEM and SOC, Run by Cortex AI in One Snowflake Account</title><link>https://kevinkeller.org/posts/snowflake-xdr-fully-automated-soc-cortex-ai/</link><pubDate>Fri, 13 Nov 2026 11:30:00 +0000</pubDate><author>kellerkev@gmail.com (Kevin Keller)</author><guid>https://kevinkeller.org/posts/snowflake-xdr-fully-automated-soc-cortex-ai/</guid><description>An art-of-the-possible project: a fully automated XDR where Cortex AI writes the detections, maps new log sources, triages, investigates, writes the reports and requests the response, all inside one Snowflake account. Humans step in only where a wrong decision is expensive, and one switch stops it all.</description></item><item><title>No Service Accounts: Langdock to Snowflake Cortex Agents as the Signed-In Employee</title><link>https://kevinkeller.org/posts/langdock-snowflake-per-user-identity-cortex-agents/</link><pubDate>Fri, 13 Nov 2026 03:30:00 +0000</pubDate><author>kellerkev@gmail.com (Kevin Keller)</author><guid>https://kevinkeller.org/posts/langdock-snowflake-per-user-identity-cortex-agents/</guid><description>A tested reference architecture for connecting an enterprise AI chat platform to Snowflake Cortex Agents through the managed MCP server, so every question runs as the employee who asked it, with their row access, their masking and their name in the audit trail.</description></item><item><title>Cortex Agents in Microsoft Sentinel: Closing the AI Blind Spot in Your SIEM</title><link>https://kevinkeller.org/posts/cortex-agents-microsoft-sentinel-siem/</link><pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate><author>kellerkev@gmail.com (Kevin Keller)</author><guid>https://kevinkeller.org/posts/cortex-agents-microsoft-sentinel-siem/</guid><description>Microsoft Sentinel&amp;rsquo;s native Snowflake connector shows your SOC logins and queries, but nothing about what Cortex Agents did. Here&amp;rsquo;s a reference implementation that sends agent traces, token usage and access history into Sentinel, so analysts can follow an agent conversation down to the data it touched.</description></item><item><title>From SAML Login to Snowflake as the User: Entra ID Passthrough Without the Secondary-Role Trap</title><link>https://kevinkeller.org/posts/snowflake-saml-oauth-passthrough-entra-id/</link><pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate><author>kellerkev@gmail.com (Kevin Keller)</author><guid>https://kevinkeller.org/posts/snowflake-saml-oauth-passthrough-entra-id/</guid><description>Your web app signs users in with SAML, and now it needs to query Snowflake as each user. A SAML assertion can&amp;rsquo;t be exchanged for an OAuth token, and the usual role-any shortcut leaves every other role active, ACCOUNTADMIN included. A tested pattern with Entra ID: a silent OIDC hop, role-scoped tokens, and a second External OAuth integration that puts Snowflake in charge of which roles the app may use.</description></item></channel></rss>