Project & Development
Privileged Account Management: Inventory, Least Privilege, Temporary Access, and Log Checks
Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
Manage privileged accounts by inventorying owners and last use, then moving to least privilege with separate everyday accounts, time-limited grants, and monthly log reviews. You finish with a table of who holds admin rights and why on servers and business systems, cloud, and employee devices, plus a cutting order, grant steps, and a monthly-check owner. A gap analysis (As-Is / To-Be) and a strength × frequency matrix decide whether to remove, separate, or time-limit each account. Common pitfalls (everyone admin on their own PC, leftover leaver and ex-contractor accounts, shared admin passwords, unchecked emergency accounts, unread logs) each get what happens, how to check, and how to prevent it. To start, copy the names of admin-role accounts from the cloud console and check each one's last sign-in date. The 4 whiteboard pages cover inventory, usage, cutting order, and operation; the task board has 5 columns and 4 parent tasks of 3 subtasks each (16 tasks).
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Privileged Account Management Board
How to use (4 pages): ① On page 1, write the purpose and list the admin accounts (boards①–⑤) → ② On page 2, tabulate how they are used and check the pitfalls (boards⑥–⑨) → ③ On page 3, write the gap and decide what to cut first (boards⑩–⑭) → ④ On page 4, set the grant steps and monthly checks (boards⑮–⑰)
1/4 Take stock of privileges
① Why and Where to Review (start here)
- Why you are reviewing e.g. Too many people hold admin rights, and nobody can explain who can do what
- Scope e.g. Servers, business systems, cloud admin consoles, employee PCs
- Period and owners e.g. One month. IT leads the work and the general affairs manager approves
② Table of Accounts with Admin Rights (one per row)
| Owner | Used for | Last used | Checked where | |
|---|---|---|---|---|
| Account 1 | e.g. The IT owner themselves | e.g. Whole-cloud settings | e.g. 3 weeks ago | e.g. Last sign-in in the cloud console |
| Account 2 | e.g. Maintenance contractor (contact unknown) | e.g. Server maintenance | e.g. More than 6 months ago | e.g. Server account list |
| Account 3 | e.g. Accounting section chief | e.g. Registering users in the accounting system | e.g. Last week | e.g. Business system admin console |
| Account 4 | e.g. Owner unknown | e.g. Unknown | e.g. No record | e.g. Device management console |
③ Servers and Business Systems
- e.g. Server admin account (maintenance contractor)
- e.g. Accounting system admin (accounting section chief)
- Move from the table in ②, and keep unknown owners too
④ Cloud
- e.g. Whole-cloud admin (IT owner)
- e.g. Email admins (two people in general affairs)
- Write whole-cloud admins and partial admins separately
⑤ Employee Devices
- e.g. Admin on each PC (the employee)
- e.g. Admin of the device management system (IT owner)
- Count devices from the device management console
2/4 Check how they are used
⑥ How each account in ② is used
| How often | What work | Shared or not | Logged or not | |
|---|---|---|---|---|
| Account 1 | e.g. 1–2 times a month | e.g. Adding users and changing settings | e.g. Only the owner | e.g. Admin actions are logged |
| Account 2 | e.g. A few times a year | e.g. Server update work | e.g. Shared by 3 contractor staff | e.g. Logged, but nobody reads it |
| Account 3 | e.g. Weekly | e.g. Registering new employees | e.g. Only the owner | e.g. Logged in the business system |
| Account 4 | e.g. Unknown | e.g. Unknown | e.g. Unknown | e.g. No record → ask for the owner |
⑦ Pitfall: everyone is admin on their own device
- What happens e.g. Anyone can install software, and software and settings the company does not know about pile up. Damage to one device spreads easily
- How to check e.g. In the device management console, count the people in the admin group
- How to prevent e.g. Use a standard user account day to day, and have IT install software on request
- Check result e.g. Applies → go to ⑫ or ⑬
⑧ Pitfall: admin accounts of leavers and contractors
- What happens e.g. Admin accounts of people who left or contractors whose contracts ended stay active
- How to check e.g. Compare the owners in ② with HR's list of leavers and the list of contractor agreements
- How to prevent e.g. Add "remove admin rights" to the checklists for leaving and for contract end
- Check result e.g. One account of a former maintenance contractor whose contract ended applies → ⑫
⑨ Pitfall: shared admin password
- What happens e.g. The logs cannot show who did what. People who left still know the password
- How to check e.g. In ⑥, count the rows marked as shared
- How to prevent e.g. Give each person their own account and sign in with an authenticator app (multi-factor) or a passkey (SMS codes are better than nothing but weaker than these)
- Check result e.g. Shared by 3 contractor staff → ⑬. Until it is split, change the password whenever the person in charge changes
3/4 Decide what to cut first
⑩ From the results of ⑥ to ⑨, write the gap between now and the target
- As-Is Current state e.g. 12 admins, 3 of them shared accounts and 2 with unknown owners
- Gap and issues e.g. Admin rights are used for everyday work too. No process for removing them
- To-Be Target e.g. Admin rights are used only by people who need them, on the days they need them, within a set scope
⑪ Strength of rights × how often used (place the accounts from ⑥)
Vertical axis: Strength of rights (bottom = weak, top = strong) / Horizontal axis: How often used (left = rarely, right = often)
- Strong × rare Candidates for limited-time grants. e.g. Whole-cloud admin, removed normally and granted only on the day of use (emergency accounts are not time-limited and are handled in ⑰)
- Strong × often Candidates to separate. e.g. Server management, with everyday and admin accounts split and the scope narrowed
- Weak × rare Candidates to remove. e.g. A business system admin who has not used it even once in the period you set
- Weak × often Keep, with a narrower role. e.g. A helpdesk role that can only reset passwords
⑫ Remove
- e.g. Accounts with unknown owners. If no owner turns up, disable them and watch what happens
- e.g. Accounts of contractors whose contracts ended
- Write the removal date and who confirms it is done
⑬ Separate
- e.g. Everyday email and work on a regular account, admin tasks only on an admin account
- e.g. Split a contractor's shared account into one per person
- Write how to disable the old account after the split
⑭ Grant for a Limited Time
- e.g. Grant whole-cloud admin only on the day of the work and remove it afterwards
- e.g. IT grants it temporarily only while installing software on a device
- Decide the steps in ⑮
4/4 Run the process
⑮ Steps to grant the rights in ⑭ only when needed (5 steps)
- Request What work, over what scope, until when e.g. Server update work. One server only, within the working hours that day
- Approve Someone other than the requester approves e.g. The IT manager approves after checking the work and the deadline
- Grant with an expiry Grant rights for the agreed scope and period e.g. Grant just before the work starts and fix the end time
- Work and keep a record Record what you did e.g. Write what you did and the result in the agreed place
- Remove and confirm Remove them at the deadline and check that they are gone e.g. Next morning, confirm they are gone from the admin list
⑯ Monthly Log Check (who checks and what to look at)
| What to look at | Who checks | What to do when something looks wrong | |
|---|---|---|---|
| Grant and removal logs | e.g. Whether the requests in ⑮ match the grants actually made | e.g. Someone who neither requested nor approved | e.g. Ask the requester about any mismatch |
| Admin sign-ins | e.g. Admin sign-ins on days with no request | e.g. General affairs manager (someone without admin rights) | e.g. Ask the person, and disable the account if they do not recognize it |
| Setting changes | e.g. Records of changed security settings | e.g. IT manager | e.g. Compare with requests, and for a change with no reason ask who made it and decide whether to revert it |
| Account list | e.g. Admins added since last month | e.g. General affairs manager | e.g. Add to the table in ② or move to ⑫ |
⑰ Emergency Accounts and the Last 2 Pitfalls
- How emergency accounts are handled e.g. Create the minimum number rather than just one, for when normal sign-in fails. Protect them with strong authentication separate from regular admins (such as a passkey) and keep the credentials in a locked place only designated people can open. Record every use and report it to the person in charge
- Pitfall: emergency accounts are not checked What happens: they will not work when needed, or someone uses them every day How to check: e.g. Each month, review the emergency account sign-in records in the table in ⑯. Check the seal on the storage place on a set inspection day How to prevent: Set an inspection day and an owner, and add a row to the table in ⑯. On that day, also check the list of people allowed to use them and whether sign-in actually works
- Pitfall: logs are kept but nobody reads them What happens: even if something odd happens, nobody can spot it afterwards How to check: Are the date of the check in ⑯ and the name of the reviewer recorded? How to prevent: Put the monthly check in the owner's calendar and leave one line on what was found
Task board contents
Not started 16 items
Audit privileges
On page 1 of the board, set the purpose and scope, then turn every account with admin rights into a table of owner, use, and last-used date. That table feeds every later page. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.
Copy the admin list
The first thing to do. In the cloud admin console, open the list of admin roles, copy the account names into the table in ②, then add each last sign-in date from the user list or detail page (check the service's help for where to find it). One console takes about 15 minutes. Done when every admin in that console is copied.
Set goal and scope
On ①, write why you are reviewing, which systems and devices are in scope, and the period and owners. Fixing the scope keeps the inventory from never ending.
Sort into 3 frames
Move the accounts in the table in ② into the frames ③ to ⑤, which are servers and business systems, cloud, and employee devices. Write "owner unknown" for accounts nobody can name and keep them.
Check actual usage
On page 2, check how the accounts in the page 1 table are used and find which pitfalls apply. What you find here becomes what you cut on page 3.
Fill usage table
On ⑥, write how often each account from ② is used, for what work, whether it is shared, and whether it is logged. Check against the console's last sign-in and work logs, and do not fill it from memory.
Check the pitfalls
In the three frames ⑦ to ⑨, check for admins on employee devices, accounts of leavers and contractors, and shared passwords, and write the result in the last note of each frame.
Find unknown owners
Ask department heads and maintenance contractors who owns each "owner unknown" account and what it is for. Until you have an answer, write "unknown" in its row on ⑥.
Prioritize cuts
On page 3, use the page 2 results to write the gap between now and the target, then decide which accounts to cut back first and how. This needs the most judgment, so work with the person in charge.
Write As-Is, To-Be
On ⑩, write the current state, the gap, and the target, one each. The target is done when it says who, only when, and over what scope.
Sort by power × use
Place each account from ⑥ in one of the four sections of ⑪. When unsure, put it on the stronger-privilege side.
Assign how to cut
Move the accounts sorted in ⑪ into the frames ⑫ to ⑭ (remove, separate, grant for a limited time) and write a due date for each.
Run the process
On page 4, decide the procedure for granting rights only when needed, how to check the logs each month, and how to handle emergency accounts. Try what you decide for one month in the Trying the process column of the task board.
Define grant steps
On ⑮, write each of the 5 steps from request to removal and who handles it. Done once you have decided who approves.
Set monthly checks
On ⑯, write which logs to check each month, who checks, and what to do when something looks wrong, then set the date of the first check.
Define break-glass
On ⑰, write how emergency (break-glass) accounts are stored, checked, and reported after use, and decide the preventive step for the other two pitfalls.