FortiSOAR Knowledge Base
FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
Mahdi1
Staff
Staff
Article Id 220048
Intro:
In an MSSP environment each tenant may have a separate connector configuration. Using all of them in a playbook is not an optimal solution.
The attached playbook collection is meant to help speed up writing MSSP playbooks by automating the configuration lookup process.

Prerequisites:
For the Connector Tenant Config Locator to work, the connector configuration for each tenant must have the tenant name in it. consider a tenant called <<libertas>> the connector configuration for this tenant must have the word "libertas" as shown below:
1lVn1OwpTe6XXP0l29LR_msedge_nUhRwfsHhA.png1lVn1OwpTe6XXP0l29LR_msedge_nUhRwfsHhA.png
How it Works:
The reference playbook takes 2 input parameters:
- Tenant Name
- Connector Name
it uses the connector name to locate the current connector version and extract its configurations
it parses the configurations for any with the tenant name in its name and return its config_id value which in turn can be used directly in connectors '

Usage:
- Import the collection to your FortiSOAR instance
- Make sure your connectors configurations have the tenant name in it
before using any connector, use the "Connector Tenant Config Locator" reference playbook to locate the current tenant configuration ID. the tenant name can be used directly from the record for it is one of its attributes (Alerts, incidents...), check the example below:
G45SZe1R6y0C7UwY1sfA_mssp_exp.pngG45SZe1R6y0C7UwY1sfA_mssp_exp.png
Contributors