Question 350
A third-party cloud app received persistent mailbox read permissions through a user consent flow after a phishing link. Which scoping query or comparison best tests the working hypothesis?
- Find recipients and hunt the spawned executable across devices
- Verify pending transactions with finance via known callback numbers
- Identify affected identities and all permission scopes
- Find all recipients and identify submitted accounts
- Map poster distribution and resulting identity sign-ins
Explanation
Correct Answer
C:In the Malicious OAuth app consent response case, incident scope depends on the app's grants, not only the initially clicked link; the observation “A third-party cloud app received persistent mailbox read permissions through a user consent flow after a phishing link” makes this scope analysis choice the fitting one.
Incorrect Answers
A:The choice is relevant to Malicious email attachment execution, where campaign scope requires both mail and endpoint visibility; for scope analysis in Malicious OAuth app consent response, incident scope depends on the app's grants, not only the initially clicked link.
B:For scope analysis in Malicious OAuth app consent response, Business email compromise wire request is a different mechanism: independent confirmation limits reliance on potentially compromised mail threads; here, incident scope depends on the app's grants, not only the initially clicked link.
D:For scope analysis in Malicious OAuth app consent response, Targeted phishing mail delivery is a different mechanism: campaign scoping goes beyond the first reporter to other targeted users; here, incident scope depends on the app's grants, not only the initially clicked link.
E:The choice is relevant to QR-code phishing landing page, where physical and web evidence jointly estimate exposed employee populations; for scope analysis in Malicious OAuth app consent response, incident scope depends on the app's grants, not only the initially clicked link.
Question 351
A SIEM rule deployment removes a required host field and the rule stops producing matches after a parser update. The finding has been corroborated and the response team has authorization to act. Which response is the most appropriate at this point?
- Roll back the faulty version and repair the field dependency
- Apply role-aware thresholds without exempting backup servers entirely
- Replace the subnet exemption with actor-and-task-scoped conditions
- Escalate the complete attack chain as one incident
- Implement appropriate rolling-window correlation with throttling
Explanation
Correct Answer
A:Restoring previous logic recovers coverage while a corrected query is tested; this is the relevant response decision mechanism for Detection-as-code regression given “A SIEM rule deployment removes a required host field and the rule stops producing matches after a parser update”.
Incorrect Answers
B:For response decision in Detection-as-code regression, Peer-group baseline mismatch is a different mechanism: unusual backup traffic can still be malicious and deserves coverage; here, restoring previous logic recovers coverage while a corrected query is tested.
C:The choice is relevant to Overbroad allowlist suppression, where narrow suppressions preserve coverage outside the approved maintenance context; for response decision in Detection-as-code regression, restoring previous logic recovers coverage while a corrected query is tested.
D:For response decision in Detection-as-code regression, Multi-stage attack sequence correlation is a different mechanism: unified case context prevents disjoint alerts from obscuring campaign progression; here, restoring previous logic recovers coverage while a corrected query is tested.
E:The choice is relevant to Sliding-window aggregation error, where window design catches boundary-spanning activity while limiting alert storms; for response decision in Detection-as-code regression, restoring previous logic recovers coverage while a corrected query is tested.
Question 352
Two analysts handling the same suspected phishing event take incompatible containment steps because the playbook says only investigate. Which source would most directly corroborate the observation?
- Detection and containment timestamps for confirmed cases
- Original alert export with source and event timestamps
- Asset inventory criticality and the detection evidence
- Disposition codes and supporting false-positive examples
- Current playbook revisions and the two case timelines
Explanation
Correct Answer
E:For corroboration in SOC runbook decision ambiguity, comparing written guidance with actual actions pinpoints the ambiguous decision branch; this applies to the reported “Two analysts handling the same suspected phishing event take incompatible containment steps because the playbook says only investigate”.
Incorrect Answers
A:For corroboration in SOC runbook decision ambiguity, SOC management performance metric is a different mechanism: verified incident milestones support meaningful measures of operational effectiveness; here, comparing written guidance with actual actions pinpoints the ambiguous decision branch.
B:The choice is relevant to SOC case evidence preservation, where immutable source context lets another analyst reproduce the investigation and distinguish collection times; for corroboration in SOC runbook decision ambiguity, comparing written guidance with actual actions pinpoints the ambiguous decision branch.
C:For corroboration in SOC runbook decision ambiguity, Alert severity versus priority is a different mechanism: business ownership and supporting telemetry are necessary to justify an urgency change; here, comparing written guidance with actual actions pinpoints the ambiguous decision branch.
D:The choice is relevant to SOC detection quality governance, where documented closures show which benign behaviors are causing the unwanted matches; for corroboration in SOC runbook decision ambiguity, comparing written guidance with actual actions pinpoints the ambiguous decision branch.
Question 353
Two organizations want to share machine-readable threat objects including indicator relationships and attack patterns. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?
- Merge duplicate observables without discarding source histories
- Configure authorized collection polling with safe rate limits
- Mark the claim unconfirmed and avoid disruptive blocking
- Normalize the shared objects into the intelligence platform
Explanation
Correct Answer
D:For response decision in STIX structured intelligence exchange, structured import preserves entities for enrichment and correlation; this applies to the reported “Two organizations want to share machine-readable threat objects including indicator relationships and attack patterns”.
Incorrect Answers
A:For the alternative Threat intelligence platform deduplication situation, preserving attribution supports later re-evaluation and false-positive handling; by contrast, for STIX structured intelligence exchange response decision, structured import preserves entities for enrichment and correlation.
B:In TAXII intelligence distribution, managed collection access supports reliable feed updates with controlled credentials; the reported STIX structured intelligence exchange case calls for a different response decision conclusion because structured import preserves entities for enrichment and correlation.
C:For the alternative Intelligence source circular reporting situation, unverified stories should not trigger high-impact controls without local risk evidence; by contrast, for STIX structured intelligence exchange response decision, structured import preserves entities for enrichment and correlation.
Question 354
A network sensor sends sensitive syslog over unencrypted UDP across an untrusted transit segment. Which evidence collection choice best supports this investigation?
- Packet capture showing UDP 514 log payloads in clear text
- Forwarder queue depth, retry and acknowledgement metrics
- Archive lifecycle and object-lock configuration evidence
- Raw sample versus parsed field mapping and parser version
- Device NTP status with raw timestamp and timezone fields
Explanation
Correct Answer
A:For corroboration in Secure syslog transport mismatch, the wire trace confirms both transport choice and exposure of event content; this applies to the reported “A network sensor sends sensitive syslog over unencrypted UDP across an untrusted transit segment”.
Incorrect Answers
B:For the alternative Forwarder queue saturation situation, these show whether events are delayed in transit rather than absent at the source; by contrast, for Secure syslog transport mismatch corroboration, the wire trace confirms both transport choice and exposure of event content.
C:In Immutable log retention requirements, retention settings reveal whether deletion or rewriting is possible by privileged operators; the reported Secure syslog transport mismatch case calls for a different corroboration conclusion because the wire trace confirms both transport choice and exposure of event content.
D:For the alternative SIEM parser field loss situation, direct comparison identifies which structured field no longer matches source syntax; by contrast, for Secure syslog transport mismatch corroboration, the wire trace confirms both transport choice and exposure of event content.
E:In Clock skew across security sensors, source clock offsets and timezone parsing explain conflicting event order; the reported Secure syslog transport mismatch case calls for a different corroboration conclusion because the wire trace confirms both transport choice and exposure of event content.
Question 355
A suspected malicious process exits quickly but a forensic memory snapshot was acquired while the host remained running. Which artifact provides the strongest corroborating detail?
- Memory image metadata and plugin process listings
- Zeek conn.log fields and DNS or TLS linkage
- File scan matches with rule name and matched offsets
- PowerShell operational events with script block content
Explanation
Correct Answer
A:Given “A suspected malicious process exits quickly but a forensic memory snapshot was acquired while the host remained running”, process objects and memory regions support investigation of hidden or terminated execution; that best addresses corroboration in Volatility memory-focused hunt.
Incorrect Answers
B:For corroboration in Volatility memory-focused hunt, Threat hunt with Zeek connection logs is a different mechanism: connection IDs and endpoint metadata support session-level pivoting; here, process objects and memory regions support investigation of hidden or terminated execution.
C:The choice is relevant to YARA rule string matching, where rule results indicate which specified byte patterns were present; for corroboration in Volatility memory-focused hunt, process objects and memory regions support investigation of hidden or terminated execution.
D:For corroboration in Volatility memory-focused hunt, PowerShell script-block hunting is a different mechanism: these records can reveal obfuscated commands and behavior invisible in process names; here, process objects and memory regions support investigation of hidden or terminated execution.
Question 356
An analyst sees multiple clients contacting suspicious domains, but firewall traffic is sourced from only one internal resolver. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?
- One resolver source IP does not imply one compromised device
- A firewall deny does not mean a successful intrusion occurred
- Current IP ownership is not evidence of past ownership
- Sensor visibility and endpoint compromise are different facts
- Geo-IP location alone is not reliable proof of theft
- A proxy 200 response alone cannot prove code executed
Explanation
Correct Answer
A:Given “An analyst sees multiple clients contacting suspicious domains, but firewall traffic is sourced from only one internal resolver”, shared infrastructure hides multiple internal requesters behind a single address; that best addresses interpretation limit in Recursive DNS resolver attribution.
Incorrect Answers
B:The choice is relevant to Firewall deny rule evidence, where dropped traffic indicates an attempted path, not application-level execution; for interpretation limit in Recursive DNS resolver attribution, shared infrastructure hides multiple internal requesters behind a single address.
C:For interpretation limit in Recursive DNS resolver attribution, DHCP lease attribution is a different mechanism: an address can move between clients while security logs retain the same string; here, shared infrastructure hides multiple internal requesters behind a single address.
D:The choice is relevant to IDS signature alert context, where IDS alerts before a firewall may describe traffic never delivered to its intended target; for interpretation limit in Recursive DNS resolver attribution, shared infrastructure hides multiple internal requesters behind a single address.
E:For interpretation limit in Recursive DNS resolver attribution, VPN session authentication audit is a different mechanism: roaming networks and provider routing can make legitimate logins appear unusual; here, shared infrastructure hides multiple internal requesters behind a single address.
F:The choice is relevant to Web proxy URL telemetry, where download completion and endpoint execution are separate investigation stages; for interpretation limit in Recursive DNS resolver attribution, shared infrastructure hides multiple internal requesters behind a single address.
Question 357
An incident was contained rapidly but recurring alert-routing mistakes caused avoidable delays throughout the week. How should the analyst classify the activity at this stage?
- Compromised identity reuse during recovery
- Recovery functionality verification
- Incomplete post-containment eradication
- Response improvement after incident closure
Explanation
Correct Answer
D:Given “An incident was contained rapidly but recurring alert-routing mistakes caused avoidable delays throughout the week”, a structured retrospective identifies process and detection gaps independent of blame; that best addresses classification in Post-incident lessons-learned review.
Incorrect Answers
A:For classification in Post-incident lessons-learned review, Credential recovery after domain compromise is a different mechanism: restoration can reintroduce attacker access when old credentials and trust paths remain valid; here, a structured retrospective identifies process and detection gaps independent of blame.
B:The choice is relevant to Ransomware isolated restore validation, where readable backup files do not establish that dependent services can operate after restoration; for classification in Post-incident lessons-learned review, a structured retrospective identifies process and detection gaps independent of blame.
C:For classification in Post-incident lessons-learned review, Incident eradication verification is a different mechanism: threat removal requires evidence that malicious processes and network pathways have ceased; here, a structured retrospective identifies process and detection gaps independent of blame.
Question 358
A service account runs unusual export queries against confidential tables outside its normal batch window. The analyst has not yet established malicious intent or downstream impact. Which interpretive boundary is most relevant to this situation?
- HTTP 500 is a symptom rather than an attack classification
- 401 and 403 do not mean the same control decision
- A 404 response is not automatically malicious
- A successful SELECT log is not proof of data exfiltration
Explanation
Correct Answer
D:The Database privileged query audit evidence “A service account runs unusual export queries against confidential tables outside its normal batch window” is decisive for interpretation limit because read access and external transfer require separate evidence of data leaving its environment.
Incorrect Answers
A:In IIS request diagnostics, application exceptions, backend timeouts and resource exhaustion share this response class; the reported Database privileged query audit case calls for a different interpretation limit conclusion because read access and external transfer require separate evidence of data leaving its environment.
B:For the alternative API gateway authentication logs situation, authentication failure differs from authorization denial after identity evaluation; by contrast, for Database privileged query audit interpretation limit, read access and external transfer require separate evidence of data leaving its environment.
C:In Apache path enumeration logs, normal broken links and crawlers also request absent web resources; the reported Database privileged query audit case calls for a different interpretation limit conclusion because read access and external transfer require separate evidence of data leaving its environment.
Question 359
A privileged account generates event 1102 shortly after a suspicious remote administration session. What record is most useful for confirming this specific pattern?
- 4624 event with logon type and source network address
- 4720 subject and new target-account identity fields
- 1102 source account and adjacent remote logon records
- 4688 new-process and creator-process fields
- 4672 subject logon ID aligned with event 4624
- Security event fields for 4625 including status and source address
Explanation
Correct Answer
C:Given “A privileged account generates event 1102 shortly after a suspicious remote administration session”, the clearing actor and prior session context determine whether maintenance or evasion is likely; that best addresses corroboration in Windows security log clearing.
Incorrect Answers
A:This option addresses Windows network logon type because the destination host records how the authenticated session was established; the Windows security log clearing corroboration question instead turns on the fact that the clearing actor and prior session context determine whether maintenance or evasion is likely.
B:That option fits Windows new account creation since the initiating principal and target name help attribute account creation; it does not fit the Windows security log clearing corroboration scenario, where the clearing actor and prior session context determine whether maintenance or evasion is likely.
D:That option fits Windows process creation auditing since the linked process details help attribute unexpected interpreter execution to its parent; it does not fit the Windows security log clearing corroboration scenario, where the clearing actor and prior session context determine whether maintenance or evasion is likely.
E:This option addresses Windows privileged logon indicator because shared logon identifiers provide an account and logon-type context for privileged sessions; the Windows security log clearing corroboration question instead turns on the fact that the clearing actor and prior session context determine whether maintenance or evasion is likely.
F:That option fits Windows 4625 authentication failures since failure status and logon type distinguish bad credentials from blocked logon rights; it does not fit the Windows security log clearing corroboration scenario, where the clearing actor and prior session context determine whether maintenance or evasion is likely.
Question 360
The SIEM shows a suspicious injection request allowed at the WAF and a matching database error at the origin. How should the detection program improve coverage for this pattern?
- Alert on export destinations not in the approved allowlist
- Detect allowed high-risk payloads with backend effect
- Alert on repeated token failures toward privileged resources
- Alert on web-worker processes spawning shells
Explanation
Correct Answer
B:The WAF bypass with origin success evidence “The SIEM shows a suspicious injection request allowed at the WAF and a matching database error at the origin” is decisive for ongoing detection improvement because joint edge-origin rules are stronger than WAF signature counts alone.
Incorrect Answers
A:For the alternative Massive object-storage upload through web app situation, contextual detection is better than flagging every large upload; by contrast, for WAF bypass with origin success ongoing detection improvement, joint edge-origin rules are stronger than WAF signature counts alone.
C:For the alternative API bearer-token guessing situation, sensitive path context raises priority above generic 401 volume; by contrast, for WAF bypass with origin success ongoing detection improvement, joint edge-origin rules are stronger than WAF signature counts alone.
D:In Web-shell request and process correlation, parent-child linkage has more value than scanning page names alone; the reported WAF bypass with origin success case calls for a different ongoing detection improvement conclusion because joint edge-origin rules are stronger than WAF signature counts alone.