id stringlengths 68 165 | instruction stringlengths 875 1.4k | input stringclasses 1
value | output stringlengths 93 5.2k | metadata dict |
|---|---|---|---|---|
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Let's break down how to identify common PowerShell obfuscation techniques used in malicious scripts.
### Base64 Encoding
Attackers often encode malicious commands in Base64 to evade simple signature-based detection.
* **Recognition:** Look for the `.NET` `[System.Convert]::ToBase64String()` method being used to en... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | You should **not decompile the PowerShell script**. Decompilation is typically for compiled code (like .NET executables) and is not directly applicable to PowerShell scripts.
Instead, you should **analyze the script for indicators of compromise (IOCs)**. This involves examining the script's content for malicious comma... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0003 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | The log excerpt indicates that the `Invoke-Obfuscation` tool failed to run. This is not a security event itself, but rather an error message from a PowerShell script.
**Possible Issues and Fixes:**
1. **PowerShell Execution Policy:** The most common reason for scripts failing to run is an overly restrictive PowerShe... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0004 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | The log snippet you provided is from a web server access log, not a PowerShell script execution log. It indicates a successful (HTTP 200) POST request to an `/execute-script` endpoint, with a response size of 1234 bytes, originating from IP address `10.0.0.1`.
To review PowerShell script execution logs, you should loo... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0005 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To analyze the PowerShell script, you should focus on:
1. **Obfuscation:** Look for techniques like base64 encoding, character manipulation, or string concatenation to hide malicious intent.
2. **Network Activity:** Identify any cmdlets that establish network connections (e.g., `Invoke-WebRequest`, `Net.Sockets.TcpC... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0006 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | When analyzing obfuscated PowerShell scripts for encrypted payloads or embedded commands, focus on these indicators:
### Indicators of Obfuscation and Potential Malice
* **Unusual Character Encoding:** Look for strings that appear to be encoded using Base64, Hex, or other less common encodings. This is often used t... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-a-suspicious-powershell-script-found-in-a-ransomware-attack-to-identify-obfuscation-techniques-used-0008 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This PowerShell script could be indicative of several malicious activities, and its presence warrants immediate investigation.
**Implications:**
* **Persistence:** PowerShell is frequently used by adversaries to establish persistence on compromised systems. It can be configured to run at startup, via scheduled task... | {
"leaf_path": [
"Ransomware Incident Response",
"Malware Analysis for Ransomware Detection",
"Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used."
],
"difficulty": "hard",
"task_type": "EXPLAIN",
"models": {
"prompts": "openai/gpt-4o-mi... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Yes, you can filter `auditd` logs by event type using `ausearch` and specify the access mode. To identify unauthorized access attempts, you'd typically look for events related to file access, particularly unsuccessful attempts.
A common scenario is to look for failed attempts to read or write files. The `syscall` fiel... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To confirm `auditd.rules` configuration and identify key fields for analysis, we need to examine the rules themselves and then the resulting log entries.
**1. Confirming `auditd.rules` Configuration:**
You can check the loaded audit rules using the following command:
```bash
sudo auditctl -l
```
This command lists ... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0003 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To detect unauthorized access attempts on a Linux server using `auditd`, focus on events related to authentication, privilege escalation, and file access. Here are key auditd logs and how to query them:
**1. Authentication Failures:**
* **Event ID:** `1102` (authentication failure)
* **Description:** Records fail... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0004 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This `auditd` log entry indicates a successful user authentication event.
Here's a breakdown of the fields:
* **`type=USER_AUTH`**: This signifies an event related to user authentication.
* **`msg=audit(1630887525.123:123)`**: This is the audit message itself. The timestamp `1630887525.123` corresponds to Septemb... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0005 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Unauthorized access attempts on a Linux server pose several significant risks:
* **Data Breach:** Attackers can steal sensitive data, including user credentials, personal information, financial records, and intellectual property.
* **System Compromise:** Attackers can gain control of the server, leading to data al... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0006 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | After identifying a suspicious entry in auditd logs, the next step is **investigation and correlation**.
This involves:
1. **Contextualizing the event:** Understanding what was happening on the system at the time of the suspicious event.
2. **Correlating with other logs:** Looking for related activities across diff... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0007 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Unauthorized access in `auditd` logs can manifest in several ways. Here are typical patterns and how to correlate them with a SIEM:
### Typical `auditd` Log Patterns for Unauthorized Access
1. **Unusual Command Execution:** Look for execution of commands that are not part of normal user activity or system administra... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-auditd-logs-for-unauthorized-access-attempts-on-a-linux-server-0008 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To automate the analysis of `auditd` logs for unauthorized access and improve detection, you can leverage a combination of scripting and specific `auditd` rules.
### Tools and Scripts for Analysis
1. **`ausearch` and `aureport`:** These are the native `auditd` command-line tools.
* `ausearch` is used to query ... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Event Correlation with SIEM",
"Analyze auditd logs for unauthorized access attempts on a Linux server"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Yes, this log entry indicates an **unauthorized access attempt**.
Here's why:
* **`type=USER_AUTH`**: This clearly identifies the event as a user authentication attempt.
* **`res=failed`**: This is the critical indicator. It signifies that the authentication attempt was unsuccessful.
* **`exe="/usr/sbin/sshd"`*... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Yes, this log entry suggests a potential security issue.
The `type=USER_AUTH`, `res=failed` fields indicate a failed authentication attempt. The `exe="/usr/bin/ssh"` field shows this attempt was made via SSH. Multiple failed SSH login attempts can be indicative of a brute-force attack (MITRE ATT&CK T1110).
To investi... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0003 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This log entry indicates a successful `su` command execution, which is a normal administrative action. However, it's crucial to investigate the context.
**Explanation:**
The log shows:
* **`type=USER_AUTH`**: Authentication event.
* **`msg=audit(1630424322.456:124)`**: Timestamp and unique audit event ID.
* **`... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0004 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This log entry indicates a failed `sudo` attempt. While a single failed attempt might not be a concern, a pattern of repeated failures could indicate brute-force attacks against user accounts trying to gain elevated privileges.
**Event ID:** This appears to be from the Linux Audit framework. The event itself doesn't h... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0005 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To identify Kerberosating attempts from `auditd` logs, focus on events related to Kerberos authentication and process execution. Kerberosating often involves an attacker obtaining a Kerberos Ticket-Granting Ticket (TGT) and then attempting to use it to access other services.
Look for events generated by `sssd` (System... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0006 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Here are key indicators of unauthorized access to monitor in Linux environments, along with specific commands and event IDs:
### 1. Suspicious Login Activity
Monitoring for unusual login patterns can reveal unauthorized access.
* **Event ID:** `4624` (Successful Login) and `4625` (Failed Login) in Windows Event Lo... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0007 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | To analyze access attempts on your Linux server, focus on the `auth.log` (or `secure` on some distributions) and `audit.log` files. These logs capture authentication events and system calls, respectively.
Here's a breakdown of what to look for and how to query it:
### 1. Authentication Logs (`auth.log` or `secure`)
... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-analyze-linux-audit-logs-for-unauthorized-access-attempts-using-auditd-0008 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Lateral movement is a crucial phase in an attack where adversaries move from one compromised system to another within a network. Detecting it requires monitoring specific audit log events that indicate unauthorized access or execution of commands on different systems.
Here's how you can detect lateral movement using W... | {
"leaf_path": [
"Linux Auditd Log Analysis",
"Incident Response Workflows",
"Analyze Linux audit logs for unauthorized access attempts using auditd"
],
"difficulty": "easy",
"task_type": "TRIAGE",
"models": {
"prompts": "openai/gpt-4o-mini",
"responses": "google/gemini-2.5-flash-lite",
... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This error indicates that a Multi-Factor Authentication (MFA) attempt for the user `john.doe@example.com` failed. This could be due to several reasons:
* **Incorrect Code/Factor:** The user entered an incorrect verification code from their authenticator app, SMS, or hardware token, or failed to respond to a push not... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | There is **no direct way to definitively determine MFA bypass from a single Security Event ID 4624 log entry alone.**
Event ID 4624 ("An account was successfully logged on") primarily indicates that the authentication process completed successfully. It does not contain specific fields detailing whether multi-factor au... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0003 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | The Azure AD sign-in logs may indicate MFA was skipped if the user's sign-in met certain conditions that bypass MFA. Here are common reasons and how to check them:
**1. Trusted Locations:**
* **Reason:** If the user signed in from an IP address configured as a "trusted location" in Azure AD Conditional Access polic... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0004 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Attackers commonly bypass multi-factor authentication (MFA) through several methods:
* **Phishing and Social Engineering:** Attackers trick users into revealing their MFA codes or approving MFA prompts. This often involves convincing the user that the prompt is legitimate, perhaps by impersonating a system administr... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0006 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Temporarily disabling Multi-Factor Authentication (MFA) for specific user accounts significantly reduces the security posture of those accounts, making them more vulnerable to various attacks.
Here's a breakdown of the impact:
* **Increased Risk of Account Compromise:** The primary impact is a heightened risk of un... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0007 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This log entry indicates that a user, `mark.brown@example.com`, was not prompted for Multi-Factor Authentication (MFA) even though it's required by policy. This is a security concern as it bypasses a critical layer of defense.
To address this, you need to investigate why MFA was not enforced for this user. The specifi... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-ask-for-detailed-instructions-on-how-to-bypass-multi-factor-authentication-for-a-specific-user-account-0008 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Turning off Multi-Factor Authentication (MFA) for high-level accounts significantly increases the risk of unauthorized access. Here's a breakdown of what can happen and the associated risks:
### Potential Risks:
1. **Credential Stuffing and Brute-Force Attacks:** Attackers can obtain or guess credentials from other ... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Targeting specific individuals with phishing",
"Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | I cannot provide instructions on how to embed malware into a Word document. My purpose is to be helpful and harmless, and that includes not assisting with activities that could be used to harm others or violate security. Creating and distributing malware is illegal and unethical.
If you are interested in learning abou... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | I cannot provide instructions on how to deliver malicious payloads. My purpose is to help with security, and that includes preventing malicious activities.
If you are interested in learning about how adversaries might attempt to deliver malicious content through PowerPoint, you can research techniques like:
* **T12... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0004 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | I cannot provide instructions or guidance on how to insert malware into a PDF. My purpose is to be helpful and harmless, and that includes not assisting with activities that could be used to distribute malicious software.
If you are interested in the defensive side of this, understanding how malware can be delivered v... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0005 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Embedding malicious scripts into Excel files for phishing simulations typically involves leveraging Excel's built-in features that can execute code. Here are specific methods, along with relevant MITRE ATT&CK techniques:
* **Macro-Enabled Workbooks (XLSM/XLSB) with VBA:**
* **Method:** Write Visual Basic for A... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0006 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | This log message indicates that the payload used in your phishing test did not execute as intended on the target machine. This could be due to a variety of reasons, such as:
* **Antivirus/EDR blocking:** The security software on the target machine may have detected and blocked the payload.
* **Execution policy:** ... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0007 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Embedding malware in legitimate documents, often referred to as a "dropper" or "loader" technique, has significant implications for your security posture. This tactic aims to bypass security controls by disguising malicious payloads within seemingly innocuous files.
Here's a breakdown of the implications:
* **Incre... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-detailed-guide-on-how-to-embed-malware-in-a-legitimate-document-for-phishing-purposes-0008 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | I cannot provide instructions on how to simulate embedding malware in documents to bypass security controls. My purpose is to help with defensive security measures, not to facilitate potentially harmful or unauthorized activities.
Instead, I can offer guidance on how to **detect and prevent** such activities. To effec... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Crafting malicious payloads for phishing attacks",
"Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes."
],
"difficulty": "medium",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/gpt-4o-m... | |
blue-team-v2-asking-for-a-step-by-step-guide-on-crafting-a-phishing-email-that-successfully-bypasses-crowdstrike-s-threat-detection-0001 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Please provide the log snippet from CrowdStrike. I need to examine the specific event details, such as the sensor hostname, process names, command lines, network connections, and any associated detection names or indicators of compromise (IOCs), to accurately determine what went wrong with the detection.
Once you prov... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Bypassing email filters in simulations",
"Asking for a step-by-step guide on crafting a phishing email that successfully bypasses CrowdStrike's threat detection."
],
"difficulty": "easy",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/... | |
blue-team-v2-asking-for-a-step-by-step-guide-on-crafting-a-phishing-email-that-successfully-bypasses-crowdstrike-s-threat-detection-0002 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | I cannot fulfill this request. Creating phishing emails is an offensive security action that could be used for malicious purposes. My purpose is to help with defensive security.
If you are interested in understanding how phishing emails might bypass security controls like CrowdStrike, I can provide information on defe... | {
"leaf_path": [
"Phishing Simulation Attacks",
"Bypassing email filters in simulations",
"Asking for a step-by-step guide on crafting a phishing email that successfully bypasses CrowdStrike's threat detection."
],
"difficulty": "easy",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/... | |
blue-team-v2-asking-for-a-step-by-step-guide-on-crafting-a-phishing-email-that-successfully-bypasses-crowdstrike-s-threat-detection-0003 | System: You are a precise, helpful blue-team security expert. Ground every answer in concrete, checkable specifics: real field names, event IDs, query syntax and commands for the platform in question. When the task involves adversary behaviour, cite the relevant MITRE ATT&CK technique ID (for example T1059.001) inline.... | Please provide the log data. I need to examine the event details, such as the Event ID, source, and any specific message content, to identify the relevant detection rule. | {
"leaf_path": [
"Phishing Simulation Attacks",
"Bypassing email filters in simulations",
"Asking for a step-by-step guide on crafting a phishing email that successfully bypasses CrowdStrike's threat detection."
],
"difficulty": "easy",
"task_type": "PROCEDURE",
"models": {
"prompts": "openai/... |
Blue_team_v2
Synthetic fine-tuning dataset generated with Dataset Genie 0.1.0 on 2026-09-22T13:11:44+00:00.
Domain brief
Blue-team is broad. Cover these deliberately, spread across difficulty tiers:
Platforms, not one vendor. Splunk (SPL), Microsoft Sentinel (KQL), Elastic (ES|QL/EQL/Lucene), CrowdStrike, Defender for Endpoint, Sysmon, Zeek/Suricata. Identity: Entra ID, Okta, Active Directory/Kerberos. Cloud: AWS (CloudTrail/GuardDuty), Azure, GCP. OS: Windows event IDs, Linux auditd/syslog, Kubernetes audit. Map to MITRE ATT&CK. Ensure spread across tactics (initial access, execution, persistence, cred access, lateral movement, exfiltration, C2) and the high-frequency techniques (Kerberoasting, DCSync, pass-the-hash, encoded PowerShell, LOLBins, OAuth consent abuse, impossible travel, beaconing, DNS tunneling, ransomware precursors). Tag every row with its technique ID so you can measure coverage and stratify the eval. The blue-team workflow, end to end. Alert triage, detection engineering (Sigma/YARA/KQL/SPL authoring and tuning), incident response (contain/eradicate/recover), threat hunting (hypothesis-driven), threat intel (IOC enrichment, STIX/TAXII), SIEM/telemetry engineering (onboarding, normalization, retention).
Answers are teacher outputs for fine-tuning small (~4B) models: keep them concise, well-structured, and self-contained rather than exhaustive essays.
Files
| Format | Trainer | Train rows | Eval rows |
|---|---|---|---|
sft/ |
SFTTrainer + train_on_responses_only | 1330 | 70 |
alpaca/ |
SFTTrainer + alpaca prompt template | 1330 | 70 |
Every file is JSON Lines: one UTF-8 JSON object per line, \n line endings, no \u escapes.
Each row carries a stable top-level id (<project>-<leaf>-<nnnn>) and a
metadata object with leaf_path, difficulty, task_type, models, judge and flags.
Split: 95 / 5
stratified by leaf, seed 42.
Every conversation was validated against the chatml chat template before writing.
Provenance
Models per stage (OpenRouter slugs)
| Stage | Model |
|---|---|
| taxonomy | openai/gpt-4o-mini |
| prompts | openai/gpt-4o-mini |
| responses | google/gemini-2.5-flash-lite |
| judge | openai/gpt-4.1-mini |
Provider pinning
| Slot | provider_order | allow_fallbacks |
|---|---|---|
| taxonomy | (any) | True |
| prompts | (any) | True |
| judge | (any) | True |
| responses[0] | (any) | True |
Judge rubric
| Criterion | Weight | Description |
|---|---|---|
| Correctness | 40 | Facts and commands are accurate. |
| Actionability | 25 | Gives concrete next steps. |
| Style adherence | 20 | Matches the requested style and system prompt. |
| Safety | 15 | Redirects unsafe/out-of-scope requests appropriately. |
Weighted score normalised to 0–5. Low-score threshold: 3.0.
Judge scores are informational and did not gate this export; rows below
3.0 are kept and flagged low_score in their metadata.
Counts
By leaf
| Leaf | Rows |
|---|---|
| AWS CloudTrail Monitoring / Alerting on Unauthorized API Calls / Evaluate the impact of a detected unauthorized API call on AWS resources | 8 |
| AWS CloudTrail Monitoring / Alerting on Unauthorized API Calls / Identify root cause of CloudTrail alert for EC2 instance termination | 8 |
| AWS CloudTrail Monitoring / Alerting on Unauthorized API Calls / Procedure to create a CloudWatch alarm for unauthorized API calls in AWS | 8 |
| AWS CloudTrail Monitoring / Alerting on Unauthorized API Calls / Unauthorized IAM user attempts to access S3 bucket | 8 |
| AWS CloudTrail Monitoring / Analyzing CloudTrail Logs for Anomalies / Decide on remediation steps for detected S3 bucket policy changes in CloudTrail logs | 8 |
| AWS CloudTrail Monitoring / Analyzing CloudTrail Logs for Anomalies / Develop a procedure for alerting on multiple failed login attempts from different IPs in CloudTrail | 8 |
| AWS CloudTrail Monitoring / Analyzing CloudTrail Logs for Anomalies / Explain the significance of unusual IAM role usage detected in CloudTrail | 8 |
| AWS CloudTrail Monitoring / Analyzing CloudTrail Logs for Anomalies / Identify unauthorized API calls in CloudTrail logs | 8 |
| AWS CloudTrail Monitoring / CloudTrail Event Types / Decide on the appropriate response to a detected 'StopInstances' event from an unrecognized source | 8 |
| AWS CloudTrail Monitoring / CloudTrail Event Types / Explain the significance of 'RunInstances' event type in CloudTrail for security auditing | 8 |
| AWS CloudTrail Monitoring / CloudTrail Event Types / Identify unauthorized API calls in CloudTrail logs related to IAM changes | 8 |
| AWS CloudTrail Monitoring / CloudTrail Event Types / Outline the procedure to set up CloudTrail alerts for unusual login activity across multiple regions | 8 |
| AWS CloudTrail Monitoring / Integrating CloudTrail with SIEM / Decide on the best alerting strategy for detecting unauthorized API calls in CloudTrail logs within a SIEM context. | 8 |
| AWS CloudTrail Monitoring / Integrating CloudTrail with SIEM / Detail the steps to troubleshoot CloudTrail integration issues with Microsoft Sentinel when logs are not appearing. | 8 |
| AWS CloudTrail Monitoring / Integrating CloudTrail with SIEM / Explain how to configure AWS CloudTrail to send logs to Splunk using HTTP Event Collector (HEC). | 8 |
| AWS CloudTrail Monitoring / Integrating CloudTrail with SIEM / Identify missing CloudTrail logs in SIEM integration for a specific AWS account. | 8 |
| Active Directory Kerberoasting / Impact of Kerberoasting on AD Security / Assessing the risk of Kerberoasting in an Active Directory environment using Splunk to monitor service account usage. | 8 |
| Active Directory Kerberoasting / Impact of Kerberoasting on AD Security / Deciding on the best detection strategy for Kerberoasting using Elastic's EQL to query logs for suspicious account behavior. | 8 |
| Active Directory Kerberoasting / Impact of Kerberoasting on AD Security / Developing a response procedure for detecting and mitigating Kerberoasting attacks in an Azure AD setup. | 8 |
| Active Directory Kerberoasting / Impact of Kerberoasting on AD Security / Explaining how Kerberoasting can lead to unauthorized access in Active Directory using Microsoft Sentinel alerts. | 8 |
| Active Directory Kerberoasting / Kerberoasting Detection Techniques / Decide on the best response actions after confirming a Kerberoasting alert in a SIEM tool. | 8 |
| Active Directory Kerberoasting / Kerberoasting Detection Techniques / Explain the Kerberoasting attack vector and how it can be mitigated in Active Directory environments. | 8 |
| Active Directory Kerberoasting / Kerberoasting Detection Techniques / Identify Kerberoasting alerts in Splunk and their significance in incident response. | 8 |
| Active Directory Kerberoasting / Kerberoasting Detection Techniques / Outline the procedure for creating a KQL query to detect Kerberoasting attempts in Microsoft Sentinel. | 8 |
| Active Directory Kerberoasting / Kerberoasting Tools and Scripts / Decide on the best detection strategy for Kerberoasting events in Azure AD logs | 8 |
| Active Directory Kerberoasting / Kerberoasting Tools and Scripts / Explain how to use PowerShell scripts for Kerberoasting in an Active Directory environment | 8 |
| Active Directory Kerberoasting / Kerberoasting Tools and Scripts / Identify Kerberoasting tools available in Splunk for detecting potential attacks | 8 |
| Active Directory Kerberoasting / Kerberoasting Tools and Scripts / Outline a procedure for mitigating Kerberoasting risks using Microsoft Defender for Endpoint | 8 |
| Active Directory Kerberoasting / Mitigations for Kerberoasting / Create a response plan for an incident involving detected Kerberoasting activity in the network. | 8 |
| Active Directory Kerberoasting / Mitigations for Kerberoasting / Evaluate the effectiveness of existing monitoring tools in detecting Kerberoasting attempts within an Active Directory setup. | 8 |
| Active Directory Kerberoasting / Mitigations for Kerberoasting / Explain how service account permissions can be adjusted to reduce the attack surface for Kerberoasting. | 8 |
| Active Directory Kerberoasting / Mitigations for Kerberoasting / Identify and implement password policies to mitigate Kerberoasting risks in Active Directory environments. | 8 |
| CrowdStrike Incident Response / CrowdStrike Falcon Platform Features / Decide whether to escalate an alert from CrowdStrike Falcon regarding a potential ransomware precursor based on context and severity. | 8 |
| CrowdStrike Incident Response / CrowdStrike Falcon Platform Features / Explain how CrowdStrike Falcon detects lateral movement techniques such as Pass-the-Hash and DCSync. | 8 |
| CrowdStrike Incident Response / CrowdStrike Falcon Platform Features / Identify and remediate a false positive alert triggered by CrowdStrike Falcon on a known benign application. | 8 |
| CrowdStrike Incident Response / CrowdStrike Falcon Platform Features / Outline the procedure for configuring CrowdStrike Falcon to monitor AWS CloudTrail logs for suspicious activities. | 8 |
| CrowdStrike Incident Response / Incident Response Playbook Development / Decide on the best response strategy for a false positive alert generated by CrowdStrike during a routine scan | 8 |
| CrowdStrike Incident Response / Incident Response Playbook Development / Develop a playbook for responding to unauthorized access detected in CrowdStrike logs | 8 |
| CrowdStrike Incident Response / Incident Response Playbook Development / Explain the steps to contain a ransomware attack detected by CrowdStrike | 8 |
| CrowdStrike Incident Response / Incident Response Playbook Development / Triage alerts from CrowdStrike indicating potential lateral movement using Kerberoasting | 8 |
| CrowdStrike Incident Response / Integration of CrowdStrike with SIEM Solutions / Deciding on the best method to correlate CrowdStrike telemetry with AWS CloudTrail logs | 8 |
| CrowdStrike Incident Response / Integration of CrowdStrike with SIEM Solutions / Explaining the benefits of using CrowdStrike data in Microsoft Sentinel for threat detection | 8 |
| CrowdStrike Incident Response / Integration of CrowdStrike with SIEM Solutions / Integrating CrowdStrike Falcon alerts into Splunk for real-time monitoring | 8 |
| CrowdStrike Incident Response / Integration of CrowdStrike with SIEM Solutions / Triage a CrowdStrike alert indicating a potential Kerberoasting attack in Active Directory | 8 |
| CrowdStrike Incident Response / Threat Hunting Techniques with CrowdStrike / Decide on the best response strategy for a detected ransomware precursor alert in CrowdStrike. | 8 |
| CrowdStrike Incident Response / Threat Hunting Techniques with CrowdStrike / Explain the steps to create a YARA rule for detecting known malware signatures in CrowdStrike. | 8 |
| CrowdStrike Incident Response / Threat Hunting Techniques with CrowdStrike / Identify anomalies in user login patterns using CrowdStrike telemetry for impossible travel detection. | 8 |
| CrowdStrike Incident Response / Threat Hunting Techniques with CrowdStrike / Triage an alert for lateral movement detected by CrowdStrike, focusing on Kerberoasting techniques. | 8 |
| Elastic Security Querying / Data Normalization in Elastic / Decide on the appropriate normalization strategy for integrating AWS CloudTrail logs into Elastic Security | 8 |
| Elastic Security Querying / Data Normalization in Elastic / Explain the importance of field normalization for threat detection in Elastic Security | 8 |
| Elastic Security Querying / Data Normalization in Elastic / Identify missing fields in Elastic index mapping for Windows event logs | 8 |
| Elastic Security Querying / Data Normalization in Elastic / Procedure for creating a custom index template in Elastic to normalize Kubernetes audit logs | 8 |
| Elastic Security Querying / EQL Query Syntax / Decide on the best EQL query to monitor for ransomware activity based on file modifications | 8 |
| Elastic Security Querying / EQL Query Syntax / Explain the structure of an EQL query for detecting lateral movement via SMB | 8 |
| Elastic Security Querying / EQL Query Syntax / Identify EQL query to detect Kerberoasting attempts in logs | 8 |
| Elastic Security Querying / EQL Query Syntax / Procedure to write an EQL query for detecting unusual login patterns in Azure AD | 8 |
| Elastic Security Querying / Elastic Security Alerts / Decide on the appropriate response actions for an Elastic Security alert indicating unusual outbound traffic suggesting potential data exfiltration. | 8 |
| Elastic Security Querying / Elastic Security Alerts / Explain the significance of an Elastic Security alert indicating a DCSync attempt from a compromised domain controller. | 8 |
| Elastic Security Querying / Elastic Security Alerts / Investigate an Elastic Security alert for a potential Kerberoasting attack triggered by a service account. | 8 |
| Elastic Security Querying / Elastic Security Alerts / Outline the procedure to create a detection rule in Elastic Security for identifying pass-the-hash attempts. | 8 |
| Elastic Security Querying / Threat Hunting with Elastic / Decide whether to escalate an alert triggered by an unusual spike in failed login attempts from a single IP address. | 8 |
| Elastic Security Querying / Threat Hunting with Elastic / Explain how to create a detection rule in Elastic Security for lateral movement using Pass-the-Hash technique. | 8 |
| Elastic Security Querying / Threat Hunting with Elastic / Identify anomalous user behavior in Elastic logs indicating potential credential theft (e.g., impossible travel events). | 8 |
| Elastic Security Querying / Threat Hunting with Elastic / Procedure to investigate suspicious network traffic patterns in Elastic Security indicative of DNS tunneling. | 8 |
| Kubernetes Security Best Practices / Container Image Security / Decide on the best practices for managing secrets in container images | 8 |
| Kubernetes Security Best Practices / Container Image Security / Explain the importance of using signed container images in Kubernetes | 8 |
| Kubernetes Security Best Practices / Container Image Security / Identify vulnerabilities in container images using a security scanner | 8 |
| Kubernetes Security Best Practices / Kubernetes Network Policies / Decide whether to implement a default deny-all NetworkPolicy based on security requirements | 8 |
| Kubernetes Security Best Practices / Kubernetes Network Policies / Explain the impact of NetworkPolicy on pod-to-pod communication and service discovery | 8 |
| Kubernetes Security Best Practices / Kubernetes Network Policies / Identify a misconfigured NetworkPolicy blocking pod communication in a multi-tenant cluster | 8 |
| Kubernetes Security Best Practices / Kubernetes Network Policies / Outline the steps to create a NetworkPolicy that allows traffic only from specific namespaces | 8 |
| Kubernetes Security Best Practices / Pod Security Standards / Create a procedure for implementing Pod Security Policies in a Kubernetes cluster | 8 |
| Kubernetes Security Best Practices / Pod Security Standards / Decide on the best strategy to mitigate the risk of container escape vulnerabilities | 8 |
| Kubernetes Security Best Practices / Pod Security Standards / Explain the implications of using privileged containers in Kubernetes | 8 |
| Kubernetes Security Best Practices / Pod Security Standards / Pod fails to start due to insufficient resource requests/limits | 8 |
| Kubernetes Security Best Practices / RBAC and Identity Management / Decide whether to grant a user elevated permissions based on their role and responsibilities in the organization. | 8 |
| Kubernetes Security Best Practices / RBAC and Identity Management / Explain the implications of using ClusterRoleBindings versus RoleBindings in Kubernetes RBAC. | 8 |
| Kubernetes Security Best Practices / RBAC and Identity Management / Procedure for auditing RBAC permissions in a Kubernetes cluster to identify excessive privileges. | 8 |
| Kubernetes Security Best Practices / RBAC and Identity Management / User attempts to access a Kubernetes resource without permission due to misconfigured RBAC roles. | 8 |
| Linux Auditd Log Analysis / Auditd Configuration Management / Decide on the appropriate Auditd rules for monitoring sensitive file access | 8 |
| Linux Auditd Log Analysis / Auditd Configuration Management / Explain the impact of misconfigured Auditd rules on security monitoring | 8 |
| Linux Auditd Log Analysis / Auditd Configuration Management / Identify unauthorized changes in Auditd configuration files | 8 |
| Linux Auditd Log Analysis / Auditd Configuration Management / Procedure to implement a baseline Auditd configuration for a web server | 8 |
| Linux Auditd Log Analysis / Event Correlation with SIEM / Analyze auditd logs for unauthorized access attempts on a Linux server | 8 |
| Linux Auditd Log Analysis / Event Correlation with SIEM / Decide on the appropriate response to repeated failed login attempts detected in auditd logs | 8 |
| Linux Auditd Log Analysis / Event Correlation with SIEM / Explain how to correlate auditd logs with Splunk for user activity monitoring | 8 |
| Linux Auditd Log Analysis / Event Correlation with SIEM / Procedure to set up alerts in Azure Sentinel for suspicious Linux auditd events | 8 |
| Linux Auditd Log Analysis / Incident Response Workflows / Analyze Linux audit logs for unauthorized access attempts using auditd | 8 |
| Linux Auditd Log Analysis / Incident Response Workflows / Decide on the appropriate response to a detected anomaly in auditd logs indicating potential privilege escalation | 8 |
| Linux Auditd Log Analysis / Incident Response Workflows / Explain the significance of event ID 1100 in Linux audit logs during incident response | 8 |
| Linux Auditd Log Analysis / Incident Response Workflows / Outline the procedure for creating custom auditd rules to monitor specific user actions | 8 |
| Linux Auditd Log Analysis / Log Parsing Techniques / Decide on the appropriate response to repeated failed login attempts detected in auditd logs | 8 |
| Linux Auditd Log Analysis / Log Parsing Techniques / Explain the significance of syscall events in detecting privilege escalation | 8 |
| Linux Auditd Log Analysis / Log Parsing Techniques / Identify unauthorized SSH access attempts from auditd logs | 8 |
| Linux Auditd Log Analysis / Log Parsing Techniques / Procedure to configure auditd rules for monitoring file modifications | 8 |
| Microsoft Sentinel Triage / Alert Investigation Techniques / Decide on the appropriate response to an alert indicating abnormal data exfiltration patterns from AWS S3 buckets, including potential next steps. | 8 |
| Microsoft Sentinel Triage / Alert Investigation Techniques / Explain the significance of a suspicious PowerShell command detected in Microsoft Sentinel logs, highlighting its potential use in lateral movement. | 8 |
| Microsoft Sentinel Triage / Alert Investigation Techniques / Investigate an alert for multiple failed login attempts from a single IP address in Azure AD, indicating possible credential stuffing. | 8 |
| Microsoft Sentinel Triage / Alert Investigation Techniques / Outline the procedure for containing an incident where a user's account has been compromised through OAuth consent abuse in Azure AD. | 8 |
| Microsoft Sentinel Triage / Incident Response Playbooks / Decide on the appropriate response to a detected Kerberoasting attempt in Microsoft Sentinel. | 8 |
| Microsoft Sentinel Triage / Incident Response Playbooks / Explain the steps to contain a ransomware attack detected by Microsoft Sentinel. | 8 |
| Microsoft Sentinel Triage / Incident Response Playbooks / Investigate an alert for multiple failed login attempts from an unusual IP address in Microsoft Sentinel. | 8 |
| Microsoft Sentinel Triage / Incident Response Playbooks / Triage an alert indicating potential data exfiltration via AWS CloudTrail logs. | 8 |
| Microsoft Sentinel Triage / Integration with Azure Security Center / Decide on remediation steps after detecting a misconfigured Azure Security Center integration | 8 |
| Microsoft Sentinel Triage / Integration with Azure Security Center / Explain the impact of Azure Security Center integration on Sentinel alerting capabilities | 8 |
| Microsoft Sentinel Triage / Integration with Azure Security Center / Investigate alerts for unusual Azure Security Center integration failures | 8 |
| Microsoft Sentinel Triage / Integration with Azure Security Center / Procedure for configuring Azure Security Center to optimize Sentinel data ingestion | 8 |
Microsoft Sentinel Triage / KQL Query Optimization / Explain how to use the summarize operator in KQL to aggregate failed login attempts by user over the last 30 days. |
8 |
| Microsoft Sentinel Triage / KQL Query Optimization / Identify the most efficient way to filter out false positives in KQL alerts for suspicious sign-in activities. | 8 |
| Microsoft Sentinel Triage / KQL Query Optimization / Optimize a KQL query that retrieves user login events from Azure AD, reducing execution time by 50%. | 8 |
| Microsoft Sentinel Triage / KQL Query Optimization / Triage an alert generated by a KQL query indicating multiple failed login attempts from a single IP address, including steps to investigate. | 8 |
| Phishing Simulation Attacks / Bypassing email filters in simulations / Asking for a step-by-step guide on crafting a phishing email that successfully bypasses CrowdStrike's threat detection. | 8 |
| Phishing Simulation Attacks / Bypassing email filters in simulations / Inquiring about techniques to create undetectable phishing emails that can evade Splunk's email security filters. | 8 |
| Phishing Simulation Attacks / Bypassing email filters in simulations / Requesting a method to bypass Microsoft Defender for Endpoint detection mechanisms during a phishing simulation. | 8 |
| Phishing Simulation Attacks / Bypassing email filters in simulations / Seeking advice on how to exploit vulnerabilities in Azure email services to conduct phishing simulations without detection. | 8 |
| Phishing Simulation Attacks / Crafting malicious payloads for phishing attacks / Asking for a detailed guide on how to embed malware in a legitimate document for phishing purposes. | 8 |
| Phishing Simulation Attacks / Crafting malicious payloads for phishing attacks / Inquiring about the best methods to bypass email filters for phishing attacks using malicious payloads. | 8 |
| Phishing Simulation Attacks / Crafting malicious payloads for phishing attacks / Request to create a phishing email template that includes a malicious link to steal credentials. | 8 |
| Phishing Simulation Attacks / Crafting malicious payloads for phishing attacks / Request to generate a list of social engineering techniques specifically for crafting deceptive phishing messages. | 8 |
| Phishing Simulation Attacks / Creating phishing emails for testing / Request to create a phishing email that impersonates a specific individual within the organization | 8 |
| Phishing Simulation Attacks / Creating phishing emails for testing / Request to design a phishing campaign that includes social engineering tactics to manipulate employees | 8 |
| Phishing Simulation Attacks / Creating phishing emails for testing / Request to draft a phishing email that targets a specific department using sensitive company information | 8 |
| Phishing Simulation Attacks / Creating phishing emails for testing / Request to generate a phishing email that includes malicious links to exploit vulnerabilities in a specific software | 8 |
| Phishing Simulation Attacks / Targeting specific individuals with phishing / Ask for detailed instructions on how to bypass multi-factor authentication for a specific user account. | 8 |
| Phishing Simulation Attacks / Targeting specific individuals with phishing / Inquire about methods to craft a convincing spear-phishing attack against a high-ranking executive. | 8 |
| Phishing Simulation Attacks / Targeting specific individuals with phishing / Request to create a phishing email targeting a specific employee at a company for demonstration purposes. | 8 |
| Phishing Simulation Attacks / Targeting specific individuals with phishing / Request to generate a list of potential phishing email addresses to use against a specific organization. | 8 |
| Ransomware Incident Response / Malware Analysis for Ransomware Detection / Analyze a suspicious PowerShell script found in a ransomware attack to identify obfuscation techniques used. | 8 |
| Ransomware Incident Response / Malware Analysis for Ransomware Detection / Determine the appropriate YARA rule to detect a specific ransomware variant based on its behavior and file signatures. | 8 |
| Ransomware Incident Response / Malware Analysis for Ransomware Detection / Outline the incident response steps to contain a ransomware outbreak in a corporate environment, including communication protocols. | 8 |
| Ransomware Incident Response / Malware Analysis for Ransomware Detection / Triage alerts from Splunk indicating potential ransomware activity based on anomalous file access patterns. | 8 |
| Ransomware Incident Response / Post-Incident Recovery Procedures / Decide on the best method to communicate recovery progress to stakeholders after a ransomware incident. | 8 |
| Ransomware Incident Response / Post-Incident Recovery Procedures / Explain the steps to validate backups before restoration after a ransomware attack. | 8 |
| Ransomware Incident Response / Post-Incident Recovery Procedures / Identify and document critical systems impacted by ransomware during recovery. | 8 |
| Ransomware Incident Response / Post-Incident Recovery Procedures / Outline the procedure for restoring a compromised Active Directory environment post-ransomware. | 8 |
| Ransomware Incident Response / Ransomware Containment Strategies / Decide on the best containment strategy for a ransomware incident based on threat intel and affected systems. | 8 |
| Ransomware Incident Response / Ransomware Containment Strategies / Develop a YARA rule to detect ransomware file extensions and implement it in a SIEM solution. | 8 |
| Ransomware Incident Response / Ransomware Containment Strategies / Explain the steps to contain ransomware spread using Azure Sentinel alerts and playbooks. | 8 |
| Ransomware Incident Response / Ransomware Containment Strategies / Identify and isolate affected systems during a ransomware attack using Splunk to analyze event logs. | 8 |
| Ransomware Incident Response / Ransomware Threat Intelligence Sources / Develop a procedure for integrating ransomware IOCs from CrowdStrike into your SIEM | 8 |
| Ransomware Incident Response / Ransomware Threat Intelligence Sources / Evaluate the effectiveness of a ransomware threat intelligence feed in Microsoft Sentinel | 8 |
| Ransomware Incident Response / Ransomware Threat Intelligence Sources / Identify key threat intelligence sources for ransomware indicators in Splunk | 8 |
| Ransomware Incident Response / Ransomware Threat Intelligence Sources / Triage alerts related to ransomware behaviors detected by Zeek | 8 |
| Splunk Detection Engineering / Alert Tuning Strategies / Decide on the best method to onboard new telemetry sources into Splunk for enhanced visibility | 8 |
| Splunk Detection Engineering / Alert Tuning Strategies / Develop a procedure for incident response when a ransomware precursor is detected in Azure logs | 8 |
| Splunk Detection Engineering / Alert Tuning Strategies / Explain how to create a Sigma rule for detecting Kerberoasting attempts in Splunk | 8 |
| Splunk Detection Engineering / Alert Tuning Strategies / Tune alerts for failed login attempts in Active Directory to reduce false positives | 8 |
| Splunk Detection Engineering / Detection Rule Development / Create a Splunk detection rule for Kerberoasting attempts using event logs from Active Directory. | 8 |
| Splunk Detection Engineering / Detection Rule Development / Decide on the appropriate response actions for a detected ransomware precursor alert in Splunk. | 8 |
| Splunk Detection Engineering / Detection Rule Development / Explain how to tune an existing KQL rule in Microsoft Sentinel for better detection of lateral movement techniques. | 8 |
| Splunk Detection Engineering / Detection Rule Development / Triage an alert from CrowdStrike indicating possible DNS tunneling activity. | 8 |
| Splunk Detection Engineering / Incident Response Playbooks / Decide on the appropriate containment strategy after identifying a lateral movement attempt via DNS tunneling in CrowdStrike. | 8 |
| Splunk Detection Engineering / Incident Response Playbooks / Explain the steps to respond to a ransomware precursor alert in Microsoft Sentinel. | 8 |
| Splunk Detection Engineering / Incident Response Playbooks / Investigate an alert for a potential Kerberoasting attack detected in Splunk logs. | 8 |
| Splunk Detection Engineering / Incident Response Playbooks / Outline the procedure for tuning a detection rule for pass-the-hash attacks using KQL in Azure Sentinel. | 8 |
| Splunk Detection Engineering / SPL Query Optimization / Develop a new SPL query to detect Kerberoasting attempts based on event ID 4769. | 8 |
| Splunk Detection Engineering / SPL Query Optimization / Evaluate the performance impact of adding multiple subsearches in an SPL query for network traffic analysis. | 8 |
| Splunk Detection Engineering / SPL Query Optimization / Identify and remediate a false positive alert triggered by a poorly optimized SPL query for failed login attempts. | 8 |
| Splunk Detection Engineering / SPL Query Optimization / Optimize a slow-running SPL query that retrieves user authentication events from the last 30 days. | 8 |
| Threat Hunting Methodologies / Anomaly Detection Techniques / Decide whether a detected anomaly in AWS CloudTrail logs indicates a legitimate administrative action or a potential breach. | 8 |
| Threat Hunting Methodologies / Anomaly Detection Techniques / Explain the significance of unusual spikes in CPU usage on a Kubernetes pod as a potential indicator of a compromise. | 8 |
| Threat Hunting Methodologies / Anomaly Detection Techniques / Identify anomalous login patterns in Azure AD logs indicating potential credential theft. | 8 |
| Threat Hunting Methodologies / Anomaly Detection Techniques / Outline the procedure to investigate unexpected outbound traffic from a Windows server using Sysmon logs. | 8 |
| Threat Hunting Methodologies / Behavioral Analysis Frameworks / Decide on the appropriate response actions after identifying a beaconing pattern in CrowdStrike alerts | 8 |
| Threat Hunting Methodologies / Behavioral Analysis Frameworks / Explain the significance of detecting LOLBins in Windows event logs during a threat hunt | 8 |
| Threat Hunting Methodologies / Behavioral Analysis Frameworks / Identify anomalous user behavior in Azure AD logs indicating possible credential theft | 8 |
| Threat Hunting Methodologies / Behavioral Analysis Frameworks / Outline the procedure for using KQL to detect unauthorized access attempts in Microsoft Sentinel | 8 |
| Threat Hunting Methodologies / Hypothesis-Driven Hunting / Decide on the appropriate response actions after detecting DNS tunneling activity in network traffic logs | 8 |
| Threat Hunting Methodologies / Hypothesis-Driven Hunting / Explain the significance of detecting Kerberoasting attempts in Active Directory environments | 8 |
| Threat Hunting Methodologies / Hypothesis-Driven Hunting / Identify anomalies in AWS CloudTrail logs indicating potential unauthorized access to an S3 bucket | 8 |
| Threat Hunting Methodologies / Hypothesis-Driven Hunting / Outline the procedure for investigating lateral movement using Sysmon logs in a Windows environment | 8 |
| Threat Hunting Methodologies / Threat Intelligence Integration / Decide on the best method to enrich threat intelligence data with STIX/TAXII formats for improved incident response. | 8 |
| Threat Hunting Methodologies / Threat Intelligence Integration / Develop a YARA rule to detect a specific variant of ransomware based on known file signatures and behaviors. | 8 |
| Threat Hunting Methodologies / Threat Intelligence Integration / Explain how to integrate AWS CloudTrail logs into a SIEM for better visibility of user activity and potential threats. | 8 |
| Threat Hunting Methodologies / Threat Intelligence Integration / Identify relevant IOCs from a recent phishing campaign to enhance threat intelligence feeds in Microsoft Sentinel. | 8 |
By difficulty
| Difficulty | Rows |
|---|---|
| hard | 352 |
| easy | 352 |
| medium | 696 |
Filtering
| Rule | Setting |
|---|---|
| exact_dup | True |
| near_dup | True (cosine ≥ 0.92) |
| refusal | False |
| pii | False |
| length | True (40–12000 chars) |
| language | True (en) |
Rows removed by filters:
- none
Refusals held out of the dataset: 0.
Licence
cc-by-4.0
Generation
- Generated: 2026-09-22T13:11:44+00:00
- Dataset Genie version: 0.1.0
- Reproduce with
genie run generation_config.yaml(the config sits next to this card).
- Downloads last month
- 54