Introduction to CTERA Edge Filer Version 7.8.x
  • 3 Minutes to read
  • Dark
  • PDF

Introduction to CTERA Edge Filer Version 7.8.x

  • Dark
  • PDF

Article summary


In addition to the new features described in this article, the features described in Introduction to CTERA Edge Filer Version 7.7.x are also incorporated in this version.

CTERA Edge Filer version 7.8.x includes the following new features:

Linux CentOS 9 Operating System

The edge filer is installed with the Linux CentOS 9 operating system to replace the CentOS 7 operating system which is end of life on June 30, 2024.

Assign a Static IP During the Installation Under ESXi

A step in the procedure to deploy the OVA under ESXi in vSphere Client provides the option to specify a static IP address instead of using DHCP to assign the IP.

For details, see ESXi.

Support for EFI Boot Mode

The edge filer supports EFI boot mode. Because of this, upgrading an edge filer to edge filer version 7.8.x requires running the upgrade twice so that both software banks have the 7.8.x version.

RAM Restriction per License Removed

The RAM restriction imposed by the EV license has been removed. The edge filer virtual machine is deployed with 4 vCPUs and 8GB of RAM. Both of these values can be changed.

Ransomware Honeypot

CTERA Ransom Protect has been enhanced to prevent data exfiltration in addition to the existing behavioral protection. Decoy files enable real-time detection and blocking of data exfiltration attacks.

For details, see Ransomware Protection: CTERA Ransom Protect.

User Interface Support for Certificates

A TLS certificate is a digital credential that ensures secure communication by encrypting data exchanged between the connected clients to the CTERA Edge Filer.

A customer that uses a privately issued certificate on the CTERA Portal is required to upload the root CA to the CTERA Edge Filer so that the edge filer is trusted by the CTERA Portal.

Importing and managing certificates on the edge filer is now available in the user interface.

For details, see Loading a Certificate to a CTERA Edge Filer.

Improved Notification System

The dashboard includes notifications in the following categories:

  • The health of the edge filer
  • The health of the connection between the edge filer and the portal.
  • Security issues.

Each edge filer screen also includes a Notifications icon, image.png. Clicking this icon displays a Notifications panel with all the current notifications displayed, either as active notifications or hidden notifications if any notifications have been marked as hidden.


For details, see Edge Filer Notifications.

Support for Bitdefender Antivirus

Antivirus software is used to prevent malware from infecting files in the organization. CTERA Edge Filers integrate with Bitdefender Anti-malware SDK to ensure data protection.

TLS 1.2 and higher must be used.


When upgrading from a version of CTERA Edge Filer 7.7.x or earlier, any quarantined files that were quarantined using McAfee Endpoint Security for Linux Threat Prevention are lost.

Every file, including an archive file, that is read, copied, moved, or edited on the CTERA Edge Filer is automatically and transparently scanned for malware before the user can access the file.


Password protected files, emails and email databases are not scanned.

Stub files are not scanned for viruses until the files are downloaded from the CTERA Portal.

For details, see Antivirus Protection.

End User License Agreement

Each time you connect to the interface, the End User License Agreement is displayed before the browser displays the LogIn page.

Ensure Files that are Constantly Being Changed Have a Snapshot Saved on the Portal

Files that are constantly being modified so that they are not synced to the portal are cloned every 5 minutes and the clone is synced to the portal.

Temporary Files are Not Synced to the Portal

Temporary files on the CTERA Edge Filer that are included in an exclusion list are not synced to the CTERA Portal. .tmp and .temp files are not synced.

For more details, see What Files are Not Synced To the CTERA Portal.

.history Directories are ignored by CTERA Migrate

When running either a discovery or migration job in CTERA Migrate, .history files are ignored.

Was this article helpful?