#138Case study1 min
HTTPS is not enough to secure your app
The padlock protects transport, not the access rules on your data.
Hackaiz team · updated 18/11/2026

01What the padlock protects
HTTPS encrypts the path between the browser and the server: no one on the network can read or change the exchange on the way. The padlock also shows that the certificate matches the site name. That is essential, but it says nothing about what the server agrees to do once the request arrives.
02What HTTPS does not protect
If an access rule lets any visitor read the customer table, that read travels quietly over HTTPS. The same goes for a secret key published in the site, an admin page without checks, or an API that trusts the identifier sent by the browser.
03What else to check
Check who can read and change each piece of data, that secret keys stay server-side and that sensitive pages require sign-in and the right role.
- 1Review the access rules of each table or resource.
- 2Look for secret keys in code sent to the browser.
- 3Try sensitive actions with an account that has no rights.
Frequently asked questions
Take the next step
Was this article helpful?