Last Attempt SecOps-Pro Questions

Cloud Discovery & Exposure (part of the broader Attack Surface Management/ASM capabilities in XSIAM) is designed to solve the problem of "blind spots" in an organization's infrastructure.

Unmanaged Assets: While the Asset Inventory shows what is currently managed, Cloud Discovery looks for what isn't . It scans cloud environments (AWS, Azure, GCP) and public-facing IP ranges to find servers or storage buckets that were created without the security team's knowledge.

Risk Identification: It identifies assets that are missing the Cortex agent or have exposed ports (like RDP or SSH open to the internet), allowing the SOC to proactively secure the attack surface before an attacker finds the same vulnerabilities.

In the automation engine of Cortex XSIAM, playbooks are constructed using several distinct task types to define the logic of a security workflow.

Conditional Task (B): This is a logic-based task used to create branches in the playbook. It evaluates a specific condition (e.g., "Was the file malicious?") and directs the playbook to different paths (Yes/No or specific output values) based on the result.

Sub-playbook Task (D): This allows an administrator to nest an existing playbook inside another. This is a best practice for modularity; for example, you can have a "Ticket Closure" sub-playbook that is called at the end of many different parent playbooks.

Why others are incorrect: * Script creation (A) is a developer activity performed in the "Automations" library, not a task type within a playbook (though a "Standard" task can run an existing script).

Data collection (C) is a specific feature in Cortex XSOAR used for sending surveys to users, but in the context of the core XSIAM automation task types taught in the CSOP curriculum, Conditional and Sub-playbook are the fundamental building blocks.