Question 460
An authorized responder at Meridian Analytics has selected the IOT camera compromise approach to scope unexpected connections from a managed surveillance camera. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Normalize account IDs event times and endpoint telemetry before building a case.
- Inspect service configuration executable hashes and authorization history.
- Join identity approval remote-access logs and endpoint session start events.
- Compare firmware and network observations to the device's approved recorder flows.
Explanation
Correct Answer
D:To scope unexpected connections from a managed surveillance camera, this step operationalizes IOT camera compromise. In particular, compare firmware and network observations to the device's approved recorder flows; acceptance requires that unexpected destinations and configuration drift are documented with timestamps.
Incorrect Answers
A:This step implements cross-platform intrusion correlation, aimed at correlate one identity's suspicious access across Windows macOS and Linux hosts. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
B:This step implements linux persistence case, aimed at investigate an unfamiliar service that persists across server reboots. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
C:This step implements laptop remote administration misuse, aimed at investigate repeated remote-management sessions to an employee laptop. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
Question 461
Highland Operations has performed this action as part of IOT camera compromise: Compare firmware and network observations to the device's approved recorder flows. The requirement is to scope unexpected connections from a managed surveillance camera. Which observation actually confirms the intended result?
- Unexpected destinations and configuration drift are documented with timestamps.
- Case links observed host activity by stable user and session identifiers.
- Timeline ties an unapproved service definition to observed execution.
- Case identifies originating account approval and executed remote tasks.
Explanation
Correct Answer
A:The relevant acceptance signal is that unexpected destinations and configuration drift are documented with timestamps. It verifies the requested result to scope unexpected connections from a managed surveillance camera rather than merely measuring unrelated activity.
Incorrect Answers
B:This is an acceptance observation for cross-platform intrusion correlation, which deals with correlate one identity's suspicious access across Windows macOS and Linux hosts. It does not verify that unexpected destinations and configuration drift are documented with timestamps in the specified case.
C:This is an acceptance observation for linux persistence case, which deals with investigate an unfamiliar service that persists across server reboots. It does not verify that unexpected destinations and configuration drift are documented with timestamps in the specified case.
D:This is an acceptance observation for laptop remote administration misuse, which deals with investigate repeated remote-management sessions to an employee laptop. It does not verify that unexpected destinations and configuration drift are documented with timestamps in the specified case.
Question 462
During Lakeside Finance's post-change review, IOT camera compromise was selected to scope unexpected connections from a managed surveillance camera. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Same display name on different endpoints may denote different principals.
- IoT devices may provide limited local telemetry and require network corroboration.
- A running service with an unfamiliar name is not necessarily malicious.
- Installed management software alone is not proof of unauthorized activity.
Explanation
Correct Answer
B:The residual risk for this case is that IoT devices may provide limited local telemetry and require network corroboration. This matters even after the measure to scope unexpected connections from a managed surveillance camera appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to cross-platform intrusion correlation under the different requirement to correlate one identity's suspicious access across Windows macOS and Linux hosts. The current case instead requires managing the risk that IoT devices may provide limited local telemetry and require network corroboration.
C:That caution belongs to linux persistence case under the different requirement to investigate an unfamiliar service that persists across server reboots. The current case instead requires managing the risk that IoT devices may provide limited local telemetry and require network corroboration.
D:That caution belongs to laptop remote administration misuse under the different requirement to investigate repeated remote-management sessions to an employee laptop. The current case instead requires managing the risk that IoT devices may provide limited local telemetry and require network corroboration.
Question 463
Cedar Health's security operations team must investigate repeated remote-management sessions to an employee laptop. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- IoT camera compromise
- Mobile-device policy breach
- Laptop remote administration misuse
- Desktop intrusion sequence
Explanation
Correct Answer
C:Laptop remote administration misuse addresses this case because the team should join identity approval remote-access logs and endpoint session start events. The direct verification is that case identifies originating account approval and executed remote tasks.
Incorrect Answers
A:IoT camera compromise would address a different operational issue: scope unexpected connections from a managed surveillance camera. The separate task is to compare firmware and network observations to the device's approved recorder flows, rather than the requested outcome to investigate repeated remote-management sessions to an employee laptop.
B:Mobile-device policy breach would address a different operational issue: assess a managed phone accessing confidential resources without required posture. The separate task is to correlate MDM compliance state identity access and application audit events, rather than the requested outcome to investigate repeated remote-management sessions to an employee laptop.
D:Desktop intrusion sequence would address a different operational issue: investigate a suspicious unsigned executable on a managed Windows laptop. The separate task is to collect process lineage persistence artifacts and security-event timeline, rather than the requested outcome to investigate repeated remote-management sessions to an employee laptop.
Question 464
An authorized responder at Mariner Logistics has selected the laptop remote administration misuse approach to investigate repeated remote-management sessions to an employee laptop. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Compare firmware and network observations to the device's approved recorder flows.
- Correlate MDM compliance state identity access and application audit events.
- Collect process lineage persistence artifacts and security-event timeline.
- Join identity approval remote-access logs and endpoint session start events.
Explanation
Correct Answer
D:To investigate repeated remote-management sessions to an employee laptop, this step operationalizes laptop remote administration misuse. In particular, join identity approval remote-access logs and endpoint session start events; acceptance requires that case identifies originating account approval and executed remote tasks.
Incorrect Answers
A:This step implements iot camera compromise, aimed at scope unexpected connections from a managed surveillance camera. It does not carry out the needed step for laptop remote administration misuse, where responders must join identity approval remote-access logs and endpoint session start events.
B:This step implements mobile-device policy breach, aimed at assess a managed phone accessing confidential resources without required posture. It does not carry out the needed step for laptop remote administration misuse, where responders must join identity approval remote-access logs and endpoint session start events.
C:This step implements desktop intrusion sequence, aimed at investigate a suspicious unsigned executable on a managed Windows laptop. It does not carry out the needed step for laptop remote administration misuse, where responders must join identity approval remote-access logs and endpoint session start events.
Question 465
Pioneer Research has performed this action as part of laptop remote administration misuse: Join identity approval remote-access logs and endpoint session start events. The requirement is to investigate repeated remote-management sessions to an employee laptop. Which observation actually confirms the intended result?
- Case identifies originating account approval and executed remote tasks.
- Unexpected destinations and configuration drift are documented with timestamps.
- Logs identify rejected or allowed access for the affected mobile identity.
- Case evidence links the binary's execution to its parent and persistence path.
Explanation
Correct Answer
A:The relevant acceptance signal is that case identifies originating account approval and executed remote tasks. It verifies the requested result to investigate repeated remote-management sessions to an employee laptop rather than merely measuring unrelated activity.
Incorrect Answers
B:This is an acceptance observation for iot camera compromise, which deals with scope unexpected connections from a managed surveillance camera. It does not verify that case identifies originating account approval and executed remote tasks in the specified case.
C:This is an acceptance observation for mobile-device policy breach, which deals with assess a managed phone accessing confidential resources without required posture. It does not verify that case identifies originating account approval and executed remote tasks in the specified case.
D:This is an acceptance observation for desktop intrusion sequence, which deals with investigate a suspicious unsigned executable on a managed Windows laptop. It does not verify that case identifies originating account approval and executed remote tasks in the specified case.
Question 466
During Willow Retail's post-change review, laptop remote administration misuse was selected to investigate repeated remote-management sessions to an employee laptop. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- IoT devices may provide limited local telemetry and require network corroboration.
- Installed management software alone is not proof of unauthorized activity.
- Mobile network location alone does not establish device compliance.
- A known filename alone is not sufficient evidence of compromise.
Explanation
Correct Answer
B:The residual risk for this case is that installed management software alone is not proof of unauthorized activity. This matters even after the measure to investigate repeated remote-management sessions to an employee laptop appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to iot camera compromise under the different requirement to scope unexpected connections from a managed surveillance camera. The current case instead requires managing the risk that installed management software alone is not proof of unauthorized activity.
C:That caution belongs to mobile-device policy breach under the different requirement to assess a managed phone accessing confidential resources without required posture. The current case instead requires managing the risk that installed management software alone is not proof of unauthorized activity.
D:That caution belongs to desktop intrusion sequence under the different requirement to investigate a suspicious unsigned executable on a managed Windows laptop. The current case instead requires managing the risk that installed management software alone is not proof of unauthorized activity.
Question 467
Northstar Manufacturing's security operations team must correlate one identity's suspicious access across Windows macOS and Linux hosts. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Desktop intrusion sequence
- Linux persistence case
- Cross-platform intrusion correlation
- Laptop remote administration misuse
Explanation
Correct Answer
C:Cross-platform intrusion correlation addresses this case because the team should normalize account IDs event times and endpoint telemetry before building a case. The direct verification is that case links observed host activity by stable user and session identifiers.
Incorrect Answers
A:Desktop intrusion sequence would address a different operational issue: investigate a suspicious unsigned executable on a managed Windows laptop. The separate task is to collect process lineage persistence artifacts and security-event timeline, rather than the requested outcome to correlate one identity's suspicious access across Windows macOS and Linux hosts.
B:Linux persistence case would address a different operational issue: investigate an unfamiliar service that persists across server reboots. The separate task is to inspect service configuration executable hashes and authorization history, rather than the requested outcome to correlate one identity's suspicious access across Windows macOS and Linux hosts.
D:Laptop remote administration misuse would address a different operational issue: investigate repeated remote-management sessions to an employee laptop. The separate task is to join identity approval remote-access logs and endpoint session start events, rather than the requested outcome to correlate one identity's suspicious access across Windows macOS and Linux hosts.
Question 468
An authorized responder at Meridian Analytics has selected the cross-platform intrusion correlation approach to correlate one identity's suspicious access across Windows macOS and Linux hosts. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Collect process lineage persistence artifacts and security-event timeline.
- Inspect service configuration executable hashes and authorization history.
- Join identity approval remote-access logs and endpoint session start events.
- Normalize account IDs event times and endpoint telemetry before building a case.
Explanation
Correct Answer
D:To correlate one identity's suspicious access across Windows macOS and Linux hosts, this step operationalizes cross-platform intrusion correlation. In particular, normalize account IDs event times and endpoint telemetry before building a case; acceptance requires that case links observed host activity by stable user and session identifiers.
Incorrect Answers
A:This step implements desktop intrusion sequence, aimed at investigate a suspicious unsigned executable on a managed Windows laptop. It does not carry out the needed step for cross-platform intrusion correlation, where responders must normalize account IDs event times and endpoint telemetry before building a case.
B:This step implements linux persistence case, aimed at investigate an unfamiliar service that persists across server reboots. It does not carry out the needed step for cross-platform intrusion correlation, where responders must normalize account IDs event times and endpoint telemetry before building a case.
C:This step implements laptop remote administration misuse, aimed at investigate repeated remote-management sessions to an employee laptop. It does not carry out the needed step for cross-platform intrusion correlation, where responders must normalize account IDs event times and endpoint telemetry before building a case.
Question 469
Highland Operations has performed this action as part of cross-platform intrusion correlation: Normalize account IDs event times and endpoint telemetry before building a case. The requirement is to correlate one identity's suspicious access across Windows macOS and Linux hosts. Which observation actually confirms the intended result?
- Case links observed host activity by stable user and session identifiers.
- Case evidence links the binary's execution to its parent and persistence path.
- Timeline ties an unapproved service definition to observed execution.
- Case identifies originating account approval and executed remote tasks.
Explanation
Correct Answer
A:The relevant acceptance signal is that case links observed host activity by stable user and session identifiers. It verifies the requested result to correlate one identity's suspicious access across Windows macOS and Linux hosts rather than merely measuring unrelated activity.
Incorrect Answers
B:This is an acceptance observation for desktop intrusion sequence, which deals with investigate a suspicious unsigned executable on a managed Windows laptop. It does not verify that case links observed host activity by stable user and session identifiers in the specified case.
C:This is an acceptance observation for linux persistence case, which deals with investigate an unfamiliar service that persists across server reboots. It does not verify that case links observed host activity by stable user and session identifiers in the specified case.
D:This is an acceptance observation for laptop remote administration misuse, which deals with investigate repeated remote-management sessions to an employee laptop. It does not verify that case links observed host activity by stable user and session identifiers in the specified case.
Question 470
During Lakeside Finance's post-change review, cross-platform intrusion correlation was selected to correlate one identity's suspicious access across Windows macOS and Linux hosts. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- A known filename alone is not sufficient evidence of compromise.
- Same display name on different endpoints may denote different principals.
- A running service with an unfamiliar name is not necessarily malicious.
- Installed management software alone is not proof of unauthorized activity.
Explanation
Correct Answer
B:The residual risk for this case is that same display name on different endpoints may denote different principals. This matters even after the measure to correlate one identity's suspicious access across Windows macOS and Linux hosts appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to desktop intrusion sequence under the different requirement to investigate a suspicious unsigned executable on a managed Windows laptop. The current case instead requires managing the risk that same display name on different endpoints may denote different principals.
C:That caution belongs to linux persistence case under the different requirement to investigate an unfamiliar service that persists across server reboots. The current case instead requires managing the risk that same display name on different endpoints may denote different principals.
D:That caution belongs to laptop remote administration misuse under the different requirement to investigate repeated remote-management sessions to an employee laptop. The current case instead requires managing the risk that same display name on different endpoints may denote different principals.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests