mid-engagement-ir-detection

Detect and document security-state changes during monitored red-team engagements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill mid-engagement-ir-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mid-engagement-ir-detection
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/mid-engagement-ir-detection
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill mid-engagement-ir-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn mid-engagement changes in a target’s behavior into defensible, deliverable security findings instead of mistakenly treating recheck failures as false positives.

Core Features & Use Cases

  • Pre/post state fingerprinting: Capture timing, response size, headers, cookies, and lockout indicators before active testing, then compute deltas after the session or upon first failed recheck.
  • SOC-patch and control-depth interpretation: Distinguish whether behavior changes are consistent with WAF rule deployment versus code-layer fixes, using structured rechecks and variant probes.
  • Operational IR evidence packaging: Convert observed state changes (including detection-induced rate limiting and concurrent attacker activity) into report-ready findings with evidence discipline and templates.
  • Use Case: During an authorized red-team exercise, you confirm an SQLi and later notice response timing and headers changing; use this Skill to document both the confirmed vulnerability window and the client’s real-time mitigation behavior as separate findings.

Quick Start

Use this Skill when running an active, monitored engagement and response patterns shift during your test so the AI captures a pre-patch fingerprint, detects state changes, validates what changed with targeted rechecks, and writes an audit-grade report with a timeline.

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 document a vulnerability that stops reproducing during a red-team engagement?

To document mid-engagement behavior changes, you capture pre-test fingerprints for timing, headers, and lockout indicators, compute state deltas upon first failed recheck, and generate an audit-grade timeline distinguishing WAF-layer mitigation from code-layer fixes.

How do I distinguish a WAF rule deployment from a code-layer fix during incident response?

Distinguishing WAF rule deployment from code-layer fixes involves capturing pre/post state fingerprints of response headers and timing, applying structured variant probes to validate the mitigation layer, and packaging the delta as an evidence-preserving finding.

What is the best way to report M365 lockout and rate-limit changes observed during active testing?

The best way to report M365 lockout and rate-limit changes is to capture baseline lockout indicators before testing, append observations to an immutable journal during the session, and convert the state delta into a report-ready finding.

Does incident response evidence packaging work for concurrent attacker activity on monitored systems?

Incident response evidence packaging handles concurrent attacker activity by using delta-based interpretation to separate your red-team actions from other operational state changes, ensuring the final report reflects true client mitigation behavior.

Why do I need pre-test fingerprint capture for security-state changes?

Pre-test fingerprint capture is needed because it establishes the baseline for timing, response size, and headers before active testing, allowing accurate delta-based interpretation when behavior shifts mid-engagement instead of treating recheck failures as false positives.