Access Control Review
Project workbook · Path 89

Review a fictional role-permission matrix, identify excess access and prepare a traceable change proposal.

The case

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.

RoleRead publishedCreate draftReview draftPublishManage roles
Viewer10010
Editor11001
Approver10110
STAGE 1

Define required permissions

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.

Your task

Write the intended matrix from the case narrative.

Required output

Required-access baseline

Record your result and evidence here or in a separate file.

Review gate

No ordinary content role requires role management.

If the gate is not met

Tie each allowed permission to a named task.

STAGE 2

Compare actual with intended

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.

Your task

Find the two excess permissions and produce a difference report.

Required output

Access difference report

Record your result and evidence here or in a separate file.

Review gate

Viewer/publish and Editor/manage roles are the two excess grants.

If the gate is not met

Compare every cell rather than only the most powerful role.

STAGE 3

Inspect resource-level conditions

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.

Your task

Add ownership and approval-separation questions to the review.

Required output

Conditional-access questions

Record your result and evidence here or in a separate file.

Review gate

A role label is not treated as proof of resource-level enforcement.

If the gate is not met

Name the resource and action in each question.

STAGE 4

Prepare a controlled change

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.

Your task

Write two change requests with checks for required tasks after removal.

Required output

Permission change proposals

Record your result and evidence here or in a separate file.

Review gate

Each proposal is specific and preserves the required task set.

If the gate is not met

Do not use remove all access as a substitute for a targeted correction.

STAGE 5

Design the recurring review record

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.

Your task

Build the review register and a completion checklist.

Required output

Access-review handoff

Record your result and evidence here or in a separate file.

Review gate

No proposed removal is recorded as already applied.

If the gate is not met

Include status and verification fields for each change.

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.

Critical condition

The report preserves the current state and does not claim real permission changes or verified enforcement.

CriterionPointsEvidence
Evidence and correctness30Calculations, source use and results match the supplied case; limitations are honest.
Required artifacts30All five stage outputs and the capstone handoff are present and inspectable.
Reasoning and decisions20Choices, assumptions, alternatives and the case-specific critical condition are explained.
Reproducibility10A reviewer can follow the stated steps and distinguish expected from observed results.
Clear communication10Labels, 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.

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.

Boundaries

This is a fictional authorization review, not identity-provider administration or a completed security audit.