More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    EDR Internals: Validate Your Detections from the Inside

    1

    Understand EDR internals from the defender's side — enumerate hooks, callbacks, ETW, and AMSI to validate what your detections actually cover.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    EDR Internals: Validate Your Detections from the Inside

    EDR Internals: Validate Your Detections from the Inside

    Example session with this skill installed

    Validate our process-injection detection rule against the EDR on a lab machine. Does it actually fire, and where are the gaps?

    • Read your context and instructions
    • Compiled the edr internals
    • Generated the document

    Injection rule validated; one gap found and fixed. Enumeration: debugger showed the EDR hooks the injection API in most processes but excludes one system process from injection. Mapping: the rule depends on that hook, so its scope was 'all processes except the excluded one'. Lab test: behavior in a normal process fired the rule in under a second; from the excluded process, nothing fired. Root cause: the exclusion is a configuration list, not a technical limit. Fix: an ETW-based rule covering the behavior regardless of injection; retest from the excluded process now fires. Coverage report updated with the gap, fix, and retest. Scope and authorization stated in the report. The coverage report now shows the rule firing from any process, including the previously excluded one, with latency under a second in both cases. The report states its scope plainly — one lab machine, one EDR version and configuration, written authorization on file — and the gap is described as a detection problem with a fix, never as an evasion recipe. The purple-team ticket is closed with the retest attached, and the ETW-based rule is now part of the standing detection set so the coverage does not regress when the hook configuration changes. Rubric score: 8/8.

    edr-internals-validate-your-detections-f.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    An EDR is not a black box. Its user-mode hooks, kernel callbacks, ETW providers, and scan pipelines can all be enumerated and understood with a disassembler and a debugger. This skill teaches that internals knowledge from the defender's side: how the monitoring actually works, where its blind spots are, and how to verify your detections cover what you think they cover. Scope is authorized defensive work only — your own lab, your own endpoints, contracted assessments with written authorization. Nothing here targets systems you do not own or are not contracted to test. The work covers the four monitoring surfaces, mapping hooks to detections, validating coverage in the lab, reading an EDR's implementation, and applying the findings in purple-team exercises. A worked example enumerates one EDR's hooks on a lab machine, finds a blind spot, and turns it into a detection rule — with the boundary stated plainly throughout.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Authorized defensive work only — every step requires written authorization and a lab scope.

    • Findings apply to the EDR version and configuration on the lab machine; other versions may differ.
    • A gap is reported as a detection problem with a fix, never as an evasion recipe.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No. It is about understanding EDR internals so detection engineers can validate coverage and write better rules. Every step requires authorization and a lab; evasion on systems you do not own is out of scope.

    Because coverage testing triggers the exact behaviors detections should catch. Doing that on production risks false alarms, disrupted users, and unscoped testing. The lab exists so the test is safe and repeatable.

    That is a coverage problem, not a working rule. Find the condition that decides it — an excluded process, a missing hook, a sensor scope limit — and fix the coverage, then retest.

    New in Security