Chapter 18 — Logging and sign-in records | Technologist Identity and access management

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 18 published. Map, example, EX052.

flowchart TD
  N0["Learning outcomes"]
  N1["18.1 Useful logs"]
  N2["18.2 Retention"]
  N3["18.3 Protecting log data"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX052"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["18.1 Useful logs"]
  N2["18.2 Retention"]
  N3["18.3 Protecting log data"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX052"]

[Learning outcomes]
    |
    v
[18.1 Useful logs]
    |
    v
[18.2 Retention]
    |
    v
[18.3 Protecting log data]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX052]

Learning outcomes

You will (1) identify useful identity logs; (2) keep them for an agreed period; (3) protect personal data in logs.

18.1 Useful logs

The directory records sign-ins, failures, MFA prompts, admin changes and group membership changes. The practice management system records who opened or changed each animal record. Kai lists which logs exist, where they are kept and for how long. He finds the directory keeps sign-in logs for only 30 days, too short to investigate a problem noticed later, and plans to export them weekly to storage kept for a year. He also confirms which administrator changes are recorded in each system. The list becomes part of the documentation index.

18.2 Retention

Kai agrees a retention period with the practice manager: identity logs for one year, practice management access logs as the supplier keeps them, which is seven years for clinical records. He documents the reasons, linking them to investigation needs and record-keeping obligations. Keeping logs longer than needed raises privacy risks and storage costs, while keeping them too short leaves questions unanswerable, so a stated, reasoned period is the aim. Retention decisions are reviewed yearly with the practice manager. Old exports past the period are deleted on a schedule.

18.3 Protecting log data

Logs contain personal data such as names, locations and times. Kai restricts access to identity logs to IT and the practice manager, and records each time someone searches them. Exports are stored encrypted. He explains to staff in the privacy notice that sign-ins are logged for security. Treating logs as sensitive keeps the monitoring itself from becoming a privacy problem and supports trust between staff and management. Kai includes log access in the monthly admin review, so watchers are also watched. Encryption keys are held by IT, not by the storage supplier.

Worked example

Directory sign-in logs, kept 30 days by default, are exported weekly to encrypted storage kept for one year.

Synthetic case. Logs and periods are synthetic.

Errors and limits

Keeping logs only for a default short period leaves later questions unanswerable.

Exercises

EX052 — Default retention. How long did the directory keep sign-in logs by default?
Show marking criteria
Rubric: 3 = 30 days;; 2 = thirty;; 1 = one year;; 0 = none.
EX053 — Agreed period. What retention was agreed for identity logs?
Show marking criteria
Rubric: 3 = one year;; 2 = year;; 1 = forever;; 0 = none.
EX054 — Log protection. How is log access controlled?
Show marking criteria
Rubric: 3 = IT and practice manager only, searches recorded;; 2 = restricted;; 1 = public;; 0 = none.

Synthesis

Known, retained and protected logs let Fernhill answer access questions responsibly.

Continue studying — chapter 18 of 30

← Chapter 17 (draft) · Course chapter index · Chapter 19 (draft) →