Menu

Authorization

Part of the Security Fundamentals section of Coddy's Cybersecurity journey. Lesson 35 of 43.

Knowing someone's password, or having an admin account, does not automatically give you permission to read their messages. You still need the owner's approval for the work you plan to do. That permission is called authorization.

Lumen keeps requests for this kind of work in a queue. To list them, run:

seclab requests

Look for these lines:

id            date  from  subject      status
stock-audit   -     Lee   Count stock  open
private-mail  -     Ken   Read mail    open

Before approving a request, read who gave permission and what they allowed. For the stock count, run:

seclab requests stock-audit

Look for these lines:

Subject:  Count stock
Permission: Ava approved the stock count
Scope: Stock totals only; no staff mail

Ava approved counting stock. The Scope line explains the limits: stock totals are allowed, but staff mail is not. You can approve the stock count and deny the separate request to read private mail:

seclab request stock-audit approve

You should see:

Approved request stock-audit.
seclab request private-mail deny

You should see:

Denied request private-mail.

These commands record your decisions. They do not carry out the requested work themselves.

challenge icon

Challenge

Easy

Ticket from Sam, IT lead

Three requests are waiting: read someone's mailbox, send a summary to an insurer, and test a personal account. Read who owns the information, who gave permission and what work they approved. Approve only the authorized request and deny the others. Leave all accounts and group memberships unchanged.

Try it yourself

Terminal

All lessons in Security Fundamentals