Configuring Storage

Overview

FortiSIEM provides a wide array of event storage options. Upon arrival in FortiSIEM, events are stored in the Online event database. The user can define retention policies for this database. When the Online event database becomes full, FortiSIEM will move the events to the Archive Event database. Similarly, the user can define retention policies for the Archive Event database. When the Archive becomes full, events are discarded.

The Online event database can be one of the following:

  • FortiSIEM EventDB
    • On local disk for All-in-one installation
    • On NFS for cluster installation
  • Elasticsearch
    • Native installation
    • AWS OpenSearch (Previously known as AWS Elasticsearch)
  • ClickHouse
    • Native installation

The Archive event database can be one of the following:

  • FortiSIEM EventDB on NFS
  • HDFS

Note the various installation documents for 3rd party databases, for example.

In this release, the following combinations are supported:

Event DB    Retention
Online Archive Online Archive
FortiSIEM EventDB
(local or NFS)		 FortiSIEM EventDB
(NFS)		 Policy-based and Space-based Policy-based and Space-based
Elasticsearch  FortiSIEM EventDB (NFS) Space-based Policy-based and Space-based
Elasticsearch  HDFS Space-based Space-based

ClickHouse

FortiSIEM EventDB (NFS)

Space-based

Policy-based and Space-based

 

Database Storage Efficiency, Query Performance, Ingestion Speed Comparison

Database / Search Engine

Storage Efficiency

Query Performance

Ingestion Speed
EventDB Medium/High Medium Medium
Elasticsearch Low High Medium
Spark/HDFS High Medium Medium
ClickHouse High High High

Configuring Online Event Database on Local Disk

This section describes how to configure the Online Event database on local disk. Use this option when you have an all-in-one system, with only the Supervisor and no Worker nodes deployed.

Setting Up the Database

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > Local Disk.
  3. Enter the following parameters :

    SettingsGuidelines
    Disk Name[Required] Local disk name.
    During FortiSIEM installation, you can add a 'Local' data disk of appropriate size as the 4th or 5th disk (Refer to your specific Installation Guide in the FortiSIEM Document Library). Use the command fdisk -l to find the disk name.

    If you want to configure Local Disk for the physical 2000F or 3500F appliances, enter "hardware" in this field. This prompts a script to run that will configure local storage.

  4. Click Test.
  5. If the test succeeds, click Deploy.

Setting Up Retention

When Online database becomes full, then events have to be deleted to make room for new events. This can be Space-based or Policy-based.

Setting Up Space-Based Retention

Space-based retention is based on two thresholds defined in the phoenix_config.txt file on the Supervisor node.

[BEGIN phDataPurger]

online_low_space_action_threshold_GB=10

online_low_space_warning_threshold_GB=20

[END]

When the Online Event database size in GB falls below the value of online_low_space_action_threshold_GB, events are deleted until the available size in GB goes slightly above the online_low_space_action_threshold_GB value. If Archive is defined, then the events are archived. Otherwise, they are purged.

If you want to change these values, then change them on the Supervisor and restart phDataManager and phDataPurger modules.

Setting Up Policy-Based Retention

Policies can be used to enforce which types of event data remains in the Online event database.

For information on how to create policies, see Creating Online Event Retention Policy. Note: This is a CPU, I/O, and memory-intensive operation. For best performance, try to write as few retention policies as possible.

How Space-Based and Policy-Based Retention Work Together

  1. First, Policy-based retention policies are applied.
  2. If the available space is still below the value of online_low_space_action_threshold_GB, then Space-based policies are enforced.

Viewing Online Data

For more information, see Viewing Online Event Data Usage.

Configuring Online Event Database on NFS

The following sections describe how to configure the Online database on NFS.

Setting Up the Database

You must choose this option when you have multiple Workers deployed and you plan to use FortiSIEM EventDB.

The NFS Storage should be configured as NFS version 3 with these options: “rw,sync,no_root_squash”.

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > NFS
  3. Enter the following parameters :

    SettingsGuidelines
    Server IP/Host[Required] the IP address/Host name of the NFS server
    Exported Directory[Required] the file path on the NFS Server which will be mounted

  4. Click Test.
  5. If the test succeeds, click Deploy.

Setting Up Retention

When the Online database becomes full, then events must be deleted to make room for new events. This can be Space-based or Policy-based.

Setting Up Space-Based Retention

Space-based retention is based on two thresholds defined in the phoenix_config.txt file on the Supervisor node.

[BEGIN phDataPurger]

online_low_space_action_threshold_GB=10

online_low_space_warning_threshold_GB=20

[END]

When the Online Event database size in GB falls below the value of online_low_space_action_threshold_GB, events are deleted until the available size in GB goes slightly above the online_low_space_action_threshold_GB value. If Archive is defined, then the events are archived. Otherwise, they are purged.

If you want to change these values, then change them on the Supervisor and restart the phDataManager and phDataPurger modules.

Setting Up Policy-Based Retention

Policies can be used to enforce which types of event data stays in the Online event database.

For information on how to create policies, see Creating Online Event Retention Policy. Note: This is a CPU, I/O, and memory-intensive operation. For best performance, try to write as few retention policies as possible.

How Space-Based and Policy-Based Retention Work Together

  1. First, Policy-based retention policies are applied.
  2. If the available space is still below the online_low_space_action_threshold_GB, then Space-based policies are enforced.

Viewing Online Data

For more information, see Viewing Online Event Data Usage.

Configuring Online Event Database on Elasticsearch

The following sections describe how to set up the Online database on Elasticsearch:

Setting Up the Database

There are three options for setting up the database:

Native Elasticsearch Using REST API

Use this option when you want FortiSIEM to use the REST API Client to communicate with Elasticsearch.

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > Elasticsearch and for ES Service Type, select Native.
  3. Enter the following parameters:

    SettingsGuidelines
    Org Storage

    Select one of the following from the drop-down list:

    • All Orgs in One Index - Select to create one index for all organizations.

    • Each Org in its own Index - Select to create an index for each organization.

    • Custom Org Assignment - Select to create, edit or delete a custom organization index. Click Edit to configure. See Custom Organization Index for Elasticsearch for more information. Click Deploy Org Assignment to deploy the currently configured custom org assignment.

    		 
    Endpoint

    [Required]

    • URL:  IP address or DNS name of the Elasticsearch cluster Coordinating node. The IP/Host must contain http or https.

    • Ingest: Select if the URL endpoint will be used to handle pipeline processing.

    • Query: Select if the URL endpoint will be used to query Elasticsearch.

      Note: Ingest and Query can both be selected for an endpoint URL.

    Click + to add more URL fields to configure any additional Elasticsearch cluster Coordinating nodes.

    Click - to remove any existing URL fields.

    Port[Required] The port number
    User Name [Optional] User name
    Password[Optional] Password associated with the user
    Shard Allocation
    • Fixed -Enter the number of Shards and Replicas.
    • Dynamic-Dynamically shards data using the Elasticsearch rollover API. Enter the number of Starting Shards and Replicas.
    Event Attribute Template
    • Default-Select if you wish to cover FortiSIEM Event attributes covering all event attribute types.
    • Custom-Select if you wish to cover specific FortiSIEM Event attributes. A reduced list of Event Attributes can improve Elasticsearch performance. After selecting Custom, click Select, and select your CSV file with your FortiSIEM Event attributes.

      For information on the listElasticEventAttributes.sh tool that gathers Event Attributes so you can build a custom event attribute template, see Administrator Tools.

     

    		 

  4. Click Test.
  5. If the test succeeds, click Deploy.

AWS OpenSearch (Previously known as AWS Elasticsearch) Using REST API

Use this option when you have FortiSIEM deployed in AWS Cloud and you want to use AWS OpenSearch (Previously known as AWS Elasticsearch).

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > Elasticsearch and for ES Service Type, select Amazon.
  3. Enter the following parameters:

    SettingsGuidelines
    Org Storage

    Select one of the following from the drop-down list:

    • All Orgs in One Index - Select to create one index for all organizations.

    • Each Org in its own Index - Select to create an index for each organization.

    • Custom Org Assignment - Select to create, edit or delete a custom organization index. Click Edit to configure. See Custom Organization Index for Elasticsearch for more information. Click Deploy Org Assignment to deploy the currently configured custom org assignment.

    		 
    Endpoint

    [Required]

    • URL:  IP address or DNS name of the Elasticsearch cluster Coordinating node. The IP/Host must contain http or https.

    • Ingest: Select if the URL endpoint will be used to handle pipeline processing.

    • Query: Select if the URL endpoint will be used to query Elasticsearch.

      Note: Ingest and Query can both be selected for an endpoint URL.

    Click + to add more URL fields.

    Click - to remove any existing URL fields.

    Port[Required] The port number
    Access Key ID[Required] Provide your AWS access key id.
    Secret Key[Required] Provide your AWS secret key.
    Shard Allocation
    • Fixed -Enter the number of Shards and Replicas.
    • Dynamic-Dynamically shards data using the Elasticsearch rollover API. Enter the number of Starting Shards and Replicas.
    Event Attribute Template
    • Default-Select if you wish to cover FortiSIEM Event attributes covering all event attribute types.
    • Custom-Select if you wish to cover specific FortiSIEM Event attributes. A reduced list of Event Attributes can improve Elasticsearch performance. After selecting Custom, click Select, and select your CSV file with your FortiSIEM Event attributes.

      For information on the listElasticEventAttributes.sh tool that gathers Event Attributes so you can build a custom event attribute template, see Administrator Tools.

     

    		 

  4. Click Test.
  5. If the test succeeds, click Deploy.

Elastic Cloud Using REST API

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > Elasticsearch and and for ES Service Type, select Elastic Cloud.
  3. Enter the following parameters:
    SettingsGuidelines
    Org Storage

    Select one of the following from the drop-down list:

    • All Orgs in One Index - Select to create one index for all organizations.

    • Each Org in its own Index - Select to create an index for each organization.

    • Custom Org Assignment - Select to create, edit or delete a custom organization index. Click Edit to configure. See Custom Organization Index for Elasticsearch for more information. Click Deploy Org Assignment to deploy the currently configured custom org assignment.

    Endpoint

    [Required]

    • URL:  IP address or DNS name of the Elasticsearch cluster Coordinating node. The IP/Host must contain http or https.

    • Ingest: Select if the URL endpoint will be used to handle pipeline processing.

    • Query: Select if the URL endpoint will be used to query Elasticsearch.

      Note: Ingest and Query can both be selected for an endpoint URL.

    Click + to add more URL fields to configure any additional Elasticsearch cluster Coordinating nodes.

    Click - to remove any existing URL fields.

    Port[Required] The port number
    User Name [Optional] User name
    Password[Optional] Password associated with the user
    Shard Allocation
    • Fixed -Enter the number of Shards and Replicas.
    • Dynamic-Dynamically shards data using the Elasticsearch rollover API. Enter the number of Starting Shards and Replicas.
    Event Attribute Template
    • Default-Select if you wish to cover FortiSIEM Event attributes covering all event attribute types.
    • Custom-Select if you wish to cover specific FortiSIEM Event attributes. A reduced list of Event Attributes can improve Elasticsearch performance. After selecting Custom, click Select, and select your CSV file with your FortiSIEM Event attributes.

      For information on the listElasticEventAttributes.sh tool that gathers Event Attributes so you can build a custom event attribute template, see Administrator Tools.

     

  4. Click Test.
  5. If the test succeeds, click Deploy.

Setting Up Space-Based / Age-Based Retention

Depending on whether you use Native Elasticsearch, AWS OpenSearch (Previously known as AWS Elasticsearch), or ElasticCloud, Elasticsearch is installed using Hot (required), Warm (optional), and Cold (optional, availability depends on Elasticsearch type) nodes and Index Lifecycle Management (ILM) (availability depends on Elasticsearch type). Similarly, the space is managed by Hot, Warm, Cold node thresholds and time age duration, whichever occurs first, if ILM is available. See What's New for the latest information on elasticsearch retention threshold compatibility. For steps, see here.

  • When the Hot node cluster storage capacity falls below the lower threshold or meets the time age duration, then:
    • if Warm nodes are defined, the events are moved to Warm nodes,
    • else if Warm nodes are not defined, but Cold nodes are defined, the events are moved to Cold nodes,
    • else, if Archive is defined then they are archived,
    • otherwise, events are purged

    This is done until storage capacity exceeds the upper threshold.

  • If Warm nodes are defined and the Warm node cluster storage capacity falls below lower threshold or meets the time age duration, then:
    • if Cold nodes are defined, the events are moved to Cold nodes,
    • else if Cold nodes are not defined, and Archive is defined, then they are archived,
    • otherwise, events are purged

    This is done until storage capacity exceeds the upper threshold.

  • If Cold nodes are defined and the Cold node cluster storage capacity falls below lower threshold, then:
    • if Archive is defined, then they are archived,
    • otherwise, events are purged

    This is done until storage capacity exceeds the upper threshold

Viewing Online Data

For more information, see Viewing Online Event Data Usage.

Configuring Online Event Database on ClickHouse

The following sections describe how to set up the Online database on ClickHouse:

Setting Up the Database

  1. Go to ADMIN > Setup > Storage.
  2. Click Online > ClickHouse
    Note: It is strongly recommended to review the information from ClickHouse Configuration to understand all available ClickHouse features before proceeding.
  3. Enter the following parameters:

    SettingsGuidelines
    Storage Tiers [Required] From the drop-down list, select the number of storage tiers. 1 tier is for Hot. 2 tiers include Hot and Warm tiers.
    Hot Tier - Disk Path

    [Required] the file path on the ClickHouse Server which will be mounted for the configured tiers.

    Click + to add a row for another disk path, and - to remove any rows.

    During FortiSIEM installation, you can add one or more 'Local' data disk of appropriate size as additional disks, i.e., 5th disk (hot), 6th disk (warm). Use the command fdisk -l or lsblk from the CLI to find the disk names.

    When using lsblk to find the disk name, please note that the path will be ‘/dev/<disk>’. In the below example, running on KVM, the 5th disk (hot) will be ‘/dev/vde’ and the 6th disk (warm) will be ‘/dev/vdf’.


  4. Click Test.
  5. If the test succeeds, click Deploy.
    To add Worker Nodes to ClickHouse Cluster, see Initial Configuration in ClickHouse Configuration.

Space-Based Retention Information

ClickHouse allows configuration of Hot tier or Hot and Warm tiers. When disk space is less than 10%, data will be purged until a minimum of 20% disk space is available. For example, if there is only the Hot tier, when only 10% space is available, the oldest data will be purged until at least 20% disk space is freed up. If two tiers are configured (Hot and Warm), when the Warm tier has less than 10% disk space left, the oldest data is purged from the Warm disk space until 20% free space is available. This space-based retention is hardcoded, and does not need to be set up.

Age-Based Retention Information

You are able to figure 3 Months, 6 Months, 1 Year, 3 Years, 5 Years, 10 Years, or Forever (50 Years). Policies can be used to enforce which types of event data stays in the Online event database.

For information on how to create policies for ClickHouse, see Creating a ClickHouse Online Event Retention Policy.

Viewing Online Data

For more information, see Viewing Online Event Data Usage.

 

Configuring Archive Event Database on NFS

The following sections describe how to set up the Archive database on NFS:

Setting Up the Database

You must choose this option when you have multiple Workers deployed and you plan to use FortiSIEM EventDB.

The NFS Storage should be configured as NFS version 3 with these options: “rw,sync,no_root_squash”.

  1. Go to ADMIN > Setup > Storage.
  2. Click Archive > NFS,
  3. Enter the following parameters:

    SettingsGuidelines
    Server IP/Host[Required] the IP address/Host name of the NFS server
    Exported Directory[Required] the file path on the NFS Server which will be mounted
    Real Time Archive(Optional) event data is written to NFS archive at the same time it is written to online storage, when enabled. Click the checkbox to enable/disable.
    Note: You must click Save in step 5 in order for the Real Time Archive setting to take effect. It is strongly recommended you confirm that the test works, in step 4 before saving.    		 

  4. Click Test.
  5. If the test succeeds, click Deploy.

Setting Up Retention

When the Archive database becomes full, then events must be deleted to make room for new events. This can be Space-based or Policy-based.

Space-Based Retention

Space-based retention is based on two thresholds defined in phoenix_config.txt file on the Supervisor node.

[BEGIN phDataPurger]

archive_low_space_action_threshold_GB=10

archive_low_space_warning_threshold_GB=20

[END]

When the Archive Event database size in GB falls below the value of archive_low_space_action_threshold_GB, events are purged until the available size in GB goes slightly above the value set for archive_low_space_action_threshold_GB.

If you want to change these values, then change them on the Supervisor and restart the phDataManager and phDataPurger modules.

Policy-Based Retention

Policies can be used to enforce which types of event data remain in the Archive event database.

For information on how to create policies, see Creating Offline (Archive) Retention Policy. Note - This is a CPU, I/O, and memory-intensive operation. For best performance, try to write as few retention policies as possible.

How Space-Based and Policy-Based Retention Work Together

  1. First, Policy-based retention policies are applied.
  2. If the available space is still below archive_low_space_action_threshold_GB, then Space-based policies are enforced.

Viewing Archive Data

For more information, see Viewing Archive Data.

Configuring Archive Event Database on HDFS

The following sections describe how to set up the Archive database on HDFS:

Setting Up the Database

HDFS provides a more scalable event archive option - both in terms of performance and storage.

  1. Go to ADMIN > Setup > Storage.
  2. Click Archive > HDFS.
  3. Enter the following parameters:

    SettingsGuidelines
    Real Time Archive

    (Optional) event data is written to HDFS archive at the same time it is written to online storage, when enabled. Click the checkbox to enable/disable.

    Note: You must click Save in step 5 in order for the Real Time Archive setting to take effect. It is strongly recommended you confirm that the test works, in step 4 before saving.

    Spark Master Node
    IP/HostIP or Host name of the Spark cluster Master node.
    PortTCP port number for FortiSIEM to communicate to Spark Master node.
    HDFS Name Node
    IP/Host IP or Host name of HDFS Name node. This is the machine which stores the HDFS metadata: the directory tree of all files in the file system, and tracks the files across the cluster.
    PortTCP port number for FortiSIEM to communicate to HDFS Name node.

  4. Click Test.
  5. If the test succeeds, click Deploy.

Setting Up Space-Based Retention

When the HDFS database becomes full, events have to be deleted to make room for new events.

This is set by Archive Thresholds defined in the GUI. Go to ADMIN > Settings > Database > Online Settings. Change the Low and High settings, as needed.

When the HDFS database size in GB rises above the value of archive_low_space_action_threshold_GB, events are purged until the available size in GB goes slightly above the value set for archive_low_space_action_threshold_GB.

Viewing Archive Data

For more information, see Viewing Archive Data.

Changing Event Storage Options

It is highly recommended to chose a specific event storage option and retain it. However, it is possible to switch to a different storage type.

Note: In all cases of changing storage type, the old event data is not migrated to the new storage. Contact FortiSIEM Support if this is needed - some special cases may be supported.

For the following cases, simply choose the new storage type from ADMIN > Setup > Storage.

  • Local to Elasticsearch
  • NFS to Elasticsearch
  • Elasticsearch to Local

The following storage change cases need special considerations:

Elasticsearch to NFS

  1. Log in to FortiSIEM GUI.
  2. Select and delete the existing Workers from ADMIN > License > Nodes > Delete.
  3. Go to ADMIN > Setup > Storage and update the Storage type as NFS server
  4. Go to ADMIN > License > Nodes and Add the recently deleted Workers in step #2.

Local to NFS

  1. SSH to the Supervisor and stop FortiSIEM processes by running:
    phtools --stop all
  2. Unmount /data by running:
    umount /data
  3. Validate that /data is unmounted by running:
    df –h
  4. Edit /etc/fstab and remove /data mount location.
  5. Log in to FortiSIEM GUI, go to ADMIN > Setup > Storage and update the Storage type as NFS server.

NFS to Local

  1. SSH to the Supervisor and stop FortiSIEM processes by running:
    phtools --stop all
  2. Unmount /data by running:
    umount /data
  3. Validate that /data is unmounted by running:
    df –h
  4. Edit /etc/fstab and remove /data mount location.
  5. Connect the new disk to Supervisor VM.
  6. Log in to FortiSIEM GUI, go to ADMIN > Setup > Storage and update the Storage type as Local Disk.

EventDB to ClickHouse

Assuming you are running FortiSIEM EventDB on a single node deployment (e.g. 2000F, 2000G, 3500G and VMs), the following steps shows how to migrate your event data to ClickHouse.

Follow these steps to migrate events from EventDB to ClickHouse.

  1. Stop all the processes on Supervisor by running the following command.
    phtools –-stop all

    Note: This will also stop all events from coming into Supervisor.

  2. Edit /etc/fstab and remove all /data entries for EventDB.

  3. If the same disk is going to be used by ClickHouse (e.g. in hardware Appliances), then copy out events from FortiSIEM EventDB to a remote location. You can bring back the old data if needed (See Step 7).

    1. Mount a new remote disk for the appliance, assuming the remote server is ready, using the following command.

      # mount -t nfs <remote server ip>:<remote share point> <local path>

    2. Copy the data, using the following command.

      # rsync -av --progress /data /<local path>

      Example: # rsync -av --progress /data /mnt/eventdb

  4. If the same disk is going to be used by ClickHouse (e.g. in hardware Appliances), then delete old data from FortiSIEM, by taking the following steps.

    1. Remove the data by running the following command.

      # rm -rf /data/*

    2. Unmount, by running the following commands.

      # note mount path for /data

      # umount /data

    3. For 2000G, run the following additional command.

      # lvremove /dev/mapper/FSIEM2000G-phx_eventdbcache: y

  5. For VM based deployments, create new disks for use by ClickHouse by taking the following steps.

    1. Edit your Virtual Machine on your hypervisor.

    2. Add a new disk to the current disk controller.

    3. Run the following in your FortiSIEM Supervisor Shell if the disk is not automatically added.

      # echo "- - -" > /sys/class/scsi_host/host0/scan

      # echo "- - -" > /sys/class/scsi_host/host1/scan

      # echo "- - -" > /sys/class/scsi_host/host2/scan

      # lsblk

  6. Log into the GUI as a full admin user and change the storage to ClickHouse by taking the following steps.

    1. Navigate to ADMIN > Setup > Storage > Online.

    2. From the Event Database drop-down list, select ClickHouse.

    3. From the Storage Tiers drop-down list, select 1.

    4. In the Disk Path field, select the disk path.

      Example: /dev/sde

    5. Click Test.

    6. Click Deploy.

  7. (Optional) Import old events. For appliances they were copied out in Step 3 above. For VMs, they may be mounted remotely. To do this, run the following command from FortiSIEM.

    # /opt/phoenix/bin/phClickHouseImport --src [Source Dir] --starttime [Start Time] --endtime [End Time] --host [IP Address of ClickHouse - default 127.0.0.1] --orgid [Organization ID (0 – 4294967295)

    More information on phClickHouseImport can be found here.

    Note the valid time format:

    <time> : "YYYY-MM-DD hh:mm:ss" (notice the quotation marks, they need to be included.)

    Example:

    phClickHouseImport --src /test/sample --starttime "2022-01-27 10:10:00" --endtime "2022-02-01 11:10:00"

    Example with import all organizations:

    [root@SP-191 mnt]# /opt/phoenix/bin/phClickHouseImport --src /mnt/eventdb/ --starttime "2022-01-27 10:10:00" --endtime "2022-03-9 22:10:00"

    Found 32 days' Data

    [█ ] 3% 3/32 [283420]█

  8. Log into FortiSIEM GUI and use the ANALYTICS tab to verify events are being ingested.

Elasticsearch to ClickHouse

To switch your Elasticsearch database to ClickHouse, take the following steps.

Note: Importing events from Elasticsearch to ClickHouse is currently not supported

  1. Stop all the processes on Supervisor by running the following command.

    phtools –-stop all

    Note: This command will also stop all events from coming into the Supervisor. Make sure phMonitor process is running.

  2. Log into your hypervisor and add disks for ClickHouse by taking the following steps. You can have 2 Tiers of disks with multiple disks in each Tier. You must have at least one Tier 1 disk.

    1. Edit your Virtual Machine on your hypervisor.

    2. Add a new disk to the current disk controller.

    3. Run the following in your FortiSIEM Supervisor Shell if the disk is not automatically added.

      # echo "- - -" > /sys/class/scsi_host/host0/scan

      # echo "- - -" > /sys/class/scsi_host/host1/scan

      # echo "- - -" > /sys/class/scsi_host/host2/scan

      # lsblk

  3. Set up ClickHouse as the online database by taking the following steps.

    1. Navigate to ADMIN > Setup > Storage > Online.

    2. From the Event Database drop-down list, select ClickHouse.

    3. From the Storage Tiers drop-down list, select 1.

      Note: If you wish to have a warm tier or multiple hot tier disks, additional disks are required

    4. Provide the disk path.

    5. Click Test.

    6. Click Deploy when the test is successful.

    Events can now come in.

  4. Log into FortiSIEM GUI and use the ANALYTICS tab to verify events are being ingested.

ClickHouse to EventDB

To switch your ClickHouse database to EventDB, take the following steps.

Note: Importing events from ClickHouse to EventDB is currently not supported.

  1. Stop all the processes on the Supervisor by running the following command.

    phtools –-stop all

    Note: This is will also stop all the events from coming into Supervisor.

  2. Stop ClickHouse Service by running the following commands.

    systemctl stop clickhouse-server

    systemctl stop phClickHouseMonitor

  3. Edit phoenix_config.txt in /opt/phoenix/config on Supervisor and set enable = false for ClickHouse.

  4. Edit and remove any mount entries in /etc/fstab that relates to ClickHouse.

  5. Unmount data by taking the following step depending on whether you are using a VM (hot and/or warm disk path) or hardware (2000F, 2000G, 3500G).

    1. For VM, run the following command.

      umount /data-clickhouse-hot-1

      If multiple tiers are used, the disks will be denoted by a number.

      Example:

      /data-clickhouse-hot-2

      /data-clickhouse-warm-1

      /data-clickhouse-warm-2

    2. For hardware, run the following command.

      umount /data-clickhouse-hot-1

    3. For 2000G, run the following additional commands.

      umount /data-clickhouse-warm-1

      lvremove /dev/mapper/FSIEM2000Gphx_hotdata : y

  6. Delete old ClickHouse data by taking the following steps.

    1. Remove old ClickHouse configuration by running the following commands.

      # rm -f /etc/clickhouse-server/config.d/*

      # rm -f /etc/clickhouse-server/users.d/*

  7. Clean up "incident" in psql, by running the following commands.

    psql -U phoenix -d phoenixdb

    truncate ph_incident;

    truncate ph_incident_detail;

  8. Configure storage for EventDB by taking the following steps.

    • For VMs, proceed with Step 9, then continue.

    • For hardware appliances 2000F, 2000G, or 3500G, proceed to Step 10.

  9. Set up EventDB as the online database by taking the following steps for EventDB Local Disk OR EventDB on NFS.

    1. For EventDB Local Disk configuration, take the following steps.

      1. Create a new disk for the VM by logging into the hypervisor and create a new disk.

      2. Log into the FortiSIEM Supervisor GUI as a full admin user.

      3. Navigate to ADMIN > Setup > Storage > Online.

      4. From the Event Database drop-down list, select EventDB Local Disk.

      5. Target the new local disk.

      6. Click Test.

      7. Click Deploy.

      8. Proceed to Step 11.

    2. For EventDB on NFS configuration, take the following steps.

      Note: Make sure remote NFS storage ready.

      1. Create a new disk for the VM by logging into the hypervisor and create a new disk.

      2. Log into FortiSIEM Supervisor GUI as a full admin user.

      3. Navigate to ADMIN > Setup > Storage > Online.

      4. From the Event Database drop-down list, select EventDB on NFS.

      5. In the IP/Host field, select IP or Host and enter the remote NFS server IP Address or Host name.

      6. In the Exported Directory field, enter the share point.

      7. Click Test.

      8. Click Deploy.

      9. Proceed to Step 11.

  10. Set up EventDB as the online database, by taking the following steps.

    1. Log into the FortiSIEM Supervisor GUI as a full admin user.

    2. Navigate to ADMIN > Setup > Storage > Online.

    3. From the Event Database drop-down list, select EventDB.

    4. Click Test.

    5. Click Deploy.

  11. Make sure phMonitor process is running. Events can now come in.

  12. Verify events are coming in by running Adhoc query in ANALYTICS.

ClickHouse to Elasticsearch

To switch your ClickHouse database to Elasticsearch, take the following steps.

Note: Importing events from ClickHouse to Elasticsearch is currently not supported.

  1. Stop all the processes on Supervisor by running the following command.

    phtools –-stop all

    Note: This is will also stop all the events from coming into Supervisor.

  2. Stop ClickHouse Service by running the following commands.

    systemctl stop clickhouse-server

    systemctl stop phClickHouseMonitor

  3. Edit phoenix_config.txt on the Supervisor and set enable = false for ClickHouse.

  4. Edit and remove any mount entries in /etc/fstab that relates to ClickHouse

  5. Unmount data by taking the following step depending on whether you are using a VM (hot and/or warm disk path) or hardware (2000F, 2000G, 3500G).

    1. For VM, run the following command.

      umount /data-clickhouse-hot-1

      If multiple tiers are used, the disks will be denoted by a number:

      Example:

      /data-clickhouse-hot-2

      /data-clickhouse-warm-1

      /data-clickhouse-warm-2

    2. For hardware, run the following command.

      umount /data-clickhouse-hot-1

    3. For 2000G, run the following additional commands.

      umount /data-clickhouse-warm-1

      lvremove /dev/mapper/FSIEM2000Gphx_hotdata : y

  6. Delete old ClickHouse data by taking the following steps.

    1. Remove old ClickHouse configuration by running the following commands.

      # rm -f /etc/clickhouse-server/config.d/*

      # rm -f /etc/clickhouse-server/users.d/*

  7. Clean up "incident" in psql, by running the following commands.

    psql -U phoenix -d phoenixdb

    truncate ph_incident;

    truncate ph_incident_detail;

  8. Make sure phMonitor process is running.

  9. Setup Elasticsearch as online database by taking the following steps.

    1. Log into the FortiSIEM Supervisor GUI as a full admin user.

    2. Navigate to ADMIN > Setup > Storage > Online.

    3. From the Event Database drop-down list, select Elasticsearch.

    4. From the ES Service Type drop-down list, select Native, Amazon, or Elastic Cloud.

    5. Configure the rest of the fields depending on the ES Service Type you selected.

    6. Click Test.

    7. Click Deploy.

  10. Wait for JavaQuerySever process to start up.

  11. Start new events.

  12. Verify events are coming in by running Adhoc query in ANALYTICS.

Changing NFS Server IP

If you are running a FortiSIEM Cluster using NFS and want to change the IP address of the NFS Server, then take the following steps.

Step 1: Temporarily Change the Event Storage Type from EventDB on NFS to EventDB on Local

  1. Go to ADMIN > License > Nodes and remove all the Worker nodes.
  2. SSH to the Supervisor and stop FortiSIEM processes by running:
    phtools --stop all
  3. Unmount /data by running:
    umount /data
  4. Validate that /data is unmounted by running:
    df –h
  5. Edit /etc/fstab and remove /data mount location.
  6. Attach new local disk to the Supervisor. It is recommended that it is at least 50~80GB.
  7. Go to ADMIN > Setup > Storage > Online.
  8. Change the storage type to Local Disk and add the local disk's partition to the Disk Name field. (e.g. /dev/sde).
  9. Click Test to confirm.
  10. Click Deploy.

Step 2: Change the NFS Server IP Address

This is a standard system administrator operation. Change the NFS Server IP address.

Step 3: Change the Event Storage Type Back to EventDB on NFS

  1. SSH to the Supervisor and stop FortiSIEM processes by running:
    phtools --stop all
  2. Umount /data by running:
    umount /data
  3. Validate that /data is unmounted by running:
    df –h
  4. Edit /etc/fstab and remove /data mount location.
  5. Go to ADMIN > Setup > Storage > Online.
  6. Change the storage type to NFS.
  7. In the Server field, with IP selected, enter the new IP address of the NFS server.
  8. In the Exported Directory field, enter the correct NFS folder's path.
  9. Click Test to confirm.
  10. Click Deploy.
  11. Go to ADMIN > License > Nodes and add back all the Worker nodes.

Custom Organization Index for Elasticsearch

From the Assign Organizations to Groups window, you can create, edit, or delete existing custom Elasticsearch groups. You can use the Search... field to locate any existing custom Elasticsearch groups. This feature is available from ADMIN > Setup > Storage > Online with Elasticsearch selected as the Event Database, and Custom Org Assignment selected for Org Storage. At the Org Storage field, click the Edit button.

Add a Custom Elasticsearch Group

To add a custom Elasticsearch group, take the following steps.

  1. Click Add.

  2. From the Organization drop-down list, select the organization.

  3. From the Group drop-down list, select a group. If an organization is not assigned to a group here, the default group for this organization is set to 50,000.

  4. Click Done.

  5. Click Save.
    Note: Saving here only save the custom Elasticsearch group.

  6. Click Deploy Org Assignment to make the change take effect.

    Note: Test and Deploy are needed after switching org storage from other options to Custom Org Assignment, and vice versa.

 

Edit a Custom Elasticsearch Group

  1. Select a Custom Elasticsearch Group.

  2. Click Edit.

  3. From the Organization drop-down list, select the organization.

    Note: If only one Organization exists, the drop-down list is not accessible.

  4. From the Group drop-down list, select a group.

  5. Click Done.

  6. Click Save.

  7. Click Deploy Org Assignment to make the change take effect.

Delete a Custom Elasticsearch Group

  1. Select a Custom Elasticsearch Group.

  2. Click Delete.

  3. Click Yes to confirm.

  4. Click Save.

  5. Click Deploy Org Assignment to make the change take effect.

 

Disk Space Management

When the Online storage is nearly full, events must either be archived or purged to make room for new events. Similarly, when the Archive storage is nearly full, events are purged to make room for new events from Online storage. This strategy keeps FortiSIEM running continuously.

This section provides details for the various storage options.

Online Event Database on Local Disk or on NFS

There are two parameters in the phoenix_config.txt file on the Supervisor node that determine the operations. They appear under the phDataPurger section.

[BEGIN phDataPurger]

- online_low_space_action_threshold_GB (default 10GB)

- online_low_space_warning_threshold_GB (default 20GB)

[END]

When Online disk space reaches the low threshold (online_low_space_action_threshold_GB) value, then events are archived (if archive directory is set) or purged. This operation continues until the Online disk space reaches the online_low_space_warning_threshold_GB value. This check is done hourly.

You can change these parameters to suit your environment and they will be preserved after upgrade. You must restart phDataPurger module to pick up your changes.

Online Event Database on Elasticsearch

Log in to the FortiSIEM GUI and go to ADMIN > Settings > Online Settings. If Elasticsearch is chosen as Online storage, depending on your elasticsearch type, and whether you have archive configured, the following choices will be available in the GUI.

  • Hot Node - Low Threshold (default 25%), High Threshold (35%), Age 90 days
  • Warm Node - Low Threshold (default 20%), High Threshold (30%), Age 90 days
  • Cold Node - Low Threshold (default 20%), High Threshold (30%)
  • Archive - Low Threshold (default 10%), High Threshold (20%)

When Hot Node disk free space reaches the Low Threshold value, events are moved until the Hot Node disk free space reaches the High Threshold value. Event destination can be one of the following:

  • Warm Node
  • Cold Node - if Warm Nodes are not defined
  • Archive - if prior nodes (Warm, Cold) are not defined
  • Purged - if neither Warm Node, Cold Node, nor Archive is defined

When Warm Node disk free space reaches the Low Threshold value, events are moved to Cold node. If Cold node is not defined, events are moved to Archive or purged (if Archive is not defined) until Warm disk free space reaches High Threshold.

When Cold Node disk free space reaches the Low Threshold value, events are moved to Archive or purged (if Archive is not defined), until Cold disk free space reaches High Threshold.

Archive Event Database on NFS

There are two parameters in the phoenix_config.txt file on the Supervisor node that determine when events are deleted. They appear under the phDataPurger section:

[BEGIN phDataPurger]

- archive_low_space_action_threshold_GB (default 10GB)

- archive_low_space_warning_threshold_GB (default 20GB)

[END]

When the Archive disk space reaches the low threshold (archive_low_space_action_threshold_GB) value, events are purged until the Archive disk space reaches the high threshold (online_low_space_warning_threshold_GB) value. This check is done hourly.

You can change these parameters to suit your environment and they will be preserved after upgrade. You must restart phDataPurger module to pick up your changes.

Archive Event Database on HDFS

This is set by configuring the Archive Threshold fields in the GUI at ADMIN > Settings > Database > Online Settings. Elasticsearch must be configured as online storage, and HDFS as offline storage in order for the Archive Threshold option/field to appear in the configuration. This is the only way to purge data from HDFS. For more information on configuring thresholds, see Setting Elasticsearch Retention Threshold.