<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LLMs |</title><link>https://sanaamironov.com/tags/llms/</link><atom:link href="https://sanaamironov.com/tags/llms/index.xml" rel="self" type="application/rss+xml"/><description>LLMs</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><image><url>https://sanaamironov.com/media/sharing.png</url><title>LLMs</title><link>https://sanaamironov.com/tags/llms/</link></image><item><title>Mapping LLM Risks in Identity Workflows</title><link>https://sanaamironov.com/blog/llm-identity-risk-mapping/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://sanaamironov.com/blog/llm-identity-risk-mapping/</guid><description>&lt;p&gt;Identity workflows are sensitive because they connect people, permissions, access, and institutional trust. When LLMs enter those workflows, the risk surface changes.&lt;/p&gt;
&lt;p&gt;A useful risk mapping does more than list threats. It connects technical failure modes to security outcomes, governance responsibilities, and concrete controls. That is why frameworks such as OWASP LLM Top 10 and NIST CSF 2.0 are useful starting points.&lt;/p&gt;
&lt;p&gt;The goal is not to reject LLM-enabled tools. It is to understand where they can help, where they can fail, and what evidence teams need before trusting them in identity-related decisions.&lt;/p&gt;</description></item></channel></rss>