Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
You have the option to encrypt or obfuscate your databases. Encryption provides secure representation of the data in the database whereas obfuscation only prevents casual observation of the contents of the database.
By default, databases are not encrypted or obfuscated. Text and binary columns can be read when using a viewing tool such as a hex editor. Consider the following options if you do not want your data stored as plain text:
Obfuscation This option provides protection against casual attempts to access data in the database but does not provide as much security as strong encryption. Obfuscation has a minimal performance impact. You do not need any special configuration to use simple obfuscation on your device.
AES 256-bit encryption This option encrypts databases with an AES 256-bit algorithm. Strong encryption provides security against skilled and determined attempts to gain access to the data but has a significant performance impact. You do not need any special configuration to use AES encryption on your device.
AES 256-bit FIPS 140-2 certified encryption (Windows and Windows Mobile only) Encryption libraries certified with the FIPS 140-2 US and Canadian government standard (using a Certicom certified cryptographic module) are provided. AES FIPS-certified encryption requires that you configure your device appropriately.
Un composant sous licence distincte est requis.
Le cryptage certifié FIPS exige une licence distincte. Toutes les technologies de cryptage fort sont soumises à des réglementations d'exportation.
Consider the effects of database cache size when choosing to encrypt or obfuscate databases. There is an overhead increase between 5-10%, which can result in decreased performance. The exact effect on performance depends on the size of your cache. If your cache is too small, encryption can add significant overhead. However, if your cache is sufficiently large, you may not see any difference at all. For more information about cache sizes, see Cache size adjustment for an UltraLite database.
Discuter à propos de cette page dans DocCommentXchange.
|Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0|