Chapter 36 — Field or community practice

Chapter 36 — Field or community practice

Lesson map

Lesson 36 published. Map, example, EX106.

flowchart TD
  N0["Learning outcomes"]
  N1["36.1 A community placement"]
  N2["36.2 Adapting the advice"]
  N3["36.3 Reflection"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX106"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["36.1 A community placement"]
  N2["36.2 Adapting the advice"]
  N3["36.3 Reflection"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX106"]

[Learning outcomes]
    |
    v
[36.1 A community placement]
    |
    v
[36.2 Adapting the advice]
    |
    v
[36.3 Reflection]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX106]

Learning outcomes

You will (1) apply security architecture skills in a community setting; (2) adapt advice for organisations without IT staff; (3) reflect on what transfers.

36.1 A community placement

As part of field practice, Lucas volunteers for four weeks with a local food bank that uses donated laptops, a free email service and a spreadsheet of client households. There is no IT staff, and volunteers change weekly. He applies the same thinking as at Fernway, but the constraints are harsher: no budget, little time and users with mixed digital confidence. He starts by listening to how volunteers work, since any advice that adds steps to a busy distribution shift will be ignored.

36.2 Adapting the advice

Lucas identifies three priorities: the client spreadsheet is shared by link with anyone, the shared volunteer account has no second factor, and laptops are not encrypted. He fixes sharing to named accounts, turns on the email provider's free second factor for the coordinator and moves volunteers to individual free accounts, and enables built-in disk encryption. He writes a one-page guide with pictures. He drops a planned password manager rollout because volunteers would not sustain it. Advice for small community groups must be minimal, free and easy to keep doing.

36.3 Reflection

In his reflective log, Lucas notes what transferred from Fernway: data classification, least privilege and asking who would notice a problem. What did not transfer: change forms, metrics dashboards and supplier questionnaires, which assume staff time. He realises that architecture is about fitting protection to the organisation, and that a simple design that volunteers follow beats a complete design they abandon. The food bank coordinator later reports that the guide is pinned by the distribution desk and new volunteers read it on their first day.

Worked example

Lucas adapts architecture advice for a food bank, fixes three priorities with free tools and reflects on what transfers from a retailer.

Synthetic case. The food bank is synthetic.

Errors and limits

Volunteer turnover erodes changes. Free services can change terms.

Exercises

• EX106 — First step. Why did Lucas start by listening to volunteers? Rubric: 3 = advice that adds steps to busy shifts is ignored;; 2 = fit;; 1 = vague;; 0 = none.
• EX107 — Dropped plan. What did Lucas drop and why? Rubric: 3 = a password manager rollout volunteers would not sustain;; 2 = sustain;; 1 = cost;; 0 = none.
• EX108 — What transferred. Name two things that transferred from Fernway. Rubric: 3 = classification, least privilege, asking who would notice;; 2 = one;; 1 = vague;; 0 = none.

Synthesis

Security architecture in community settings means minimal, free measures that volunteers will actually keep doing.

Continue studying — chapter 36 of 40

← Chapter 35 (draft) · Course chapter index · Chapter 37 (draft) →