Chapter 5 — Security literacy | Technologist Security architecture and engineering

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 5 — Security literacy

Lesson map

Lesson 05 published. Map, example, EX013.

flowchart TD
  N0["Learning outcomes"]
  N1["5.1 Core terms"]
  N2["5.2 Common attacks"]
  N3["5.3 Talking to depot staff"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX013"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["5.1 Core terms"]
  N2["5.2 Common attacks"]
  N3["5.3 Talking to depot staff"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX013"]

[Learning outcomes]
    |
    v
[5.1 Core terms]
    |
    v
[5.2 Common attacks]
    |
    v
[5.3 Talking to depot staff]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX013]

Learning outcomes

You will (1) explain core security terms; (2) recognise common attacks on logistics firms; (3) communicate security simply to depot staff.

5.1 Core terms

Ruth teaches a shared vocabulary. Confidentiality keeps information from the wrong people; integrity keeps it correct; availability keeps it usable when needed. A vulnerability is a weakness; a threat is something that could exploit it; risk combines likelihood and impact. A control reduces risk. Tomás uses these terms when writing up his depot walk, so that Sam and the operations manager understand exactly what he means. Shared vocabulary avoids misunderstandings like calling every problem a hack. He adds a one-page glossary to the depot's shared folder so new staff can look terms up later.

5.2 Common attacks

Tomás studies attacks seen in logistics: fake delivery text messages that steal customer details, invoice fraud where criminals pose as fuel suppliers, ransomware that stops sorting and deliveries, and theft of handheld devices from vans. He links each to Brightwater's systems. Invoice fraud targets the finance office; ransomware would hit the tracking service and conveyor. Knowing the real attacks against a sector focuses training and controls better than generic lists, because staff recognise threats that resemble their own work. He checks each attack against the last year of help desk tickets to see which have already happened locally.

5.3 Talking to depot staff

Tomás prepares a ten-minute briefing for a shift change. He avoids jargon and uses three stories: a driver who reported a phishing text, a lost handheld that was wiped remotely and an invoice email with a changed bank account. Each ends with one action: report, report, call to check. Staff ask practical questions, such as whether personal phones are affected. Ruth reminds him that good security communication is short, concrete and respectful of people's time, and invites questions instead of blaming mistakes.

Worked example

Tomás defines core terms, links four logistics attacks to Brightwater and gives a ten-minute story-based briefing to depot staff.

Synthetic case. Stories and staff are synthetic.

Errors and limits

One briefing fades quickly. Stories must match real local risks to stay credible.

Exercises

EX013 — Risk definition. How is risk defined in the chapter? Rubric: 3 = likelihood combined with impact;; 2 = both;; 1 = threat only;; 0 = none.
EX014 — Finance target. Which attack targets Brightwater's finance office? Rubric: 3 = invoice fraud posing as a fuel supplier;; 2 = invoice fraud;; 1 = ransomware;; 0 = none.
EX015 — Briefing actions. What were the three briefing actions? Rubric: 3 = report, report, call to check;; 2 = two;; 1 = vague;; 0 = none.

Synthesis

Shared terms, sector-specific attacks and short practical briefings build security literacy.

Continue studying — chapter 05 of 30

← Chapter 04 (draft) · Course chapter index · Chapter 06 (draft) →