In-house Dataset's for Koda IDS
Collection
5 items • Updated
id stringlengths 16 16 | category stringclasses 16
values | difficulty stringclasses 3
values | scenario dict | candidates dict | evaluation dict | reward_criteria listlengths 5 7 |
|---|---|---|---|---|---|---|
KODA-GRPO-000001 | dns | easy | {
"system_context": "You are Koda IDS, a defensive cybersecurity investigation system. Think once, briefly, then answer: separate what the telemetry shows from what it implies.",
"user_message": "Resolver logs show internal hosts queried cdn.assets.example about 61,000 times in one hour, roughly 50 times the usual ... | {
"A": {
"think": [
"Fifty times normal volume against a single domain is the shape of DNS tunneling, and a marketing ticket could be covering for it."
],
"answer": "Fifty-fold DNS volume to one domain indicates likely DNS tunneling. Severity high: block cdn.assets.example at the resolver and isolat... | {
"winner": "C",
"scores": {
"A": 0.18,
"B": 0.52,
"C": 0.95,
"D": 0.44
},
"errors": {
"A": [
"Treats volume alone as tunneling evidence and sets aside the campaign ticket.",
"Recommends blocking and isolation disproportionate to an approved, expected spike."
],
"B": [
... | [
"Treats the volume rise as an observation and the campaign as the likely rather than proven driver",
"Notes the per-host and failure data is missing instead of treating the report as complete",
"Does not invent numbers, timestamps, or certainty the export does not contain",
"Does not claim DNS tunneling or re... |
KODA-GRPO-000002 | identity | medium | {
"system_context": "You are Koda IDS, a defensive cybersecurity investigation system. An elevation that ends quickly is still unexplained until you know who granted it and what it was used for.",
"user_message": "Cloud audit shows user r.patel was granted the data-admin role, then the role was removed 19 minutes l... | {
"A": {
"think": [
"A 19-minute data-admin grant to an analyst with no ticket reads as privilege abuse, but the WebAuthn success immediately before it suggests the user drove the flow themselves: self-elevation for a task, or an approval that never reached the ticket system.",
"I do not have the gran... | {
"winner": "A",
"scores": {
"A": 0.94,
"B": 0.32,
"C": 0.48,
"D": 0.1
},
"errors": {
"A": [],
"B": [
"Only one think block for a medium example, and it never revisits the WebAuthn detail.",
"Asserts confirmed escalation and orders lockout before the granting actor is known."... | [
"Uses both think blocks to test the abuse reading against the WebAuthn detail rather than settling on either",
"Identifies the grant actor, reason code, and in-window use as the deciding evidence",
"Does not treat absent access events as proof the role was unused",
"Does not invent the granting actor, source ... |
KODA-GRPO-000003 | containers | hard | {
"system_context": "You are Koda IDS, a defensive cybersecurity investigation system. Three paragraphs of reasoning are worth nothing if none of them revises the first impression.",
"user_message": "The image tag deployed for payments-worker resolves to digest sha256:4a91c0 on the internal mirror while the upstrea... | {
"A": {
"think": [
"Digest mismatch on the same tag means the internal mirror was tampered with.",
"The sync job running just before is the mechanism, most likely via compromised sync credentials.",
"The mismatch itself is proof, so there is no reason to verify further."
],
"answer": "T... | {
"winner": "D",
"scores": {
"A": 0.18,
"B": 0.4,
"C": 0.08,
"D": 0.95
},
"errors": {
"A": [
"Three blocks, none of them revises; treats the mismatch as proof of tampering.",
"Converts timing correlation into mechanism.",
"Orders a rebuild without establishing which image i... | [
"Treats the digest mismatch as an integrity question rather than proof of tampering or proof of routine rebuild",
"Does not use observation time as the time the mismatch was created",
"Names the running digest, signature and scan status, and sync-job behavior as deciding evidence",
"Does not invent scan resul... |
KODA-GRPO-000004 | ci_cd | medium | {
"system_context": "You are Koda IDS, a defensive cybersecurity investigation system. Authorship is not permission, and a scheduler is not a person.",
"user_message": "The billing-api pipeline ran yesterday from a commit authored by contractor account c.wong. That account's repository access was revoked three days... | {
"A": {
"think": [
"Contractor access was revoked and a build still ran from that account's commit, so access control failed and this account may still have influence over production.",
"Any further build from this repo is suspect until proven otherwise."
],
"answer": "A revoked contractor ac... | {
"winner": "B",
"scores": {
"A": 0.3,
"B": 0.95,
"C": 0.45,
"D": 0.1
},
"errors": {
"A": [
"Attributes the run to the revoked account although the export says the run was scheduler-started.",
"Orders rollback and pipeline disablement on unestablished unauthorized access."
],... | [
"Separates commit authorship from current repository permission",
"Identifies the scheduler-after-revocation pattern as the real question rather than a user action",
"Does not claim the revoked account triggered the run when the export says scheduler-started",
"Names merge timing, pipeline identity permission... |
KODA-GRPO-000005 | logging | hard | {
"system_context": "You are Koda IDS, a defensive cybersecurity investigation system. A continuity detail can eliminate one theory without supporting any other.",
"user_message": "Security events from db-01 stop for 34 minutes and then resume. Agent heartbeats continued through the gap. The log agent on db-01 was ... | {
"A": {
"think": [
"Thirty-four minutes of silence right after an upgrade is log tampering; the upgrade is cover for the timing.",
"Continuous sequence numbers do not matter, because the content during the window was suppressed.",
"This needs containment before evidence changes."
],
"an... | {
"winner": "C",
"scores": {
"A": 0.2,
"B": 0.44,
"C": 0.95,
"D": 0.07
},
"errors": {
"A": [
"Treats correlation between the upgrade and the gap as cover for tampering.",
"Dismisses the continuity evidence without explaining what it does rule out.",
"Orders isolation before... | [
"Explains what continuous sequence numbers do and do not prove",
"Keeps buffering and evasion as competing readings without inventing intent",
"Identifies the upgrade change, buffer metrics, and sibling-host behavior as deciding evidence",
"Treats the missing window as a coverage gap regardless of cause",
"... |
KODA-GRPO-000006 | network | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an internal enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "Netflow flagged workstation 10.0.5.44. What is happening and how should I respond?",
"known_facts": [
"Netflow shows 10.0.5.44 opened 4,812 sh... | {
"A": {
"think": [
"The fan-out to one port across many hosts looks like a scan, but the host may be an approved scanner, so I want to stop it quickly."
],
"answer": "Block the entire workstation VLAN at the firewall and investigate later."
},
"B": {
"think": [
"Nothing was denied and... | {
"winner": "D",
"scores": {
"A": 6,
"B": 4,
"C": 5,
"D": 10
},
"errors": {
"A": [
"Blocks the whole VLAN without scoping containment to the single source host"
],
"B": [
"Treats policy-allowed traffic as benign and skips the scan pattern entirely"
],
"C": [
... | [
"Identifies the fan-out pattern without inventing tool attribution",
"Scopes containment to the source host instead of the VLAN",
"Separates confidence in the scan from confidence in compromise",
"Names the checks that would confirm or falsify the conclusion",
"States confidence levels explicitly"
] |
KODA-GRPO-000007 | remote-access | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise remote-access environment. Evidence is limited to what the listed tools return.",
"user_message": "Auth log review flagged user j.mercer overnight. Should I treat this as an incident?",
"known_facts": [
"auth_log_review shows 38 MFA... | {
"A": {
"think": [
"The reset at 01:50 sits right before the MFA storm, so account takeover is plausible rather than coincidental.",
"The outbound volume is the part I cannot explain away, but until I know who requested the reset I will not call it confirmed."
],
"answer": "Likely account tak... | {
"winner": "B",
"scores": {
"A": 7,
"B": 10,
"C": 4,
"D": 6
},
"errors": {
"A": [
"Recommends credential changes before preserving the logs that identify the reset requester"
],
"B": [],
"C": [
"Assumes the reset was legitimate without checking its requester and expl... | [
"Treats the reset-MFA-transfer sequence as a correlation rather than a coincidence",
"Names falsifying conditions and the checks that would settle them",
"Notes when a required capability such as threat_intel_lookup is unavailable",
"Calibrates severity as provisional instead of declaring compromise",
"Pres... |
KODA-GRPO-000008 | cloud | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a cloud environment. Evidence is limited to what the listed tools return.",
"user_message": "An alert fired on IAM activity for the payments principal. What do you make of it?",
"known_facts": [
"cloud_audit_query shows access key AKIA7F3Q used a... | {
"A": {
"think": [
"The key use and the policy attach land three minutes apart, which suggests one story, but the 03:00 deployment could legitimately have used this principal.",
"The facts that settle it are the deployment role, the object-read events, and the actual policy diff; config_diff and log_... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 4,
"D": 6
},
"errors": {
"A": [],
"B": [
"Attributes the policy attach to the deployment without checking whether the deploy used this principal and ignores the missing ticket"
],
"C": [
"Declares confirmed compromise... | [
"Correlates the key use, policy attach, and deployment before concluding",
"Names the checks that would confirm automation versus compromise",
"Contains the key before completing the investigation",
"Withholds a compromise verdict without read or exfiltration evidence",
"States provisional severity together... |
KODA-GRPO-000009 | email | hard | {
"system_context": "You are Koda IDS, an analyst assistant for mail security. Evidence is limited to what the listed tools return.",
"user_message": "Mail gateway and audit logs produced this cluster for the CFO mailbox. Walk me through it.",
"known_facts": [
"A message reached the CFO at 09:08 whose reply-t... | {
"A": {
"think": [
"SPF and DKIM both pass, which usually means the message is properly authenticated.",
"The link domain is only three days old, but new domains are common for vendors and contractors.",
"The forwarding rule gives me pause, though users do set personal rules, so I will mention ... | {
"winner": "C",
"scores": {
"A": 4,
"B": 6,
"C": 10,
"D": 5
},
"errors": {
"A": [
"Treats passing SPF and DKIM as proof of legitimacy when the DKIM domain is a third party, and ignores the forwarding rule"
],
"B": [
"Claims certainty the evidence does not support and blo... | [
"Looks past passing SPF and DKIM to what was actually authenticated",
"Connects the reply-to mismatch, new link domain, and inbox rule into one chain",
"Names sandbox_detonation as unavailable instead of waiting on it",
"Revises the initial benign impression explicitly",
"Preserves message headers and mailb... |
KODA-GRPO-000010 | api | easy | {
"system_context": "You are Koda IDS, an analyst assistant for a public API gateway. Evidence is limited to what the listed tools return.",
"user_message": "The gateway rate-limited a burst of traffic to /v1/transfers. Are we under attack?",
"known_facts": [
"rate_limit_metrics shows /v1/transfers received 1... | {
"A": {
"think": [
"Forty-one sources in one /24 failing auth across ten thousand attempts is a credential-guessing pattern even though nothing succeeded; a retry loop would usually keep the source count near one or two hosts, so I read intent as guessing while leaving the misconfiguration path open."
... | {
"winner": "A",
"scores": {
"A": 10,
"B": 6,
"C": 4,
"D": 5
},
"errors": {
"A": [],
"B": [
"Treats failed attempts as proof the episode is over and skips containment"
],
"C": [
"Declares compromise with no successful authentication anywhere in the evidence"
],
... | [
"Reasons from source fan-out to likely intent without declaring compromise",
"Scopes containment to the observed /24 instead of rotating all keys",
"Names the check that would distinguish guessing from a retry storm",
"States severity and confidence together",
"Keeps the block concise and evidence-bound"
] |
KODA-GRPO-000011 | database | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise data platform. Evidence is limited to what the listed tools return.",
"user_message": "The customer table saw a huge off-hours read. Is this an incident?",
"known_facts": [
"db_audit_review shows service account etl_reader SELECTed ... | {
"A": {
"think": [
"2.4 million rows and a gigabyte-scale transfer off-hours is the shape of data theft."
],
"answer": "Treat as data exfiltration: isolate the database host and open a critical incident. Severity critical."
},
"B": {
"think": [
"etl_reader is a service account, so rea... | {
"winner": "D",
"scores": {
"A": 5,
"B": 4,
"C": 7,
"D": 10
},
"errors": {
"A": [
"Isolates the database host before capturing audit and flow evidence"
],
"B": [
"Trusts the account name and ignores the timing anomaly entirely"
],
"C": [
"Stops short of che... | [
"Correlates the schedule change with the off-hours read",
"Names the specific checks that settle intent",
"Collects evidence before recommending isolation",
"Does not treat a service account name as proof of legitimacy",
"Calibrates severity as provisional with stated confidence",
"Uses two think blocks: ... |
KODA-GRPO-000012 | endpoint | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a managed endpoint fleet. Evidence is limited to what the listed tools return.",
"user_message": "EDR flagged a finance workstation. What is your read?",
"known_facts": [
"edr_console shows powershell.exe launched with an encoded command from WIN... | {
"A": {
"think": [
"A deployment ticket exists for the macro template and it landed minutes before this alert.",
"That ticket probably covers exactly this behavior, so the alert is likely benign."
],
"answer": "Expected macro template behavior; close the alert. Severity low."
},
"B": {
... | {
"winner": "B",
"scores": {
"A": 6,
"B": 10,
"C": 5,
"D": 3
},
"errors": {
"A": [
"Treats the existence of a deployment ticket as authorization for this specific command"
],
"B": [],
"C": [
"Rebuilds the host before capturing the command line or comparing it with the... | [
"Separates why the parent process ran from what it was allowed to execute",
"Names the correlation that would confirm or rule out sanctioned behavior",
"Preserves the command line before remediation",
"Does not treat absent persistence as proof of innocence",
"States severity with a confidence level",
"Us... |
KODA-GRPO-000013 | telemetry | hard | {
"system_context": "You are Koda IDS, an analyst assistant responsible for detection coverage. Evidence is limited to what the listed tools return.",
"user_message": "One subnet went silent in the SIEM overnight. Attacker or outage?",
"known_facts": [
"log_search returns zero events from subnet 10.20.0.0/16 ... | {
"A": {
"think": [
"Logging went silent on one subnet minutes after an upgrade, which is exactly how an attacker covers tracks.",
"The upgrade itself could be the cover story rather than the cause.",
"I will treat the gap as a confirmed intrusion window and escalate now."
],
"answer": "... | {
"winner": "C",
"scores": {
"A": 5,
"B": 4,
"C": 10,
"D": 7
},
"errors": {
"A": [
"Assumes log suppression by an attacker while the forwarder demonstrably kept transmitting"
],
"B": [
"Uses absence of firewall denies as proof nothing happened inside the gap"
],
"... | [
"Revises the intrusion reading when forwarder traffic contradicts it",
"Distinguishes queued events from dropped events and names the check",
"Reports the gap as unmonitored instead of inventing activity",
"Correlates across sources for the silent window",
"Separates detection assurance from confirmed compr... |
KODA-GRPO-000014 | monitoring | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a SIEM-driven detection environment. Evidence is limited to what the listed tools return.",
"user_message": "Brute-force alerts stopped firing last night but auth failures keep climbing. What happened?",
"known_facts": [
"log_search shows the rul... | {
"A": {
"think": [
"The content update makes timing point at routine tuning, but a suppression range outside the ticket scope is not automatically authorized by that ticket.",
"What settles it: diff the rule against the approved content package, confirm who held the svc-siem-admin session at 21:07, a... | {
"winner": "A",
"scores": {
"A": 10,
"B": 6,
"C": 4,
"D": 5
},
"errors": {
"A": [],
"B": [
"Treats timing proximity as authorization for a suppression outside ticket scope"
],
"C": [
"Attributes the edit to compromise without checking the session or the approved pack... | [
"Separates change timing from change authorization",
"Names the diff and session checks that would confirm scope",
"Restores detection coverage before waiting on answers",
"Does not assume admin-account activity is compromise",
"States severity with a confidence level",
"Uses two think blocks: expected ca... |
KODA-GRPO-000015 | data-handling | hard | {
"system_context": "You are Koda IDS, an analyst assistant for a regulated data environment. Evidence is limited to what the listed tools return.",
"user_message": "A large export went out and then a workstation uploaded hundreds of megabytes. Walk me through it.",
"known_facts": [
"db_audit_review shows use... | {
"A": {
"think": [
"Self-approval, then a bulk export, then a personal-cloud upload: that chain is classic insider exfiltration.",
"The timestamps line up too neatly for coincidence.",
"I am confident enough to call this confirmed theft."
],
"answer": "Confirmed insider data theft by a.... | {
"winner": "D",
"scores": {
"A": 6,
"B": 4,
"C": 8,
"D": 10
},
"errors": {
"A": [
"Declares confirmed theft without matching the upload to the export or checking approval policy"
],
"B": [
"Treats the ticket as full authorization and skips the self-approval conflict"
... | [
"Weighs the ticket against the self-approval conflict instead of trusting either alone",
"Names the checks that separate sanctioned migration from theft",
"States that forensic_imaging is unavailable rather than implying file proof",
"Preserves evidence while containing access",
"Calibrates severity with st... |
KODA-GRPO-000016 | containers | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a container platform. Evidence is limited to what the listed tools return.",
"user_message": "A production pod differs from its repo manifest. How alarmed should I be?",
"known_facts": [
"deployment_history shows workload payments-api-7d9f was de... | {
"A": {
"think": [
"Workstation deployments happen during hotfixes, especially at 04:12.",
"The hotfix ticket exists, so the whole deployment was sanctioned."
],
"answer": "Approved hotfix; no action required."
},
"B": {
"think": [
"The hotfix ticket explains the deployment but ... | {
"winner": "B",
"scores": {
"A": 6,
"B": 10,
"C": 5,
"D": 4
},
"errors": {
"A": [
"Treats the ticket as covering a privilege change the ticket never mentions"
],
"B": [],
"C": [
"Declares a backdoor with no evidence of host writes or anomalous egress"
],
"D":... | [
"Separates deployment authorization from spec authorization",
"Names the checks that decide drift versus compromise",
"Recommends reverting to the declared manifest before deeper work",
"Does not equate quiet network traffic with safety",
"States severity with confidence and a no-compromise caveat",
"Uses... |
KODA-GRPO-000017 | dns | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "Resolver telemetry on one host looks odd. Worth a look?",
"known_facts": [
"dns_query shows host 10.0.7.12 issued 3,200 queries in five minutes, 92 per... | {
"A": {
"think": [
"Nine in ten lookups failing with random labels reads as beaconing even though total volume is small and nothing large left the host."
],
"answer": "Likely DNS beaconing from kiosk-lobby-2: block the observed domains at the resolver, isolate the terminal, and pull its process lis... | {
"winner": "C",
"scores": {
"A": 8,
"B": 5,
"C": 10,
"D": 3
},
"errors": {
"A": [
"Advises isolation without first checking whether any query actually resolved"
],
"B": [
"Attributes NXDOMAIN noise to captive portals with no supporting evidence"
],
"C": [],
"... | [
"Recognizes NXDOMAIN rate and label entropy as a beacon signal",
"Checks whether any query resolved before concluding",
"Does not clear a host merely because transfers are small",
"States severity with a confidence level",
"Keeps containment scoped to the resolver and the one host"
] |
KODA-GRPO-000018 | backup | hard | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise backup environment. Evidence is limited to what the listed tools return.",
"user_message": "Backup verification failed overnight and the catalog looks touched. What do I do?",
"known_facts": [
"file_integrity_check shows 14 backup s... | {
"A": {
"think": [
"Rewritten indexes with unchanged payloads reads like catalog maintenance that went wrong.",
"The login from jump-03 is odd, but break-glass work happens on jump hosts.",
"I will raise it with the backup team in the morning."
],
"answer": "Probable maintenance mishap;... | {
"winner": "D",
"scores": {
"A": 5,
"B": 6,
"C": 7,
"D": 10
},
"errors": {
"A": [
"Defers to tomorrow while recoverability is already unverified"
],
"B": [
"Declares destruction without checking offsite copies or identifying the pull source"
],
"C": [
"Trea... | [
"Revises the accidental-corruption reading against the unfamiliar source host",
"Names checks that separate resync from staging for destruction",
"Flags forensic_imaging as unavailable instead of implying host file proof",
"Protects recoverability by freezing mutations and verifying offsite copies",
"Separa... |
KODA-GRPO-000019 | identity | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an identity platform. Evidence is limited to what the listed tools return.",
"user_message": "A login spray ended in one success, then something got granted. Connected?",
"known_facts": [
"auth_log_review shows 612 login attempts across 47 distin... | {
"A": {
"think": [
"A spray from one source that ends in success, followed four minutes later by a consent grant carrying offline_access, reads as a single operation rather than two coincidences.",
"What would falsify it: m.abel confirming she approved the prompt, and the app appearing in our sanctio... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 4,
"D": 6
},
"errors": {
"A": [],
"B": [
"Treats the spray success and the immediate consent grant as unrelated routine events"
],
"C": [
"Recommends directory-wide rotation without scoping to the affected account"
... | [
"Correlates the spray success with the consent grant by timing and scope",
"Names the facts that would confirm or rule out takeover",
"Revokes the grant before completing the investigation",
"Scopes remediation to affected accounts rather than the directory",
"States severity with a confidence level",
"Us... |
KODA-GRPO-000020 | api | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a multi-tenant API platform. Evidence is limited to what the listed tools return.",
"user_message": "Partner traffic is returning rows we did not expect. Is this an incident?",
"known_facts": [
"log_search shows 88 requests using tenant A tokens ... | {
"A": {
"think": [
"The requests used a valid token and stayed inside published rate limits.",
"Nothing was rejected, so the platform treated the calls as legitimate."
],
"answer": "Authorized traffic within limits; no action required."
},
"B": {
"think": [
"A valid token explai... | {
"winner": "B",
"scores": {
"A": 5,
"B": 10,
"C": 4,
"D": 6
},
"errors": {
"A": [
"Equates successful authentication with correct authorization"
],
"B": [],
"C": [
"Dismisses confirmed cross-tenant reads as ID collision without checking responses"
],
"D": [
... | [
"Separates authentication from authorization",
"Correlates the exposure with the 16:30 rollout using config_diff",
"Scopes remediation to the affected path and objects",
"Distinguishes confirmed exposure from unproven cause",
"Preserves request records before making changes",
"States severity with split c... |
KODA-GRPO-000021 | cloud | easy | {
"system_context": "You are Koda IDS, an analyst assistant for a cloud environment. Evidence is limited to what the listed tools return.",
"user_message": "An audit flagged a storage bucket. How bad is it?",
"known_facts": [
"cloud_audit_query shows bucket payroll-exports grants allUsers storage.objectViewer... | {
"A": {
"think": [
"Terraform applied the policy, so somebody intended the change."
],
"answer": "Intentional sharing from the 11:12 apply; no action required."
},
"B": {
"think": [
"Public buckets are common for static assets, and 17 requests is a small number."
],
"answer": ... | {
"winner": "C",
"scores": {
"A": 4,
"B": 5,
"C": 10,
"D": 3
},
"errors": {
"A": [
"Assumes terraform intent with no ticket or confirmation"
],
"B": [
"Minimizes a regulated-data bucket based on request count alone"
],
"C": [],
"D": [
"Treats public payr... | [
"Treats missing intent evidence as uncertainty rather than permission",
"Checks whether anonymous GETs retrieved the sensitive objects",
"Removes the grant before investigating intent",
"Judges severity by data class rather than request volume",
"States severity with a confidence level"
] |
KODA-GRPO-000022 | network | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "Switch telemetry flagged a workstation on the access VLAN. What is happening?",
"known_facts": [
"netflow_analyzer shows 10.0.5.77 sent ARP requests fo... | {
"A": {
"think": [
"ARP traffic at that rate is ordinary network churn, and nothing was denied."
],
"answer": "Normal network noise; no action required."
},
"B": {
"think": [
"One host answering for three addresses in ninety seconds is MAC impersonation behavior, whether a misconfigur... | {
"winner": "B",
"scores": {
"A": 5,
"B": 10,
"C": 6,
"D": 4
},
"errors": {
"A": [
"Treats absent firewall denies as proof the activity is benign"
],
"B": [],
"C": [
"Declares a confirmed interception with no evidence of captured traffic"
],
"D": [
"Igno... | [
"Identifies MAC impersonation without overclaiming interception",
"Names inventory and port-mirror checks that would confirm",
"Avoids treating absent denies as benign proof",
"States severity with a confidence level",
"Keeps containment scoped to one host"
] |
KODA-GRPO-000023 | endpoint | easy | {
"system_context": "You are Koda IDS, an analyst assistant for a managed endpoint fleet. Evidence is limited to what the listed tools return.",
"user_message": "EDR reports a rename storm on a designer workstation.",
"known_facts": [
"edr_console shows 214 files on design-ws-09 renamed with a .lockedj extens... | {
"A": {
"think": [
"Ransomware encrypts system files, and here they are untouched."
],
"answer": "Not ransomware since system files are intact; resume normal monitoring."
},
"B": {
"think": [
"214 renames are disruptive but I cannot name the extension without a threat feed lookup."
... | {
"winner": "C",
"scores": {
"A": 5,
"B": 6,
"C": 10,
"D": 4
},
"errors": {
"A": [
"Uses untouched system files to dismiss mass renaming"
],
"B": [
"Blocks containment on a threat-feed lookup that is unavailable"
],
"C": [],
"D": [
"Attributes renames to... | [
"Judges on behavior rather than family attribution",
"Notes that threat_intel_lookup is unavailable instead of waiting on it",
"Preserves process and file evidence before cleanup",
"Checks shares reached by the affected host",
"States severity with a confidence level"
] |
KODA-GRPO-000024 | identity | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an identity platform. Evidence is limited to what the listed tools return.",
"user_message": "Sign-in logs put one user in two countries at once. Real?",
"known_facts": [
"auth_log_review shows m.torres signed in at 08:02 from Bogota on a new dev... | {
"A": {
"think": [
"Two completed MFA sign-ins seventeen minutes apart on different continents cannot both be one user holding one phone, so one session is stolen even though both carried valid factors.",
"What would settle which side is real: device fingerprint history for the new authenticator, whe... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 4,
"D": 6
},
"errors": {
"A": [],
"B": [
"Treats successful MFA on both sessions as proof one user controlled them"
],
"C": [
"Equates factor success with session legitimacy"
],
"D": [
"Disables the acco... | [
"Recognizes that two continents with one phone implies a stolen session",
"Names device and registration checks that identify the stolen side",
"Contains before confirming which sign-in is real",
"Avoids permanent lockout without supporting evidence",
"States severity with a confidence level",
"Uses two t... |
KODA-GRPO-000025 | containers | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a container platform. Evidence is limited to what the listed tools return.",
"user_message": "Kubernetes RBAC changed overnight. How much does this matter?",
"known_facts": [
"config_diff shows clusterrolebinding pipeline-runner-admin granting cl... | {
"A": {
"think": [
"Runners sometimes need broader rights during migrations.",
"A missing ticket does not prove malice when incidents move fast."
],
"answer": "Probable emergency grant; check with the platform team later. Severity low."
},
"B": {
"think": [
"cluster-admin on a r... | {
"winner": "D",
"scores": {
"A": 5,
"B": 7,
"C": 6,
"D": 10
},
"errors": {
"A": [
"Treats missing tickets as acceptable for standing RBAC changes"
],
"B": [
"Recommends removal but skips investigating who applied it and whether it was used"
],
"C": [
"Decla... | [
"Separates a control break from established compromise",
"Names the usage and authentication checks that decide intent",
"Removes the excess grant while preserving audit evidence",
"Checks whether the source host is authorized for cluster access",
"States severity with a confidence level",
"Uses two think... |
KODA-GRPO-000026 | ci_cd | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a build and release environment. Evidence is limited to what the listed tools return.",
"user_message": "A workflow changed outside the normal release path. Look into it?",
"known_facts": [
"deployment_history shows workflow release.yml gained a ... | {
"A": {
"think": [
"The artifact came out signed and the runner image is clean, so pipeline output looks normal.",
"I will let it stand and revisit if something breaks."
],
"answer": "Output looks correct; no action required."
},
"B": {
"think": [
"A clean signature only tells m... | {
"winner": "B",
"scores": {
"A": 5,
"B": 10,
"C": 6,
"D": 5
},
"errors": {
"A": [
"Treats a valid signature as evidence the added step was reviewed"
],
"B": [],
"C": [
"Assumes chain of custody without inspecting the added step"
],
"D": [
"Rotates signi... | [
"Separates artifact signing from change review",
"Names the checks on the script host and step logs",
"Reverts to the reviewed workflow before deeper analysis",
"Avoids key rotation before scoping the execution",
"States severity with a confidence level",
"Uses two think blocks: normal-looking output, the... |
KODA-GRPO-000027 | database | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise data platform. Evidence is limited to what the listed tools return.",
"user_message": "Table auditing stopped on the customer table overnight. Thoughts?",
"known_facts": [
"db_audit_review shows the audit trigger on customers was dr... | {
"A": {
"think": [
"The grant and the drop are connected, and the ticket wording does not match the right that was given."
],
"answer": "Malicious schema change; suspend p.novak and svc_reporting. Severity critical."
},
"B": {
"think": [
"Migrations sometimes drop and recreate trigger... | {
"winner": "C",
"scores": {
"A": 6,
"B": 5,
"C": 10,
"D": 7
},
"errors": {
"A": [
"Suspends accounts before reconstructing what happened after the trigger dropped"
],
"B": [
"Explains the drop as migration with no release or ticket evidence"
],
"C": [],
"D": ... | [
"Connects the grant mismatch with the later trigger drop as one chain",
"Names checks that separate botched migration from evasion",
"Revokes rights and restores auditing before questioning actors",
"Plans reconstruction of the unaudited window",
"States severity with a confidence level",
"Uses two think ... |
KODA-GRPO-000028 | cloud | hard | {
"system_context": "You are Koda IDS, an analyst assistant for a cloud environment. Evidence is limited to what the listed tools return.",
"user_message": "Root activity and key changes on the production account overnight. Where do I start?",
"known_facts": [
"cloud_audit_query shows a root sign-in at 01:44 ... | {
"A": {
"think": [
"Root with valid MFA at 01:44 could be the owner handling an emergency.",
"Key creation often follows root sessions in operational work.",
"The describe calls may be troubleshooting."
],
"answer": "Probable owner activity; confirm with the account owner in the morning... | {
"winner": "D",
"scores": {
"A": 5,
"B": 4,
"C": 7,
"D": 10
},
"errors": {
"A": [
"Waits for morning while a live key and unexplained region activity remain"
],
"B": [
"Treats root MFA success as proof the owner performed the actions"
],
"C": [
"Claims conf... | [
"Revises the emergency-ops reading against the MFA-removal sequence",
"Names the owner-confirmation facts that would falsify takeover",
"Notes that threat_intel_lookup is unavailable for ASN context",
"Contains key and instance risk before intent is proven",
"Preserves root audit records while acting",
"S... |
KODA-GRPO-000029 | monitoring | hard | {
"system_context": "You are Koda IDS, an analyst assistant for a detection platform. Evidence is limited to what the listed tools return.",
"user_message": "Paging has been quiet for two days. Is that good news?",
"known_facts": [
"log_search shows the dead-man switch synthetic event has not fired since 03:4... | {
"A": {
"think": [
"Quiet paging with a healthy router is not good news; six severity mappings were demoted minutes after a dead-man switch went silent, and both facts came from configuration rather than load.",
"My initial outage reading gives way to configuration interference unless someone shows t... | {
"winner": "A",
"scores": {
"A": 10,
"B": 6,
"C": 5,
"D": 4
},
"errors": {
"A": [],
"B": [
"Attributes the demotion to intended tuning without diffing the approved package"
],
"C": [
"Declares insider suppression before identifying who ran the automation"
],
... | [
"Reads quiet paging as a coverage problem rather than an all-clear",
"Connects the dead-man silence with the severity demotion",
"Names the diff, identity, and replay checks that settle it",
"Restores mappings and reports the window as unmonitored",
"Withholds a compromise verdict pending the actor check",
... |
KODA-GRPO-000030 | remote-access | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "A file server took an outside RDP session last night. Worth escalating?",
"known_facts": [
"firewall_query shows rule R-2210 opened TCP/3389 to srv-fil... | {
"A": {
"think": [
"An internet-open RDP rule with no ticket, a first external login by a local account idle for a month, and 1.2 GB leaving in one session is an intrusion pattern until proven otherwise; the missing ticket is what rules out routine support. I would close the rule, terminate the session, an... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 6,
"D": 4
},
"errors": {
"A": [],
"B": [
"Leaves an internet-open RDP rule in place for a support team no ticket evidences"
],
"C": [
"Equates a policy breach with confirmed compromise without reviewing session activi... | [
"Links open rule, first external login, and idle local account into one chain",
"Uses the missing ticket to reject routine-support explanations",
"Contains by closing the rule and terminating the session",
"Plans review of what the account actually accessed",
"States severity with a confidence level"
] |
KODA-GRPO-000031 | dns | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "Users report certificate warnings on the portal right after a DNS change. What happened?",
"known_facts": [
"dns_query shows the A record for portal.ac... | {
"A": {
"think": [
"Certificate warnings right after a record change mean users reached a host that does not match the certificate, which an engineer testing could also cause."
],
"answer": "Probable engineering change; confirm with the DNS owners tomorrow. Severity low."
},
"B": {
"think":... | {
"winner": "B",
"scores": {
"A": 6,
"B": 10,
"C": 5,
"D": 4
},
"errors": {
"A": [
"Waits for confirmation while users keep reaching the new host"
],
"B": [],
"C": [
"Calls it migration despite no ticket and matching certificate warnings"
],
"D": [
"Mini... | [
"Connects the unticketed change with the certificate warnings",
"Recommends revert and block before investigation completes",
"Asks whether users submitted credentials to the new host",
"Does not minimize based on session count alone",
"States severity with a confidence level"
] |
KODA-GRPO-000032 | email | medium | {
"system_context": "You are Koda IDS, an analyst assistant for mail security. Evidence is limited to what the listed tools return.",
"user_message": "DMARC failures exploded this morning. Attack or our fault?",
"known_facts": [
"log_search shows DMARC failures for acme-corp.example rose from about 10 per day... | {
"A": {
"think": [
"Failure volume at that scale means someone is spoofing our domain.",
"Failures just show the SPF system working as designed."
],
"answer": "Spoofing campaign; no action beyond monitoring since DMARC rejects them."
},
"B": {
"think": [
"The include removal at ... | {
"winner": "C",
"scores": {
"A": 6,
"B": 5,
"C": 10,
"D": 6
},
"errors": {
"A": [
"Treats authentication failures as attacks without tracing the DNS edit that preceded them"
],
"B": [
"Assumes authorized offboarding with no ticket evidence"
],
"C": [],
"D": [... | [
"Correlates the failure spike with the preceding TXT edit",
"Separates authorized offboarding from unauthorized change",
"Identifies the actor behind the 08:55 edit as the primary question",
"Checks whether legitimate partner mail is being harmed",
"States severity with a confidence level",
"Uses two thin... |
KODA-GRPO-000033 | identity | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an identity platform. Evidence is limited to what the listed tools return.",
"user_message": "A dormant admin account came back to life. How do I read this?",
"known_facts": [
"auth_log_review shows account e.whitfield, unused for 187 days, signe... | {
"A": {
"think": [
"Dormant accounts are sometimes reopened by their owners for emergencies.",
"The retained role may be intentional for continuity during transition."
],
"answer": "Probably the former employee returning; confirm with HR before acting. Severity medium."
},
"B": {
"thi... | {
"winner": "D",
"scores": {
"A": 6,
"B": 4,
"C": 7,
"D": 10
},
"errors": {
"A": [
"Defers to HR while an exempt dormant admin session stays active"
],
"B": [
"Treats a closed ticket as completion without checking the unchecked step"
],
"C": [
"Declares comp... | [
"Notices the offboarding step that was never completed",
"Weighs dormancy, geography, and MFA exemption together",
"Contains session and token before identifying the operator",
"Confirms with HR rather than assuming identity theft",
"States severity with a confidence level",
"Uses two think blocks: proces... |
KODA-GRPO-000034 | database | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise data platform. Evidence is limited to what the listed tools return.",
"user_message": "One database login is showing up from two servers. Problem?",
"known_facts": [
"db_audit_review shows login app_orders active concurrently from a... | {
"A": {
"think": [
"Two hosts sharing one login means either inventory is wrong or the credential leaked; both readings justify the same first move, because I cannot tell them apart from the database side alone.",
"What would settle it: whether app-node-19 exists in asset and deployment records, what... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 6,
"D": 4
},
"errors": {
"A": [],
"B": [
"Assumes scale-out without any deployment or ticket evidence"
],
"C": [
"Rekeys everything before capturing query history or identifying the host"
],
"D": [
"Defe... | [
"Frames the ambiguity as rogue host versus inventory gap",
"Names inventory, process, and query-pattern checks",
"Captures query history before rotating the credential",
"Restricts access while the question stays open",
"States severity with a confidence level",
"Uses two think blocks: both readings, then... |
KODA-GRPO-000035 | api | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a multi-tenant API platform. Evidence is limited to what the listed tools return.",
"user_message": "Our payment webhook took hundreds of duplicate deliveries during maintenance. Anything to worry about?",
"known_facts": [
"log_search shows 412 d... | {
"A": {
"think": [
"The maintenance ticket covers this window, so retries are expected behavior.",
"Duplicate writes on our side are an application bug rather than a security issue."
],
"answer": "Partner maintenance retries; file an idempotency bug. Severity low."
},
"B": {
"think": ... | {
"winner": "B",
"scores": {
"A": 6,
"B": 10,
"C": 7,
"D": 4
},
"errors": {
"A": [
"Treats the ticket as covering duplicate application while idempotency stays missing"
],
"B": [],
"C": [
"Declares replay attack without checking signature verification or partner sourc... | [
"Separates why retries happened from why duplicates were accepted",
"Names idempotency and signature checks that decide the risk",
"Hardens the consumer before labeling the traffic",
"Verifies the source against partner registration",
"States severity with a confidence level",
"Uses two think blocks: beni... |
KODA-GRPO-000036 | telemetry | hard | {
"system_context": "You are Koda IDS, an analyst assistant responsible for log pipeline integrity. Evidence is limited to what the listed tools return.",
"user_message": "The main collector changed behavior overnight and is sending data somewhere new.",
"known_facts": [
"file_integrity_check shows /opt/colle... | {
"A": {
"think": [
"Volume up fourfold, an unknown destination, and a changed binary together mean a compromised collector.",
"Fastest containment is pulling power before anything else leaves."
],
"answer": "Collector compromised; power off collector-02 and open a critical incident. Severity ... | {
"winner": "C",
"scores": {
"A": 7,
"B": 5,
"C": 10,
"D": 4
},
"errors": {
"A": [
"Destroys volatile evidence by powering off before preserving records"
],
"B": [
"Assumes a vendor patch with no release or ticket evidence"
],
"C": [],
"D": [
"Explains f... | [
"Revises the patch reading against the missing login and unknown peer",
"Names checks that separate tampered update from vendor release",
"Flags forensic_imaging as unavailable while still isolating",
"Marks the event window untrusted rather than deleting it",
"Preserves evidence off the affected host",
"... |
KODA-GRPO-000037 | cloud | hard | {
"system_context": "You are Koda IDS, an analyst assistant for a cloud environment. Evidence is limited to what the listed tools return.",
"user_message": "IAM shows an escalation chain completed last night. Break it down for me.",
"known_facts": [
"iam_review shows role build-deploy gained iam:PassRole on r... | {
"A": {
"think": [
"Self-approved tickets happen when managers are offline.",
"The chain completed without errors, so it may have been planned work."
],
"answer": "Likely planned elevation; confirm with security architecture later. Severity medium."
},
"B": {
"think": [
"PassRol... | {
"winner": "D",
"scores": {
"A": 5,
"B": 7,
"C": 4,
"D": 10
},
"errors": {
"A": [
"Treats self-approval as acceptable while an admin session stays live"
],
"B": [
"Suspends the user before reconstructing what the admin session did"
],
"C": [
"Accepts a self... | [
"Recognizes a completed escalation chain rather than a single odd action",
"Names self-approval as the control failure",
"Contains by detaching policy and disabling sessions before actor analysis",
"Notes threat_intel_lookup is unavailable for ASN context",
"Plans reconstruction of the post-escalation sessi... |
KODA-GRPO-000038 | endpoint | easy | {
"system_context": "You are Koda IDS, an analyst assistant for a managed endpoint fleet. Evidence is limited to what the listed tools return.",
"user_message": "A workstation has an unsigned binary sitting in a public folder. Act?",
"known_facts": [
"file_integrity_check shows C:\\Users\\Public\\svcupdate.ex... | {
"A": {
"think": [
"Unsigned binaries in the Public folder show up from installers regularly."
],
"answer": "Probably an installer leftover; delete it later. Severity low."
},
"B": {
"think": [
"With no outbound connections, nothing is communicating, so risk is nil."
],
"answe... | {
"winner": "C",
"scores": {
"A": 5,
"B": 5,
"C": 10,
"D": 4
},
"errors": {
"A": [
"Treats missing inventory as an acceptable explanation without checking persistence"
],
"B": [
"Uses absent egress as proof the file is harmless"
],
"C": [],
"D": [
"Recom... | [
"Treats unexplained presence as risk without claiming malice",
"Checks persistence before deciding",
"Asks the user about the 08:31 launch",
"Preserves the file before deletion or rebuild",
"States severity with a confidence level"
] |
KODA-GRPO-000039 | network | easy | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise network. Evidence is limited to what the listed tools return.",
"user_message": "Netflow shows an 18 GB off-hours transfer to a new destination. Suspicious?",
"known_facts": [
"netflow_analyzer shows srv-fs-02 sent 18 GB to 198.51.1... | {
"A": {
"think": [
"An unticketed egress rule added twenty minutes before an off-hours transfer, from an account outside its usual hours to a destination with no history, is a staging pattern, and the truncated file logs mean I cannot show what else was read. I would remove the rule, terminate the session,... | {
"winner": "A",
"scores": {
"A": 10,
"B": 5,
"C": 4,
"D": 5
},
"errors": {
"A": [],
"B": [
"Attributes the transfer to a scheduled job with no ticket or job history"
],
"C": [
"Ignores the unticketed rule and the destination with no history"
],
"D": [
"... | [
"Chains the new rule, off-hours login, and unknown destination",
"Notes the logging gap instead of pretending full visibility",
"Contains by removing the rule and session",
"Preserves flow records before deeper analysis",
"States severity with a confidence level"
] |
KODA-GRPO-000040 | identity | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an identity platform. Evidence is limited to what the listed tools return.",
"user_message": "A user got MFA-pushed 14 times, then her password changed itself. Take it from there.",
"known_facts": [
"auth_log_review shows 14 push prompts for l.ch... | {
"A": {
"think": [
"Failed pushes followed by a reset from somewhere else is a classic takeover attempt.",
"The recovery email being used suggests the attacker holds her mailbox."
],
"answer": "Confirmed takeover; disable the account and freeze payment approvals. Severity critical."
},
"B... | {
"winner": "D",
"scores": {
"A": 6,
"B": 4,
"C": 5,
"D": 10
},
"errors": {
"A": [
"Claims confirmed takeover without checking whether the reset was hers"
],
"B": [
"Treats blocked pushes as the end of the incident while a reset follows"
],
"C": [
"Assumes a... | [
"Recognizes the reset channel as separate from the failed pushes",
"Names checks on recovery email, sessions, and approval activity",
"Contains sessions before attribution completes",
"Withholds confirmed takeover despite a coherent attack story",
"States severity with a confidence level",
"Uses two think... |
KODA-GRPO-000041 | containers | medium | {
"system_context": "You are Koda IDS, an analyst assistant for a container platform. Evidence is limited to what the listed tools return.",
"user_message": "A pod rolled out with no scan record and the admission policy changed first. Coincidence?",
"known_facts": [
"log_search shows admission records for pod... | {
"A": {
"think": [
"The release ticket exists, so version 2.9.1 was approved to ship.",
"Scan records lag when scanners run on demand."
],
"answer": "Approved release with scanner lag; no action required."
},
"B": {
"think": [
"The release ticket covers shipping 2.9.1, but it do... | {
"winner": "B",
"scores": {
"A": 6,
"B": 10,
"C": 6,
"D": 4
},
"errors": {
"A": [
"Treats the release ticket as covering both the image and the policy downgrade"
],
"B": [],
"C": [
"Deletes the workload before comparing the digest or scoping the warn window"
],
... | [
"Separates release approval from scan and policy state",
"Names digest and policy-actor checks that settle it",
"Scopes the bypass window to other workloads",
"Restores enforcement before the investigation completes",
"States severity with a confidence level",
"Uses two think blocks: the ticket explanatio... |
KODA-GRPO-000042 | database | medium | {
"system_context": "You are Koda IDS, an analyst assistant for an enterprise data platform. Evidence is limited to what the listed tools return.",
"user_message": "A temp account read 91k payment rows during maintenance. Inside or outside the ticket?",
"known_facts": [
"db_audit_review shows user dba.temp cr... | {
"A": {
"think": [
"The maintenance ticket covers work in this window, so the reads were probably part of it."
],
"answer": "Maintenance activity; no action required."
},
"B": {
"think": [
"A temporary account created and destroyed in thirty minutes is cleanup, which maintenance often... | {
"winner": "C",
"scores": {
"A": 5,
"B": 6,
"C": 10,
"D": 6
},
"errors": {
"A": [
"Uses window overlap to excuse reads the ticket never covered"
],
"B": [
"Explains away the manual drop and external transfer as routine"
],
"C": [],
"D": [
"Declares exfi... | [
"Separates what the ticket authorized from what the account did",
"Correlates the external transfer with the read window",
"Preserves audit evidence before interviews",
"Withholds an exfiltration verdict pending correlation",
"States severity with a confidence level",
"Uses two think blocks: timing overla... |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 93