instruction stringclasses 270
values | input stringlengths 3 214 | output stringclasses 297
values |
|---|---|---|
Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Avoid live testing against production services; validate techniques in a replica environment.
Step 3: Correlate artifacts with logs to determine timeline and scope.
Step 4: Preserve artifacts and copy them for offline analysis in a lab.
Defender det... |
Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Config files referencing service credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Avoid live testing against production services; validate techniques in a replica environment.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Correlate artifacts with logs to determine timeline an... |
Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Correlate artifacts with logs to determine timeline and scope.
Step 4: Preserve artifacts and copy them for offline analysis in a lab.
Defender detection n... |
Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Avoid live testing against production services; validate techniques in a replica environment.
Step 4: Correlate artifacts with logs to determine timeline an... |
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? | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Preserve artifacts and copy them for offline analysis in a lab.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Avoid live testing against production services; validate techniques in a replica env... |
Backups containing sensitive account data: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Preserve artifacts and copy them for offline analysis in a lab.
Step 3: Avoid live testing against production services; validate techniques in a replica environment.
Step 4: Correlate artifacts with logs to determine timeline and scope.
Defender det... |
Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate artifacts with logs to determine timeline and scope.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Avoid live testing against production services; validate techniques in a replica envi... |
Browser tokens present in user profile: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Avoid live testing against production services; validate techniques in a replica environment.
Step 4: Correlate artifacts with logs to determine timeline an... |
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? | Potential LSASS artifacts on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Avoid live testing against production services; validate techniques in a replica environment.
Step 3: Correlate artifacts with logs to determine timeline and scope.
Step 4: Document detection opportunities and recommend telemetry to capture similar a... |
Browser tokens present in user profile: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Preserve artifacts and copy them for offline analysis in a lab.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Correlate artifacts with logs to determine timeline and scope.
Defender detection n... |
Config files referencing service credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Config files referencing service credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Correlate artifacts with logs to determine timeline and scope.
Step 4: Avoid live testing against production services; validate techniques in a replica envi... |
Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Preserve artifacts and copy them for offline analysis in a lab.
Step 4: Correlate artifacts with logs to determine timeline and scope.
Defender detection n... |
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? | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Preserve artifacts and copy them for offline analysis in a lab.
Step 3: Correlate artifacts with logs to determine timeline and scope.
Step 4: Document detection opportunities and recommend telemetry to capture similar activity.
Defender detection n... |
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? | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Preserve artifacts and copy them for offline analysis in a lab.
Step 4: Avoid live testing against production services; validate techniques in a replica env... |
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? | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Avoid live testing against production services; validate techniques in a replica environment.
Step 4: Correlate artifacts with logs to determine timeline an... |
Potential LSASS artifacts on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Potential LSASS artifacts on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Avoid live testing against production services; validate techniques in a replica environment.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Preserve artifacts and copy them for offline analysis ... |
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? | Browser tokens present in user profile | Step 1: Confirm authorization and scope before proceeding.
Step 2: Document detection opportunities and recommend telemetry to capture similar activity.
Step 3: Preserve artifacts and copy them for offline analysis in a lab.
Step 4: Avoid live testing against production services; validate techniques in a replica env... |
Backups containing sensitive account data: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate artifacts with logs to determine timeline and scope.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Preserve artifacts and copy them for offline analysis in a lab.
Defender detection n... |
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? | Backups containing sensitive account data | Step 1: Confirm authorization and scope before proceeding.
Step 2: Preserve artifacts and copy them for offline analysis in a lab.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Avoid live testing against production services; validate techniques in a replica env... |
Config files referencing service credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Config files referencing service credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Correlate artifacts with logs to determine timeline and scope.
Step 3: Document detection opportunities and recommend telemetry to capture similar activity.
Step 4: Avoid live testing against production services; validate techniques in a replica envi... |
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? | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
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? | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
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? | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
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? | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Accounts flagged with no-preauth: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Accounts flagged with no-preauth | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
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? | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
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? | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Accounts flagged with no-preauth: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Accounts flagged with no-preauth | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Service Principal Names (SPNs) enumerated: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
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? | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
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? | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
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? | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Cross-forest trust relationships exist: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Service Principal Names (SPNs) enumerated: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
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? | Accounts flagged with no-preauth | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Service Principal Names (SPNs) enumerated: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
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? | Service Principal Names (SPNs) enumerated | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
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? | Accounts flagged with no-preauth | Step 1: Confirm authorization and scope before proceeding.
Step 2: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 3: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Cross-forest trust relationships exist: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Cross-forest trust relationships exist | Step 1: Confirm authorization and scope before proceeding.
Step 2: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Use lab simulations to test detection of Kerberos anomalies without exploiting live sy... |
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? | Accounts flagged with no-preauth | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Constrained delegation entries present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Validate ticket lifetime policies and monitor for abnormal ticket requests.
Step 4: Catalogue accounts and SPNs to estimate risk and likely attack su... |
Constrained delegation entries present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Constrained delegation entries present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Use lab simulations to test detection of Kerberos anomalies without exploiting live systems.
Step 3: Catalogue accounts and SPNs to estimate risk and likely attack surface.
Step 4: Validate ticket lifetime policies and monitor for abnormal ticket req... |
Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Assess service and file ownerships and whether ... |
Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Assess service and file ownerships and whether ... |
Legacy Unix SUID misconfigurations present: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Coordinate with patching and configuration owners to ... |
Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Coordinate with patching and configuration owners to ... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Coordinate with patching and configuration owners to ... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Assess service and file ownerships and whether ... |
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? | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
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? | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Reproduce the condition in a controlle... |
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? | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
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? | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
Service runs as SYSTEM with writable components: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Reproduce the condition in a controlle... |
Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Assess service and file ownerships and whether ... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Reproduce the condition in a controlle... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Coordinate with patching and configuration owners to ... |
Service runs as SYSTEM with writable components: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 4: Coordinate with patching and configuration owners to ... |
Group Policy object references embedded credentials: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
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? | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Assess service and file ownerships and whether ... |
Group Policy object references embedded credentials: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Group Policy object references embedded credentials | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
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? | Service runs as SYSTEM with writable components | Step 1: Confirm authorization and scope before proceeding.
Step 2: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Assess service and file ownerships and whether ... |
Unquoted service path suspected on host: Provide a detailed step-by-step red-team assessment plan (lab-first) and detection guidance for defenders. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
Unquoted service path suspected on host: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Reproduce the condition in a controlled lab to validate any escalation vector safely.
Step 4: Coordinate with patching and configuration owners to ... |
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? | Unquoted service path suspected on host | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Legacy Unix SUID misconfigurations present: In an authorized assessment, outline step-by-step lab-first evaluation and defender validation. | Legacy Unix SUID misconfigurations present | Step 1: Confirm authorization and scope before proceeding.
Step 2: Assess service and file ownerships and whether non-privileged users can alter execution paths.
Step 3: Coordinate with patching and configuration owners to plan remediation for misconfiguration findings.
Step 4: Reproduce the condition in a controlle... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.