Fortinet Document Library

Version:

Version:

Version:

Version:


Table of Contents

Download PDF
Copy Link

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

Find the FortiSIEM Offer in Azure Using the Azure Marketplace

  1. On the Azure portal, search for Marketplace and navigate to Azure Marketplace.

  2. Search for the keyword "fortisiem".

  3. Select the Create drop-down, and choose Fortinet FortiSIEM for Azure.


    At this point, Azure will take you through the steps to create a virtual machine by first taking you to the Create a virtual machine page. Follow the steps in Create a VM Using a FortiSIEM 6.4.0 Azure Marketplace Image to continue.

 

Create a VM Using a FortiSIEM 6.4.0 Azure Marketplace Image

From the Create a virtual machine page, take the following steps:

  1. From the Resource group drop-down list, select a resource group.

  2. In the Virtual machine name field, enter a name for your virtual machine.

  3. From the Size drop-down list, select a size based on your node type and hardware requirements.

  4. The Username field is specified as azureuser.

  5. From the Stored Keys drop-down list, select your existing key pair. If needed, generate a new key pair, then select it here.

  6. When done with this step for configuration , click Next: Disks >.

  7. Use these partition values:

    Volume Name Size Disk Name
    Data Disk LUN 0 100GB

    /opt

    Data Disk LUN 1 60GB /cmdb
    Data Disk LUN 2 60GB /svn
    Data Disk LUN 3 60GB+ /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.

  8. After entering your disk partition values, click Next: Networking >.

  9. From the Networking page (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).

  10. Click Next: Management >.

  11. From the Management page (Management tab), accept the defaults provided or change them as needed per the Azure documentation.

  12. Click Next: Advanced >.

  13. From the Advanced page (Advanced tab), choose the default values.

  14. Click Next: Tags >.

  15. From the Tags page (Tags tab), add a Name tag and any other tags as needed.


  16. Click Next: Review + create >.

  17. From the Review + create page tab, verify that all the information is correct. Click Create.

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


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

  20. On the Resource page, note the Public IP address and copy it to the clipboard.

  21. (Optional) Configure the DNS name according to Azure documentation.

  22. SSH to the FortiSIEM VM with user azureuser (as specified here) and the downloaded SSH key. Run sudo su – to become user root. Run configFSM.sh.

 

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. Note: After Installation, a 5th option to change your network configuration (5 change_network_config) is available. This allows you to change your network settings and/or host name.


  8. Determine whether your network supports IPv4-only, IPv6-only, or both IPv4 and IPv6 (Dual Stack). Choose 1 for IPv4-only, choose 2 for IPv6-only, or choose 3 for both IPv4 and IPv6.
  9. If you choose 1 (IPv4) or choose 3 (Both IPv4 and IPv6), and press Next, then you will move to step 10. If you choose 2 (IPv6), and press Next, then skip to step 11.

  10. Configure the IPv4 network by entering the following fields. Press Next.

    Option Description
    IPv4 Address The Supervisor's IPv4 address
    Netmask The Supervisor's subnet
    Gateway Network gateway address
    DNS1, DNS2 Addresses of the DNS servers

  11. If you chose 1 in step 8, then you will need to skip to step 12. If you chose 2 or 3 in step 8, then you will configure the IPv6 network by entering the following fields, then press Next.

    Option Description
    IPv6 Address The Supervisor's IPv6 address
    prefix (Netmask) The Supervisor's IPv6 prefix
    Gateway ipv6 IPv6 Network gateway address
    DNS1 IPv6, DNS2 IPv6 Addresses of the IPv6 DNS server 1 and DNS server2

    Note: If you chose option 3 in step 8 for both IPv4 and IPv6, then even if you configure 2 DNS servers for IPv4 and IPv6, the system will only use the first DNS server from IPv4 and the first DNS server from the IPv6 configuration.

    Note: In many dual stack networks, IPv4 DNS server(s) can resolve names to both IPv4 and IPv6. In such environments, if you do not have an IPv6 DNS server, then you can use public IPv6 DNS servers or use IPv4-mapped IPv6 address.

  12. Configure Hostname for Supervisor. Press Next.


    Note: FQDN is no longer needed.

  13. 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.
    Note: By default, “google.com” is shown for the connectivity test, but if configuring IPv6, you must enter an accessible internally approved IPv6 DNS server, for example: “ipv6-dns.fortinet.com"
    Note: When configuring both IPv4 and IPv6, only testing connectivity for the IPv6 DNS is required because the IPV6 takes higher precedence. So update the host field with an approved IPv6 DNS server.

  14. 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) or 64 (for both IPv4 and IPv6).

    --dns1, --dns2

    Addresses of the DNS server 1 and DNS server 2.

    --i6

    IPv6-formatted address

    --m6

    IPv6 prefix

    --g6

    IPv6 gateway

    -o

    Installation option (install_without_fips, install_with_fips, enable_fips, disable_fips, change_network_config*)
    *Option only available after installation.

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

    --testpinghost

    The URL used to test connectivity

  15. 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. Use link https://<supervisor-ip> to login. Please note that if you are logging into FortiSIEM with an IPv6 address, you should input https://[IPv6 address] on the browser tab.
  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 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 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 and host name. 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 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 > 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 > Settings > System > Event Worker and enter the IP of the Supervisor node. Click Save.
  4. 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.
  5. 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 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.

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

Install Log

The install ansible log file is located here: /usr/local/fresh-install/logs/ansible.log.

Errors can be found at the end of the file.

 

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

Find the FortiSIEM Offer in Azure Using the Azure Marketplace

  1. On the Azure portal, search for Marketplace and navigate to Azure Marketplace.

  2. Search for the keyword "fortisiem".

  3. Select the Create drop-down, and choose Fortinet FortiSIEM for Azure.


    At this point, Azure will take you through the steps to create a virtual machine by first taking you to the Create a virtual machine page. Follow the steps in Create a VM Using a FortiSIEM 6.4.0 Azure Marketplace Image to continue.

 

Create a VM Using a FortiSIEM 6.4.0 Azure Marketplace Image

From the Create a virtual machine page, take the following steps:

  1. From the Resource group drop-down list, select a resource group.

  2. In the Virtual machine name field, enter a name for your virtual machine.

  3. From the Size drop-down list, select a size based on your node type and hardware requirements.

  4. The Username field is specified as azureuser.

  5. From the Stored Keys drop-down list, select your existing key pair. If needed, generate a new key pair, then select it here.

  6. When done with this step for configuration , click Next: Disks >.

  7. Use these partition values:

    Volume Name Size Disk Name
    Data Disk LUN 0 100GB

    /opt

    Data Disk LUN 1 60GB /cmdb
    Data Disk LUN 2 60GB /svn
    Data Disk LUN 3 60GB+ /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.

  8. After entering your disk partition values, click Next: Networking >.

  9. From the Networking page (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).

  10. Click Next: Management >.

  11. From the Management page (Management tab), accept the defaults provided or change them as needed per the Azure documentation.

  12. Click Next: Advanced >.

  13. From the Advanced page (Advanced tab), choose the default values.

  14. Click Next: Tags >.

  15. From the Tags page (Tags tab), add a Name tag and any other tags as needed.


  16. Click Next: Review + create >.

  17. From the Review + create page tab, verify that all the information is correct. Click Create.

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


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

  20. On the Resource page, note the Public IP address and copy it to the clipboard.

  21. (Optional) Configure the DNS name according to Azure documentation.

  22. SSH to the FortiSIEM VM with user azureuser (as specified here) and the downloaded SSH key. Run sudo su – to become user root. Run configFSM.sh.

 

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. Note: After Installation, a 5th option to change your network configuration (5 change_network_config) is available. This allows you to change your network settings and/or host name.


  8. Determine whether your network supports IPv4-only, IPv6-only, or both IPv4 and IPv6 (Dual Stack). Choose 1 for IPv4-only, choose 2 for IPv6-only, or choose 3 for both IPv4 and IPv6.
  9. If you choose 1 (IPv4) or choose 3 (Both IPv4 and IPv6), and press Next, then you will move to step 10. If you choose 2 (IPv6), and press Next, then skip to step 11.

  10. Configure the IPv4 network by entering the following fields. Press Next.

    Option Description
    IPv4 Address The Supervisor's IPv4 address
    Netmask The Supervisor's subnet
    Gateway Network gateway address
    DNS1, DNS2 Addresses of the DNS servers

  11. If you chose 1 in step 8, then you will need to skip to step 12. If you chose 2 or 3 in step 8, then you will configure the IPv6 network by entering the following fields, then press Next.

    Option Description
    IPv6 Address The Supervisor's IPv6 address
    prefix (Netmask) The Supervisor's IPv6 prefix
    Gateway ipv6 IPv6 Network gateway address
    DNS1 IPv6, DNS2 IPv6 Addresses of the IPv6 DNS server 1 and DNS server2

    Note: If you chose option 3 in step 8 for both IPv4 and IPv6, then even if you configure 2 DNS servers for IPv4 and IPv6, the system will only use the first DNS server from IPv4 and the first DNS server from the IPv6 configuration.

    Note: In many dual stack networks, IPv4 DNS server(s) can resolve names to both IPv4 and IPv6. In such environments, if you do not have an IPv6 DNS server, then you can use public IPv6 DNS servers or use IPv4-mapped IPv6 address.

  12. Configure Hostname for Supervisor. Press Next.


    Note: FQDN is no longer needed.

  13. 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.
    Note: By default, “google.com” is shown for the connectivity test, but if configuring IPv6, you must enter an accessible internally approved IPv6 DNS server, for example: “ipv6-dns.fortinet.com"
    Note: When configuring both IPv4 and IPv6, only testing connectivity for the IPv6 DNS is required because the IPV6 takes higher precedence. So update the host field with an approved IPv6 DNS server.

  14. 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) or 64 (for both IPv4 and IPv6).

    --dns1, --dns2

    Addresses of the DNS server 1 and DNS server 2.

    --i6

    IPv6-formatted address

    --m6

    IPv6 prefix

    --g6

    IPv6 gateway

    -o

    Installation option (install_without_fips, install_with_fips, enable_fips, disable_fips, change_network_config*)
    *Option only available after installation.

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

    --testpinghost

    The URL used to test connectivity

  15. 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. Use link https://<supervisor-ip> to login. Please note that if you are logging into FortiSIEM with an IPv6 address, you should input https://[IPv6 address] on the browser tab.
  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 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 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 and host name. 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 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 > 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 > Settings > System > Event Worker and enter the IP of the Supervisor node. Click Save.
  4. 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.
  5. 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 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.

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

Install Log

The install ansible log file is located here: /usr/local/fresh-install/logs/ansible.log.

Errors can be found at the end of the file.