Is it necessary to encrypt chat messages before storing it into firebase?

Question

As far as I know, Firebase sends data over an HTTPS connection, so that the data is already being encrypted. Although Firebase provides security rules to protect my data structure, I can still be able to see the string messages in the database.

I'm just curious whether it is a good idea to encrypt messages before pushing the data to Firebase or not. Should I just move on from this topic to something else?

Thank you.

Thanks for the question @JeffMinsungKim ... You made my searching for the same question much easier. — PhillipJacobs, Jan 01 '20 at 21:43
@Phillip Jacobs No problem buddy. I'm the one thanking your kind words. :) — JeffMinsungKim, Jan 02 '20 at 00:03

score 42 · Accepted Answer · answered Dec 16 '17 at 15:26

42

You seem to have a good grasp of how Firebase Database works: the data is encrypted in transit, and it is stored on encrypted disks on the servers. If you enable local persistence on the device, the on device data is not encrypted.

But administrators of the app can see the data in the Firebase console. If it is a requirement of your app that administrators can't read this data, then you'll need to encrypt it on the client before sending it to Firebase. A while ago a developer explained their end-to-end encrypted chat on the firebase-talk mailing list.

answered Dec 16 '17 at 15:26

Frank van Puffelen

565,676
79
828
807

1

Thank you so much for your in-depth answer, Frank. It helped me understand a lot of things at once. – JeffMinsungKim Dec 16 '17 at 22:58
1

Good to hear Jeff. I look forward to seeing your end-to-end encryption solution (and answers on future questions in this area)! – Frank van Puffelen Dec 17 '17 at 01:04

score 29 · Answer 2 · answered Jun 08 '18 at 06:29

Hey Jeff: you're right that when you write some data into Firebase/Firestore, the data:

Is protected over the wire using HTTPS.
Then, when it lands on the Firebase REST frontend server, HTTPS terminates and the server has access to the full payload
Then the REST server routes the data to the backend/database, which also has access to the data.
When the data is written into disk, it's encrypted at-rest, but the at-rest encryption keys are also available to Google and your administrators will also see the Firestore contents

Encrypting data client side (End-to-End Encryption) prohibits all these participants/roles seeing your data.

Encrypting data on client side is fairly simple (compatibility across mobile platforms and browsers is tricky). The other tricky part is the key management to enable one user access to the decryption key without the other user sending the key over in an unsecure channel.

The way you can implement this is:

Create private & public keys for your users when you sign them up
Encrypt data on user1's device with user2's public key
Write the encrypted data into Firestore
When user2 reads up the encrypted data, her private key will be able to decrypt it.

Check out this Firebase E2EE chat sample on GitHub for iOS: https://github.com/VirgilSecurity/demo-firebase-ios and Android: https://github.com/VirgilSecurity/demo-firebase-android

HTH, David

following your steps I think the question would be where do you store the private and public keys of the users when they sign up? In the database or locally on their devices? — Johhan Santana, Jul 08 '20 at 00:05
My thought would be to store each user's public key in Firestore and store their private keys locally on their devices using flutter_secure_storage or biometric_storage. — Code on the Rocks, Mar 19 '21 at 18:02

Is it necessary to encrypt chat messages before storing it into firebase?

2 Answers2

Linked