Path 89 · The permission ledger · Intermediate
Compare granted access with the work required.
A guided, practical route through access control review.
What you will be able to do
Review a fictional role-permission matrix, identify excess access and prepare a traceable change proposal.
Plan about 7h 52m in total. Reading and practice are editorial estimates; video runtimes come from public provider metadata. Your pace will vary.
Table of Contents
Before you begin
Check your starting point
What you need
Basic identity concepts and spreadsheet use. No real account permissions are changed.
The selected public provider lessons are free to view. The original case can be completed with paper, a text editor or freely available local tools. Paid exams, certificates, subscriptions and optional provider software are not required for this project.
Completing this Coursya path does not award a provider certificate. Any provider assessment, account requirement or credential must be checked separately on its official page.
Three readiness questions
Is a job title sufficient evidence of needed access?
No. Map actual tasks and resources.
Should a review silently change real permissions?
No. Prepare and authorize specific changes.
Does removing excess access prove all security is solved?
No.
Use a workable pace
At 5 hours per week, allow about 2 weeks. Start with Stage 1, continue in order and reserve 2h for the capstone. If a gate fails, use its repair step before advancing. At another weekly budget, divide 472 estimated minutes by your available weekly minutes and round up.
Keep a small evidence folder. A checked box means you reviewed your output; it is not a certificate or proof that a provider lesson was watched.
The working case
Two grants need review
A workshop portal has Viewer, Editor and Approver roles. Viewers may read published files; Editors may also create drafts; Approvers may review drafts and publish. The current matrix accidentally gives Viewer the publish permission and gives Editor role-management permission.
| Role | Read published | Create draft | Review draft | Publish | Manage roles |
|---|---|---|---|---|---|
| Viewer | 1 | 0 | 0 | 1 | 0 |
| Editor | 1 | 1 | 0 | 0 | 1 |
| Approver | 1 | 0 | 1 | 1 | 0 |

The table and explanations preserve the essential case information when the diagram is unavailable.
Your route
Five outputs, then a final handoff
- 01Define required permissionsRequired-access baseline
About 1h 37m including assigned learning and practice. - 02Compare actual with intendedAccess difference report
About 1h 15m including assigned learning and practice. - 03Inspect resource-level conditionsConditional-access questions
About 1h 5m including assigned learning and practice. - 04Prepare a controlled changePermission change proposals
About 1h including assigned learning and practice. - 05Design the recurring review recordAccess-review handoff
About 55m including assigned learning and practice. - FINALCapstone reviewCombine the evidence into one inspectable handoff.
About 2h .
0 of 6 outputs checked. JavaScript adds browser-only progress saving.
The complete lesson and all downloads remain available. Use the printable project workbook to track your progress.
Use the minimum useful source material
The courses behind this route
IBM
Free Cybersecurity Architecture Course: Identity to Response
The existing identity-and-access architecture lesson supports roles, authorization and review questions without requiring a paid tenant.
Selected material only; this path does not claim completion of the entire provider course.
Course publication and selected public lesson metadata were checked on 13 October 2026. This is not a claim of full video playback, provider-course completion or permanent availability. Recheck the linked source if a lesson changes.
Learn, make, inspect
The five-stage workshop
Define required permissions
Video 31m · reading budget 0m · original practice about 1h 5m.
Start from the operations each role must perform. Separate ordinary content actions from administration of roles themselves. Least privilege is a task-based design principle, not a reason to remove access without understanding the work. The case defines a simplified baseline for a fictional portal.
Watch these selected lessons
Do the work
Write the intended matrix from the case narrative.
Save this output
Required-access baseline
Pass the review gate
No ordinary content role requires role management.
If you need another attempt
Tie each allowed permission to a named task.
Compare actual with intended
Video 0m · reading budget 0m · original practice about 1h 15m.
Compare each role-action pair and classify it as required and granted, required but missing, or granted without a stated need. A matrix makes excess access visible but does not show per-resource conditions. Preserve the current state as evidence and propose changes in a separate table.
Original application stage. Use your preceding outputs and the supplied case; there is no additional required provider lesson.
Do the work
Find the two excess permissions and produce a difference report.
Save this output
Access difference report
Pass the review gate
Viewer/publish and Editor/manage roles are the two excess grants.
If you need another attempt
Compare every cell rather than only the most powerful role.
Inspect resource-level conditions
Video 0m · reading budget 0m · original practice about 1h 5m.
Role membership may be only one part of authorization. An editor might be allowed to create drafts but not edit every organizer’s draft. Record these conditions separately from the coarse matrix. The exercise does not inspect a live implementation, so conditions remain requirements to verify later.
Original application stage. Use your preceding outputs and the supplied case; there is no additional required provider lesson.
Do the work
Add ownership and approval-separation questions to the review.
Save this output
Conditional-access questions
Pass the review gate
A role label is not treated as proof of resource-level enforcement.
If you need another attempt
Name the resource and action in each question.
Prepare a controlled change
Video 0m · reading budget 0m · original practice about 1h .
A change proposal should name the exact grant to remove, the reason, owner and rollback plan. Consider whether legitimate work depends on the access and how that work will continue. No actual account changes are needed for this learning case. Keep the proposed and approved states distinct.
Original application stage. Use your preceding outputs and the supplied case; there is no additional required provider lesson.
Do the work
Write two change requests with checks for required tasks after removal.
Save this output
Permission change proposals
Pass the review gate
Each proposal is specific and preserves the required task set.
If you need another attempt
Do not use remove all access as a substitute for a targeted correction.
Design the recurring review record
Video 0m · reading budget 0m · original practice about 55m.
A review record should show who assessed access, when, against which baseline and with what evidence. Add a review trigger for role changes, departures or new sensitive actions. The package provides the template only; it does not create an external schedule or modify any user account.
Original application stage. Use your preceding outputs and the supplied case; there is no additional required provider lesson.
Do the work
Build the review register and a completion checklist.
Save this output
Access-review handoff
Pass the review gate
No proposed removal is recorded as already applied.
If you need another attempt
Include status and verification fields for each change.
Make the result inspectable
Your final project
Deliver the baseline, current-versus-required comparison, conditional-access questions, change proposals and review register. Add a missing required permission in a copy and show how the checker distinguishes it from excess access.
The ZIP includes synthetic input data, a project workbook, worked reference, evidence log, scoring rubric and case-specific materials. Code projects include source and clearly stated local execution requirements.
Use one consistent rubric
| Criterion | Maximum | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The critical condition
The report preserves the current state and does not claim real permission changes or verified enforcement.
Compare with a worked reference
The current matrix has two grants not present in the case baseline: Viewer can publish and Editor can manage roles. Removing those two in the proposed matrix leaves Viewer read-only, Editor able to read and create drafts, and Approver able to read, review and publish.
Know the boundary
This is a fictional authorization review, not identity-provider administration or a completed security audit.
Questions before you finish
Do I need to finish every source course?
No. This path names selected lessons or reading sections. Complete the full provider course only if it supports your wider goal. The path does not claim equivalence to that course.
How do I know when to advance?
Use the output and review gate in each stage. If evidence is missing or a result conflicts with the case, follow the repair step and retry before advancing.
Can I do the project without paid software?
The selected public provider lessons are free to view. The original case can be completed with paper, a text editor or freely available local tools. Paid exams, certificates, subscriptions and optional provider software are not required for this project.
What does my checklist prove?
It records your own review in this browser only. It does not verify viewing, skill, a provider credential or a real-world deployment.
What if a lesson or tool changes?
Use the linked course and provider page to inspect current availability. Record the change and revisit the relevant assignment; do not invent a replacement lesson or claim an unavailable activity was completed.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.