In a multi-tenant Cortex XSOAR deployment, an architect needs to restrict access to specific playbooks so that Tenant A analysts cannot view or execute playbooks owned by Tenant B. Where is this access control configured?
Trap 1: Global Server Configuration settings
Global settings apply across the entire server, not specific tenant partitions.
Trap 2: Playbook JSON source code permissions
Playbook JSON source code holds the automation logic itself, not tenant-scoped access rules; editing it cannot prevent Tenant B playbooks appearing to Tenant A. It is tempting because playbooks are defined in JSON, but tenant isolation is enforced through role-based access control configuration instead.
Trap 3: Integration instance parameters
Integration instance parameters hold connection credentials and configuration for fetching data, not role-based visibility of playbooks. Multi-tenant playbook access is enforced through tenant roles and labels. It is tempting because integration settings do govern what a tenant's analysts can reach, but they control connectivity, not authorisation.
- A
Global Server Configuration settings
Why it fails: Global settings apply across the entire server, not specific tenant partitions.
- B
Role-Based Access Control (RBAC) settings under Settings > Common > Roles
RBAC allows granular control over what objects a role can access.
- C
Playbook JSON source code permissions
Why it fails: Playbook JSON source code holds the automation logic itself, not tenant-scoped access rules; editing it cannot prevent Tenant B playbooks appearing to Tenant A. It is tempting because playbooks are defined in JSON, but tenant isolation is enforced through role-based access control configuration instead.
- D
Integration instance parameters
Why it fails: Integration instance parameters hold connection credentials and configuration for fetching data, not role-based visibility of playbooks. Multi-tenant playbook access is enforced through tenant roles and labels. It is tempting because integration settings do govern what a tenant's analysts can reach, but they control connectivity, not authorisation.