Digital Identity and the AAA Security Model
Identify the identifier, attributes and credentials of a digital identity, and diagnose whether a failure lies in authentication, authorization or accounting.
Who are you, what may you do, and what did you do?
On Riya Menon's first morning as an intern at the Tulsi Health head office in Kothrud, Neha Kulkarni creates an account for her called riya.menon. Riya types the password Neha gave her, changes it, and opens the folder of stock reports she will be working on. When she tries the folder of staff salaries, she sees "Access denied". The next morning Neha can look at a record that says Riya opened the stock report at 10:14. In those few minutes the computer system answered three questions: who are you, what are you allowed to do, and what did you actually do? Security people call these three answers authentication, authorization and accounting, and together they form the AAA security model.
Your identity inside a computer
A computer cannot see your face or recognise your voice the way a colleague can. It knows you only through a set of stored facts, and that set is your digital identity: the way a system represents a person, a device or a program. At Tulsi Health, Riya's digital identity is her account. It has three kinds of pieces, and it helps to keep them apart.
The identifier is the name the system uses to tell accounts apart, such as a username or an email address like riya.menon@tulsihealth.in. It must be unique, but it is not secret; colleagues write it in emails all the time. Attributes are facts attached to the identity: Riya's job title (intern), her location (Kothrud head office), her start date and the date her internship ends. Credentials are the proof she can show that she really is the owner of that identifier, such as a password, a code sent to her phone or her fingerprint. Your college ID card works the same way: the roll number is the identifier, the branch and year printed on it are attributes, and the photo that has to match your face is the proof.
The identifier names the account, the attributes describe the person behind it, and the credentials prove the claim. Mixing them up causes trouble, for example treating an email address as if it were a secret.
One person usually has many digital identities: Riya also has a college portal login, a personal email account and a UPI app on her phone, each with its own identifier and credentials. Devices and programs have identities too. Each of the 14 billing laptops has its own name on the network, and the Tulsi Health app's server program (the software on a computer in the cloud that answers the app's requests) has its own account for reaching the customer database, the organised store of customer records. An identity should belong to exactly one person or one thing. When the evening staff at a store all share one login called nashikstore, the system can no longer tell who did what, and every question that follows becomes harder to answer.
The AAA model on a train journey
Think about a long-distance train journey from Pune to Nashik. When the travelling ticket examiner (TTE) comes round, he checks that the name on your ticket matches your ID card: that is authentication. Your ticket allows you one particular berth in one particular coach, and not a seat in AC First Class: that is authorization. And the reservation chart he marks as he goes is a record of who travelled, in which berth, and when: that is accounting.
A train journey runs all three checks. The ID check proves who you are, the ticket decides where you may sit, and the chart keeps the record.
Computer systems run the same three checks in the same order, every time you log in. The order matters. A system cannot decide what you may do until it knows who you are, and a record of actions is only useful if each action is tied to a proven identity.
Typing a username only makes a claim. Authentication turns the claim into a proven identity, authorization uses that identity to allow or refuse actions, and accounting records the result.
Authentication: proving the claim
Anyone can type riya.menon into a login box. The identifier is only a claim, and authentication is the step that checks the claim by asking for credentials that only the real owner should have. If the password matches, the system accepts that this person is Riya and lets the session begin. A session is the period between logging in and logging out during which the system remembers who you are, so you do not have to prove it again on every click.
The weakness of authentication is that it checks the credential, not the person. If someone learns Riya's password, the system will greet them as Riya, with all of Riya's access. That is why so much of account security is about making credentials hard to steal and hard to guess, and about asking for more than one kind of proof for important accounts. A TTE who checks only that you are holding a ticket, and never looks at the ID card, can be fooled by anyone who picks up a lost ticket.
Authorization: deciding what you may do
Once the system knows who you are, authorization decides what you are allowed to do: which folders you can open, which records you can change, which buttons you can press. Riya can open the stock reports because her attributes say she is an intern working on stock, and she is refused the salary folder because nothing about her job needs it. Authentication and authorization are easy to confuse because they happen one after the other, but they answer different questions. Getting into the building is not the same as having a key to every room.
Authorization fails in two ways. If it is too strict, people cannot do their work and start sharing logins to get around it. If it is too generous, an ordinary mistake or a stolen password reaches far more than it should. The safest starting point is to give each identity only what its job needs.
Accounting: keeping the record
Accounting means recording what each identity did and when: logins, failed logins, files opened, records changed, settings altered. These records are called logs. The name comes from early networks that charged customers for the time they spent connected, so the record was literally used for billing. Today logs are used to investigate incidents, to spot unusual behaviour such as a login at 3 am from a city where nobody works, and to show auditors that rules are being followed.
Accounting is what makes accountability possible: each action can be traced to one person, who can be asked about it. It only works if the first two steps were done properly. A log full of entries from the shared nashikstore account says that something happened, but not who did it. Logs also need protecting, because an intruder who can quietly delete log entries can erase their own tracks.
Authentication happens once at the start of the session. Authorization happens on every request, and accounting writes down both the allowed and the refused attempts.
Sort the Tulsi Health moments below into the part of a digital identity or the AAA step they belong to. Ask yourself one question for each card: is it a fact about the person, a proof, a permission, or a record?
When one of the three breaks
Each step fails in its own way, and the fix depends on which step broke. Weak authentication lets an impostor in under someone else's name. Over-generous authorization lets a genuine user, or anyone using their account, reach far more than the job needs. Missing accounting means an incident happens and nobody can say who did it or when it started. Shared accounts quietly damage all three at once.
In each situation below, you are Neha looking at a problem at Tulsi Health. Decide which part of the AAA model failed, because that tells you where the fix belongs.