mid-engagement-ir-detection

Monitor and log security state changes during active red-team engagements.

13|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/pdparchitect/rook --skill mid-engagement-ir-detection-pdparchitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mid-engagement-ir-detection
Source: https://github.com/pdparchitect/rook/tree/main/skills/mid-engagement-ir-detection
Command: npx skills add https://github.com/pdparchitect/rook --skill mid-engagement-ir-detection-pdparchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of losing valid vulnerability findings when a client's security team (SOC) deploys mitigations mid-engagement, ensuring you capture both the vulnerability and the IR responsiveness as distinct, valuable findings.

Core Features & Use Cases

  • State-Change Tracking: Automatically monitors baseline response times and lockout counts to detect when a target's security posture shifts.
  • Evidence Preservation: Provides a structured methodology to document the original vulnerability PoC alongside the subsequent mitigation event.
  • Operational Metrics: Quantifies client IR effectiveness by measuring detection latency and mitigation depth (WAF vs. code-level).

Quick Start

Use the mid-engagement-ir-detection skill to initialize the baseline monitoring for the current target and begin logging engagement traffic for state-change analysis.

Frequently Asked Questions about mid-engagement-ir-detection

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

FAQPage Schema
How do I track vulnerability findings when SOC deploys mitigations mid-engagement?

Mid-engagement state-change tracking monitors baseline response times and lockout counts to detect target security posture shifts, preserving both the original vulnerability PoC and the subsequent mitigation event as distinct findings.

What is the best way to measure client incident response effectiveness during a red-team test?

Measuring client incident response effectiveness requires tracking detection latency and mitigation depth, quantifying whether the response involves WAF deployment or code-level fixes during active security auditing.

How do I document real-time WAF rule deployment during active red-team engagements?

Append-only logging of test results systematically documents real-time WAF rule deployment by recording baseline fingerprints and identifying temporal deltas in target behavior during concurrent attacker activity detection.

How does baseline fingerprinting detect concurrent attacker activity during security auditing?

Baseline fingerprinting detects concurrent attacker activity by establishing initial target response patterns and continuously monitoring for temporal deltas, enabling SOC monitoring to identify unauthorized shifts in security posture.

Why do I lose valid vulnerability findings when a client's security team deploys mitigations mid-test?

Valid vulnerability findings are lost when target state changes overwrite original proof-of-concept evidence, requiring systematic baseline monitoring and evidence preservation to capture both the vulnerability and IR responsiveness.

Does mid-engagement-ir-detection support monitoring security state changes without external dependencies?

Mid-engagement-ir-detection operates without external dependencies, using internal systematic baseline fingerprinting and append-only logging to monitor security state changes and validate vulnerability findings independently.