<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Identity-Threat - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/identity-threat/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 02 Nov 2026 15:08:37 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/identity-threat/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Microsoft Entra ID: Managed Device Client Sign-In to Graph Enumeration</title><link>https://feed.craftedsignal.io/briefs/2026-11-entra-id-graph-enumeration/</link><pubDate>Mon, 02 Nov 2026 15:08:37 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-entra-id-graph-enumeration/</guid><description>Identification of a pattern where a non-interactive Microsoft Entra ID client sign-in, characterized by managed device context and an Edge user agent, is followed by the use of the same access token by a scripted client to perform directory enumeration via Microsoft Graph.</description><content:encoded>&lt;p>This threat brief describes a detection pattern for unauthorized Microsoft Graph API usage. It correlates non-interactive Microsoft Entra ID sign-ins (asserting managed, Azure AD joined device context and an Edge user agent) with subsequent activity where the exact access token is used by a scripted client to query at least three distinct directory-enumeration paths in Microsoft Graph. This approach utilizes the unique token identifier to correlate activity, rather than relying on session identifiers.&lt;/p>
</content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cloud-security</category><category>identity-threat</category><category>privilege-escalation</category><category>persistence</category></item></channel></rss>