Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

AC 8.4: Permission and the audit trail

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

50 minutes

Who changed the sales column?

On Friday the shared sales table has a column of wrong numbers. Who changed it? An analyst? A manager? An old account?

If nobody can say, nobody can fix the cause.

The last two steps of the IAAA model solve this. One limits what a person may do. The other records what they did.

Key words

WordWhat it meansExample
AuthorisationMaking sure a logged-in user can only do what they are allowed to do.
Role-based accessAccess set by a person's job in the system.analyst
Access control listA list that says which users may do which actions on one resource. Short form: ACL.
ResourceA file, folder, printer or system that can be used.
AccountabilityAny action can be traced back to the user who did it.
Audit logA record of who did what, and when.
User activity monitoringWatching what users do in a system.
Least privilegeGiving each person only the access they need.
Shared accountOne login used by many people.

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can explain the last two steps of the IAAA model, with the techniques used and their benefits and drawbacks.

Starter: what you already know

Have a go

Starter: what you already know

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Authorisation decides what you may do

Authorisation comes after login. The system now knows who you are. It decides what you may do.

The aim: an authenticated user can only reach the resources and do the actions they are allowed to.

This follows least privilege. A viewer may read a table. Only its owner may delete it.

Role-based access and ACLs

Role-based access gives rights by the role. Everyone in the analyst role gets analyst rights. When someone changes job, you change their role.

An access control list is attached to one resource. It lists exactly which users may do which actions.

Roles are easier for many people. ACLs are finer for one file.

Worked example: roles and an ACL

WhoRole-based: any tableACL on customer_names
Viewer SamRead onlyNo entry: no access
Analyst AishaRead and writeRead and write
Analyst RajRead and writeRead only (set by the owner)
Owner LeeRead, write and deleteRead and write

The cells students fill in are left blank in this preview.

Accountability traces every action

Accountability means every action can be traced back to the person who did it.

It needs: unique logins (no shared accounts), audit logs that record who did what and when, and user activity monitoring that watches for odd behaviour.

Logs must be protected. If an attacker can delete the log, the trail is gone.

The lesson goes on

9 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.