Chapter 7 — Identity and access management: organizational integration
Lesson map
Lesson 07 published. Map, example, EX031.
flowchart TD
N0["Learning outcomes"]
N1["7.1 Change management"]
N2["7.2 HR and lifecycle"]
N3["7.3 Incident response"]
N4["7.4 Ownership and training"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5
N5 --> EX["Worked example"]
EX --> Q["Exercise EX031"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["7.1 Change management"]
N2["7.2 HR and lifecycle"]
N3["7.3 Incident response"]
N4["7.4 Ownership and training"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX031"]
[Learning outcomes]
|
v
[7.1 Change management]
|
v
[7.2 HR and lifecycle]
|
v
[7.3 Incident response]
|
v
[7.4 Ownership and training]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX031]
Learning outcomes
You will (1) integrate the privileged access design with change management, HR and incident response; (2) assign ownership; (3) train staff.
7.1 Change management
Just-in-time elevation works best when tied to change management. Marta links elevation requests to change tickets, so each request names the change it supports, and approved change windows define when standard requests are automatically approved. Emergency elevation outside windows needs a reason and is reviewed the next working day. This integration means privileged activity can be traced from the change that justified it to the actions taken, which helps both auditors and engineers investigating problems after a change. Auditors can follow this trail easily.
7.2 HR and lifecycle
Administrator status must follow employment. When HR records that an administrator moves role or leaves, their administrator account is disabled and their keys revoked the same day. New administrators receive access only after their manager's approval and completion of a short training module. Marta works with HR to add administrator status to the leaver checklist and to the six-monthly access review, so privileged accounts are never left behind when the people who held them have gone. The training module takes about thirty minutes.
7.3 Incident response
The incident response plan is updated so that suspected misuse of privileged access has a clear procedure: revoke active elevations, disable the account, preserve logs, inform the security lead and investigate. Emergency accounts in the vault are documented for use if normal administrator access fails during an incident. Marta runs a tabletop exercise with the IT team, discovering that nobody knew the vault's emergency release procedure at night. The procedure is simplified and printed in the incident pack. The exercise is repeated yearly.
7.4 Ownership and training
Each part of the design has an owner: the IT manager owns administrator policy, the security lead owns monitoring, HR owns lifecycle triggers and the operations director approves change windows. Marta runs short training for administrators covering why the changes matter, how to request elevation, what is monitored and what to do if a key is lost. Training is practical and brief, and administrators leave with a one-page guide. Clear ownership and training keep the design working after the project ends.
Worked example
Elevation links to change tickets, HR triggers disable administrator accounts on the same day, a tabletop exercise simplifies night-time vault release, and four owners are named.
Synthetic case. Processes, owners and exercises are synthetic.
Errors and limits
Introducing just-in-time elevation without linking it to change management loses the reason behind each elevation.
Exercises
- EX031 — Change link. How is elevation linked to change management? Rubric: 3 = requests name the change ticket; windows auto-approve;; 2 = tickets;; 1 = vague;; 0 = none.
- EX032 — Leaver admin. When are a leaving administrator's account and keys removed? Rubric: 3 = same day as HR records it;; 2 = same day;; 1 = month;; 0 = none.
- EX033 — Tabletop finding. What did the tabletop exercise reveal? Rubric: 3 = nobody knew night-time vault release procedure;; 2 = vault;; 1 = vague;; 0 = none.
- EX034 — Owners named. Name two owners in the design. Rubric: 3 = IT manager, security lead, HR, operations director (two);; 2 = one;; 1 = vague;; 0 = none.
- EX035 — Training contents. Name two topics in administrator training. Rubric: 3 = why, how to request, what is monitored, lost keys (two);; 2 = one;; 1 = vague;; 0 = none.
Synthesis
Linking privileged access to change, HR, incident response and clear owners embeds it in how the organisation works.
Continue studying — chapter 07 of 12
← Chapter 06 (draft) · Course chapter index · Chapter 08 (draft) →