Thanks for your reply @nocodeventure,

Yes, the idea is to get consent first, but I wanted to first find out if anyone had gone through these steps already or had set up a kind of bug bounty setup to find security vulnerabilities. I don’t know if Bubble does this already… maybe @allenyang can chime in… When I mean security vulnerabilities of course I mean real system backdoors that can allow hackers to penetrate the database.

I already have a lot of security measures in place, but for the business that I have started I want to go one step further. These are just some of the steps we have taken apart from the ones you have already mentioned (Thanks BTW),

  1. All user data is encrypted using AES 256 bit encryption.
  2. Keys for encrypted data is held in a different location to Bubble.
  3. Enforced more secure passwords in Signup (Users have to use passwords with numbers, Upper and lower case letters and special characters).
  4. Removed ‘Run as’ feature for Collaborators and Admins.
  5. Removed ‘Run as’ feature for App owners. Not even App owners can look at users data.
  6. Applied Privacy rules and used conditional statements (Only if user is logged in, Only if user is the creater of X Data type, Only if the user, etc…
  7. Applied 2FA to the Web App (Not yet implemented)
  8. Applied 2FA to Bubble account.
  9. Used a 20+ character long password for Bubble account.

I don’t know if I’m missing anything but if anyone has any other recommendations feel free to join the discussion. I’m curious to see what other people have done to make their app a lot more secure.

Regards

2 Likes