How do I install the Detecting Insider Threat With Ueba skill?

Run npx skillmds@latest add gabrielmoreira/detecting-insider-threat-with-ueba in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Detecting Insider Threat With Ueba safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only, executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Detecting Insider Threat With Ueba?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Detecting Insider Threat With Ueba free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Detecting Insider Threat With Ueba?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Detecting Insider Threat With Ueba by gabrielmoreira

Name: Detecting Insider Threat With Ueba
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Detecting Insider Threat With Ueba

Implement User and Entity Behavior Analytics (UEBA) using Elasticsearch/OpenSearch to build behavioral baselines, calculate anomaly scores, perform peer group analysis, and alert on insider threat indicators such as data exfiltration, privilege abuse, and unauthorized access. Use when building or tuning a UEBA pipeline rather than a one-off manual hunt.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Detecting Insider Threat with UEBA

Overview

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 risk scores using statistical deviation and peer group comparison, and correlating multiple low-confidence indicators into high-confidence insider threat alerts.

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.

---name: detecting-insider-threat-with-uebadescription: Implement User and Entity Behavior Analytics (UEBA) using Elasticsearch/OpenSearch to build behavioral baselines, calculate anomaly scores, perform peer group analysis, and alert on insider threat indicators such as data exfiltration, privilege abuse, and unauthorized access. Use when building or tuning a UEBA pipeline rather than a one-off manual hunt.license: Apache-2.0--- # Detecting Insider Threat with UEBA ## Overview 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 risk scores using statistical deviation and peer group comparison, and correlating multiple low-confidence indicators into high-confidence insider threat alerts. ## 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.

Frequently asked questions