Linux mount use wipefs3/28/2023 Wipe the filesystem of exiting filesystem and partition table. For each disk, ( /cmdb, /svn, /data) complete the following steps:.Import the latest FortiSIEM VA image on one of the supported platforms.If you have to perform these on an existing installation of FortiSIEM, then you must have additional disks of the same capacity to encrypt and copy the data to it. This avoids the need for additional disks. It is best to perform these steps on a fresh installation prior to initializing the product. To verify if the package is installed, run the following command: Note 3: The cryptsetup command is not included in FortiSIEM. The less secure alternative is to use keys that are not protected by a passphrase and stored in a file on the root partition. If you want strong security, then you must protect encryption keys with a passphrase and that requires a human to type them and mount the “opened” disks. Note 2: Disk encryption key management is an operational challenge. The root disk contains binaries and some internal system and application logs, not data. Note 1: We do not recommend encrypting the root disk which presents an operational challenge during boot up to provide a passphrase. If you are using NFS or Elastic storage, you must perform additional steps for the actual data directories on these servers in addition to supervisor ( /cmdb, /svn). The steps below show how to encrypt /cmdb, /svn, and /data disks on a FortiSIEM supervisor VM node with local disk for EventDB ( /data). Disk Encryption of Data on FortiSIEM Supervisor | FortiSIEM 6.3.0ĭisk Encryption of Data on FortiSIEM Supervisor
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |