Fortinet black logo

Fresh Installation

Copy Link
Copy Doc ID 730247f7-04e0-11eb-96b9-00505692583a:496685
Download PDF

Fresh Installation

This section describes how to install FortiSIEM for the current release.

Pre-Installation Checklist

Before you begin, check the following:

  • Ensure that your system can connect to the network. You will be asked to provide a DNS Server and a host that can be resolved by the DNS Server and responds to ping. The host can either be an internal host or a public domain host like google.com.
  • Deployment type – Enterprise or Service Provider. The Service Provider deployment provides multi-tenancy.
  • Whether FIPS should be enabled
  • Install type:
    • All-in-one with Supervisor only, or
    • Cluster with Supervisor and Workers
  • Storage type
    • Online – Local or NFS or Elasticsearch
    • Archive – NFS or HDFS
  • Before beginning FortiSIEM deployment, you must configure external storage
  • Determine hardware requirements and choose the Azure instance type accordingly:
Node vCPU RAM Local Disks
Supervisor (All in one) Minimum – 12
Recommended - 32

Minimum

  • without UEBA – 24GB
  • with UEBA - 32GB

Recommended

  • without UEBA – 32GB
  • with UEBA - 64GB

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

Local Event database – based on need

Supervisor (Cluster) Minimum – 12
Recommended - 32

Minimum

  • without UEBA – 24GB
  • with UEBA - 32GB

Recommended

  • without UEBA – 32GB
  • with UEBA - 64GB

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

Workers Minimum – 8
Recommended - 16

Minimum – 16GB

Recommended – 24GB

OS – 25GB

OPT – 100GB

Collector Minimum – 4
Recommended – 8 ( based on load)

Minimum – 4GB

Recommended – 8GB

OS – 25GB

OPT – 100GB

Note: compared to FortiSIEM 5.x, you need one more disk (OPT) which provides a cache for FortiSIEM.

For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Before proceeding to FortiSIEM deployment, you must configure the external storage.

  • For NFS deployment, see FortiSIEM - NFS Storage Guide here.
  • For Elasticsearch deployment, see FortiSIEM - Elasticsearch Storage Guide here.

All-in-one Installation

This is the simplest installation with a single Virtual Appliance. If storage is external, then you must configure external storage before proceeding with installation.

Create a FortiSIEM Image in Azure Using the Published VHD

  1. Go to the Fortinet Support website https://support.fortinet.com to download the Azure package FSM_Full_All_AZURE_6.1.1_Build0118.zip.

    See Downloading FortiSIEM Products for more information on downloading products from the support website.

  2. Download the package for Super/Worker and Collector (for example, FSM_Full_All_AZURE_6.1.1_Build0118.zip) to the location where you want to install the image.
  3. Unzip the .zip file to get the FortiSIEM-VA-Azure-6.1.1.0118.vhd file.
  4. Upload the .vhd file to a container in an Azure Storage account in the location where you want to create an Image.

  5. Wait for it to complete uploading fully (the file is approximately 25GB).
  6. Navigate to the uploaded VHD and copy the URL of the object.
  7. Navigate to the Azure Images page and click Add.
  8. Provide the following information:
    1. Enter the image Name, select the appropriate Resource group, and Location.
    2. Choose Linux as the OS type and Gen 1 as the VM generation.
    3. Paste the URL of the object from step 6 under Storage blob.
    4. Choose Standard SSD as Storage type.
    5. Click Create.

  9. If you entered the information correctly, you should see the message: Successfully created Image.

  10. Navigate to Home > Images and search for your image name.
  11. Click the Image.

Create a VM Using a FortiSIEM 6.1.1 Azure Image

  1. On the FortiSIEM 6.1.1 Azure Image page, Click Create VM.

  2. On the Create a virtual machine page, choose a Resource group, specify a Virtual machine name, select an appropriate VM Size based node type and hardware requirements, and generate a new Key pair (or use an existing one). The Username is specified as azureuser.

  3. Also select Inbound ports to port 22 and 443 (for production, use the Advanced tab for fine grained controls). Click Next: Disks

    Use these partition values:

    Volume NameSizeDisk Name
    Data Disk LUN 0100GB

    /opt

    For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

    Data Disk LUN 160GB/cmdb
    Data Disk LUN 260GB/svn
    Data Disk LUN 360GB+/data (see the following note)

    Note on Data Disk LUN 3:

    • Add a 4th Data Disk if using local storage in an All In One deployment. Otherwise, a separate NFS share or Elasticsearch cluster must be used for event storage.
    • 60GB is the minimum event DB disk size for small deployments, provision significantly more event storage for higher EPS deployments. See the FortiSIEM Sizing Guide for additional information.
    • NFS or Elasticsearch event DB storage is mandatory for multi-node cluster deployments.
    • Choose Standard SSD volume type for all volumes. For the CMDB partition, you can choose to modify your volume type to Premium SSD or Ultra SSD based on your system workload if you see the consistently high IOPS requirement in your deployment.

  4. In the Networking tab, accept the defaults except for NIC network security groups. For production, choose Advanced and configure the required inbound ports and IP addresses (refer to Azure documentation). Click Next: Management.

  5. In the Management tab, accept the defaults (or change them as per Azure documentation). Click Next: Advanced.

  6. In Tags tab, add a Name tag and other tags as needed. Click Next: Review + create.

  7. In the Review + create tab, verify that all the information is correct. Click Create.

  8. If you chose to create a new SSH key, then you will be asked to download the private key and create the resource. Click Download private key and create resource.

  9. Wait for deployment to succeed, then click Go to resource.

  10. On the Resource page, note the public IP and copy it to the clipboard.

  11. (Optional) Configure the DNS name as according to Azure documentation.
  12. SSH to the FortiSIEM VM with user azureuser (as specified in page 8, step 2) and the downloaded SSH key. Run sudo su – to become user root. Alternatively, the root user name, is also enabled with the default password ProspectHills. You will have to change this password upon first log in or disable it if you prefer to only log in with SSH key.

Configure FortiSIEM via GUI

Follow these steps to configure FortiSIEM by using a simple GUI.

  1. At the root command prompt, go to /usr/local/bin and enter configFSM.sh, for example:

    # configFSM.sh

  2. In VM console, select 1 Set Timezone and then press Next.

  3. Select your Location, and press Next.

  4. Select your Continent, and press Next.

  5. Select the Country and City for your timezone, and press Next.

  6. Select 1 Supervisor. Press Next.

    note icon

    Regardless of whether you select Supervisor, Worker, or Collector, you will see the same series of screens.

  7. If you want to enable FIPS, then choose 2 install_with_fips. Otherwise, choose 1 install_without_fips. You have the option of enabling FIPS (option 3) or disabling FIPS (option 4) later.

  8. Configure the network by entering the following fields. Press Next.

    OptionDescription
    Host NameThe Supervisor's host name
    IPv4 AddressThe Supervisor's IPv4 address
    NetmaskThe Supervisor's subnet
    GatewayNetwork gateway address
    FQDNFully-qualified domain name
    DNS1, DNS2Addresses of the DNS servers

  9. Test network connectivity by entering a host name that can be resolved by your DNS Server (entered in the previous step) and responds to ping. The host can either be an internal host or a public domain host like google.com. In order for the migration to complete, the system still needs https connectivity to FortiSIEM OS update servers – os-pkgs-cdn.fortisiem.fortinet.com and os-pkgs-c8.fortisiem.fortinet.com. Then, click Next.

  10. The final configuration confirmation is displayed. Verify that the parameters are correct. If they are not, then press Back to return to previous dialog boxes to correct any errors. If everything is OK, then press Run.

    The options are described in the following table.

    OptionDescription
    -rThe FortiSIEM component being configured
    -zThe time zone being configured
    -iIPv4-formatted address
    -mAddress of the subnet mask
    -gAddress of the gateway server used
    --hostHost name
    -fFQDN address: fully-qualified domain name
    -tThe IP type. The values can be either 4 (for ipv4) or 6 (for v6) Note: the 6 value is not currently supported.

    --dns1, --dns2

    Addresses of the DNS server 1 and DNS server 2.

    -o

    Installation option (install_without_fips, install_with_fips, enable_fips, disable_fips, change_ip, or migrate_6_1_1)

    -zTime zone. Possible values are US/Pacific, Asia/Shanghai, Europe/London, or Africa/Tunis

    --testpinghost

    The URL used to test connectivity

  11. It will take some time for this process to finish. When it is done, proceed to Upload the FortiSIEM License. If the VM fails, you can inspect the ansible.log file located at /usr/local/fresh-install/logs to try and identify the problem.

Upload the FortiSIEM License

note icon

Before proceeding, make sure that you have obtained valid FortiSIEM license from Forticare. For more information, see the Licensing Guide.

You will now be asked to input a license.

  1. Open a Web browser and log in to the FortiSIEM UI.
  2. The License Upload dialog box will open.

  3. Click Browse and upload the license file.

    Make sure that the Hardware ID shown in the License Upload page matches the license.

  4. For User ID and Password, choose any Full Admin credentials.

    For the first time installation, enter admin as the user and admin*1 as the password. You will then be asked to create a new password for GUI access.

  5. Choose License type as Enterprise or Service Provider.

    This option is available only for a first time installation. Once the database is configured, this option will not be available.

  6. Proceed to Choose an Event Database.

Choose an Event Database

For a fresh installation, you will be taken to the Event Database Storage page. You will be asked to choose between Local Disk, NFS or Elasticsearch options. For more details, see Configuring Storage.

After the License has been uploaded, and the Event Database Storage setup is configured, FortiSIEM installation is complete. If the installation is successful, the VM will reboot automatically. Otherwise, the VM will stop at the failed task.

You can inspect the ansible.log file located at /usr/local/fresh-install/logs if you encounter any issues during FortiSIEM installation.

After installation completes, ensure that the phMonitor is up and running, for example:

# phstatus

The response should be similar to the following.

Cluster Installation

For larger installations, you can choose Worker nodes, Collector nodes, and external storage (NFS or Elasticsearch).

Install Supervisor

Follow the steps in All-in-one Install with two differences:

  • Setting up hardware - you do not need to add an EBS Volume 5 for Event database.
  • Setting up an Event database - Configure the cluster for either NFS or Elasticsearch.

    NFS

    Elasticsearch

You must choose external storage listed in Choose an Event Database.

Install Workers

Once the Supervisor is installed, follow the same steps in All-in-one Install to install a Worker except you need to only choose OS and OPT disks. The recommended CPU and memory settings for Worker node, and required hard disk settings are:

  • CPU = 8
  • Memory = 24 GB
  • Two hard disks:
    • OS – 25GB
    • OPT – 100GB
      For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Register Workers

Once the Worker is up and running, add the Worker to the Supervisor node.

  1. Go to ADMIN > License > Nodes.
  2. Select Worker from the drop-down list and enter the Worker's IP address. Click Add.

  3. See ADMIN > Health > Cloud Health to ensure that the Workers are up, healthy, and properly added to the system.

Install Collectors

Once Supervisor and Workers are installed, follow the same steps in All-in-one Install to install a Collector except when adding disks, you need to only add a data disk for OPT. The recommended CPU and memory settings for Collector node, and required hard disk settings are:

  • CPU = 4
  • Memory = 8GB
  • Two hard disks:
    • OS – 25GB
    • OPT – 100GB
      For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Register Collectors

Collectors can be deployed in Enterprise or Service Provider environments.

Enterprise Deployments

For Enterprise deployments, follow these steps.

  1. Log in to Supervisor with 'Admin' privileges.
  2. Go to ADMIN > Settings > System > Event Worker.
    1. Enter the IP of the Worker node. If a Supervisor node is only used, then enter the IP of the Supervisor node. Multiple IP addresses can be entered on separate lines. In this case, the Collectors will load balance the upload of events to the listed Event Workers.
      Note: Rather than using IP addresses, a DNS name is recommended. The reasoning is, should the IP addressing change, it becomes a matter of updating the DNS rather than modifying the Event Worker IP addresses in FortiSIEM.
    2. Click OK.
  3. Go to ADMIN > Setup > Collectors and add a Collector by entering:
    1. Name – Collector Name
    2. Guaranteed EPS – this is the EPS that Collector will always be able to send. It could send more if there is excess EPS available.
    3. Start Time and End Time – set to Unlimited.
  4. SSH to the Collector and run following script to register Collectors:

    phProvisionCollector --add <user> '<password>' <Super IP or Host> <Organization> <CollectorName>

    The password should be enclosed in single quotes to ensure that any non-alphanumeric characters are escaped.

    1. Set user and password using the admin user name and password for the Supervisor.
    2. Set Super IP or Host as the Supervisor's IP address.
    3. Set Organization. For Enterprise deployments, the default name is Super.
    4. Set CollectorName from Step 2a.

      The Collector will reboot during the Registration.

  5. Go to ADMIN > Health > Collector Health for the status.

Service Provider Deployments

For Service Provider deployments, follow these steps.

  1. Log in to Supervisor with 'Admin' privileges.
  2. Go to ADMIN > Settings > System > Event Worker.
    1. Enter the IP of the Worker node. If a Supervisor node is only used, then enter the IP of the Supervisor node. Multiple IP addresses can be entered on separate lines. In this case, the Collectors will load balance the upload of events to the listed Event Workers.
      Note: Rather than using IP addresses, a DNS name is recommended. The reasoning is, should the IP addressing change, it becomes a matter of updating the DNS rather than modifying the Event Worker IP addresses in FortiSIEM.
    2. Click OK.

  3. Go to ADMIN > Setup > Organizations and click New to add an Organization.

  4. Enter the Organization Name, Admin User, Admin Password, and Admin Email.
  5. Under Collectors, click New.
  6. Enter the Collector Name, Guaranteed EPS, Start Time, and End Time.

    The last two values could be set as Unlimited. Guaranteed EPS is the EPS that the Collector will always be able to send. It could send more if there is excess EPS available.

  7. SSH to the Collector and run following script to register Collectors:

    phProvisionCollector --add <user> '<password>' <Super IP or Host> <Organization> <CollectorName>

    The password should be enclosed in single quotes to ensure that any non-alphanumeric characters are escaped.

    1. Set user and password using the admin user name and password for the Organization that the Collector is going to be registered to.
    2. Set Super IP or Host as the Supervisor's IP address.
    3. Set Organization as the name of an organization created on the Supervisor.
    4. Set CollectorName from Step 6.

      The Collector will reboot during the Registration.

  8. Go to ADMIN > Health > Collector Health and check the status.

Fresh Installation

This section describes how to install FortiSIEM for the current release.

Pre-Installation Checklist

Before you begin, check the following:

  • Ensure that your system can connect to the network. You will be asked to provide a DNS Server and a host that can be resolved by the DNS Server and responds to ping. The host can either be an internal host or a public domain host like google.com.
  • Deployment type – Enterprise or Service Provider. The Service Provider deployment provides multi-tenancy.
  • Whether FIPS should be enabled
  • Install type:
    • All-in-one with Supervisor only, or
    • Cluster with Supervisor and Workers
  • Storage type
    • Online – Local or NFS or Elasticsearch
    • Archive – NFS or HDFS
  • Before beginning FortiSIEM deployment, you must configure external storage
  • Determine hardware requirements and choose the Azure instance type accordingly:
Node vCPU RAM Local Disks
Supervisor (All in one) Minimum – 12
Recommended - 32

Minimum

  • without UEBA – 24GB
  • with UEBA - 32GB

Recommended

  • without UEBA – 32GB
  • with UEBA - 64GB

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

Local Event database – based on need

Supervisor (Cluster) Minimum – 12
Recommended - 32

Minimum

  • without UEBA – 24GB
  • with UEBA - 32GB

Recommended

  • without UEBA – 32GB
  • with UEBA - 64GB

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

Workers Minimum – 8
Recommended - 16

Minimum – 16GB

Recommended – 24GB

OS – 25GB

OPT – 100GB

Collector Minimum – 4
Recommended – 8 ( based on load)

Minimum – 4GB

Recommended – 8GB

OS – 25GB

OPT – 100GB

Note: compared to FortiSIEM 5.x, you need one more disk (OPT) which provides a cache for FortiSIEM.

For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Before proceeding to FortiSIEM deployment, you must configure the external storage.

  • For NFS deployment, see FortiSIEM - NFS Storage Guide here.
  • For Elasticsearch deployment, see FortiSIEM - Elasticsearch Storage Guide here.

All-in-one Installation

This is the simplest installation with a single Virtual Appliance. If storage is external, then you must configure external storage before proceeding with installation.

Create a FortiSIEM Image in Azure Using the Published VHD

  1. Go to the Fortinet Support website https://support.fortinet.com to download the Azure package FSM_Full_All_AZURE_6.1.1_Build0118.zip.

    See Downloading FortiSIEM Products for more information on downloading products from the support website.

  2. Download the package for Super/Worker and Collector (for example, FSM_Full_All_AZURE_6.1.1_Build0118.zip) to the location where you want to install the image.
  3. Unzip the .zip file to get the FortiSIEM-VA-Azure-6.1.1.0118.vhd file.
  4. Upload the .vhd file to a container in an Azure Storage account in the location where you want to create an Image.

  5. Wait for it to complete uploading fully (the file is approximately 25GB).
  6. Navigate to the uploaded VHD and copy the URL of the object.
  7. Navigate to the Azure Images page and click Add.
  8. Provide the following information:
    1. Enter the image Name, select the appropriate Resource group, and Location.
    2. Choose Linux as the OS type and Gen 1 as the VM generation.
    3. Paste the URL of the object from step 6 under Storage blob.
    4. Choose Standard SSD as Storage type.
    5. Click Create.

  9. If you entered the information correctly, you should see the message: Successfully created Image.

  10. Navigate to Home > Images and search for your image name.
  11. Click the Image.

Create a VM Using a FortiSIEM 6.1.1 Azure Image

  1. On the FortiSIEM 6.1.1 Azure Image page, Click Create VM.

  2. On the Create a virtual machine page, choose a Resource group, specify a Virtual machine name, select an appropriate VM Size based node type and hardware requirements, and generate a new Key pair (or use an existing one). The Username is specified as azureuser.

  3. Also select Inbound ports to port 22 and 443 (for production, use the Advanced tab for fine grained controls). Click Next: Disks

    Use these partition values:

    Volume NameSizeDisk Name
    Data Disk LUN 0100GB

    /opt

    For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

    Data Disk LUN 160GB/cmdb
    Data Disk LUN 260GB/svn
    Data Disk LUN 360GB+/data (see the following note)

    Note on Data Disk LUN 3:

    • Add a 4th Data Disk if using local storage in an All In One deployment. Otherwise, a separate NFS share or Elasticsearch cluster must be used for event storage.
    • 60GB is the minimum event DB disk size for small deployments, provision significantly more event storage for higher EPS deployments. See the FortiSIEM Sizing Guide for additional information.
    • NFS or Elasticsearch event DB storage is mandatory for multi-node cluster deployments.
    • Choose Standard SSD volume type for all volumes. For the CMDB partition, you can choose to modify your volume type to Premium SSD or Ultra SSD based on your system workload if you see the consistently high IOPS requirement in your deployment.

  4. In the Networking tab, accept the defaults except for NIC network security groups. For production, choose Advanced and configure the required inbound ports and IP addresses (refer to Azure documentation). Click Next: Management.

  5. In the Management tab, accept the defaults (or change them as per Azure documentation). Click Next: Advanced.

  6. In Tags tab, add a Name tag and other tags as needed. Click Next: Review + create.

  7. In the Review + create tab, verify that all the information is correct. Click Create.

  8. If you chose to create a new SSH key, then you will be asked to download the private key and create the resource. Click Download private key and create resource.

  9. Wait for deployment to succeed, then click Go to resource.

  10. On the Resource page, note the public IP and copy it to the clipboard.

  11. (Optional) Configure the DNS name as according to Azure documentation.
  12. SSH to the FortiSIEM VM with user azureuser (as specified in page 8, step 2) and the downloaded SSH key. Run sudo su – to become user root. Alternatively, the root user name, is also enabled with the default password ProspectHills. You will have to change this password upon first log in or disable it if you prefer to only log in with SSH key.

Configure FortiSIEM via GUI

Follow these steps to configure FortiSIEM by using a simple GUI.

  1. At the root command prompt, go to /usr/local/bin and enter configFSM.sh, for example:

    # configFSM.sh

  2. In VM console, select 1 Set Timezone and then press Next.

  3. Select your Location, and press Next.

  4. Select your Continent, and press Next.

  5. Select the Country and City for your timezone, and press Next.

  6. Select 1 Supervisor. Press Next.

    note icon

    Regardless of whether you select Supervisor, Worker, or Collector, you will see the same series of screens.

  7. If you want to enable FIPS, then choose 2 install_with_fips. Otherwise, choose 1 install_without_fips. You have the option of enabling FIPS (option 3) or disabling FIPS (option 4) later.

  8. Configure the network by entering the following fields. Press Next.

    OptionDescription
    Host NameThe Supervisor's host name
    IPv4 AddressThe Supervisor's IPv4 address
    NetmaskThe Supervisor's subnet
    GatewayNetwork gateway address
    FQDNFully-qualified domain name
    DNS1, DNS2Addresses of the DNS servers

  9. Test network connectivity by entering a host name that can be resolved by your DNS Server (entered in the previous step) and responds to ping. The host can either be an internal host or a public domain host like google.com. In order for the migration to complete, the system still needs https connectivity to FortiSIEM OS update servers – os-pkgs-cdn.fortisiem.fortinet.com and os-pkgs-c8.fortisiem.fortinet.com. Then, click Next.

  10. The final configuration confirmation is displayed. Verify that the parameters are correct. If they are not, then press Back to return to previous dialog boxes to correct any errors. If everything is OK, then press Run.

    The options are described in the following table.

    OptionDescription
    -rThe FortiSIEM component being configured
    -zThe time zone being configured
    -iIPv4-formatted address
    -mAddress of the subnet mask
    -gAddress of the gateway server used
    --hostHost name
    -fFQDN address: fully-qualified domain name
    -tThe IP type. The values can be either 4 (for ipv4) or 6 (for v6) Note: the 6 value is not currently supported.

    --dns1, --dns2

    Addresses of the DNS server 1 and DNS server 2.

    -o

    Installation option (install_without_fips, install_with_fips, enable_fips, disable_fips, change_ip, or migrate_6_1_1)

    -zTime zone. Possible values are US/Pacific, Asia/Shanghai, Europe/London, or Africa/Tunis

    --testpinghost

    The URL used to test connectivity

  11. It will take some time for this process to finish. When it is done, proceed to Upload the FortiSIEM License. If the VM fails, you can inspect the ansible.log file located at /usr/local/fresh-install/logs to try and identify the problem.

Upload the FortiSIEM License

note icon

Before proceeding, make sure that you have obtained valid FortiSIEM license from Forticare. For more information, see the Licensing Guide.

You will now be asked to input a license.

  1. Open a Web browser and log in to the FortiSIEM UI.
  2. The License Upload dialog box will open.

  3. Click Browse and upload the license file.

    Make sure that the Hardware ID shown in the License Upload page matches the license.

  4. For User ID and Password, choose any Full Admin credentials.

    For the first time installation, enter admin as the user and admin*1 as the password. You will then be asked to create a new password for GUI access.

  5. Choose License type as Enterprise or Service Provider.

    This option is available only for a first time installation. Once the database is configured, this option will not be available.

  6. Proceed to Choose an Event Database.

Choose an Event Database

For a fresh installation, you will be taken to the Event Database Storage page. You will be asked to choose between Local Disk, NFS or Elasticsearch options. For more details, see Configuring Storage.

After the License has been uploaded, and the Event Database Storage setup is configured, FortiSIEM installation is complete. If the installation is successful, the VM will reboot automatically. Otherwise, the VM will stop at the failed task.

You can inspect the ansible.log file located at /usr/local/fresh-install/logs if you encounter any issues during FortiSIEM installation.

After installation completes, ensure that the phMonitor is up and running, for example:

# phstatus

The response should be similar to the following.

Cluster Installation

For larger installations, you can choose Worker nodes, Collector nodes, and external storage (NFS or Elasticsearch).

Install Supervisor

Follow the steps in All-in-one Install with two differences:

  • Setting up hardware - you do not need to add an EBS Volume 5 for Event database.
  • Setting up an Event database - Configure the cluster for either NFS or Elasticsearch.

    NFS

    Elasticsearch

You must choose external storage listed in Choose an Event Database.

Install Workers

Once the Supervisor is installed, follow the same steps in All-in-one Install to install a Worker except you need to only choose OS and OPT disks. The recommended CPU and memory settings for Worker node, and required hard disk settings are:

  • CPU = 8
  • Memory = 24 GB
  • Two hard disks:
    • OS – 25GB
    • OPT – 100GB
      For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Register Workers

Once the Worker is up and running, add the Worker to the Supervisor node.

  1. Go to ADMIN > License > Nodes.
  2. Select Worker from the drop-down list and enter the Worker's IP address. Click Add.

  3. See ADMIN > Health > Cloud Health to ensure that the Workers are up, healthy, and properly added to the system.

Install Collectors

Once Supervisor and Workers are installed, follow the same steps in All-in-one Install to install a Collector except when adding disks, you need to only add a data disk for OPT. The recommended CPU and memory settings for Collector node, and required hard disk settings are:

  • CPU = 4
  • Memory = 8GB
  • Two hard disks:
    • OS – 25GB
    • OPT – 100GB
      For OPT - 100GB, the 100GB disk for /opt will consist of a single disk that will split into 2 partitions, /OPT and swap. The partitions will be created and managed by FortiSIEM when configFSM.sh runs.

Register Collectors

Collectors can be deployed in Enterprise or Service Provider environments.

Enterprise Deployments

For Enterprise deployments, follow these steps.

  1. Log in to Supervisor with 'Admin' privileges.
  2. Go to ADMIN > Settings > System > Event Worker.
    1. Enter the IP of the Worker node. If a Supervisor node is only used, then enter the IP of the Supervisor node. Multiple IP addresses can be entered on separate lines. In this case, the Collectors will load balance the upload of events to the listed Event Workers.
      Note: Rather than using IP addresses, a DNS name is recommended. The reasoning is, should the IP addressing change, it becomes a matter of updating the DNS rather than modifying the Event Worker IP addresses in FortiSIEM.
    2. Click OK.
  3. Go to ADMIN > Setup > Collectors and add a Collector by entering:
    1. Name – Collector Name
    2. Guaranteed EPS – this is the EPS that Collector will always be able to send. It could send more if there is excess EPS available.
    3. Start Time and End Time – set to Unlimited.
  4. SSH to the Collector and run following script to register Collectors:

    phProvisionCollector --add <user> '<password>' <Super IP or Host> <Organization> <CollectorName>

    The password should be enclosed in single quotes to ensure that any non-alphanumeric characters are escaped.

    1. Set user and password using the admin user name and password for the Supervisor.
    2. Set Super IP or Host as the Supervisor's IP address.
    3. Set Organization. For Enterprise deployments, the default name is Super.
    4. Set CollectorName from Step 2a.

      The Collector will reboot during the Registration.

  5. Go to ADMIN > Health > Collector Health for the status.

Service Provider Deployments

For Service Provider deployments, follow these steps.

  1. Log in to Supervisor with 'Admin' privileges.
  2. Go to ADMIN > Settings > System > Event Worker.
    1. Enter the IP of the Worker node. If a Supervisor node is only used, then enter the IP of the Supervisor node. Multiple IP addresses can be entered on separate lines. In this case, the Collectors will load balance the upload of events to the listed Event Workers.
      Note: Rather than using IP addresses, a DNS name is recommended. The reasoning is, should the IP addressing change, it becomes a matter of updating the DNS rather than modifying the Event Worker IP addresses in FortiSIEM.
    2. Click OK.

  3. Go to ADMIN > Setup > Organizations and click New to add an Organization.

  4. Enter the Organization Name, Admin User, Admin Password, and Admin Email.
  5. Under Collectors, click New.
  6. Enter the Collector Name, Guaranteed EPS, Start Time, and End Time.

    The last two values could be set as Unlimited. Guaranteed EPS is the EPS that the Collector will always be able to send. It could send more if there is excess EPS available.

  7. SSH to the Collector and run following script to register Collectors:

    phProvisionCollector --add <user> '<password>' <Super IP or Host> <Organization> <CollectorName>

    The password should be enclosed in single quotes to ensure that any non-alphanumeric characters are escaped.

    1. Set user and password using the admin user name and password for the Organization that the Collector is going to be registered to.
    2. Set Super IP or Host as the Supervisor's IP address.
    3. Set Organization as the name of an organization created on the Supervisor.
    4. Set CollectorName from Step 6.

      The Collector will reboot during the Registration.

  8. Go to ADMIN > Health > Collector Health and check the status.