performing-user-behavior-analytics

Detects anomalous user behavior using SIEM baselines, impossible travel analysis, and statistical z-scores.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-user-behavior-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-user-behavior-analytics
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/soc-operations/performing-user-behavior-analytics
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-user-behavior-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SOC teams struggle to identify compromised accounts and insider threats that evade rule-based detection. This Skill builds behavioral baselines from 30-90 days of authentication and access logs, then flags deviations like impossible travel, off-hours logins, abnormal data access volumes, and privilege abuse.

Core Features & Use Cases

  • Behavioral Baselining: Builds per-user statistical profiles (login hours, IPs, countries, apps) from historical SIEM data using Splunk SPL queries.
  • Anomaly Detection: Detects impossible travel via GeoIP distance/speed calculations, off-hours access via baseline deviation, data exfiltration via z-score analysis, and privilege abuse via host-count anomalies.
  • Risk Scoring: Aggregates multiple anomaly signals into a composite risk score weighted by user priority for investigation prioritization.
  • Use Case: A SOC analyst suspects credential compromise after unusual O365 login alerts. Run the impossible travel and off-hours detection queries to confirm a login from Moscow two hours after a New York login, then escalate with a composite risk score.

Quick Start

Use this skill to build user behavior baselines from the last 30 days of authentication logs and flag any impossible travel or anomalous login activity in the past 24 hours.

Frequently Asked Questions about performing-user-behavior-analytics

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

FAQPage Schema
How do I detect impossible travel logins in Splunk?

Use iplocation on source IPs, then streamstats to compare consecutive logins per user, computing haversine distance divided by time difference. Flag events where speed exceeds 900 km/h and distance exceeds 500 km, after excluding known VPN and proxy ranges.

What is UEBA and how does it detect insider threats?

UEBA (User and Entity Behavior Analytics) builds statistical baselines of normal user activity from 30-90 days of logs, then flags deviations using z-scores. It catches insider threats like abnormal file download volumes or off-hours access that rule-based detection misses.

What data do I need before running UEBA detection queries?

You need at least 30 days of authentication logs (VPN, O365, Windows Security events) normalized to CIM, a GeoIP database like MaxMind GeoLite2, and identity enrichment data such as department, role, and manager for peer comparison and risk weighting.

Why does impossible travel detection generate false positives?

Corporate VPN egress, cloud/CDN IPs, and mobile carrier CGNAT make GeoIP locations jump geographically for legitimate sessions. Exclude known VPN/proxy ranges and verify GeoIP accuracy before escalating alerts.

What are the limitations of behavioral baseline detection?

Baselines can be poisoned if attacker activity exists in the training window, and low-activity accounts produce unstable statistics with near-zero standard deviation. Require minimum event counts, floor the stdev, and rebuild baselines from known-good periods after confirmed incidents.