After a suspicious service principal incident, one of the first triage questions is what else this identity can reach.
I published a new blog on how I used Microsoft Sentinel data federation and custom graphs to investigate hidden privilege paths without moving all of the supporting access context into the analytics tier.
In this example, I traced a rogue service principal to two high-value resources, a Key Vault and a storage account, using federated context that remained in ADLS Gen2.
My biggest takeaway is that a small number of well-structured context tables can go a long way in an investigation. That is not to say large-scale ingestion does not have its place, but when the goal is faster triage and clearer decision-making, the investigation question should help guide the design.
Microsoft is making it easier to work this way, and I’m excited to see where data federation and custom graphs go from here.
https://nineliveszerotrust.com/blog/sentinel-data-federation-custom-graphs/
#MicrosoftSentinel #MicrosoftSecurity #MicrosoftDefender #KQL #CloudSecurity






