Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support & Infrastructure Let’s talk

System Security / 2026 Essentials

Access Control: Start with Deny, Then Grant What Is Needed

Authentication identifies a user; authorisation decides what that user may do.

Compiled for Sorlavit Kim · Published · 1 min read

Signing in should not unlock every record. Applications must verify permission for the requested action and resource. OWASP recommends denying access by default and validating permissions on every request, including calls made directly to an endpoint rather than through the visible interface.

What matters

  • Define permissions around actual responsibilities and resource ownership.
  • Enforce checks on the server instead of relying on hidden buttons.
  • Test access between accounts, roles, and organisations, not just a successful login.

Practical example: A customer portal confirms that an invoice belongs to the signed-in customer before returning it.

One action today: Test whether a normal user can retrieve another user’s record by changing its identifier.

Source & further reading

OWASP — Authorization Cheat Sheet

Independently written summary reviewed on 31 October 2026. The example illustrates a possible application; it is not a client case study.

Share this article

Back to results