Access Control Matrix
What is an Access Control Matrix?
An access control matrix is a table that defines which users or roles can perform which actions on which systems, applications or data, used to design, review and audit access rights.
Updated November 2026 · 3 min read
An access control matrix is a table that shows which users or roles can do what to which systems, applications or data. Rows list the people or roles, called subjects, columns list the resources, called objects, and each cell records the permitted actions, such as read, write, approve or administer. The matrix makes access rights explicit, so they can be designed deliberately, reviewed and checked for conflicts.
The idea has two lives. In computer security, it is a formal model of protection, introduced by Butler Lampson in a 1971 paper and developed by G. Scott Graham and Peter Denning in 1972 and by Michael Harrison, Walter Ruzzo and Jeffrey Ullman in 1976. In governance, risk and compliance, an access control matrix is a practical document, usually a spreadsheet or a report from an identity system, that maps business roles to the permissions they need and is used to design roles, enforce segregation of duties and support access reviews.
How the Matrix Works
A simplified matrix for a hypothetical finance system might look like this:
| Role | Vendor records | Invoices | Payments | General ledger |
|---|---|---|---|---|
| Accounts payable clerk | Read | Create, edit | None | Read |
| AP manager | Read | Approve | None | Read |
| Treasury analyst | Read | Read | Create, release | Read |
| Vendor master administrator | Create, edit | None | None | None |
| Controller | Read | Read | Approve over $50,000 | Post journals |
Reading across a row shows everything one role can do. Reading down a column shows everyone who can touch one resource.
How It Is Implemented
Real systems rarely store a full matrix, because most cells are empty. Instead they store it in one of two ways:
- Access control lists (ACLs) store each column: for each resource, the list of subjects and their rights. File systems and cloud storage permissions typically work this way.
- Capability lists store each row: for each subject, the resources and rights it holds, like a set of keys.
Most organizations assign permissions to roles rather than individuals, an approach known as role-based access control (RBAC), so the matrix maps roles to permissions and a separate assignment maps people to roles.
Uses in Governance and Compliance
- Least privilege. Designing roles so each has only the access needed for the job.
- Segregation of duties. Checking that no role, or combination of roles held by one person, allows a conflicting pair of actions, such as creating a vendor and paying it.
- User access reviews. Giving managers and system owners a clear view of who has what, so they can confirm or remove access, typically quarterly for critical systems.
- Audit evidence. Supporting IT general controls testing for SOX, SOC 2 and ISO 27001 audits.
- Onboarding and role changes. Defining what access a new starter or a person changing jobs should receive, and what should be removed.
An Example
Consider a hypothetical manufacturer preparing for its first SOX audit. It builds an access control matrix for its ERP system covering 40 roles and 300 permissions, and runs it against a list of 25 conflicting permission pairs. The analysis finds 17 users who can both create vendors and release payments, mostly because they were given extra roles to cover colleagues' holidays and never had them removed. The company removes the conflicts where possible and, for three small-site employees who must keep both, adds a compensating control: a monthly review of their payments by the controller.
Common Pitfalls
- Role explosion, with hundreds of near-identical roles that no one can review meaningfully.
- Access that accumulates as people change jobs and keep their old permissions.
- A matrix that lives only in a spreadsheet and drifts away from what systems actually allow.
- Rubber-stamp access reviews, where managers approve everything because the list is too long to check.
An access control matrix is a building block of internal controls, and the conflicts it reveals are often documented in a risk control matrix.
Related terms
Segregation of Duties (SoD)
Splitting key steps across people so no one can commit and hide an error.
IT General Controls (ITGC)
Baseline controls over access, change and operations that keep IT reliable.
SOX Compliance
Meeting US public company requirements for controls over financial reporting.
SOC 2
An independent CPA report on a service provider's security and related controls.