Question 490
Several endpoints make regular outbound HTTPS requests to a domain with no legitimate business purpose. What acceptance test would provide the most relevant closure evidence?
- Check that neighboring hosts show no new unauthorized sessions or probes
- Verify no further remote code retrieval occurs during monitored execution
- Assess transferred data and verify no recurring staging or egress
- Watch for replacement destinations and abnormal periodic egress
Explanation
Correct Answer
D:For recovery and closure validation involving “Watch for replacement destinations and” and the report “a domain with no legitimate business purpose”, successful cleanup should eliminate the controlling process, not merely one indicator. “Remove the implant and investigate the mechanism that planted it” is a repair to confirm.
Incorrect Answers
A:For recovery and closure validation, contrasting “Check that neighboring hosts show” with “a domain with no legitimate business purpose”, validation must cover potential secondary victims as well as the source. For this “a domain with no legitimate business purpose” event, “Watch for replacement destinations and abnormal periodic” is still outstanding.
B:For recovery and closure validation, contrasting “Verify no further remote code” with “a domain with no legitimate business purpose”, a clean endpoint must no longer bootstrap the attack chain. “a domain with no legitimate business purpose” is not evaluated through the “for replacement destinations and abnormal periodic egress” requirement.
C:For recovery and closure validation, contrasting “Assess transferred data and verify” with “a domain with no legitimate business purpose”, closure needs exposure scope as well as absence of active malware. Here, “Watch for replacement destinations and abnormal” must account for “a domain with no legitimate business purpose”.
Question 491
A cloud API key appears in a public code repository, but no suspicious infrastructure has yet been identified. Which longer-term repair is most appropriate for this case?
- Correct role-delegation boundaries and enforce privileged change monitoring
- Replace embedded long-lived keys with managed workload identities or short-lived tokens
- Enable appropriately scoped object data-access auditing and retention
- Create cross-account forensic acquisition automation and restricted evidence storage
Explanation
Correct Answer
B:For eradication and systemic correction involving “Replace embedded long-lived keys with” and the report “no suspicious infrastructure has yet been identified”, removing hardcoded secrets reduces recurrence across deployments. “Revoke the exposed key and move workloads to unaffected credentials” is near-term containment.
Incorrect Answers
A:For eradication and systemic correction, contrasting “Correct role-delegation boundaries and enforce” with “no suspicious infrastructure has yet been identified”, a durable fix stops non-administrative workloads from assigning privileges. The option does not link “no suspicious infrastructure has yet been identified” to “Replace embedded long-lived keys with managed workload”.
C:For eradication and systemic correction, contrasting “Enable appropriately scoped object data-access” with “no suspicious infrastructure has yet been identified”, future incident response needs visibility into actual data operations. Only “embedded long-lived keys with managed workload” would test the “no suspicious infrastructure has yet been identified” condition.
D:For eradication and systemic correction, contrasting “Create cross-account forensic acquisition automation” with “no suspicious infrastructure has yet been identified”, repeatable tooling ensures responders can capture cloud resources promptly. The “no suspicious infrastructure has yet been identified” report requires a finding about “with managed workload identities or short-lived tokens”.
Question 492
Evidence collected at a remote office is sent through an unsecured consumer file-sharing link. Which post-response observation most strongly supports resolution?
- Verify an uninterrupted series of custody entries and seal checks
- Audit hold status and deletion approvals before any disposal
- Confirm lawful receipt, unchanged seals and recorded arrival time
- Compare received hashes and check recipient audit logs
Explanation
Correct Answer
D:For recovery and closure validation involving “Compare received hashes and check” and the report “sent through an unsecured consumer file-sharing link”, verification ensures the expected data reached only approved investigators. “Establish encrypted evidence transfer with access auditing and retention rules” is the lasting control change.
Incorrect Answers
A:For recovery and closure validation, contrasting “Verify an uninterrupted series of” with “sent through an unsecured consumer file-sharing link”, the history should explain control of the exhibit from collection to storage. The incident detail “sent through an unsecured consumer file-sharing link” still calls for “hashes and check recipient audit logs”.
B:For recovery and closure validation, contrasting “Audit hold status and deletion” with “sent through an unsecured consumer file-sharing link”, defensible disposition depends on evidence that no preservation duty remains. “Compare received hashes and check recipient” addresses a gap left by the “sent through an unsecured consumer file-sharing link” observation.
C:For recovery and closure validation, contrasting “Confirm lawful receipt, unchanged seals” with “sent through an unsecured consumer file-sharing link”, successful transport requires both regulatory compliance and physical integrity. Against “sent through an unsecured consumer file-sharing link”, this does not establish “Compare received hashes and check recipient”.
Question 493
An analyst encounters a live process that has deleted its executable from disk but is still running. Which THREE steps together preserve evidence, contain present exposure, and correct the root weakness? Choose THREE.
- Restrict the process's network access before terminating it when feasible
- Capture process memory, mapped modules and open file descriptors
- Record process tree, open sockets and associated user context
- Route workload logs off-host and automate ephemeral evidence capture
- Update procedures for memory-only or deleted-binary persistence
- Improve playbooks to collect RAM before shutdown when safe and lawful
Explanation
Correct Answers
A:For assessment and interpretation involving “Restrict the process's network access” and the report “executable from disk but is still running”, containment can prevent harm while preserving a short window for evidence collection. The linked case facts, including “its executable from disk but is still running”, should be preserved for independent review.
B:For assessment and interpretation involving “Capture process memory, mapped modules” and the report “executable from disk but is still running”, memory-backed execution artifacts may survive removal of the original executable. For assessment and interpretation involving “Capture process memory, mapped modules” and the report “executable from disk but is still running”, the linked case facts, including “its executable from disk but is still running”, should be preserved for independent review.
E:For assessment and interpretation involving “Update procedures for memory-only or” and the report “executable from disk but is still running”, investigators need an evidence path that does not rely solely on filesystem scans. For assessment and interpretation involving “Update procedures for memory-only or” and the report “executable from disk but is still running”, the linked case facts, including “its executable from disk but is still running”, should be preserved for independent review.
Incorrect Answers
C:For assessment and interpretation, contrasting “Record process tree, open sockets” with “executable from disk but is still running”, a coordinated snapshot links the shell to a user, process and network peer. “procedures for memory-only or deleted-binary” remains unverified against the reported “executable from disk but is still running”.
D:For assessment and interpretation, contrasting “Route workload logs off-host and” with “executable from disk but is still running”, centralized evidence survives routine container recycling. For “executable from disk but is still running”, the missing check concerns “the process's network access before terminating”.
F:For assessment and interpretation, contrasting “Improve playbooks to collect RAM” with “executable from disk but is still running”, a defined order of volatility prevents irreversible evidence loss. The incident detail “executable from disk but is still running” still calls for “process's network access before terminating it”.
Question 494
A production control system uses a legacy protocol that lacks built-in authentication and receives spoofed write commands. Which conclusion is the best starting hypothesis for triage?
- Recognize safety and operational continuity constraints in OT response
- Recognize excessive standing third-party access to safety-relevant networks
- Recognize protocol trust limitations rather than assume commands are authenticated
- Recognize an availability side effect affecting OT monitoring and safety assurance
Explanation
Correct Answer
C:For assessment and interpretation involving “Recognize protocol trust limitations rather” and the report “built-in authentication and receives spoofed write commands”, older industrial protocols may accept writes based on network reachability alone. “Capture protocol transactions, source paths and controller state changes” is a check against premature attribution.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize safety and operational continuity” with “built-in authentication and receives spoofed write commands”, indiscriminate shutdown can create physical hazards even when cyber compromise is suspected. Here, “limitations rather than assume commands are authenticated” must account for “built-in authentication and receives spoofed write commands”.
B:For assessment and interpretation, contrasting “Recognize excessive standing third-party access” with “built-in authentication and receives spoofed write commands”, persistent vendor privileges expand the window and scope of potential misuse. “built-in authentication and receives spoofed write commands” needs a more direct result for “protocol trust limitations rather than assume”.
D:For assessment and interpretation, contrasting “Recognize an availability side effect” with “built-in authentication and receives spoofed write commands”, overly broad filtering can blind operations without stopping the underlying process. The case fact “built-in authentication and receives spoofed write commands” makes “limitations rather than assume commands are authenticated” the better test.
Question 495
A shared mailbox has an unknown delegate who can send messages as the finance department. Which longer-term repair is most appropriate for this case?
- Review role assignments and enforce approved delegate provisioning
- Correct downstream client and attachment exposure on affected devices
- Review tenant consent policy and least-privilege application permissions
- Secure recovery factors and investigate compromised credential pathways
Explanation
Correct Answer
A:For eradication and systemic correction involving “Review role assignments and enforce” and the report “can send messages as the finance department”, administrative process changes reduce hidden privilege grants. “Remove unauthorized delegation and suspend the suspected principal” is the interim response.
Incorrect Answers
B:For eradication and systemic correction, contrasting “Correct downstream client and attachment” with “can send messages as the finance department”, recipients who opened files may need endpoint response in addition to mail cleanup. The “can send messages as the finance department” report requires a finding about “assignments and enforce approved delegate provisioning”.
C:For eradication and systemic correction, contrasting “Review tenant consent policy and” with “can send messages as the finance department”, stronger grant governance makes persistence harder to reestablish. In “can send messages as the finance department”, the necessary control concerns “role assignments and enforce approved delegate provisioning”.
D:For eradication and systemic correction, contrasting “Secure recovery factors and investigate” with “can send messages as the finance department”, remediation prevents re-entry through alternate authentication methods. For this “can send messages as the finance department” event, “role assignments and enforce approved” is still outstanding.
Question 496
A device repeatedly executes a script from a temporary directory after reboot, although the associated user denies running it. Which conclusion is the best starting hypothesis for triage?
- Recognize the weakness of detection without an accurate software baseline
- Recognize autostart persistence associated with a transient file location
- Recognize the need to differentiate approved scripts from encoded malicious commands
- Recognize suspicious parent-child execution despite the signed parent
Explanation
Correct Answer
B:For assessment and interpretation involving “Recognize autostart persistence associated with” and the report “although the associated user denies running it”, repeated execution after boot suggests a scheduled or registry-based launcher. “Preserve autoruns, task scheduler logs, file hashes and process ancestry” is the independent record to examine.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize the weakness of detection” with “although the associated user denies running it”, unknown executables are difficult to interpret when legitimate deployments are undocumented. Against “although the associated user denies running it”, this does not establish “persistence associated with a transient file location”.
C:PowerShell itself is not proof of compromise. “although the associated user denies running it” is why proof of “autostart persistence associated with a transient” matters here.
D:For assessment and interpretation, contrasting “Recognize suspicious parent-child execution despite” with “although the associated user denies running it”, a legitimate application can be abused to launch unexpected secondary commands. The option does not link “although the associated user denies running it” to “persistence associated with a transient file location”.
Question 497
A user's email is silently forwarded to an unfamiliar external address after an OAuth application was granted consent. What interpretation should guide the incident handler's first analysis?
- Recognize malicious mail-rule persistence after mailbox compromise
- Recognize possible unauthorized mail access through app consent and forwarding
- Recognize that absence of sent mail does not exclude mailbox data access
- Recognize an unauthorized delegated-permission path for impersonation
Explanation
Correct Answer
B:For assessment and interpretation involving “Recognize possible unauthorized mail access” and the report “after an OAuth application was granted consent”, a token-bearing app may read mail independently of the user's password. “Preserve consent events, app permissions, forwarding settings and access logs” is an investigative cross-check.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize malicious mail-rule persistence after” with “after an OAuth application was granted consent”, attackers use rules to conceal responses and continue fraud after passwords change. “mail access through app consent and forwarding” remains unverified against the reported “after an OAuth application was granted consent”.
C:For assessment and interpretation, contrasting “Recognize that absence of sent” with “after an OAuth application was granted consent”, read-only theft can leave no visible sent item or rule. “after an OAuth application was granted consent” gives a different evidentiary target: “through app consent and forwarding”.
D:For assessment and interpretation, contrasting “Recognize an unauthorized delegated-permission path” with “after an OAuth application was granted consent”, send-as or full-access rights permit abuse without logging into the mailbox owner account. The incident detail “after an OAuth application was granted consent” still calls for “mail access through app consent”.
Question 498
Security analysts can query infrastructure changes but cannot tell which object data an attacker may have read. What handling decision most directly interrupts further exposure?
- Revoke suspicious grants and suspend the misused identity
- Revoke the exposed key and move workloads to unaffected credentials
- Pause automated deletion for affected assets under an approved response workflow
- Restrict suspect storage access and preserve available access logs immediately
Explanation
Correct Answer
D:Immediate access control limits further disclosure while gaps are assessed. “Identify enabled data-access logs, object paths and relevant request identities” is the corroboration step, where safe.
Incorrect Answers
A:For immediate response and containment, contrasting “Revoke suspicious grants and suspend” with “object data an attacker may have read”, containment closes newly created access while preserving legitimate administration. The comparison turns on “object data an attacker may have read” versus “suspect storage access and preserve available”.
B:For immediate response and containment, contrasting “Revoke the exposed key and” with “object data an attacker may have read”, rapid rotation prevents continued use while maintaining approved service access. The case fact “object data an attacker may have read” makes “and preserve available access logs immediately” the better test.
C:For immediate response and containment, contrasting “Pause automated deletion for affected” with “object data an attacker may have read”, controlled retention prevents evidence destruction while respecting service risk. “suspect storage access and preserve” is the criterion not satisfied for “object data an attacker may have read”.
Question 499
An exploited web server has been patched, but analysts have not established whether attacker credentials still work. Which preventive correction targets the problem at its source?
- Rebuild missing transactions from verified log sources and clean backups
- Enforce configuration-as-code and periodic policy drift detection
- Repair the exploit path and remove unauthorized accounts or persistence
- Apply breached-password screening, rate controls and MFA hardening
Explanation
Correct Answer
C:For eradication and systemic correction involving “Repair the exploit path and” and the report “not established whether attacker credentials still work”, eradication must address both the exploited flaw and follow-on footholds. “Revoke suspicious sessions and rotate affected credentials before reconnecting” is the short-term measure to contrast with remediation.
Incorrect Answers
A:Restoration should reconstruct the trusted business state, not merely boot the database. In “not established whether attacker credentials still work”, the necessary control concerns “the exploit path and remove unauthorized”.
B:For eradication and systemic correction, contrasting “Enforce configuration-as-code and periodic policy” with “not established whether attacker credentials still work”, preventive controls target recurring unauthorized deviations from the approved baseline. For this “not established whether attacker credentials still work” event, “path and remove unauthorized accounts or persistence” is still outstanding.
D:For eradication and systemic correction, contrasting “Apply breached-password screening, rate controls” with “not established whether attacker credentials still work”, durable measures address password reuse and automated abuse together. Here, “exploit path and remove unauthorized accounts” must account for “not established whether attacker credentials still work”.
Question 500
Several endpoints make regular outbound HTTPS requests to a domain with no legitimate business purpose. Which assessment avoids the most important mistaken assumption here?
- Recognize staged payload retrieval rather than one static malware file
- Recognize beacon-like periodic communications as possible command-and-control
- Recognize DNS tunneling or encoded data movement as the key suspicion
- Recognize lateral reconnaissance rather than routine endpoint updating
- Recognize potential malware-assisted collection and exfiltration
Explanation
Correct Answer
B:For assessment and interpretation involving “Recognize beacon-like periodic communications as” and the report “a domain with no legitimate business purpose”, repeated timed requests may represent remote tasking rather than interactive browsing. “Preserve proxy logs, DNS responses, endpoint processes and TLS metadata” is a check against premature conclusions.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize staged payload retrieval rather” with “a domain with no legitimate business purpose”, changing remote objects can deliver new execution stages after initial compromise. “a domain with no legitimate business purpose” is why proof of “periodic communications as possible command-and-control” matters here.
C:For assessment and interpretation, contrasting “Recognize DNS tunneling or encoded” with “a domain with no legitimate business purpose”, high-entropy labels and repeated queries can carry data or commands through DNS. “beacon-like periodic communications as possible command-and-control” cannot be inferred from that “a domain with no legitimate business purpose” finding.
D:For assessment and interpretation, contrasting “Recognize lateral reconnaissance rather than” with “a domain with no legitimate business purpose”, a sweep across peers and ports signals discovery for follow-on compromise. Only “periodic communications as possible command-and-control” would test the “a domain with no legitimate business purpose” condition.
E:For assessment and interpretation, contrasting “Recognize potential malware-assisted collection and” with “a domain with no legitimate business purpose”, archiving followed by unexplained upload is more suspicious than either event alone. The “a domain with no legitimate business purpose” report requires a finding about “beacon-like periodic communications as possible”.