Chapter 21 — Human factors and cyber policy: service integration
Lesson map
Lesson 21 published. Map, example, EX061.
flowchart TD
N0["Learning outcomes"]
N1["21.1 Reporting and response"]
N2["21.2 Finance and vendors"]
N3["21.3 Keeping it simple"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX061"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["21.1 Reporting and response"]
N2["21.2 Finance and vendors"]
N3["21.3 Keeping it simple"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX061"]
[Learning outcomes]
|
v
[21.1 Reporting and response]
|
v
[21.2 Finance and vendors]
|
v
[21.3 Keeping it simple]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX061]
Learning outcomes
You will (1) integrate reporting with incident response at a small organisation; (2) connect verification controls with finance and vendor management; (3) keep integration simple enough to sustain.
21.1 Reporting and response
Lucas links the reporting service to Brightwell's incident response plan. When triage confirms a malicious email that reached several clinics, the IT contractor removes it from all mailboxes, blocks the sender and checks whether anyone entered details on a linked page. If someone did, their account is reset and their security key checked. Staff who reported are thanked. The plan is two pages long and lists phone numbers, so that it can be followed quickly by anyone on duty, even outside normal working hours.
21.2 Finance and vendors
Lucas connects verification controls to finance and vendor management. The supplier list now records verified phone numbers and the name of the person who verified them. Vendors receive a letter explaining that Brightwell will always call back on known numbers before granting remote access or changing payment details, and asking them to inform Brightwell of any change in writing. Integration with vendors spreads the burden of verification and makes legitimate vendors partners in resisting impersonation rather than sources of friction. Most vendors reply within a month.
21.3 Keeping it simple
Lucas resists adding complexity. Brightwell has no security team, so every integration must be maintainable by the practice manager and the IT contractor. He uses existing systems wherever possible: the accounting system's hold feature, the email platform's report button and a shared spreadsheet of verified vendor numbers. He documents each link in one page. Marta reminds him that a simple system that keeps working is better than an elaborate one that fails when its designer leaves the placement. The documents are stored in one shared folder.
Worked example
Lucas links reporting to a two-page response plan, records verified vendor numbers, informs vendors of callback rules and keeps integrations simple.
Synthetic case. Integration is synthetic.
Errors and limits
Vendors may ignore letters. Spreadsheets drift.
Exercises
- EX061 — Response steps. What happens when a malicious email reached several clinics? Rubric: 3 = removed, sender blocked and clicks checked;; 2 = three steps;; 1 = vague;; 0 = none.
- EX062 — Vendor letter. What does the vendor letter explain? Rubric: 3 = Brightwell always calls back on known numbers;; 2 = callback;; 1 = vague;; 0 = none.
- EX063 — Maintainability. Who must be able to maintain integrations? Rubric: 3 = the practice manager and IT contractor;; 2 = small team;; 1 = a security team;; 0 = none.
Synthesis
Integration links reporting, response, finance and vendors in ways a small team can sustain.
Continue studying — chapter 21 of 30
← Chapter 20 (draft) · Course chapter index · Chapter 22 (draft) →