Question 600
Firewall events appear to occur five minutes after the corresponding endpoint alerts even though packet traces show the reverse order. What security condition most directly explains the pattern?
- Unprotected log transport
- Insufficient protected log retention
- Security telemetry time synchronization drift
- Multi-path duplicate logging
Explanation
Correct Answer
C:Given “Firewall events appear to occur five minutes after the corresponding endpoint alerts even though packet traces show the reverse order”, unsynchronized source clocks can invert an investigation timeline without changing actual causality; that best addresses classification in Clock skew across security sensors.
Incorrect Answers
A:The choice is relevant to Secure syslog transport mismatch, where plain UDP syslog lacks transport confidentiality and native reliable delivery guarantees; for classification in Clock skew across security sensors, unsynchronized source clocks can invert an investigation timeline without changing actual causality.
B:For classification in Clock skew across security sensors, Immutable log retention requirements is a different mechanism: accessible archives need retention and tamper controls appropriate to the investigation period; here, unsynchronized source clocks can invert an investigation timeline without changing actual causality.
D:For classification in Clock skew across security sensors, Duplicate event ingestion is a different mechanism: two feeds can deliver the same source event twice and inflate detections and costs; here, unsynchronized source clocks can invert an investigation timeline without changing actual causality.
Question 601
A user workstation requests many Kerberos service tickets for unusually privileged service principals. Which investigative step would most directly establish the relevant scope?
- Compare the requesting user with normal application-to-service usage
- Correlate user diversity, source reuse and any successful sign-ins
- Review token use and mailbox access by the granted app
- Identify first affected host and shared-volume write scope
- Compare downloads with job duties and approved migration tasks
- Verify payment instructions using an independent known contact
Explanation
Correct Answer
A:In the Kerberoasting service-ticket harvesting case, unexpected breadth of SPNs and encryption types can suggest ticket harvesting; the observation “A user workstation requests many Kerberos service tickets for unusually privileged service principals” makes this scope analysis choice the fitting one.
Incorrect Answers
B:For the alternative Password spraying across employees situation, successes following the wave require immediate scoping of accessed services; by contrast, for Kerberoasting service-ticket harvesting scope analysis, unexpected breadth of SPNs and encryption types can suggest ticket harvesting.
C:In OAuth consent phishing, scope assessment determines whether consent led to actual data retrieval; the reported Kerberoasting service-ticket harvesting case calls for a different scope analysis conclusion because unexpected breadth of SPNs and encryption types can suggest ticket harvesting.
D:For the alternative Ransomware file encryption situation, filesystem and network-share telemetry locate where propagation or data impact began; by contrast, for Kerberoasting service-ticket harvesting scope analysis, unexpected breadth of SPNs and encryption types can suggest ticket harvesting.
E:In Insider bulk source-code copying, context is needed to distinguish theft from scheduled knowledge transfer; the reported Kerberoasting service-ticket harvesting case calls for a different scope analysis conclusion because unexpected breadth of SPNs and encryption types can suggest ticket harvesting.
F:For the alternative Business email compromise payment diversion situation, out-of-band confirmation tests authenticity without relying on the compromised thread; by contrast, for Kerberoasting service-ticket harvesting scope analysis, unexpected breadth of SPNs and encryption types can suggest ticket harvesting.
Question 602
A file server shows 4624 logon type 3 for an account during access to a shared folder. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?
- Confirm authorization and disable a proven rogue account
- Verify share permissions and review abnormal client hosts
- Preserve failures and investigate the referenced accounts
- Preserve the tree and examine the spawned executable
Explanation
Correct Answer
B:In the Windows network logon type case, access scope should be tested before treating the session as malicious; the observation “A file server shows 4624 logon type 3 for an account during access to a shared folder” makes this response decision choice the fitting one.
Incorrect Answers
A:In Windows new account creation, validate the business request before interrupting legitimate provisioning; the reported Windows network logon type case calls for a different response decision conclusion because access scope should be tested before treating the session as malicious.
C:In Windows 4625 authentication failures, do not assume a brute-force compromise until failure codes and legitimate access history are reviewed; the reported Windows network logon type case calls for a different response decision conclusion because access scope should be tested before treating the session as malicious.
D:For the alternative Windows process creation auditing situation, process lineage informs investigation without treating every interpreter launch as malicious; by contrast, for Windows network logon type response decision, access scope should be tested before treating the session as malicious.
Question 603
A finance user unexpectedly grants another account broad access to audit storage and then signs out. Which engineering change provides the most relevant ongoing visibility?
- Alert on audit-policy reduction followed by privileged modifications
- Baseline nonhuman principals by expected resource and action
- Correlate sensitive file-copy spikes with removable-device arrival
- Alert on broad privileges granted by first-time administrators
Explanation
Correct Answer
D:Given “A finance user unexpectedly grants another account broad access to audit storage and then signs out”, role-history features distinguish normal IAM workflows from rare escalation; that best addresses ongoing detection improvement in Privileged identity rare administrative action.
Incorrect Answers
A:In SIEM audit policy tampering, event order and sensitive asset scope increase confidence; the reported Privileged identity rare administrative action case calls for a different ongoing detection improvement conclusion because role-history features distinguish normal IAM workflows from rare escalation.
B:For the alternative Service principal unusual resource access situation, workload-specific behavior is more useful than human-login anomaly criteria; by contrast, for Privileged identity rare administrative action ongoing detection improvement, role-history features distinguish normal IAM workflows from rare escalation.
C:In DLP alert for removable media transfer, joining device and classification telemetry avoids noisy USB-only alerts; the reported Privileged identity rare administrative action case calls for a different ongoing detection improvement conclusion because role-history features distinguish normal IAM workflows from rare escalation.
Question 604
After malware cleanup, analysts close an incident even though the original command-and-control beacon still appears in proxy logs. Which source would most directly corroborate the observation?
- Endpoint process state joined to post-remediation proxy events
- EDR findings, forensic timeline and trusted baseline image
- Incident timeline, decision log and SLA breach evidence
- Isolated restore logs, checksums and application consistency tests
Explanation
Correct Answer
A:For corroboration in Incident eradication verification, continued connections may reveal surviving persistence or an uninvolved second host; this applies to the reported “After malware cleanup, analysts close an incident even though the original command-and-control beacon still appears in proxy logs”.
Incorrect Answers
B:The choice is relevant to Trusted endpoint rebuild, where the scope of compromise determines whether local remediation is sufficient; for corroboration in Incident eradication verification, continued connections may reveal surviving persistence or an uninvolved second host.
C:For corroboration in Incident eradication verification, Post-incident lessons-learned review is a different mechanism: documented milestones support objective evaluation of what slowed the response; here, continued connections may reveal surviving persistence or an uninvolved second host.
D:The choice is relevant to Ransomware isolated restore validation, where a staged restore proves usable data and configuration dependencies; for corroboration in Incident eradication verification, continued connections may reveal surviving persistence or an uninvolved second host.
Question 605
Three feeds provide the same malware hash with different labels and observation times, inflating the analyst's case list. Which source would most directly corroborate the observation?
- TAXII API collection metadata and authentication settings
- STIX bundle objects with IDs and relationship references
- Normalized hash with source references and timestamps
- Primary-source chain and publication timestamps
- File hashes paired with behavioral execution telemetry
Explanation
Correct Answer
C:The Threat intelligence platform deduplication evidence “Three feeds provide the same malware hash with different labels and observation times, inflating the analyst's case list” is decisive for corroboration because a single observable can link to several different sightings and assessments.
Incorrect Answers
A:This option addresses TAXII intelligence distribution because collection discovery and credentials define what intelligence can be retrieved; the Threat intelligence platform deduplication corroboration question instead turns on the fact that a single observable can link to several different sightings and assessments.
B:That option fits STIX structured intelligence exchange since object types and links preserve context beyond a plain text indicator list; it does not fit the Threat intelligence platform deduplication corroboration scenario, where a single observable can link to several different sightings and assessments.
D:That option fits Intelligence source circular reporting since tracing citations exposes whether new reporting adds observations or simply copies a claim; it does not fit the Threat intelligence platform deduplication corroboration scenario, where a single observable can link to several different sightings and assessments.
E:This option addresses Malware hash IoC specificity because hash and process behavior provide both exact and resilient indicators; the Threat intelligence platform deduplication corroboration question instead turns on the fact that a single observable can link to several different sightings and assessments.
Question 606
Three SIEM rules create separate cases for the same suspicious endpoint process and analyst effort is tripled. What qualification is most important before drawing a firm conclusion?
- Two sensors can report different severity without one being broken
- A detector title is not an incident narrative
- Model confidence is not equivalent to business risk
- Same host and time alone do not prove alerts are duplicates
Explanation
Correct Answer
D:For interpretation limit in Repeated duplicate detection tickets, independent attack steps may deserve separate conclusions within a shared case; this applies to the reported “Three SIEM rules create separate cases for the same suspicious endpoint process and analyst effort is tripled”.
Incorrect Answers
A:That option fits Conflicting alert severity from two sources since they may measure attempt confidence versus observed endpoint consequence; it does not fit the Repeated duplicate detection tickets interpretation limit scenario, where independent attack steps may deserve separate conclusions within a shared case.
B:This option addresses Alert escalation missing supporting evidence because the downstream team needs supporting observations and uncertainty, not just a label; the Repeated duplicate detection tickets interpretation limit question instead turns on the fact that independent attack steps may deserve separate conclusions within a shared case.
C:That option fits Low-confidence alert with crown-jewel impact since a rare severe outcome can justify attention despite weak preliminary signals; it does not fit the Repeated duplicate detection tickets interpretation limit scenario, where independent attack steps may deserve separate conclusions within a shared case.
Question 607
A detection engineer excludes an entire server subnet to reduce a noisy administrative tool alert. The analyst has not yet established malicious intent or downstream impact. What qualification is most important before drawing a firm conclusion?
- An exclusion is not a risk treatment by itself
- An anomaly score is relative to the chosen baseline
- A threshold is meaningful only with its window semantics
- A syntactically valid SIEM query may still match nothing
Explanation
Correct Answer
A:The Overbroad allowlist suppression evidence “A detection engineer excludes an entire server subnet to reduce a noisy administrative tool alert” is decisive for interpretation limit because hiding an event from a rule does not prevent the underlying behavior.
Incorrect Answers
B:In Peer-group baseline mismatch, a high score may describe a normal job in the wrong comparison cohort; the reported Overbroad allowlist suppression case calls for a different interpretation limit conclusion because hiding an event from a rule does not prevent the underlying behavior.
C:For the alternative Sliding-window aggregation error situation, the same event rate can trigger or evade depending on aggregation design; by contrast, for Overbroad allowlist suppression interpretation limit, hiding an event from a rule does not prevent the underlying behavior.
D:In Detection-as-code regression, correct parser fields and event semantics are necessary beyond syntax checks; the reported Overbroad allowlist suppression case calls for a different interpretation limit conclusion because hiding an event from a rule does not prevent the underlying behavior.
Question 608
A staff laptop writes confidential engineering documents to a USB device during a planned offboarding period. Which engineering change provides the most relevant ongoing visibility?
- Baseline nonhuman principals by expected resource and action
- Alert on public links created for high-sensitivity files
- Alert on broad privileges granted by first-time administrators
- Alert on audit-policy reduction followed by privileged modifications
- Correlate sensitive file-copy spikes with removable-device arrival
Explanation
Correct Answer
E:Joining device and classification telemetry avoids noisy USB-only alerts; this is the relevant ongoing detection improvement mechanism for DLP alert for removable media transfer given “A staff laptop writes confidential engineering documents to a USB device during a planned offboarding period”.
Incorrect Answers
A:This option addresses Service principal unusual resource access because workload-specific behavior is more useful than human-login anomaly criteria; the DLP alert for removable media transfer ongoing detection improvement question instead turns on the fact that joining device and classification telemetry avoids noisy USB-only alerts.
B:That option fits Public sharing policy violation since classification-aware policies lower noise from ordinary public marketing content; it does not fit the DLP alert for removable media transfer ongoing detection improvement scenario, where joining device and classification telemetry avoids noisy USB-only alerts.
C:This option addresses Privileged identity rare administrative action because role-history features distinguish normal IAM workflows from rare escalation; the DLP alert for removable media transfer ongoing detection improvement question instead turns on the fact that joining device and classification telemetry avoids noisy USB-only alerts.
D:That option fits SIEM audit policy tampering since event order and sensitive asset scope increase confidence; it does not fit the DLP alert for removable media transfer ongoing detection improvement scenario, where joining device and classification telemetry avoids noisy USB-only alerts.
Question 609
A backup set is recent but its management console shows attacker logins during the same compromise window. Which engineering change provides the most relevant ongoing visibility?
- Enforce secure boot and monitor privileged driver loading
- Test immutable backups and alert on recovery-system tampering
- Segregate backup administration and enforce protected retention
- Enforce image provenance and monitor unexpected miner traffic
Explanation
Correct Answer
C:Separate credentials and immutable copies mitigate destructive attacker access; this is the relevant ongoing detection improvement mechanism for Ransomware backup recovery selection given “A backup set is recent but its management console shows attacker logins during the same compromise window”.
Incorrect Answers
A:In Kernel rootkit suspected on endpoint, reducing unsigned or unexpected kernel code helps prevent persistence; the reported Ransomware backup recovery selection case calls for a different ongoing detection improvement conclusion because separate credentials and immutable copies mitigate destructive attacker access.
B:For the alternative Active ransomware encryption response situation, reliable recovery and early warning reduce the impact of future campaigns; by contrast, for Ransomware backup recovery selection ongoing detection improvement, separate credentials and immutable copies mitigate destructive attacker access.
D:For the alternative Cryptojacking in production cluster situation, admission controls and runtime detection reduce repeat deployments; by contrast, for Ransomware backup recovery selection ongoing detection improvement, separate credentials and immutable copies mitigate destructive attacker access.
Question 610
A web application accepts crafted input and the audit trail shows unexpected reads from restricted customer tables. The analyst has not yet established malicious intent or downstream impact. What caution prevents an unsupported inference from these records?
- A clean vulnerability scan does not prove the host is no longer compromised
- Rate limiting alone cannot correct broken object-level authorization
- Removing the public file alone does not make the old password safe
- Filtering obvious SQL keywords alone is an incomplete fix
Explanation
Correct Answer
D:Input can be encoded or reformulated, while prepared statements preserve query structure; this is the relevant interpretation limit mechanism for Confirmed SQL injection data exposure given “A web application accepts crafted input and the audit trail shows unexpected reads from restricted customer tables”.
Incorrect Answers
A:In Web-shell persistence after patching, patch status and attacker artifact removal are separate requirements; the reported Confirmed SQL injection data exposure case calls for a different interpretation limit conclusion because input can be encoded or reformulated, while prepared statements preserve query structure.
B:For the alternative Automated scraping of protected records situation, a slow attacker may still access records belonging to other users; by contrast, for Confirmed SQL injection data exposure interpretation limit, input can be encoded or reformulated, while prepared statements preserve query structure.
C:In Leaked application database password, anyone who copied the string can still attempt authentication until rotation; the reported Confirmed SQL injection data exposure case calls for a different interpretation limit conclusion because input can be encoded or reformulated, while prepared statements preserve query structure.