Access Control Models
Assign roles and permissions with least privilege, and identify whether a situation uses role-based access, an access control list or owner-decided access.
Who decides which doors open for Riya?
On Riya Menon's first day as an intern at Tulsi Health, Neha Kulkarni, who leads IT and security, has to answer a practical question: which of the company's systems should Riya's new account be able to open? Deciding it from scratch for every person and every file would take forever and would never be consistent. So organisations follow an access control model: an agreed way of writing down and applying the rules for who can do what with which resource. Three models cover most of what you will meet. Role-based access control hands out access by job, access control lists attach a list of names to each resource, and discretionary access control lets the owner of a resource decide. Each one answers the same question in a different way, and each one fails in its own typical way.
Three ways to decide access: by the role printed on your card, by a list kept at each door, or by whatever the owner chooses.
Role-based access control: access comes with the job
Think of a college ID card with coloured stickers on it: a green "Library" sticker, a blue "Hostel" sticker, a red "Lab assistant" sticker. The guard at each door does not need to know you personally; he looks at the sticker. Role-based access control (RBAC) works the same way. A role is a named job, such as Pharmacist, Store manager or Accounts. Permissions are given to roles, never directly to people, and each person is given one or more roles. A permission is one allowed action on one resource, such as "view prescriptions" or "edit stock prices". A resource is anything that needs protecting: a folder, a database (an organised store of records, like a digital register), an app screen, a printer.
The work therefore happens in two separate steps, called role and permission assignment. First, someone who understands the business decides what each role needs: a Pharmacist must view and edit prescriptions, but has no reason to see staff salaries. Second, each person is assigned the roles that match their job. Farida holds the Pharmacist role and, with it, exactly the Pharmacist permissions, the same set as every other pharmacist in the chain.
People never receive permissions directly. Change what the Pharmacist role can do, and all 18 pharmacists change at once.
This is why RBAC is the most common model in organisations. When Tulsi Health opens a fifteenth store, the new staff are given existing roles and need no special decisions. When someone changes jobs, you swap their role rather than hunting down dozens of individual permissions. It also makes questions easy to answer: "who can see salaries?" becomes "who holds the Accounts role?"
RBAC fails in two common ways. The first is roles that are too broad: a single "Staff" role that can do everything, which is no better than having no rules. The second is the opposite, called role explosion: so many special roles ("Pharmacist who also does Saturday stock counts at Nashik") that nobody understands them any more. A good set of roles is small, matches real jobs, and follows the principle of least privilege: each role gets the least access that still lets the job be done.
The grid below starts with every role able to edit everything, which is how many small businesses actually begin. Your task is to take access away until each role has just what its job needs. Cells left with more access than needed are risks; cells cut below what is needed break someone's work.
Access control lists: a guest list at each door
A wedding hall in Pune might keep a guest list at the door of the family room. The guard checks your name against the list for that room, and the list belongs to the room, not to you. An access control list (ACL) is exactly this: a list attached to one resource that names who may use it and what they may do. The supplier contracts folder on Tulsi Health's shared drive might carry the list "sameer: edit, vikram: edit, neha: view". Anyone not on the list is refused.
ACLs are how most computer systems actually store permissions underneath. When you open the "Sharing" or "Properties" box of a folder on a shared drive, the list of names and ticks you see is its ACL. They are precise, because every resource can have its own rules. Their weakness is that the lists are spread out across thousands of files and folders. To find out everything Riya can reach, you would have to read every list in the company, which is why an intern's name often stays on a list long after the internship has ended.
RBAC and ACLs work well together. Instead of writing individual names on the list at each door, you write role names: "Accounts: edit" on the contracts folder. Then the list stays short and stable, and moving a person in or out of the Accounts role updates every door at once.
Discretionary access control: the owner decides
In a WhatsApp group, the person who created it decides who joins, who becomes an admin and whether to share an invite link. Nobody above them checks. Discretionary access control (DAC) follows the same idea: the owner of a resource, usually whoever created it, decides at their own discretion who else may use it. When Rohan creates a document on the cloud drive and shares it with two colleagues, he is using DAC. Most personal computers and file-sharing tools work this way by default.
DAC is flexible and needs no central team, which is why people like it. Its weakness is that security then depends on the judgment of every single owner. A rushed employee picks "anyone with the link can view" on a file of customer addresses, and the link gets forwarded outside the company. Nobody approved it, and nobody may notice. The stricter alternative, mandatory access control, takes the choice away from owners entirely: a central authority labels data (for example "Confidential") and the system enforces the rules no matter what the owner wants, the way a military office handles secret files.
Real organisations mix them: roles for the main systems, lists stored on each folder, and owner sharing for everyday documents, watched with regular reviews.
Telling the models apart in practice
At Tulsi Health all three models are in use at once. The MedLedger billing software has fixed roles (cashier, pharmacist, store manager), so it is role-based. The shared drive stores a list on every folder, so it uses ACLs. Staff documents on the cloud drive are shared by their creators, so that is discretionary. Knowing which model is in use tells you where to look when something goes wrong: a bad role definition, a stale name on a list, or an owner who shared too widely.
Sort each situation below by the model it describes. Look for the clue: is access coming from a job title, from a list stored on the thing itself, or from the owner's personal choice?