Skill

detecting-insider-threat-with-ueba

From asi

Implements UEBA using Elasticsearch/OpenSearch to build behavioral baselines, compute anomaly scores, peer group analysis, and detect insider threats like data exfiltration and privilege abuse.

Python

security

npx claudepluginhub plurigrid/asi --plugin asi

Tool Access

This skill uses the workspace's default tool permissions.

Preview

User and Entity Behavior Analytics (UEBA) moves beyond static rule-based detection to model normal behavior for users, hosts, and applications, then flag statistically significant deviations that may indicate insider threats. Using Elasticsearch as the analytics backend, this skill covers building behavioral baselines from authentication logs, file access events, and network activity, computing...

SKILL.md

Similar Skills

detecting-insider-threat-with-ueba

5.9k

Implements UEBA with Elasticsearch/OpenSearch to build behavioral baselines, compute anomaly scores via z-score and peer analysis, and detect insider threats like data exfiltration.

3 files

cybersecurity-skills

detecting-insider-threat-with-ueba

Implements UEBA with Elasticsearch/OpenSearch to build user behavior baselines, compute anomaly scores via z-score and peer groups, and detect insider threats like data exfiltration and privilege abuse.

3 files

cybersecurity-skills-zh

performing-user-behavior-analytics

Performs UEBA to detect anomalous user activities like impossible travel, unusual access patterns, privilege abuse, and insider threats using Splunk SIEM baselines and statistical analysis. For SOC teams spotting compromised accounts.

asi

Stats

Parent Repo Stars16

Parent Repo Forks5

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Detecting Insider Threat with UEBA

Overview

When to Use

When investigating security incidents that require detecting insider threat with ueba
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques

Prerequisites

Elasticsearch 8.x or OpenSearch 2.x cluster with security audit data
Log sources: Active Directory authentication, VPN, DLP, file server access, email
Python 3.9+ with elasticsearch client library
Baseline period of 30+ days of normal user activity data
Defined peer groups based on department, role, or job function

Steps

Step 1: Ingest and Normalize Activity Logs

Configure log pipelines to ingest authentication, file access, email, and network logs into Elasticsearch with a unified user identity field.

Step 2: Build Behavioral Baselines

Calculate per-user baselines for login times, data volume, application usage, and access patterns over a rolling 30-day window using Elasticsearch aggregations.

Step 3: Calculate Anomaly Scores

Compare current activity against baselines using z-score deviation and peer group comparison to generate per-user risk scores.

Step 4: Correlate and Alert

Combine multiple anomalous indicators (unusual hours + large downloads + new system access) into composite risk scores that trigger SOC investigation workflows.

Expected Output

JSON report containing per-user risk scores, anomalous activity details, peer group deviations, and recommended investigation actions.