Fortinet Document Library

Version:


Table of Contents

6.1.0
Download PDF
Copy Link

Fresh Installation

Pre-Installation Checklist

Before you begin, check the following:

  • Ensure that your system can connect to the internet
  • 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:
Node vCPU RAM Local Disks
Supervisor (All in one) Minimum – 16
Recommended - 32

Minimum

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

Recommended

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

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

Local Event database – based on need

Supervisor (Cluster) Minimum – 16
Recommended - 32

Minimum

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

Recommended

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

OS – 25GB

OPT – 100GB

CMDB – 60GB

SVN – 60GB

 

Workers Minimum – 8
Recommended - 8

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.

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.

Import FortiSIEM into KVM

  1. Go to the Fortinet Support website https://support.fortinet.com to download the KVM package FSM_Full_All_KVM_6.1.0_build0112.zip. See Downloading FortiSIEM Products for more information on downloading products from the support website.
  2. Download the packages for Super/Worker and Collector to the location where you want to install the image. For example: FSM_Full_All_KVM_6.1.0_build0112.zip .
  3. Unzip the .zip file to get the FortiSIEM-6.1.0.0112.qcow2 file.
  4. Copy the above unzipped qcow2 file into the storage image location separately for the installation of super, worker, and collector. For example:

    /var/lib/libvirt/images/super/FortiSIEM-6.1.0.0112.qcow2

    /var/lib/libvirt/images/worker/FortiSIEM-6.1.0.0112.qcow2

    /var/lib/libvirt/images/collector/FortiSIEM-6.1.0.0112.qcow2

  5. Start the KVM Manager for the KVM server by clicking Virtual Machine Manager.

  6. Click Create a new virtual machine from the Virtual Machine Manager.
  7. Select Import existing disk image (Architecture defaults to x86_64).

  8. Click Forward from the above step, and select the OS type as Linux and Verision to CentOS 7.0, then click Forward.

  9. Click Browse... from the New VM dialog box to find the location for the file (for example, FortiSIEM-6.1.0.0112.qcow2). Or, you can directly copy the path and the qcow2 file name under Provide the existing storage path. Click Forward.

  10. In the New VM dialog box, change Memory from 1024 to 32000 (32 GB). Change the CPUs from 1 to 8. Click Forward.

  11. Before clicking Finish, make sure to check that the Network selection is a Bridge, and Customize configuration before install is selected. Then, click Finish.

  12. Start to make the configuration. This is the place where you change the name from the default name centos 7.0 in the Overview.

    caution icon

    In every step in this configuration, you must click Apply to save your changes.

  13. Click VirtIO Disk 1 (the default disk) and check that the Source path is correct. Click Apply.

  14. Click Boot Options and make sure that VirtIO Disk 1 is checked. Click Apply.

  15. Add an extra three disks by clicking Add Hardware. Assign to them the disk image size to 100GB, 60GB, and 60GB respectively with the same Bus type of VirtIO. Click Finish to save the result.
  16. Disk Size Disk Name
    Hard Disk 2 100GB /opt
    Hard Disk 3 60GB /cmdb
    Hard Disk 4 60GB /svn
    Hard Disk 5 60GB+ /data (see the following note)

    Note on Hard Disk 5:

  • Add a 5th 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.
  • Click Begin Installation at the top of the dialog box to start the installation process.

  • At the end of booting, log in with the default login credentials: User: root and Password: ProspectHills.
  • You will be required to change the password. Remember this password for future use.
  • At this point, you can continue configuring FortiSIEM by using the GUI.

    Configure FortiSIEM via GUI

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

    1. Log in as user root with the password you set in Step 19 above.
    2. At the command prompt, go to /usr/local/bin and enter configFSM.sh, for example:

      # configFSM.sh

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

    4. Select your Region, and press Next.

    5. Select your Country, and press Next.

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

    7. Select 1 Supervisor. Press Next.

      note icon

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

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

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

      Option Description
      Host Name The Supervisor's host name
      IPv4 Address The Supervisor's IPv4 address
      NetMask The Supervisor's subnet
      Gateway Network gateway address
      FQDN Fully-qualified domain name
      DNS1, DNS2 Addresses of the DNS servers

    10. Test network connectivity by connecting to a well-known public internet site, as shown in the following dialog box. Press Next.

    11. 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.

      Option Description
      -r The FortiSIEM component being configured
      -z The time zone being configured
      -i IPv4-formatted address
      -m Address of the subnet mask
      -g Address of the gateway server used
      --host Host name
      -f FQDN address: fully-qualified domain name
      -t The 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 servers

      -o

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

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

      --testpinghost

      The URL used to test connectivity

    12. It will take some time to complete the FortiSIEM installation. If the installation is successful, then 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:

    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.

    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.

    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 an 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 settings for Worker node are:

    • CPU = 8
    • Memory = 24 GB
    • Two hard disks:
      • OS – 25GB
      • OPT – 100GB

     

    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 you need to only choose OS and OPT disks. The recommended settings for Collector node are:

    • CPU = 4
    • Memory = 8GB
    • Two hard disks:
      • OS – 25GB
      • OPT – 100GB

    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 > 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.
    3. SSH to the Collector and run following script to register Collectors:

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

      1. Set user and password use 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.

    4. 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 and enter the IP of the Worker node. 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>

      1. Set user and password use the admin User Name and password for the Supervisor.
      2. Set Super IP or Host as the Supervisor's IP address.
      3. Set Organization as the name of an organization created on the Super.
      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

    Pre-Installation Checklist

    Before you begin, check the following:

    • Ensure that your system can connect to the internet
    • 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:
    Node vCPU RAM Local Disks
    Supervisor (All in one) Minimum – 16
    Recommended - 32

    Minimum

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

    Recommended

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

    OS – 25GB

    OPT – 100GB

    CMDB – 60GB

    SVN – 60GB

    Local Event database – based on need

    Supervisor (Cluster) Minimum – 16
    Recommended - 32

    Minimum

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

    Recommended

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

    OS – 25GB

    OPT – 100GB

    CMDB – 60GB

    SVN – 60GB

     

    Workers Minimum – 8
    Recommended - 8

    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.

    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.

    Import FortiSIEM into KVM

    1. Go to the Fortinet Support website https://support.fortinet.com to download the KVM package FSM_Full_All_KVM_6.1.0_build0112.zip. See Downloading FortiSIEM Products for more information on downloading products from the support website.
    2. Download the packages for Super/Worker and Collector to the location where you want to install the image. For example: FSM_Full_All_KVM_6.1.0_build0112.zip .
    3. Unzip the .zip file to get the FortiSIEM-6.1.0.0112.qcow2 file.
    4. Copy the above unzipped qcow2 file into the storage image location separately for the installation of super, worker, and collector. For example:

      /var/lib/libvirt/images/super/FortiSIEM-6.1.0.0112.qcow2

      /var/lib/libvirt/images/worker/FortiSIEM-6.1.0.0112.qcow2

      /var/lib/libvirt/images/collector/FortiSIEM-6.1.0.0112.qcow2

    5. Start the KVM Manager for the KVM server by clicking Virtual Machine Manager.

    6. Click Create a new virtual machine from the Virtual Machine Manager.
    7. Select Import existing disk image (Architecture defaults to x86_64).

    8. Click Forward from the above step, and select the OS type as Linux and Verision to CentOS 7.0, then click Forward.

    9. Click Browse... from the New VM dialog box to find the location for the file (for example, FortiSIEM-6.1.0.0112.qcow2). Or, you can directly copy the path and the qcow2 file name under Provide the existing storage path. Click Forward.

    10. In the New VM dialog box, change Memory from 1024 to 32000 (32 GB). Change the CPUs from 1 to 8. Click Forward.

    11. Before clicking Finish, make sure to check that the Network selection is a Bridge, and Customize configuration before install is selected. Then, click Finish.

    12. Start to make the configuration. This is the place where you change the name from the default name centos 7.0 in the Overview.

      caution icon

      In every step in this configuration, you must click Apply to save your changes.

    13. Click VirtIO Disk 1 (the default disk) and check that the Source path is correct. Click Apply.

    14. Click Boot Options and make sure that VirtIO Disk 1 is checked. Click Apply.

    15. Add an extra three disks by clicking Add Hardware. Assign to them the disk image size to 100GB, 60GB, and 60GB respectively with the same Bus type of VirtIO. Click Finish to save the result.
    16. Disk Size Disk Name
      Hard Disk 2 100GB /opt
      Hard Disk 3 60GB /cmdb
      Hard Disk 4 60GB /svn
      Hard Disk 5 60GB+ /data (see the following note)

      Note on Hard Disk 5:

    • Add a 5th 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.
  • Click Begin Installation at the top of the dialog box to start the installation process.

  • At the end of booting, log in with the default login credentials: User: root and Password: ProspectHills.
  • You will be required to change the password. Remember this password for future use.
  • At this point, you can continue configuring FortiSIEM by using the GUI.

    Configure FortiSIEM via GUI

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

    1. Log in as user root with the password you set in Step 19 above.
    2. At the command prompt, go to /usr/local/bin and enter configFSM.sh, for example:

      # configFSM.sh

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

    4. Select your Region, and press Next.

    5. Select your Country, and press Next.

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

    7. Select 1 Supervisor. Press Next.

      note icon

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

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

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

      Option Description
      Host Name The Supervisor's host name
      IPv4 Address The Supervisor's IPv4 address
      NetMask The Supervisor's subnet
      Gateway Network gateway address
      FQDN Fully-qualified domain name
      DNS1, DNS2 Addresses of the DNS servers

    10. Test network connectivity by connecting to a well-known public internet site, as shown in the following dialog box. Press Next.

    11. 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.

      Option Description
      -r The FortiSIEM component being configured
      -z The time zone being configured
      -i IPv4-formatted address
      -m Address of the subnet mask
      -g Address of the gateway server used
      --host Host name
      -f FQDN address: fully-qualified domain name
      -t The 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 servers

      -o

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

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

      --testpinghost

      The URL used to test connectivity

    12. It will take some time to complete the FortiSIEM installation. If the installation is successful, then 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:

    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.

    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.

    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 an 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 settings for Worker node are:

    • CPU = 8
    • Memory = 24 GB
    • Two hard disks:
      • OS – 25GB
      • OPT – 100GB

     

    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 you need to only choose OS and OPT disks. The recommended settings for Collector node are:

    • CPU = 4
    • Memory = 8GB
    • Two hard disks:
      • OS – 25GB
      • OPT – 100GB

    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 > 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.
    3. SSH to the Collector and run following script to register Collectors:

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

      1. Set user and password use 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.

    4. 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 and enter the IP of the Worker node. 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>

      1. Set user and password use the admin User Name and password for the Supervisor.
      2. Set Super IP or Host as the Supervisor's IP address.
      3. Set Organization as the name of an organization created on the Super.
      4. Set CollectorName from Step 6.

        The Collector will reboot during the Registration.

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