Security is not just about adding a firewall. It starts with a question: what access does this person or service actually need?
1. Identify an action and a resource
Replace “database access” with precise needs: read a table, add an order or manage the schema. These actions do not require the same privilege level.
2. Verify on the server
Hiding a button or a link does not prevent a direct request. The server must verify identity, resource permissions and the validity of every sensitive action.
3. Limit duration and observe
Temporary authorisation and appropriate logs reduce exposure and support investigation. Never put secrets, passwords or tokens in logs.
Request
→ authenticated identity?
→ permission for this resource?
→ valid action?
→ allow, otherwise deny
→ log the decision without secretsYour turn to build
List the actions of a learner, instructor and administrator on a course platform. Assign only the necessary permissions to each role.
Your discovery progress is saved on this device. You can clear it from My learning.