Protego field desk

Chapter 3 · Identity and Access

6. Read an Access Decision

Use a role policy to predict what the server should allow or deny.

Video transcript

Casey can sign in. Can Casey edit the schedule? Authorization decides whether an identity is allowed to perform an action on a resource. The booking app makes that decision on the server. Casey asks to read the schedule. The server checks the role, action and resource. The viewer rule permits reading, so the server returns the team schedule. When the server evaluates an edit for the same viewer, it denies the action. Casey's role permits the app to show the schedule. The policy reserves edits for users with the scheduler role. Write down the signed-in user's role. Name the action and which record it applies to. Record what the server should allow or deny. One identity can get different decisions for different actions. Use the knowledge check to read a role policy.

Course outlineLesson 6 of 8
Ethical Hacking for Beginners: course overview

Lesson notes

Authorization checks whether a particular identity can take a particular action on a resource. The booking app allows viewers to read the schedule and reserves edits for schedulers.

The server enforces that rule on each relevant request. Hiding an edit button helps users navigate the interface, while enforcement takes place at the service that handles the action.

Record the role, action, resource, and expected decision for every check. Include allowed behavior when verifying a fix so legitimate work remains available.

Try it

Write expected outcomes for three cases: viewer reads schedule, viewer edits schedule, and scheduler edits schedule.

OWASP ASVS Authorization
Knowledge Check

1. The viewer can sign in and read the schedule. What should the server do with a viewer edit under this policy?

2. Which record defines a useful expected authorization outcome?

3. Where must the app enforce restrictions on edits?