Use the administration guide to understand how to customize and administer FortiSOAR, including system, security and user management, and configuring templates.
When you log on to FortiSOAR for the first time as a csadmin user, you will be mandated to change your password. This enhances the security of your csadmin account and prevents unauthorized parties from accessing the administration account for FortiSOAR. Ensure that you note down your csadmin password since if you forget your initial csadmin password, then you have to request FortiSOAR to reset this password. Also, when you are changing your csadmin password, you must ensure that you also update the email ID that is specified for csadmin, which by default is set to
Also, note that from version 7.0.0 onwards, if you want to move any file from and to a FortiSOAR system, then you must install SCP (
yum install openssh-clients -y) or any SCP client. This is required since the
openssh-clients package has been removed from FortiSOAR for security compliance.
Some of the common task that an administrator can perform are:
- License management
- System configuration
- Security management
- User management
- Appliance management
- Password Vault management
- Playbook configuration
- Application management
You can perform administration tasks using the Settings () icon in the upper right-hand corner near the User Profile icon.
To manage different modules, appropriate rights must be assigned to users. In FortiSOAR, modules are applied to roles, for example, the
Security module is applied to the
Security Administrator role. Role permissions are based on the Create, Read, Update, and Delete model (CRUD). Each module within FortiSOAR has explicit CRUD permissions that you can modify and save within a single Role.
For example, to perform all tasks for system configuration, you must be assigned a role that has
CRUD permissions on the
Application module, or to be able to add and manage users, you must be assigned a role that at the minimum has
Update permissions on the
By default, FortiSOAR has at least one role in place after installation, the
|Task||Permissions required on the module|
|System configuration: Customizing FortiSOAR and configure several default options used throughout the system, including setting up authentication mechanisms and configuring dashboards and templates.|| Create, Read, Update, and Delete (CRUD) permissions on
|Security management: Managing teams and roles.|| CRUD permissions on
|User management: Adding and removing users and editing their permissions.|| CRUD permissions on
|Appliances management: Configuring data models, including picklist values and system navigation.|| CRUD permissions on
|Password Vault management: Integrating with third-party external vaults to manage sensitive data|| CRUD permissions on
|Playbook management: Configuring playbook collections and playbooks|| CRUD permissions on