authentication-tracing

Trace Entra ID authentication flows to distinguish fresh MFA from token reuse.

231|64|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/SCStelz/security-investigator --skill authentication-tracing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: authentication-tracing
Source: https://github.com/SCStelz/security-investigator/tree/main/.github/skills/authentication-tracing
Command: npx skills add https://github.com/SCStelz/security-investigator --skill authentication-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs forensic analysis of Entra ID authentication flows to determine whether suspicious sign-ins reflect legitimate MFA activity or credential/token theft.

Core Features & Use Cases

  • Forensic analysis of SessionId chains to distinguish legitimate activity from credential theft.
  • IP progression and geographic anomaly assessment using Investigation JSON ip_enrichment data.
  • Step-by-step workflows for tracing interactive MFA versus token reuse across SigninLogs and AADNonInteractiveUserSignInLogs.

Quick Start

Run an authentication tracing analysis after running a user investigation to map signins to SessionId values.

Frequently Asked Questions about authentication-tracing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace Entra ID sign-ins to detect token reuse?▼

Trace Entra ID sign-ins to detect token reuse by analyzing SessionId chains across SigninLogs and AADNonInteractiveUserSignInLogs. This process distinguishes fresh MFA activity from credential theft by mapping interactive events against non-interactive token usage.

What is forensic analysis of SessionId chains in Entra ID?▼

Forensic analysis of SessionId chains is the process of tracking authentication flows to determine if a sign-in required fresh MFA or reused a previous token. It identifies token theft by evaluating interactive MFA events against subsequent non-interactive sessions.

How do I assess geographic anomalies in Microsoft Entra ID sign-in logs?▼

Assess geographic anomalies in Entra ID sign-in logs by analyzing IP progression using pre-generated investigation JSON ip_enrichment data. This maps geographic movements within SessionId chains to detect impossible travel or suspicious token usage locations.

Do I need a pre-generated investigation JSON to trace authentication flows?▼

Yes, you need a pre-generated investigation JSON to provide the ip_enrichment data required for geographic anomaly assessment. You must run a user investigation first to map sign-ins to SessionId values before starting the authentication tracing workflow.

Does this authentication tracing workflow analyze AADNonInteractiveUserSignInLogs?▼

Yes, this authentication tracing workflow analyzes AADNonInteractiveUserSignInLogs alongside SigninLogs. It compares interactive MFA events with non-interactive token reuse across both log sources to provide a repeatable forensic workflow for identifying credential theft.