iBase does support SQL Server's 'Transparent Data Encryption' feature. There are quite a few iBase customers running TDE on their databases, and it works fine. With TDE the data is encrypted by the SQL Server engine as it is written to the database file. So the data on the hard disk is encrypted, but data in the server's memory or on the network is not encrypted.

iBase also supports SSL for the client-server connection. This keeps the iBase data encrypted while it travels over the network from client to and from the SQL Server. Like TDE, SSL is a pretty common choice for iBase customers, and it seems to be reliable and problem-free.

There are some links to additional information in this IBM Technote:

       What levels of encryption are available for IBM i2 iBase using a SQL datastore?

        http://www-01.ibm.com/support/docview.wss?uid=swg21694554

Warning : iBase does NOT support column-level encryption, also known as cell level encryption. This is where, for example, a single column in a Table is encrypted. Customers who want that protection should use Transparent Data Encryption instead.

"Always Encrypted" is a fairly new feature from Microsoft, it was introduced in SQL Server 2016. iBase does NOT currently support 'Always Encrypted'. The reason is that the client application must be written specifically to be a 'Always Encrypted' application. It also requires the client to run on .NET Framework 4.6 or later. iBase is an OLE DB application, it does not communicate with SQL Server using the .NET Data Provider. Therefore, iBase is currently Not compatible with the "Always Encrypted" feature of SQL Server.