<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threat Modeling on securecode.dev</title><link>https://securecode.dev/tags/threat-modeling/</link><description>Recent content in Threat Modeling on securecode.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://securecode.dev/tags/threat-modeling/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Security Risks in SaaS Platforms</title><link>https://securecode.dev/insights/ai-security-risks-in-saas-platforms/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/ai-security-risks-in-saas-platforms/</guid><description>&lt;p>AI-enabled SaaS features often get reviewed as isolated prompts or model calls, but the meaningful risk usually sits in the surrounding application workflow. Permissions, tenant boundaries, tool execution, retrieval pipelines, and output handling all matter more than the model alone.&lt;/p></description></item><item><title>Threat Modeling Modern APIs</title><link>https://securecode.dev/insights/threat-modeling-modern-apis/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/threat-modeling-modern-apis/</guid><description>&lt;p>Threat modeling APIs is often reduced to a short checklist around authentication and transport security. That rarely surfaces the issues that matter most. Real API risk tends to come from workflow design, trust assumptions between services, and weak authorization at object or action boundaries.&lt;/p></description></item><item><title>Practical Product Security Reviews</title><link>https://securecode.dev/insights/practical-product-security-reviews/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/practical-product-security-reviews/</guid><description>&lt;p>Product security reviews are easy to make expensive and hard to make useful. A review that produces a long list of generic best practices may look thorough while still failing to help the team make better decisions.&lt;/p></description></item></channel></rss>