Question 220
During Willow Retail's post-change review, ingress filtering was selected to reject spoofed external packets claiming to originate from private internal ranges. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- An overbroad allow-any rule defeats segmentation even when logging is enabled.
- Auto-suspending an employee solely on one anomaly can create avoidable outages.
- Placing both assets behind one perimeter firewall does not separate them.
- Blocking only destination ports does not verify source-address validity.
Explanation
Correct Answer
D:The residual risk for this case is that blocking only destination ports does not verify source-address validity. This matters even after the measure to reject spoofed external packets claiming to originate from private internal ranges appears to work and should be reflected in the operational plan.
Incorrect Answers
A: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 blocking only destination ports does not verify source-address validity.
B:That caution belongs to low-confidence behavior alert under the different requirement to decide next action when a single unusual-login alert lacks malware or account-change evidence. The current case instead requires managing the risk that blocking only destination ports does not verify source-address validity.
C:That caution belongs to east-west application segmentation under the different requirement to keep a compromised workstation from reaching a finance database directly. The current case instead requires managing the risk that blocking only destination ports does not verify source-address validity.
Question 221
Northstar Manufacturing's security operations team must restrict workloads from making arbitrary internal connections. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- East-west deny-by-default
- Ingress filtering
- SIEM enrichment
- Indicator feed lifecycle
Explanation
Correct Answer
A:East-west deny-by-default addresses this case because the team should deploy least-privilege internal ACLs based on approved service flow maps. The direct verification is that new connections outside allow-listed service dependencies are blocked.
Incorrect Answers
B: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 restrict workloads from making arbitrary internal connections.
C: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 restrict workloads from making arbitrary internal connections.
D:Indicator feed lifecycle would address a different operational issue: prevent stale threat indicators from blocking legitimate traffic indefinitely. The separate task is to apply indicator expiration rules and source provenance when syncing feeds, rather than the requested outcome to restrict workloads from making arbitrary internal connections.
Question 222
An authorized responder at Meridian Analytics has selected the east-west deny-by-default approach to restrict workloads from making arbitrary internal connections. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Implement source-address validation at an appropriate network boundary.
- Deploy least-privilege internal ACLs based on approved service flow maps.
- Join DNS endpoint asset and identity logs using validated event keys.
- Apply indicator expiration rules and source provenance when syncing feeds.
Explanation
Correct Answer
B:To restrict workloads from making arbitrary internal connections, this step operationalizes east-west deny-by-default. In particular, deploy least-privilege internal ACLs based on approved service flow maps; acceptance requires that new connections outside allow-listed service dependencies are blocked.
Incorrect Answers
A: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 east-west deny-by-default, where responders must deploy least-privilege internal ACLs based on approved service flow maps.
C: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 east-west deny-by-default, where responders must deploy least-privilege internal ACLs based on approved service flow maps.
D:This step implements indicator feed lifecycle, aimed at prevent stale threat indicators from blocking legitimate traffic indefinitely. It does not carry out the needed step for east-west deny-by-default, where responders must deploy least-privilege internal ACLs based on approved service flow maps.
Question 223
Highland Operations has performed this action as part of east-west deny-by-default: Deploy least-privilege internal ACLs based on approved service flow maps. The requirement is to restrict workloads from making arbitrary internal connections. Which observation actually confirms the intended result?
- Controlled test sources with invalid ingress address ranges are dropped.
- The enriched incident maps suspicious traffic to a managed host and identity.
- New connections outside allow-listed service dependencies are blocked.
- Expired indicators are retired and relevant current ones remain searchable.
Explanation
Correct Answer
C:The relevant acceptance signal is that new connections outside allow-listed service dependencies are blocked. It verifies the requested result to restrict workloads from making arbitrary internal connections rather than merely measuring unrelated activity.
Incorrect Answers
A: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 new connections outside allow-listed service dependencies are blocked in the specified case.
B: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 new connections outside allow-listed service dependencies are blocked in the specified case.
D:This is an acceptance observation for indicator feed lifecycle, which deals with prevent stale threat indicators from blocking legitimate traffic indefinitely. It does not verify that new connections outside allow-listed service dependencies are blocked in the specified case.
Question 224
During Lakeside Finance's post-change review, east-west deny-by-default was selected to restrict workloads from making arbitrary internal connections. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Blocking only destination ports does not verify source-address validity.
- An IP address can be shared or reassigned and is not always a stable user ID.
- Automating blocking without expiration can cause avoidable false positives.
- An overbroad allow-any rule defeats segmentation even when logging is enabled.
Explanation
Correct Answer
D:The residual risk for this case is that an overbroad allow-any rule defeats segmentation even when logging is enabled. This matters even after the measure to restrict workloads from making arbitrary internal connections appears to work and should be reflected in the operational plan.
Incorrect Answers
A: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 an overbroad allow-any rule defeats segmentation even when logging is enabled.
B: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 an overbroad allow-any rule defeats segmentation even when logging is enabled.
C:That caution belongs to indicator feed lifecycle under the different requirement to prevent stale threat indicators from blocking legitimate traffic indefinitely. The current case instead requires managing the risk that an overbroad allow-any rule defeats segmentation even when logging is enabled.
Question 225
Cedar Health's security operations team must catch a newly disclosed vulnerable library before code is promoted to production. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- CI dependency scanning
- Secret leakage in repository
- SOAR enrichment step
- Low-confidence behavior alert
Explanation
Correct Answer
A:CI dependency scanning addresses this case because the team should run software dependency and vulnerability checks in the CI pipeline. The direct verification is that build status rejects artifacts that violate documented severity policy.
Incorrect Answers
B:Secret leakage in repository would address a different operational issue: prevent deployment credentials being committed into application source control. The separate task is to use managed secret storage and automated precommit secret detection, rather than the requested outcome to catch a newly disclosed vulnerable library before code is promoted to production.
C: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 catch a newly disclosed vulnerable library before code is promoted to production.
D:Low-confidence behavior alert would address a different operational issue: decide next action when a single unusual-login alert lacks malware or account-change evidence. The separate task is to collect additional identity device and session logs before disruptive containment, rather than the requested outcome to catch a newly disclosed vulnerable library before code is promoted to production.
Question 226
An authorized responder at Mariner Logistics has selected the CI dependency scanning approach to catch a newly disclosed vulnerable library before code is promoted to production. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Use managed secret storage and automated precommit secret detection.
- Run software dependency and vulnerability checks in the CI pipeline.
- Orchestrate read-only enrichment before a responder chooses containment.
- Collect additional identity device and session logs before disruptive containment.
Explanation
Correct Answer
B:To catch a newly disclosed vulnerable library before code is promoted to production, this step operationalizes CI dependency scanning. In particular, run software dependency and vulnerability checks in the CI pipeline; acceptance requires that build status rejects artifacts that violate documented severity policy.
Incorrect Answers
A:This step implements secret leakage in repository, aimed at prevent deployment credentials being committed into application source control. It does not carry out the needed step for CI dependency scanning, where responders must run software dependency and vulnerability checks in the CI pipeline.
C: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 CI dependency scanning, where responders must run software dependency and vulnerability checks in the CI pipeline.
D:This step implements low-confidence behavior alert, aimed at decide next action when a single unusual-login alert lacks malware or account-change evidence. It does not carry out the needed step for CI dependency scanning, where responders must run software dependency and vulnerability checks in the CI pipeline.
Question 227
Pioneer Research has performed this action as part of CI dependency scanning: Run software dependency and vulnerability checks in the CI pipeline. The requirement is to catch a newly disclosed vulnerable library before code is promoted to production. Which observation actually confirms the intended result?
- A test secret triggers the repository guard while valid runtime retrieval works.
- The case includes reputation evidence timestamps and lineage references.
- Build status rejects artifacts that violate documented severity policy.
- Case notes record a supported classification with corroborating facts.
Explanation
Correct Answer
C:The relevant acceptance signal is that build status rejects artifacts that violate documented severity policy. It verifies the requested result to catch a newly disclosed vulnerable library before code is promoted to production rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for secret leakage in repository, which deals with prevent deployment credentials being committed into application source control. It does not verify that build status rejects artifacts that violate documented severity policy in the specified case.
B:This is an acceptance observation for soar enrichment step, which deals with shorten triage by gathering file reputation and endpoint lineage into one case. It does not verify that build status rejects artifacts that violate documented severity policy in the specified case.
D:This is an acceptance observation for low-confidence behavior alert, which deals with decide next action when a single unusual-login alert lacks malware or account-change evidence. It does not verify that build status rejects artifacts that violate documented severity policy in the specified case.
Question 228
During Willow Retail's post-change review, CI dependency scanning was selected to catch a newly disclosed vulnerable library before code is promoted to production. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Deleting one Git commit may not erase the secret from all history or caches.
- Automated enrichment is information gathering not proof that a file is malicious.
- Auto-suspending an employee solely on one anomaly can create avoidable outages.
- Passing a dependency scan does not establish runtime configuration safety.
Explanation
Correct Answer
D:The residual risk for this case is that passing a dependency scan does not establish runtime configuration safety. This matters even after the measure to catch a newly disclosed vulnerable library before code is promoted to production appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to secret leakage in repository under the different requirement to prevent deployment credentials being committed into application source control. The current case instead requires managing the risk that passing a dependency scan does not establish runtime configuration safety.
B:That caution belongs to soar enrichment step under the different requirement to shorten triage by gathering file reputation and endpoint lineage into one case. The current case instead requires managing the risk that passing a dependency scan does not establish runtime configuration safety.
C:That caution belongs to low-confidence behavior alert under the different requirement to decide next action when a single unusual-login alert lacks malware or account-change evidence. The current case instead requires managing the risk that passing a dependency scan does not establish runtime configuration safety.
Question 229
Northstar Manufacturing's security operations team must prevent deployment credentials being committed into application source control. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Secret leakage in repository
- CI dependency scanning
- Data at rest safeguards
- UEBA travel anomaly validation
Explanation
Correct Answer
A:Secret leakage in repository addresses this case because the team should use managed secret storage and automated precommit secret detection. The direct verification is that a test secret triggers the repository guard while valid runtime retrieval works.
Incorrect Answers
B:CI dependency scanning would address a different operational issue: catch a newly disclosed vulnerable library before code is promoted to production. The separate task is to run software dependency and vulnerability checks in the CI pipeline, rather than the requested outcome to prevent deployment credentials being committed into application source control.
C:Data at rest safeguards would address a different operational issue: protect confidential files left on a stolen employee laptop. The separate task is to encrypt storage with centrally managed key-recovery and access controls, rather than the requested outcome to prevent deployment credentials being committed into application source control.
D:UEBA travel anomaly validation would address a different operational issue: triage an impossible-travel login alert for a user accessing a VPN gateway. The separate task is to compare IdP sessions device posture VPN egress and MFA events before classifying, rather than the requested outcome to prevent deployment credentials being committed into application source control.
Question 230
An authorized responder at Meridian Analytics has selected the secret leakage in repository approach to prevent deployment credentials being committed into application source control. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Run software dependency and vulnerability checks in the CI pipeline.
- Use managed secret storage and automated precommit secret detection.
- Encrypt storage with centrally managed key-recovery and access controls.
- Compare IdP sessions device posture VPN egress and MFA events before classifying.
Explanation
Correct Answer
B:To prevent deployment credentials being committed into application source control, this step operationalizes secret leakage in repository. In particular, use managed secret storage and automated precommit secret detection; acceptance requires that a test secret triggers the repository guard while valid runtime retrieval works.
Incorrect Answers
A:This step implements ci dependency scanning, aimed at catch a newly disclosed vulnerable library before code is promoted to production. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
C:This step implements data at rest safeguards, aimed at protect confidential files left on a stolen employee laptop. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
D:This step implements ueba travel anomaly validation, aimed at triage an impossible-travel login alert for a user accessing a VPN gateway. It does not carry out the needed step for secret leakage in repository, where responders must use managed secret storage and automated precommit secret detection.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests