It might be good to look into encrypting user data in the database so that if the database was stolen, purchasing data couldn't be retrieved. I'm not an expert on encryption so maybe someone else could correct me if I'm wrong, but this is my understanding of our situation:
Because the website should be accessible on different devices and by different users within a group, we can't create and store the encryption key on the client's end without it being a huge pain in the ass for the users
If the encryption key is stored on the server so that user data can be decrypted no matter where the client accesses the data from, I don't think it really reduces the attack surface.
The only way a person should be able to access the database is through the server anyways, so if that's compromised, the encryption key is useless
Maybe it's pointless to encrypt the user data, but its probably worth looking into.
It might be good to look into encrypting user data in the database so that if the database was stolen, purchasing data couldn't be retrieved. I'm not an expert on encryption so maybe someone else could correct me if I'm wrong, but this is my understanding of our situation:
Maybe it's pointless to encrypt the user data, but its probably worth looking into.