ad_mindmap_scenarios.jsonl

{"instruction": "Stolen VPN credential allowing remote access: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Public-facing web app with possible misconfiguration: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Public-facing web app with possible misconfiguration", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Exposed remote management interface reachable: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Exposed remote management interface reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Stolen VPN credential allowing remote access: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Exposed remote management interface reachable: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Exposed remote management interface reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Public-facing web app with possible misconfiguration: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Public-facing web app with possible misconfiguration", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Phishing foothold on user workstation: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Phishing foothold on user workstation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Stolen VPN credential allowing remote access: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Exposed remote management interface reachable: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Exposed remote management interface reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Stolen VPN credential allowing remote access: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Public-facing web app with possible misconfiguration: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Public-facing web app with possible misconfiguration", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Exposed remote management interface reachable: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Exposed remote management interface reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Stolen VPN credential allowing remote access: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Search non-destructively for credential material in user profiles and browser stores.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Supplier/third-party compromise suspected: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Supplier/third-party compromise suspected", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Public-facing web app with possible misconfiguration: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Public-facing web app with possible misconfiguration", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "User opened document with embedded macro: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "User opened document with embedded macro", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Phishing foothold on user workstation: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Phishing foothold on user workstation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Compromised webmail session token obtained: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Compromised webmail session token obtained", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 3: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 4: Map the local network perspective and identify what domain resources are reachable.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 3: Enumerate visible services and shares without altering state to avoid noisy detection.\n\nStep 4: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "OAuth app consent token acquired: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "OAuth app consent token acquired", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Map the local network perspective and identify what domain resources are reachable.\n\nStep 3: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nStep 4: Search non-destructively for credential material in user profiles and browser stores.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Stolen VPN credential allowing remote access: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Stolen VPN credential allowing remote access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with defenders to capture telemetry for each test to validate detection capabilities.\n\nStep 3: Map the local network perspective and identify what domain resources are reachable.\n\nStep 4: Assess potential for lateral movement from this host and prioritize targets accordingly.\n\nDefender detection notes:\n\n  - Unusual inbound/external sessions, new device profiles in VPN logs.\n\n  - EDR alerts on document macro execution or unknown process creation.\n\nMitigations & hardening:\n\n  - Enforce phishing-resistant MFA and stricter session controls.\n\n  - Harden endpoints and restrict execution of macros from untrusted sources.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain-joined VM with read access to DC info: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain-joined VM with read access to DC info", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to a multi-share file server: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to a multi-share file server", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 3: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Ability to perform internal DNS queries: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Ability to perform internal DNS queries", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Identify critical hosts (DCs, CAs, backup servers) and plan lab-focused follow-ups.\n\nStep 4: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Read-only view into asset inventory/CMDB: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Read-only view into asset inventory/CMDB", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 3: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nStep 4: Prioritize targets that are likely to yield credentials or privileged access.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network foothold with standard user rights: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network foothold with standard user rights", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prioritize targets that are likely to yield credentials or privileged access.\n\nStep 3: Use passive discovery sources first (DNS, ARP, CMDB) to map the environment.\n\nStep 4: Enumerate directory objects that are accessible and capture LDAP responses for analysis.\n\nDefender detection notes:\n\n  - Increased LDAP or DNS query patterns from an atypical host.\n\n  - Access to internal inventory systems from non-standard accounts.\n\nMitigations & hardening:\n\n  - Restrict directory query capabilities and monitor access to inventory systems.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "DPAPI masterkeys located for certain profiles: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "DPAPI masterkeys located for certain profiles", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Correlate artifacts with logs to determine timeline and scope.\n\nStep 4: Document detection opportunities and recommend telemetry to capture similar activity.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 4: Correlate artifacts with logs to determine timeline and scope.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Potential LSASS artifacts on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Potential LSASS artifacts on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Avoid live testing against production services; validate techniques in a replica environment.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Browser tokens present in user profile: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Browser tokens present in user profile", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 3: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Preserve artifacts and copy them for offline analysis in a lab.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Backups containing sensitive account data: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Backups containing sensitive account data", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Preserve artifacts and copy them for offline analysis in a lab.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Config files referencing service credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate artifacts with logs to determine timeline and scope.\n\nStep 3: Document detection opportunities and recommend telemetry to capture similar activity.\n\nStep 4: Avoid live testing against production services; validate techniques in a replica environment.\n\nDefender detection notes:\n\n  - Unusual process memory access or credential-dump related telemetry.\n\n  - Unexpected access to backup or config repositories.\n\nMitigations & hardening:\n\n  - Apply Credential Guard, limit backup access, and harden DPAPI storage.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Accounts flagged with no-preauth: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Accounts flagged with no-preauth", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Accounts flagged with no-preauth: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Accounts flagged with no-preauth", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Accounts flagged with no-preauth: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Accounts flagged with no-preauth", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service Principal Names (SPNs) enumerated: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service Principal Names (SPNs) enumerated", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Accounts flagged with no-preauth: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Accounts flagged with no-preauth", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Cross-forest trust relationships exist", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Accounts flagged with no-preauth: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Accounts flagged with no-preauth", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nStep 4: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Constrained delegation entries present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.\n\nStep 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.\n\nStep 4: Validate ticket lifetime policies and monitor for abnormal ticket requests.\n\nDefender detection notes:\n\n  - Abnormal increases in ticket requests or requests for uncommon services.\n\nMitigations & hardening:\n\n  - Enable pre-auth where feasible and enforce short ticket lifetimes.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Group Policy object references embedded credentials: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Group Policy object references embedded credentials", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 4: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Service runs as SYSTEM with writable components", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unquoted service path suspected on host: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unquoted service path suspected on host", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Legacy Unix SUID misconfigurations present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Legacy Unix SUID misconfigurations present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.\n\nStep 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.\n\nStep 4: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.\n\nDefender detection notes:\n\n  - Unusual modifications to service binaries or creation of new scheduled tasks.\n\nMitigations & hardening:\n\n  - Apply least-privilege to services, fix unquoted paths, and enforce code signing.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Access to an internal web application that can act as pivot: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Access to an internal web application that can act as pivot", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Valid low-priv domain user credentials present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Valid low-priv domain user credentials present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nStep 3: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 4: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Local admin on one host available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Local admin on one host available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory reachable hosts and identify administrative interfaces and services used for administration.\n\nStep 3: Ensure defenders capture relevant telemetry (authentication events, process creation, network flows).\n\nStep 4: Plan low-noise lateral attempts in a lab before exercising any live action in production.\n\nDefender detection notes:\n\n  - Unusual remote process execution patterns across multiple hosts.\n\n  - Authentication events from uncommon source hosts for user accounts.\n\nMitigations & hardening:\n\n  - Restrict legacy administrative protocols and enforce modern authentication.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Domain admin compromise confirmed for lab simulation: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Domain admin compromise confirmed for lab simulation", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Long-lived service account available for assessment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Long-lived service account available for assessment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nStep 3: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 4: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "GPO modification rights discovered for some accounts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "GPO modification rights discovered for some accounts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Catalog potential persistence mechanisms and evaluate forensic artifacts each creates.\n\nStep 3: Document removal steps and test clean-up procedures to verify defenders can restore systems.\n\nStep 4: Simulate persistence in an isolated lab and ensure the blue-team can detect the artifacts.\n\nDefender detection notes:\n\n  - Changes to group policies, replication anomalies, or strange certificate issuance events.\n\nMitigations & hardening:\n\n  - Harden GPO authorizations, monitor for unauthorized changes, and enforce change control on privileged actions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "EDR product blocking common tooling: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "EDR product blocking common tooling", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "EDR product blocking common tooling: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "EDR product blocking common tooling", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "EDR product blocking common tooling: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "EDR product blocking common tooling", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "EDR product blocking common tooling: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "EDR product blocking common tooling", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Network IDS with strict thresholds: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Network IDS with strict thresholds", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "EDR product blocking common tooling: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "EDR product blocking common tooling", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 3: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nStep 4: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Host-level script execution control enabled: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Host-level script execution control enabled", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based experiments to evaluate stealth approaches without bypassing protections in production.\n\nStep 3: Assess which telemetry sources are capturing blocking events and identify false positives for tuning.\n\nStep 4: Work with defenders to understand detection logic and provide labeled samples for rule refinement.\n\nDefender detection notes:\n\n  - Alerts for script blocking or process termination logged by EDR.\n\nMitigations & hardening:\n\n  - Keep endpoint protections up to date; use allowlisting and strong application control policies.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Need to simulate ransomware-style impact: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Need to simulate ransomware-style impact", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nStep 4: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Limited egress bandwidth environment: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Limited egress bandwidth environment", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 3: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large sensitive dataset present on fileshare: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large sensitive dataset present on fileshare", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan mock impact exercises that demonstrate potential business impacts without destructive actions.\n\nStep 3: Validate blue-team detection of suspicious data aggregation and unusual outbound patterns.\n\nStep 4: Simulate staging of data within an isolated lab, capturing file access and process telemetry.\n\nDefender detection notes:\n\n  - Large sequential file reads from atypical accounts or hosts.\n\n  - Anomalous outbound connections to unknown external endpoints or DNS tunneling patterns.\n\nMitigations & hardening:\n\n  - Enforce DLP rules for sensitive file access and restrict direct outbound connections from critical hosts.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "M365 tenant with many apps and OAuth consents: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "M365 tenant with many apps and OAuth consents", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 3: Enumerate identity and application configuration in a read-only manner.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD tenant with conditional access: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Azure AD tenant with conditional access", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate identity and application configuration in a read-only manner.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Azure AD Connect server present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Azure AD Connect server present", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Plan lab-based OAuth/consent simulations to help defenders tune detections.\n\nStep 3: Validate multi-factor and conditional access coverage for high-risk accounts.\n\nStep 4: Enumerate identity and application configuration in a read-only manner.\n\nDefender detection notes:\n\n  - Unusual token issuance or refresh patterns in identity logs.\n\nMitigations & hardening:\n\n  - Harden app consent policies, require admin consent for high-privilege scopes, and monitor identity logs.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM site with many distribution points: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "SCCM site with many distribution points", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM site with many distribution points: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "SCCM site with many distribution points", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nStep 3: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM site with many distribution points: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "SCCM site with many distribution points", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nStep 3: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nStep 3: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM admin console reachable: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "SCCM admin console reachable", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nStep 3: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "SCCM site with many distribution points: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "SCCM site with many distribution points", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Simulate client push or package deployment workflows in lab to validate detection and access controls.\n\nStep 3: Inventory SCCM roles and distribution point capabilities and document secrets exposure possibilities.\n\nDefender detection notes:\n\n  - Unexpected package deployments or changes in SCCM job logs.\n\nMitigations & hardening:\n\n  - Restrict access to SCCM roles and harden distribution point permissions.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Enterprise CA present with many templates: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Enterprise CA present with many templates", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate who has enrollment rights and whether those rights are excessive.\n\nStep 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nStep 3: Validate who has enrollment rights and whether those rights are excessive.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate who has enrollment rights and whether those rights are excessive.\n\nStep 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nStep 3: Validate who has enrollment rights and whether those rights are excessive.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nStep 3: Validate who has enrollment rights and whether those rights are excessive.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Enterprise CA present with many templates: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Enterprise CA present with many templates", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nStep 3: Validate who has enrollment rights and whether those rights are excessive.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Enterprise CA present with many templates: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Enterprise CA present with many templates", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate who has enrollment rights and whether those rights are excessive.\n\nStep 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nStep 3: Validate who has enrollment rights and whether those rights are excessive.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Web enrollment services available", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate who has enrollment rights and whether those rights are excessive.\n\nStep 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Enterprise CA present with many templates: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Enterprise CA present with many templates", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Validate who has enrollment rights and whether those rights are excessive.\n\nStep 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.\n\nDefender detection notes:\n\n  - Unusual certificate issuance or renewal outside of maintenance windows.\n\nMitigations & hardening:\n\n  - Harden CA role membership, restrict template edit/issue rights, and audit certificate issuance.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Anomalous certificate issuance logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Unexpected use of administrative utilities across many hosts: What step-by-step, lab-first actions and telemetry should a red-team and blue-team collect in an authorized test?", "input": "Unexpected use of administrative utilities across many hosts", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nStep 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 4: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Large-scale LDAP brute force attempts detected in logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Large-scale LDAP brute force attempts detected in logs", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.\n\nStep 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.\n\nStep 4: Tune detection rules with labeled data from lab reproductions to reduce false positives.\n\nDefender detection notes:\n\n  - Recurring patterns of similar failed authentication across many accounts.\n\nMitigations & hardening:\n\n  - Implement cross-source correlation, logging retention, and analytic playbooks for common attack flows.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Coordinating blue-team telemetry collection: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Coordinating blue-team telemetry collection", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Define clear scope, rules of engagement, and escalation contacts.\n\nStep 4: Establish emergency stop procedures and communication channels.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Define clear scope, rules of engagement, and escalation contacts.\n\nStep 3: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 4: Establish emergency stop procedures and communication channels.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Define clear scope, rules of engagement, and escalation contacts.\n\nStep 3: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 4: Establish emergency stop procedures and communication channels.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Define clear scope, rules of engagement, and escalation contacts.\n\nStep 4: Establish emergency stop procedures and communication channels.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}
{"instruction": "Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders.", "input": "Red-team exercise kickoff", "output": "Step 1: Confirm authorization and scope before proceeding.\n\nStep 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.\n\nStep 3: Establish emergency stop procedures and communication channels.\n\nStep 4: Define clear scope, rules of engagement, and escalation contacts.\n\nDefender detection notes:\n\n  - Ensure logging/configuration is preserved for post-exercise analysis.\n\nMitigations & hardening:\n\n  - Document and obtain written authorizations before activities.\n\nNote: High-level, non-actionable guidance intended for authorized lab assessments and defender tuning."}