Chapter 32 — Identity and access management: interdisciplinary interfaces

Lesson map

Lesson 32 published. Map, example, EX094.

flowchart TD
  N0["Learning outcomes"]
  N1["32.1 Working with HR"]
  N2["32.2 Finance and legal"]
  N3["32.3 Speaking across disciplines"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX094"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["32.1 Working with HR"]
  N2["32.2 Finance and legal"]
  N3["32.3 Speaking across disciplines"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX094"]

[Learning outcomes]
    |
    v
[32.1 Working with HR]
    |
    v
[32.2 Finance and legal]
    |
    v
[32.3 Speaking across disciplines]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX094]

Learning outcomes

You will (1) work with HR, finance and legal colleagues; (2) align identity with data protection duties; (3) communicate across disciplines.

32.1 Working with HR

HR is the source of truth for joiners, movers and leavers, so Elena works closely with the HR officer. She explains why timely, accurate dates matter and agrees simple rules: leaving dates are entered as soon as resignation is accepted, team moves are entered before the move date, and corrections are flagged. HR in turn asks for a monthly list of accounts without HR matches, which helps them find records they forgot to update. Each discipline benefits from the other's information.

32.2 Finance and legal

Finance cares about separation of duties and audit evidence; legal cares about data protection and contracts with suppliers. Elena meets both. Finance agrees the second approval for new suppliers and asks for a yearly list of finance access for auditors. Legal reviews her data handling and confirms that sign-in logs may be kept for a year for security purposes, documented in Greenhill's records of processing. Each discussion is recorded with decisions and owners. Follow-up meetings are scheduled every six months to keep the arrangements current and to review any new systems.

32.3 Speaking across disciplines

Each discipline uses different words. HR says starters and leavers; IT says provisioning and deprovisioning; finance says segregation of duties. Elena keeps a short glossary and uses the listener's terms. She frames identity work in each group's concerns: for HR, fewer chases from IT; for finance, cleaner audits; for legal, demonstrable compliance. Speaking others' language turns identity from an IT project into shared work that colleagues support. She also checks understanding by asking colleagues to explain decisions back in their own words, which quickly reveals misunderstandings before they cause problems in practice.

Worked example

HR agrees timely date rules, finance agrees second supplier approval and yearly access lists, and legal confirms one-year log retention.

Synthetic case. Colleagues and agreements are synthetic.

Errors and limits

Treating identity as purely an IT project leaves HR, finance and legal unaware of their part.

Exercises

• EX094 — HR benefit. What does HR receive from the identity work?
  Show marking criteria

  Rubric: 3 = monthly list of accounts without HR match;; 2 = list;; 1 = vague;; 0 = none.
• EX095 — Legal decision. What did legal confirm about logs?
  Show marking criteria

  Rubric: 3 = one-year retention for security, documented;; 2 = one year;; 1 = forever;; 0 = none.
• EX096 — Glossary purpose. Why does Elena keep a glossary?
  Show marking criteria

  Rubric: 3 = different disciplines use different terms;; 2 = terms;; 1 = exam;; 0 = none.

Synthesis

Working with HR, finance and legal, and speaking their language, makes identity a shared responsibility.

Continue studying — chapter 32 of 40

← Chapter 31 (draft) · Course chapter index · Chapter 33 (draft) →