← All case studies

Which systems need an access review first?

I designed a way to prioritise access reviews when a team could only take on part of the work at once.

Deciding what comes first

I classified systems by the access they granted, the business impact of misuse and the dependencies that could hold up a review. Recording the reason for each choice gave the team a way to revisit it when new evidence arrived.

For example, a rarely used account can still deserve an early review if it can change permissions across several systems. The number of users alone would miss that risk.

Public modelRisk and dependency determine scope

A scope matrix combines identity exposure and business impact while keeping later sequencing visible rather than disguising it as low risk.