Question 770
An application cannot reach a database subnet and the perimeter log contains repeated denied TCP connection attempts. What security condition most directly explains the pattern?
- Signature-based network detection
- Firewall policy-denial record
- Dynamic address attribution problem
- Remote-access VPN connection record
Explanation
Correct Answer
B:In the Firewall deny rule evidence case, a deny event documents the enforcement decision for a packet matching a particular rule; the observation “An application cannot reach a database subnet and the perimeter log contains repeated denied TCP connection attempts” makes this classification choice the fitting one.
Incorrect Answers
A:For the alternative IDS signature alert context situation, an IDS match indicates a pattern in observed traffic but does not by itself confirm successful exploitation; by contrast, for Firewall deny rule evidence classification, a deny event documents the enforcement decision for a packet matching a particular rule.
C:For the alternative DHCP lease attribution situation, DHCP leases can change which device owned an IP at a specific historical time; by contrast, for Firewall deny rule evidence classification, a deny event documents the enforcement decision for a packet matching a particular rule.
D:In VPN session authentication audit, VPN authentication and assigned virtual IP logs document remote network access distinct from normal web login; the reported Firewall deny rule evidence case calls for a different classification conclusion because a deny event documents the enforcement decision for a packet matching a particular rule.
Question 771
A busy application host reports a rate-limit warning, then a monitoring dashboard shows suspiciously few subsequent events. Which evidence collection choice best supports this investigation?
- Journal suppression counters and daemon configuration
- sudo log entry including user, TTY and COMMAND fields
- journald or auth log entries for sshd and PAM
- Unified log entries collected with log show predicates
Explanation
Correct Answer
A:The Linux dropped syslog messages evidence “A busy application host reports a rate-limit warning, then a monitoring dashboard shows suspiciously few subsequent events” is decisive for corroboration because dropped-message warnings explain why the apparent event volume suddenly fell.
Incorrect Answers
B:In Linux sudo elevation audit, these attributes expose who requested elevation and the command that was invoked; the reported Linux dropped syslog messages case calls for a different corroboration conclusion because dropped-message warnings explain why the apparent event volume suddenly fell.
C:For the alternative Linux SSH authentication messages situation, the sequence of SSH and PAM outcomes provides the reason and affected username; by contrast, for Linux dropped syslog messages corroboration, dropped-message warnings explain why the apparent event volume suddenly fell.
D:In macOS unified log investigation, subsystem and process predicates expose events not found in old syslog text files; the reported Linux dropped syslog messages case calls for a different corroboration conclusion because dropped-message warnings explain why the apparent event volume suddenly fell.
Question 772
A departing researcher copies confidential designs to a personal file-sharing account hours before access termination. Which engineering change provides the most relevant ongoing visibility?
- Monitor unusual sensitive uploads near access lifecycle events
- Flag sensitive data changes lacking approved change references
- Audit insider-case access and retention by investigator role
- Automate termination-to-access revocation with reconciliation
Explanation
Correct Answer
A:Given “A departing researcher copies confidential designs to a personal file-sharing account hours before access termination”, context-based DLP alerts reduce noise from routine collaboration; that best addresses ongoing detection improvement in Suspected employee intellectual-property export.
Incorrect Answers
B:For ongoing detection improvement in Suspected employee intellectual-property export, Unauthorized change to payroll records is a different mechanism: business-process controls complement technical access checks; here, context-based DLP alerts reduce noise from routine collaboration.
C:The choice is relevant to Employee privacy during insider case, where case governance should detect inappropriate investigative browsing; for ongoing detection improvement in Suspected employee intellectual-property export, context-based DLP alerts reduce noise from routine collaboration.
D:For ongoing detection improvement in Suspected employee intellectual-property export, Former contractor access remains active is a different mechanism: lifecycle controls reduce lag between HR status and effective access; here, context-based DLP alerts reduce noise from routine collaboration.
Question 773
An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers. Which working hypothesis is best supported by these facts?
- Premature incident-impact communication
- Broken forensic chain-of-custody documentation
- Uncoordinated parallel containment
- Dynamic severity reassessment
Explanation
Correct Answer
D:The Incident severity change during response evidence “An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers” is decisive for classification because response priority should change when confirmed scope and potential business impact expand.
Incorrect Answers
A:In Public incident communications control, unverified public statements can harm customers and undermine coordinated disclosure; the reported Incident severity change during response case calls for a different classification conclusion because response priority should change when confirmed scope and potential business impact expand.
B:For the alternative Evidence transfer between response teams situation, untracked evidence handling makes authenticity and later reproduction harder to establish; by contrast, for Incident severity change during response classification, response priority should change when confirmed scope and potential business impact expand.
C:In Incident commander coordination gap, multiple teams need a single commander and an agreed action timeline to avoid conflicting interventions; the reported Incident severity change during response case calls for a different classification conclusion because response priority should change when confirmed scope and potential business impact expand.
Question 774
A remote access gateway shows an approved user signing in from an unfamiliar country and establishing a session. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?
- Preserve lease records and correct incident asset attribution
- Triage as an attempt and examine target evidence before escalation
- Review the session and revoke suspicious VPN access after validation
- Validate the change request before altering the firewall rule
Explanation
Correct Answer
C:In the VPN session authentication audit case, risk-based response focuses on actual access and identity assurance; the observation “A remote access gateway shows an approved user signing in from an unfamiliar country and establishing a session” makes this response decision choice the fitting one.
Incorrect Answers
A:For response decision in VPN session authentication audit, DHCP lease attribution is a different mechanism: fixing identity mapping prevents unnecessary containment of an innocent endpoint; here, risk-based response focuses on actual access and identity assurance.
B:The choice is relevant to IDS signature alert context, where investigators should not claim host compromise solely from a perimeter match; for response decision in VPN session authentication audit, risk-based response focuses on actual access and identity assurance.
D:The choice is relevant to Firewall deny rule evidence, where opening access without review could remove the segment boundary protecting the database; for response decision in VPN session authentication audit, risk-based response focuses on actual access and identity assurance.
Question 775
A standard user is added to a high-privilege group by a previously unused administrator account. Which engineering change provides the most relevant ongoing visibility?
- Protect signing material in restricted key stores and monitor export attempts
- Require strong identity proofing for sensitive factor resets
- Alert on sensitive group additions from unusual grantors
- Add secret scanning in code and credential issuance workflows
Explanation
Correct Answer
C:For ongoing detection improvement in Privilege escalation via group membership, contextual identity monitoring improves visibility beyond group-change counts; this applies to the reported “A standard user is added to a high-privilege group by a previously unused administrator account”.
Incorrect Answers
A:For ongoing detection improvement in Privilege escalation via group membership, Compromised federation signing key is a different mechanism: key management and separation of duties reduce future extraction risk; here, contextual identity monitoring improves visibility beyond group-change counts.
B:The choice is relevant to Unauthorized MFA factor registration, where recovery procedures are often weaker than normal MFA sign-ins; for ongoing detection improvement in Privilege escalation via group membership, contextual identity monitoring improves visibility beyond group-change counts.
D:The choice is relevant to Exposed cloud API credential, where early detection prevents publication and long-lived secret reuse; for ongoing detection improvement in Privilege escalation via group membership, contextual identity monitoring improves visibility beyond group-change counts.
Question 776
A detection engineer excludes an entire server subnet to reduce a noisy administrative tool alert. What monitoring improvement would best help detect recurrence?
- Use CI tests with sample log fixtures on rule updates
- Track excluded-hit volume and sampled exception outcomes
- Build an ordered rule with tested entity joins
- Test detection with events near window edges
- Review precision and missed detections by peer group
Explanation
Correct Answer
B:In the Overbroad allowlist suppression case, an allowlist needs governance because legitimate context can change; the observation “A detection engineer excludes an entire server subnet to reduce a noisy administrative tool alert” makes this ongoing detection improvement choice the fitting one.
Incorrect Answers
A:This option addresses Detection-as-code regression because automated content validation catches common breaking changes before production; the Overbroad allowlist suppression ongoing detection improvement question instead turns on the fact that an allowlist needs governance because legitimate context can change.
C:This option addresses Multi-stage attack sequence correlation because sequence logic reduces false positives from common individual activities; the Overbroad allowlist suppression ongoing detection improvement question instead turns on the fact that an allowlist needs governance because legitimate context can change.
D:That option fits Sliding-window aggregation error since boundary-focused cases expose errors invisible in mid-window test datasets; it does not fit the Overbroad allowlist suppression ongoing detection improvement scenario, where an allowlist needs governance because legitimate context can change.
E:This option addresses Peer-group baseline mismatch because role-based metrics make tuning tradeoffs visible; the Overbroad allowlist suppression ongoing detection improvement question instead turns on the fact that an allowlist needs governance because legitimate context can change.
Question 777
A helpdesk reset is followed by enrollment of a new authenticator for a privileged identity from an unfamiliar device. What qualification is most important before drawing a firm conclusion?
- Removing a group membership does not undo actions already completed
- Deleting a commit or file does not invalidate a copied secret
- A newly registered factor is not necessarily fraudulent
- Password resets alone do not repair a compromised token-signing trust
- A password reset may leave certain already-issued tokens active temporarily
Explanation
Correct Answer
C:In the Unauthorized MFA factor registration case, legitimate device replacement is common but must be verified for high-risk users; the observation “A helpdesk reset is followed by enrollment of a new authenticator for a privileged identity from an unfamiliar device” makes this interpretation limit choice the fitting one.
Incorrect Answers
A:This option addresses Privilege escalation via group membership because separate forensic review is required for privileged activity during the exposure window; the Unauthorized MFA factor registration interpretation limit question instead turns on the fact that legitimate device replacement is common but must be verified for high-risk users.
B:That option fits Exposed cloud API credential since the credential remains usable until explicitly revoked or expired; it does not fit the Unauthorized MFA factor registration interpretation limit scenario, where legitimate device replacement is common but must be verified for high-risk users.
D:That option fits Compromised federation signing key since the fundamental trust anchor needs rotation and relying-party coordination; it does not fit the Unauthorized MFA factor registration interpretation limit scenario, where legitimate device replacement is common but must be verified for high-risk users.
E:This option addresses Employee account takeover because revocation and token validity must be considered explicitly; the Unauthorized MFA factor registration interpretation limit question instead turns on the fact that legitimate device replacement is common but must be verified for high-risk users.
Question 778
An endpoint repeatedly requests long unique subdomains beneath one external zone with steady small DNS responses. Which investigative step would most directly establish the relevant scope?
- Inspect base-domain frequency and subdomain entropy by client
- Correlate fallback queries with later SMB authentication attempts
- Check Origin or Referer behavior and SameSite cookie settings
- Trace the injection submission and later viewer requests
Explanation
Correct Answer
A:For scope analysis in DNS tunneling over queries, grouping by resolver client differentiates unusual encoded labels from normal service discovery; this applies to the reported “An endpoint repeatedly requests long unique subdomains beneath one external zone with steady small DNS responses”.
Incorrect Answers
B:In LLMNR or NBNS name-resolution poisoning, unexpected follow-up authentication can show whether the spoofed resolution lured credentials; the reported DNS tunneling over queries case calls for a different scope analysis conclusion because grouping by resolver client differentiates unusual encoded labels from normal service discovery.
C:For the alternative Cross-site request forgery situation, these controls help establish whether a cross-site request could be accepted silently; by contrast, for DNS tunneling over queries scope analysis, grouping by resolver client differentiates unusual encoded labels from normal service discovery.
D:In Stored cross-site scripting, the two-stage timeline separates persistence from a one-time reflected payload; the reported DNS tunneling over queries case calls for a different scope analysis conclusion because grouping by resolver client differentiates unusual encoded labels from normal service discovery.
Question 779
A content author needs to describe a detection in a vendor-neutral format before converting it to different SIEM queries. How should the analyst classify the activity at this stage?
- Zeek network metadata hunting
- YARA signature-based artifact matching
- OSQuery structured endpoint enumeration
- Sigma generic log-detection rule
Explanation
Correct Answer
D:In the Sigma analytic rule portability case, sigma expresses event selection and conditions independent of a particular SIEM's query syntax; the observation “A content author needs to describe a detection in a vendor-neutral format before converting it to different SIEM queries” makes this classification choice the fitting one.
Incorrect Answers
A:In Threat hunt with Zeek connection logs, connection logs summarize sessions and protocol observations without requiring full payload storage; the reported Sigma analytic rule portability case calls for a different classification conclusion because sigma expresses event selection and conditions independent of a particular SIEM's query syntax.
B:For the alternative YARA rule string matching situation, YARA combines textual or hexadecimal patterns with conditional logic to identify files or memory content; by contrast, for Sigma analytic rule portability classification, sigma expresses event selection and conditions independent of a particular SIEM's query syntax.
C:In OSQuery endpoint state hunt, SQL-like queries expose operating-system state for fleet investigation; the reported Sigma analytic rule portability case calls for a different classification conclusion because sigma expresses event selection and conditions independent of a particular SIEM's query syntax.
Question 780
A sanctioned software deployment generates the same process chain that a newly deployed rule labels as remote execution. How should the analyst classify the activity at this stage?
- Asset-criticality-adjusted alert triage
- Duplicate incident generation from overlapping rules
- Authorized-change-driven false positive
- Incomplete escalation package
Explanation
Correct Answer
C:Given “A sanctioned software deployment generates the same process chain that a newly deployed rule labels as remote execution”, the alert may correctly detect behavior but misclassify its approved operational context; that best addresses classification in Benign admin activity resembling attack.
Incorrect Answers
A:The choice is relevant to Low-confidence alert with crown-jewel impact, where low model confidence can still warrant fast examination on a high-impact asset; for classification in Benign admin activity resembling attack, the alert may correctly detect behavior but misclassify its approved operational context.
B:For classification in Benign admin activity resembling attack, Repeated duplicate detection tickets is a different mechanism: independent detectors may observe one event chain but should not create redundant investigations; here, the alert may correctly detect behavior but misclassify its approved operational context.
D:For classification in Benign admin activity resembling attack, Alert escalation missing supporting evidence is a different mechanism: tier 2 cannot efficiently scope or contain a case without observations, affected entities and actions taken; here, the alert may correctly detect behavior but misclassify its approved operational context.