Question 280
During Lakeside Finance's post-change review, log retention policy was selected to preserve incident evidence across systems that rotate logs at different intervals. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Discarding original timezone offsets can obscure source-clock faults.
- Patching new images leaves already-running vulnerable instances to remediate.
- Unverified infection counts should not be presented as confirmed business loss.
- Long retention without privacy access controls increases sensitive-data exposure.
Explanation
Correct Answer
D:The residual risk for this case is that long retention without privacy access controls increases sensitive-data exposure. This matters even after the measure to preserve incident evidence across systems that rotate logs at different intervals appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to timestamp normalization under the different requirement to correlate security events collected from systems with different time zones. The current case instead requires managing the risk that long retention without privacy access controls increases sensitive-data exposure.
B:That caution belongs to golden-image patch baseline under the different requirement to deploy new workloads without inherited vulnerable system packages. The current case instead requires managing the risk that long retention without privacy access controls increases sensitive-data exposure.
C:That caution belongs to executive incident briefing under the different requirement to communicate impact to leadership during an active multi-site ransomware event. The current case instead requires managing the risk that long retention without privacy access controls increases sensitive-data exposure.
Question 281
Cedar Health's security operations team must detect password spraying where each source makes a few failures across many users. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- SIEM correlation
- SIEM enrichment
- AI clustering of malicious infrastructure
- Ingress filtering
Explanation
Correct Answer
A:SIEM correlation addresses this case because the team should aggregate authentication failures by source and target diversity over time. The direct verification is that the alert contains distinct-account count and correlated source details.
Incorrect Answers
B:SIEM enrichment would address a different operational issue: link an anomalous DNS request to the endpoint account and business owner. The separate task is to join DNS endpoint asset and identity logs using validated event keys, rather than the requested outcome to detect password spraying where each source makes a few failures across many users.
C:AI clustering of malicious infrastructure would address a different operational issue: group related suspicious infrastructure before launching an investigation. The separate task is to cluster indicators on shared infrastructure traits then validate overlaps manually, rather than the requested outcome to detect password spraying where each source makes a few failures across many users.
D:Ingress filtering would address a different operational issue: reject spoofed external packets claiming to originate from private internal ranges. The separate task is to implement source-address validation at an appropriate network boundary, rather than the requested outcome to detect password spraying where each source makes a few failures across many users.
Question 282
An authorized responder at Mariner Logistics has selected the SIEM correlation approach to detect password spraying where each source makes a few failures across many users. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Join DNS endpoint asset and identity logs using validated event keys.
- Aggregate authentication failures by source and target diversity over time.
- Cluster indicators on shared infrastructure traits then validate overlaps manually.
- Implement source-address validation at an appropriate network boundary.
Explanation
Correct Answer
B:To detect password spraying where each source makes a few failures across many users, this step operationalizes SIEM correlation. In particular, aggregate authentication failures by source and target diversity over time; acceptance requires that the alert contains distinct-account count and correlated source details.
Incorrect Answers
A:This step implements siem enrichment, aimed at link an anomalous DNS request to the endpoint account and business owner. It does not carry out the needed step for SIEM correlation, where responders must aggregate authentication failures by source and target diversity over time.
C:This step implements ai clustering of malicious infrastructure, aimed at group related suspicious infrastructure before launching an investigation. It does not carry out the needed step for SIEM correlation, where responders must aggregate authentication failures by source and target diversity over time.
D:This step implements ingress filtering, aimed at reject spoofed external packets claiming to originate from private internal ranges. It does not carry out the needed step for SIEM correlation, where responders must aggregate authentication failures by source and target diversity over time.
Question 283
Pioneer Research has performed this action as part of SIEM correlation: Aggregate authentication failures by source and target diversity over time. The requirement is to detect password spraying where each source makes a few failures across many users. Which observation actually confirms the intended result?
- The enriched incident maps suspicious traffic to a managed host and identity.
- Candidate clusters have concrete linking artifacts such as certificates or DNS patterns.
- The alert contains distinct-account count and correlated source details.
- Controlled test sources with invalid ingress address ranges are dropped.
Explanation
Correct Answer
C:The relevant acceptance signal is that the alert contains distinct-account count and correlated source details. It verifies the requested result to detect password spraying where each source makes a few failures across many users rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for siem enrichment, which deals with link an anomalous DNS request to the endpoint account and business owner. It does not verify that the alert contains distinct-account count and correlated source details in the specified case.
B:This is an acceptance observation for ai clustering of malicious infrastructure, which deals with group related suspicious infrastructure before launching an investigation. It does not verify that the alert contains distinct-account count and correlated source details in the specified case.
D:This is an acceptance observation for ingress filtering, which deals with reject spoofed external packets claiming to originate from private internal ranges. It does not verify that the alert contains distinct-account count and correlated source details in the specified case.
Question 284
During Willow Retail's post-change review, SIEM correlation was selected to detect password spraying where each source makes a few failures across many users. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- An IP address can be shared or reassigned and is not always a stable user ID.
- Shared hosting and CDNs can create false linkages between unrelated tenants.
- Blocking only destination ports does not verify source-address validity.
- A per-user threshold alone may miss distributed low-frequency attacks.
Explanation
Correct Answer
D:The residual risk for this case is that a per-user threshold alone may miss distributed low-frequency attacks. This matters even after the measure to detect password spraying where each source makes a few failures across many users appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to siem enrichment under the different requirement to link an anomalous DNS request to the endpoint account and business owner. The current case instead requires managing the risk that a per-user threshold alone may miss distributed low-frequency attacks.
B:That caution belongs to ai clustering of malicious infrastructure under the different requirement to group related suspicious infrastructure before launching an investigation. The current case instead requires managing the risk that a per-user threshold alone may miss distributed low-frequency attacks.
C:That caution belongs to ingress filtering under the different requirement to reject spoofed external packets claiming to originate from private internal ranges. The current case instead requires managing the risk that a per-user threshold alone may miss distributed low-frequency attacks.
Question 285
Northstar Manufacturing's security operations team must link an anomalous DNS request to the endpoint account and business owner. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- SIEM enrichment
- SIEM correlation
- East-west deny-by-default
- Known exploited vulnerability priority
Explanation
Correct Answer
A:SIEM enrichment addresses this case because the team should join DNS endpoint asset and identity logs using validated event keys. The direct verification is that the enriched incident maps suspicious traffic to a managed host and identity.
Incorrect Answers
B:SIEM correlation would address a different operational issue: detect password spraying where each source makes a few failures across many users. The separate task is to aggregate authentication failures by source and target diversity over time, rather than the requested outcome to link an anomalous DNS request to the endpoint account and business owner.
C:East-west deny-by-default would address a different operational issue: restrict workloads from making arbitrary internal connections. The separate task is to deploy least-privilege internal ACLs based on approved service flow maps, rather than the requested outcome to link an anomalous DNS request to the endpoint account and business owner.
D:Known exploited vulnerability priority would address a different operational issue: prioritize an exposed appliance with a CISA KEV-listed flaw. The separate task is to accelerate vendor-supported mitigation or patching and monitor for exploitation, rather than the requested outcome to link an anomalous DNS request to the endpoint account and business owner.
Question 286
An authorized responder at Meridian Analytics has selected the SIEM enrichment approach to link an anomalous DNS request to the endpoint account and business owner. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Aggregate authentication failures by source and target diversity over time.
- Join DNS endpoint asset and identity logs using validated event keys.
- Deploy least-privilege internal ACLs based on approved service flow maps.
- Accelerate vendor-supported mitigation or patching and monitor for exploitation.
Explanation
Correct Answer
B:To link an anomalous DNS request to the endpoint account and business owner, this step operationalizes SIEM enrichment. In particular, join DNS endpoint asset and identity logs using validated event keys; acceptance requires that the enriched incident maps suspicious traffic to a managed host and identity.
Incorrect Answers
A:This step implements siem correlation, aimed at detect password spraying where each source makes a few failures across many users. It does not carry out the needed step for SIEM enrichment, where responders must join DNS endpoint asset and identity logs using validated event keys.
C:This step implements east-west deny-by-default, aimed at restrict workloads from making arbitrary internal connections. It does not carry out the needed step for SIEM enrichment, where responders must join DNS endpoint asset and identity logs using validated event keys.
D:This step implements known exploited vulnerability priority, aimed at prioritize an exposed appliance with a CISA KEV-listed flaw. It does not carry out the needed step for SIEM enrichment, where responders must join DNS endpoint asset and identity logs using validated event keys.
Question 287
Highland Operations has performed this action as part of SIEM enrichment: Join DNS endpoint asset and identity logs using validated event keys. The requirement is to link an anomalous DNS request to the endpoint account and business owner. Which observation actually confirms the intended result?
- The alert contains distinct-account count and correlated source details.
- New connections outside allow-listed service dependencies are blocked.
- The enriched incident maps suspicious traffic to a managed host and identity.
- Change record links affected version KEV entry and verification evidence.
Explanation
Correct Answer
C:The relevant acceptance signal is that the enriched incident maps suspicious traffic to a managed host and identity. It verifies the requested result to link an anomalous DNS request to the endpoint account and business owner rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for siem correlation, which deals with detect password spraying where each source makes a few failures across many users. It does not verify that the enriched incident maps suspicious traffic to a managed host and identity in the specified case.
B:This is an acceptance observation for east-west deny-by-default, which deals with restrict workloads from making arbitrary internal connections. It does not verify that the enriched incident maps suspicious traffic to a managed host and identity in the specified case.
D:This is an acceptance observation for known exploited vulnerability priority, which deals with prioritize an exposed appliance with a CISA KEV-listed flaw. It does not verify that the enriched incident maps suspicious traffic to a managed host and identity in the specified case.
Question 288
During Lakeside Finance's post-change review, SIEM enrichment was selected to link an anomalous DNS request to the endpoint account and business owner. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- A per-user threshold alone may miss distributed low-frequency attacks.
- An overbroad allow-any rule defeats segmentation even when logging is enabled.
- CVSS alone does not show whether exploitation is occurring in the wild.
- An IP address can be shared or reassigned and is not always a stable user ID.
Explanation
Correct Answer
D:The residual risk for this case is that an IP address can be shared or reassigned and is not always a stable user ID. This matters even after the measure to link an anomalous DNS request to the endpoint account and business owner appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to siem correlation under the different requirement to detect password spraying where each source makes a few failures across many users. The current case instead requires managing the risk that an IP address can be shared or reassigned and is not always a stable user ID.
B:That caution belongs to east-west deny-by-default under the different requirement to restrict workloads from making arbitrary internal connections. The current case instead requires managing the risk that an IP address can be shared or reassigned and is not always a stable user ID.
C:That caution belongs to known exploited vulnerability priority under the different requirement to prioritize an exposed appliance with a CISA KEV-listed flaw. The current case instead requires managing the risk that an IP address can be shared or reassigned and is not always a stable user ID.
Question 289
Cedar Health's security operations team must automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- SOAR containment approval
- SOAR enrichment step
- Detection signature revision
- Model precision tradeoff
Explanation
Correct Answer
A:SOAR containment approval addresses this case because the team should require analyst confirmation for high-impact actions and log the workflow decision. The direct verification is that audit trails show approver indicator and exact policy change.
Incorrect Answers
B:SOAR enrichment step would address a different operational issue: shorten triage by gathering file reputation and endpoint lineage into one case. The separate task is to orchestrate read-only enrichment before a responder chooses containment, rather than the requested outcome to automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption.
C:Detection signature revision would address a different operational issue: restore detection for a new variant that evades an outdated network rule. The separate task is to test a narrow signature update against known-good and malicious PCAP fixtures, rather than the requested outcome to automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption.
D:Model precision tradeoff would address a different operational issue: reduce false security escalations caused by overly sensitive anomaly detection. The separate task is to review precision recall and threshold effects on a validated sample, rather than the requested outcome to automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption.
Question 290
An authorized responder at Mariner Logistics has selected the SOAR containment approval approach to automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Orchestrate read-only enrichment before a responder chooses containment.
- Require analyst confirmation for high-impact actions and log the workflow decision.
- Test a narrow signature update against known-good and malicious PCAP fixtures.
- Review precision recall and threshold effects on a validated sample.
Explanation
Correct Answer
B:To automate malicious-domain block creation without authorizing uncontrolled fleet-wide disruption, this step operationalizes SOAR containment approval. In particular, require analyst confirmation for high-impact actions and log the workflow decision; acceptance requires that audit trails show approver indicator and exact policy change.
Incorrect Answers
A:This step implements soar enrichment step, aimed at shorten triage by gathering file reputation and endpoint lineage into one case. It does not carry out the needed step for SOAR containment approval, where responders must require analyst confirmation for high-impact actions and log the workflow decision.
C:This step implements detection signature revision, aimed at restore detection for a new variant that evades an outdated network rule. It does not carry out the needed step for SOAR containment approval, where responders must require analyst confirmation for high-impact actions and log the workflow decision.
D:This step implements model precision tradeoff, aimed at reduce false security escalations caused by overly sensitive anomaly detection. It does not carry out the needed step for SOAR containment approval, where responders must require analyst confirmation for high-impact actions and log the workflow decision.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests