◇ OpenCyber Academy
Technologist · Chapter 6 · English

Chapter 6 — Operating systems and virtualization

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

Chapter 6 — Operating systems and virtualization

Lesson map

Lesson 06 published. Map, example, EX016.

flowchart TD
  N0["Learning outcomes"]
  N1["6.1 Accounts and locks"]
  N2["6.2 Safe testing"]
  N3["6.3 Fewer prompts"]
  N4["Lab — Prompts during opening hours before and after"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX016"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["6.1 Accounts and locks"]
  N2["6.2 Safe testing"]
  N3["6.3 Fewer prompts"]
  N4["Lab — Prompts during opening hours before and after"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX016"]

[Learning outcomes]
    |
    v
[6.1 Accounts and locks]
    |
    v
[6.2 Safe testing]
    |
    v
[6.3 Fewer prompts]
    |
    v
[Lab — Prompts during opening hours before and after]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX016]

Learning outcomes

You will (1) configure accounts and screen locks to suit clinic work; (2) use virtual machines for safe testing; (3) reduce security prompts that interrupt patient care.

6.1 Accounts and locks

Lucas reviews reception computer settings. Shared accounts are used at reception, and screens lock after fifteen minutes with a long password. He proposes named accounts with quick badge unlock, so staff can lock screens whenever they step away and return in seconds. The screen lock time drops to three minutes because unlocking becomes fast. Making the secure action quick allows a stricter setting to be accepted, which shows how usability and security can support each other. The practice manager agrees to a trial.

6.2 Safe testing

Before changing clinic computers, Lucas tests settings in virtual machines on a lab computer. A virtual machine is a software computer that can be reset to a clean state. He tests badge unlock software, screen lock timings and update schedules without risking real patient systems. Virtual machines also allow him to view suspicious attachments forwarded for analysis safely, without opening them on staff computers, under the IT contractor's supervision. He records every test result in a simple log, including settings that failed, so the IT contractor can repeat the tests later on other machines.

6.3 Fewer prompts

Reception computers show update prompts during clinic hours. Lucas configures updates to install at night when clinics are closed and suppresses non-urgent prompts during opening hours. He counts prompts before and after on a test machine over a simulated week. Fewer interruptions reduce the chance that staff click through prompts without reading them, which Herley (2009) noted is a rational response to frequent, low-value warnings. Urgent security updates can still prompt during the day if the contractor decides they cannot wait, but such cases are expected to be rare and are logged when they happen.

Lab — Prompts during opening hours before and after

# Prompts during opening hours on a test machine over a simulated week (synthetic).
before = {"update restart": 12, "update available": 8, "other": 3}
after = {"update restart": 0, "update available": 0, "other": 3}
print("before:", sum(before.values()), "after:", sum(after.values()))

Run with python3 lab_prompts.py. Verified output:

before: 23 after: 3

Worked example

Lucas proposes named accounts with badge unlock and a shorter lock time, tests in virtual machines and moves updates to night.

Synthetic case. Settings are synthetic; Herley (2009) is real.

Errors and limits

Badge readers cost money. Night updates need computers left on.

Exercises

Synthesis

Operating system settings can make secure actions fast and reduce interrupting prompts.

Continue studying — chapter 06 of 30

← Chapter 05 (draft) · Course chapter index · Chapter 07 (draft) →