Question 670A packet-capture review includes raw employee identification numbers in a general operations ticket. The team proposes: Minimize or redact personally identifying information before broad incident collaboration. Which security principle best explains the decision? Personally identifiable information needs purpose-limited handling even inside security records. Multiple flow attributes together reveal behavior that simple port labels may miss. Lessons learned translate incident evidence into improved detection and resilience. Forensic collection order should consider evidence that disappears when a system powers off. ExplanationCorrect Answer A:Personally identifiable information needs purpose-limited handling even inside security records. Minimize or redact personally identifying information before broad incident collaboration. That is the direct response to this rule. Verify using: The shared ticket retains useful connection metadata without exposing employee identity fields. Incorrect Answers B:Multiple flow attributes together reveal behavior that simple port labels may miss. This does not establish the proposed intervention. The governing principle here is: Personally identifiable information needs purpose-limited handling even inside security records. Apply it by: Minimize or redact personally identifying information before broad incident collaboration. C:Lessons learned translate incident evidence into improved detection and resilience. This does not establish the proposed intervention. The governing principle here is: Personally identifiable information needs purpose-limited handling even inside security records. Apply it by: Minimize or redact personally identifying information before broad incident collaboration. D:Forensic collection order should consider evidence that disappears when a system powers off. This does not establish the proposed intervention. The governing principle here is: Personally identifiable information needs purpose-limited handling even inside security records. Apply it by: Minimize or redact personally identifying information before broad incident collaboration.
Question 671A security team teaches only eradication steps and skips preparation, detection and lessons-learned review in exercises. What is the most direct risk if this problem remains unresolved? The same failure could recur without measurable improvement. A playbook could fix one symptom while preserving underlying weaknesses. Uncoordinated actions could magnify a security outage. Incident reporting could cause a second privacy exposure. ExplanationCorrect Answer B:A playbook could fix one symptom while preserving underlying weaknesses. Map the exercise to all intended NIST incident-response lifecycle activities. This limits the consequence because incident handling has linked readiness, analysis, response, recovery and improvement work. Incorrect Answers A:Lessons learned translate incident evidence into improved detection and resilience. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A playbook could fix one symptom while preserving underlying weaknesses. C:An incident response plan assigns roles, authority and coordination before a crisis. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A playbook could fix one symptom while preserving underlying weaknesses. D:Personally identifiable information needs purpose-limited handling even inside security records. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A playbook could fix one symptom while preserving underlying weaknesses.
Question 672A monitoring team claims success because a large number of allowed benign sessions produced no alert but never checks known attacks. What is the most appropriate security operations response? Use correctly anchored expressions and test them against representative permitted and disallowed strings. Test both benign and positive cases before accepting the detection classifier. Separate process, registry, API and network artifact semantics when interpreting the alert. Determine whether a lawful decrypted endpoint or proxy artifact is available before claiming reconstruction. ExplanationCorrect Answer B:Test both benign and positive cases before accepting the detection classifier. True negatives and false negatives cannot be distinguished without ground-truth test cases. The practical confirmation is: Labeled benign sessions stay quiet and safe positive simulations produce the intended alerts. Incorrect Answers A:Regular-expression anchors restrict pattern matches to intended string positions. That is relevant to a different intervention. For the stated situation, the required action is: Test both benign and positive cases before accepting the detection classifier. The governing reason is: True negatives and false negatives cannot be distinguished without ground-truth test cases. C:Host action fields and connection fields represent different event types despite shared timestamps. That is relevant to a different intervention. For the stated situation, the required action is: Test both benign and positive cases before accepting the detection classifier. The governing reason is: True negatives and false negatives cannot be distinguished without ground-truth test cases. D:Encrypted captures do not automatically reveal application file bytes for stream extraction. That is relevant to a different intervention. For the stated situation, the required action is: Test both benign and positive cases before accepting the detection classifier. The governing reason is: True negatives and false negatives cannot be distinguished without ground-truth test cases.
Question 673A defender confuses a file SHA-256 hash in a sandbox report with the remote URL contacted by the process. After the change — Separate file hashes, URL indicators and host event evidence in the analysis notes. — which result would best demonstrate that it worked? The analyst states only what the capture proves and flags the missing payload attribution. The case record places the digest and URL in correctly typed fields. The case timeline clearly labels a firewall denial versus a file quarantine. Each test error is linked to the application that generated it. ExplanationCorrect Answer B:The case record places the digest and URL in correctly typed fields. The observation confirms the corrected dependency: Different indicator types identify files, destinations and behaviors, not interchangeable artifacts. The avoided exposure is: Misclassified indicators could generate incorrect detection rules. Incorrect Answers A:Network contact alone does not prove which business data, if any, crossed the boundary. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The case record places the digest and URL in correctly typed fields. C:Endpoint alert source and enforcement action are essential for interpreting event severity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The case record places the digest and URL in correctly typed fields. D:Log correlation requires entity context beyond an IP address and timestamp. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The case record places the digest and URL in correctly typed fields.
Question 674A monitoring dashboard shows a detection but the exported log omits timezone and original event identifier. The team proposes: Preserve event IDs, source timestamps and normalization offsets with the collected evidence. Which security principle best explains the decision? Event provenance and time normalization are essential to credible correlation. Operating-system logging locations and event structures depend on the platform. Antimalware health does not establish host-network access control effectiveness. Dynamic malware reporting should be interpreted with containment boundaries intact. ExplanationCorrect Answer A:Event provenance and time normalization are essential to credible correlation. This links the root condition to the proposed change. Preserve event IDs, source timestamps and normalization offsets with the collected evidence. The expected result is: Raw and normalized times map to the same event with stable identifiers. Incorrect Answers B:Operating-system logging locations and event structures depend on the platform. This does not establish the proposed intervention. The governing principle here is: Event provenance and time normalization are essential to credible correlation. Apply it by: Preserve event IDs, source timestamps and normalization offsets with the collected evidence. C:Antimalware health does not establish host-network access control effectiveness. This does not establish the proposed intervention. The governing principle here is: Event provenance and time normalization are essential to credible correlation. Apply it by: Preserve event IDs, source timestamps and normalization offsets with the collected evidence. D:Dynamic malware reporting should be interpreted with containment boundaries intact. This does not establish the proposed intervention. The governing principle here is: Event provenance and time normalization are essential to credible correlation. Apply it by: Preserve event IDs, source timestamps and normalization offsets with the collected evidence.
Question 675A SOC needs the exact HTTP request body involved in a suspected upload but stores only NetFlow summaries. After the change — Collect an authorized limited packet capture or application transaction record for the event. — which result would best demonstrate that it worked? An approved capture shows the relevant request content while access to raw payload is restricted. The trend dashboard retains traffic volume patterns with sharply reduced raw-data exposure. SYN counters align with reduced connection capacity while application-layer request totals stay low. The callback confirms the request is fraudulent and the protected code remains undisclosed. ExplanationCorrect Answer A:An approved capture shows the relevant request content while access to raw payload is restricted. Flow records describe connection metadata but do not contain complete application payloads. The test establishes that the fix addresses the specific failure. Incorrect Answers B:NetFlow can efficiently summarize communicating endpoints, ports, bytes and timing without full payload retention. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An approved capture shows the relevant request content while access to raw payload is restricted. C:Transport protocol exhaustion and layer-seven denial of service leave different telemetry signatures. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An approved capture shows the relevant request content while access to raw payload is restricted. D:Authority and urgency cues can facilitate social engineering even without technical intrusion. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An approved capture shows the relevant request content while access to raw payload is restricted.
Question 676A ransomware simulation restores a server from backup without checking whether the malicious persistence mechanism remains. What is the most appropriate security operations response? Map the exercise to all intended NIST incident-response lifecycle activities. Define clear response leadership, escalation paths and communication approvals in the incident plan. Normalize total throughput against each site's baseline and critical service profile. Eradicate validated persistence and test clean recovery before reconnecting the restored service. ExplanationCorrect Answer D:Eradicate validated persistence and test clean recovery before reconnecting the restored service. Recovery should confirm the cause of compromise is removed, not only that files exist. The acceptance test is specific: The clean restored host passes malware and configuration checks before production access. Incorrect Answers A:Incident handling has linked readiness, analysis, response, recovery and improvement work. That is relevant to a different intervention. For the stated situation, the required action is: Eradicate validated persistence and test clean recovery before reconnecting the restored service. The governing reason is: Recovery should confirm the cause of compromise is removed, not only that files exist. B:An incident response plan assigns roles, authority and coordination before a crisis. That is relevant to a different intervention. For the stated situation, the required action is: Eradicate validated persistence and test clean recovery before reconnecting the restored service. The governing reason is: Recovery should confirm the cause of compromise is removed, not only that files exist. C:Network profiling requires asset-specific context rather than one universal traffic threshold. That is relevant to a different intervention. For the stated situation, the required action is: Eradicate validated persistence and test clean recovery before reconnecting the restored service. The governing reason is: Recovery should confirm the cause of compromise is removed, not only that files exist.
Question 677A security operations group enables endpoint antivirus but receives no lateral traffic telemetry from its isolated workload segment. What is the most direct risk if this problem remains unresolved? Lateral movement could remain unseen despite healthy endpoint software. An unmanaged device could bypass host-only monitoring. Stale mapping may cause containment of the wrong host. Unrecognized variants could bypass a signature-only rule. ExplanationCorrect Answer A:Lateral movement could remain unseen despite healthy endpoint software. Deploy approved network monitoring at the segment boundary alongside endpoint controls. This limits the consequence because endpoint and network sensors expose different visibility and detection opportunities. Incorrect Answers B:Agentless and agent-based approaches differ in coverage, enforcement depth and deployment prerequisites. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Lateral movement could remain unseen despite healthy endpoint software. C:Session attribution is time-dependent when ephemeral ports and NAT mappings are reused. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Lateral movement could remain unseen despite healthy endpoint software. D:Rule-based signatures and behavior-based detection detect different classes of activity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Lateral movement could remain unseen despite healthy endpoint software.
Question 678A suspicious file has two different SHA digests in tickets because one analyst recorded a modified copy. The team proposes: Track file versions, algorithms, sources and hashes before correlating indicator matches. Which security principle best explains the decision? Hash comparisons require consistent algorithms and immutable artifact boundaries. Packet filtering uses header attributes whereas deep inspection may require accessible higher-layer content. TCP stream reconstruction requires ordered payload data and verifiable evidence handling. A false negative occurs when actual in-scope malicious behavior is not detected. ExplanationCorrect Answer A:Hash comparisons require consistent algorithms and immutable artifact boundaries. That mechanism makes the proposed response appropriate. Track file versions, algorithms, sources and hashes before correlating indicator matches. Evidence: The digest register distinguishes the original file from the changed analysis copy. Incorrect Answers B:Packet filtering uses header attributes whereas deep inspection may require accessible higher-layer content. This does not establish the proposed intervention. The governing principle here is: Hash comparisons require consistent algorithms and immutable artifact boundaries. Apply it by: Track file versions, algorithms, sources and hashes before correlating indicator matches. C:TCP stream reconstruction requires ordered payload data and verifiable evidence handling. This does not establish the proposed intervention. The governing principle here is: Hash comparisons require consistent algorithms and immutable artifact boundaries. Apply it by: Track file versions, algorithms, sources and hashes before correlating indicator matches. D:A false negative occurs when actual in-scope malicious behavior is not detected. This does not establish the proposed intervention. The governing principle here is: Hash comparisons require consistent algorithms and immutable artifact boundaries. Apply it by: Track file versions, algorithms, sources and hashes before correlating indicator matches.
Question 679A host-based anomaly model marks every software update as malicious due to a sudden spike in process launches. What is the most direct risk if this problem remains unresolved? Uncontrolled model drift could overwhelm the SOC with false positives. An analyst could incorrectly claim malware was removed when only a port was blocked. A hidden scheduled process might execute repeatedly. A fabricated sequence could misidentify the first affected host. ExplanationCorrect Answer A:Uncontrolled model drift could overwhelm the SOC with false positives. This consequence follows from the failed control. Test predictive-AI alerts with labeled maintenance events and revise the baseline conservatively. Verify improvement when: Known updates are correctly classified while a separate safe suspicious simulation is flagged. Incorrect Answers B:Endpoint alert source and enforcement action are essential for interpreting event severity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uncontrolled model drift could overwhelm the SOC with false positives. C:Operating-system background launch mechanisms can persist beyond user sessions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uncontrolled model drift could overwhelm the SOC with false positives. D:Corroboration requires accounting for clock skew and differing observation points. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uncontrolled model drift could overwhelm the SOC with false positives.
Question 680A Linux host produces repeated authentication denials but the investigator runs a generic network throughput query. What is the most direct risk if this problem remains unresolved? A credential attack could be dismissed as ordinary password mistakes. Uncontrolled custody could undermine forensic reliability. A valid system service could be interrupted without resolving the alert. Authentication abuse might be hidden in an irrelevant traffic dashboard. ExplanationCorrect Answer D:Authentication abuse might be hidden in an irrelevant traffic dashboard. Operating-system authentication events are more direct evidence for account failures than link usage. An effective remedy is: Inspect the host's authentication journal and account access policy for the affected period. The success indicator is: The exact account and rejection reason appear in the collected authentication trail. Incorrect Answers A:A successful logon following repeated failures can be meaningful when paired with device and location evidence. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Authentication abuse might be hidden in an irrelevant traffic dashboard. B:Chain of custody connects collection, handling and analysis to a defensible evidence history. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Authentication abuse might be hidden in an irrelevant traffic dashboard. C:Process names alone are weak identifiers for host-based analysis. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Authentication abuse might be hidden in an irrelevant traffic dashboard.