Menu

Individual skill

xdr-pro

0upvotes

Operate extended detection and response — correlating endpoint, identity, network, and cloud telemetry into unified incidents.

skills/xdr-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
53
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

XDR extends EDR's endpoint visibility across domains — identity, email, network, cloud — correlating them into unified incidents with a single investigation timeline. The promise is real: attacks that look benign in any single telemetry source become obvious in combination. The risk is also real: XDR marketed as "the SOC in a box" leads to underinvestment in the analysts and processes that make correlation valuable.

This skill covers operating XDR well: cross-domain correlation design, incident-queue management, tuning across sources, and honest measurement of what the platform adds over standalone tools.

Think in attack stories, not alerts: XDR's value is connecting the phish click (email) to the credential use (identity) to the anomalous process (endpoint) to the data staging (cloud) into one incident. Configure and tune for story completeness — a correlated incident missing the identity half is a story with the motive removed.

## When to use

- Unifying detection across endpoint, identity, email, and cloud telemetry.
- Reducing alert fatigue through correlation (many alerts → one incident).
- Building cross-domain investigation workflows for analysts.
- Evaluating XDR platform claims against your actual telemetry needs.