Azure SQL Server offers Transparent Data Encryption (TDE) by default, with the flick of a virtual switch:
There is no option to select an algorithm and I am not using "Bring Your Own Key".
Which encryption algorithm is being used and what is the key length?
All articles I find such as this one and this one have circular references to one another with no clear answer.
If you run this in your SQL Azure database
select * from sys.dm_database_encryption_keys
you should see the encryption algorithm being used and the key length.
In my case I have TDE enabled in one of my databases and I can see that the key_algorithm is AES and the key_lenght is 256.
It is AES 256
See this article:
https://learn.microsoft.com/en-us/azure/sql-database/transparent-data-encryption-azure-sql?tabs=azure-portal
Related
How can I apply AES encryption to hadoop? Is it possible? If not, help me encrypt the data file in hadoop
The latest versions of hadoop supports encryption. We can create encrypted zones and the data that we transfer to these zones will be encrypted automatically and the data retrieved from this zone will be decrypted automatically. This is also known as REST data encryption. The detailed steps are given in the apache website. This doesn't need any change in the code that access this data.
This can be also equated to server side encryption.
If you want custom encryption to be applied to the files in hdfs, it will be little complex, because you have to apply the encryption/decryption logic in all the programs that uses these data. If the data is encrypted using custom encryption logic, the RecordReader and RecordWriter classes needs to be modified to work with the data.
I'm developing BIRT reports, which are deployed as a WEBAPP on Jetty.
Currently all the passwords in my Connection Provider Stores are Base64 'encrypted', but I'm wondering if and how I can use another encryption algorithm for my encrypted-properties.
<encrypted-property name="odaPassword" encryptionID="base64" value="......."/>
I've read something about Encryption Extension Points but I'm not sure if this concept also applies to BIRT webapps and how to implement this / where to put them.
Best regards,
Richard
Base 64 is an encoding method, not an encryption method. See https://stackoverflow.com/a/4070709/2782404. What are you currently using for encryption?
Have you seen this example of encryption extension point implementation for BIRT? http://www.informit.com/articles/article.aspx?p=1748986&seqNum=6
If so, source code might be helpful for understanding your specific problem
Could anyone point me to documentation of encryption options available for couchbase? With SQL Server we have the option to encrypt data at table or db level. Is it possible to encrypt couchbase data in a similar way?
I believe that Gazzang is what you want to look at in regards to data encryption for Couchbase:
Gazzang for Couchbase offers a powerful, policy-driven solution that enables you to encrypt your data stored in Couchbase Server. With Gazzang, data files in Couchbase Server are encrypted on disk. This ensures that your data is not compromised if your database is stolen, copied, lost, or otherwise improperly accessed.
Source and more information on Gazzang: http://www.couchbase.com/couchbase-server/connectors/gazzang
You could also use file system encryption - windows provides the option.
I know that in iOS, if the .sqlite is updated / read by SQL statement, then SQLCipher can be used to do encryption and decryption.
Is there any suggestion if Core Data is used instead ? The requirements are:
Core Data is used instead
Backup via itune for the application data is still be encrypted
Thanks
If you want the SQLite to be encrypted when the device is locked only, then the on-disk encryption feature introduced in iOS 4 is your answer.
Otherwise, you may need to encrypt stuff programmatically. Cf. Core Data SQLite encryption?.
But AFAIK, there's no built-in support of any SQLite encryption feature in Core Data.
I am using firebird server 2.50. As far as I know there is no way to encrypt a database in Firebird. So how to secure the user data?
Manually encrypting all data before saving would cause trouble since i will not be able to use something like "starting with".
I use CentOs for Database servers. These servers are communicating with an Application Server which runs on Windows Server 2008.
Encryption is one kind of several protection measures which can be done against potential adversaries. And there are other methods too. You need common security analysis before you go with decision whether to encrypt or not, and if not than what. You have to look who are adversaries, where they could hit, etc-etc-etc. Blind use of encryption may be waste of resource/time/money/etc. Do security analysis first.
DB encryption is possible in version 3:
With Firebird 3 comes the ability to encrypt data stored in database. Not all of the database file is encrypted:
just data, index and blob pages.
To make it possible to encrypt a database you need to obtain or write a database crypt plug-in.
Refer to Firebird-3.0.0_Alpha1-ReleaseNotes for details