Administrators from Building 3 have been added to Cortex XSIAM to perform limited functions on a subset of endpoints. Custom roles have been created and applied to the administrators to limit their permissions, but their access should also be constrained through the principle of least privilege according to the endpoints they are allowed to manage. All endpoints are part of an endpoint group named "Building3," and some endpoints may also be members of other endpoint groups.
Which technical control will restrict the ability of the administrators to manage endpoints outside of their area of responsibility, while maintaining visibility to Building 3's endpoints?
Answer : C
To enforce least privilege for Building 3 administrators, SBAC must be enabled in Restrictive Mode and the administrators' scope must be limited to EG:Building3. This ensures they can only manage endpoints within the Building 3 group, even if those endpoints are also part of other groups, while blocking access to endpoints outside their responsibility.
What is the primary benefit of setting the "--memory-swap" option to "-1" during Cortex XSIAM engine deployment?
Answer : C
Setting the '--memory-swap' option to '-1' during Cortex XSIAM engine deployment configures the container to run without requiring swap capabilities. This ensures the engine operates fully within allocated RAM, improving stability and avoiding issues related to memory swapping.
When activating the Cortex XSIAM tenant, how is the data at rest configured with AES 128 encryption?
Answer : B
During Cortex XSIAM tenant activation, data at rest is configured with AES 128 encryption by selecting 'BYOK' (Bring Your Own Key) under the Advanced Encryption Method option and following the wizard's instructions. This ensures secure key management and compliance with encryption standards.
How must Cloud Identity Engine be deployed and activated on Cortex XSIAM?
Answer : C
Cloud Identity Engine must be deployed in the same region as Cortex XSIAM to ensure compliance and proper data handling. Once integrated, the ingestion can be verified by checking the pan_dss_raw dataset, which records the raw directory synchronization logs.
An engineer wants to onboard data from a third-party vendor's firewall. There is no content pack available for it, so the engineer creates custom data source integration and parsing rules to generate a dataset with the firewall data.
How can the analytics capabilities of Cortex XSIAM be used on the data?
Answer : B
To leverage Cortex XSIAM analytics on custom-ingested firewall data, a data model rule must be created with the key network fields (source IP, source port, target IP, target port, IP protocol) mapped. This enables the data to align with XSIAM's analytics engine and be used for BIOCs, correlation rules, and advanced detections.
How can a Cortex XSIAM engineer resolve the issue when a SOC analyst escalates missing details after merging two similar incidents?
Answer : A
When two incidents are merged in Cortex XSIAM, the War Room of the destination incident retains the merged details and activity logs. If a SOC analyst reports missing details, checking the destination incident's War Room will provide the complete context and history.
A Cortex XSIAM engineer is implementing role-based access control (RBAC) and scope-based access control (SBAC) for users accessing the Cortex XSIAM tenant with the following requirements:
Users managing machines in Europe should be able to manage and control all endpoints and installations, create profiles and policies, view alerts, and initiate Live Terminal, but only for endpoints in the Europe region.
Users managing machines in Europe should not be able to create, modify, or delete new or existing user roles.
The Europe region endpoints are identified by both of the following:
Endpoint Tag = "Europe-Servers" and Endpoint Group = "Europe" for servers in Europe
Endpoint Group = "Europe" and Endpoint Tag = "Europe-Workstation" for workstations in Europe
Which two sets of implementation actions should the engineer take? (Choose two.)
Answer : A, D
To meet the requirements, the engineer must enable scope enforcement by setting SBAC mode to Restrictive and assigning the Europe endpoint group (EG:Europe) as the scope. For role assignment, the correct predefined role is Privileged IT Admin, since it allows endpoint management, policy creation, and Live Terminal but does not permit user role management.