OpenCyber Academy
Bachelor's · Chapter 32 · English
Course code: OCA-099Chapter 32: OCA-099-C032

Chapter 32 — Security architecture and engineering: interdisciplinary interfaces

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 32 published. Map, example, EX094.

flowchart TD
  N0["Learning outcomes"]
  N1["32.1 Different languages"]
  N2["32.2 Working with legal and privacy"]
  N3["32.3 Resolving conflicts"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX094"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["32.1 Different languages"]
  N2["32.2 Working with legal and privacy"]
  N3["32.3 Resolving conflicts"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX094"]
[Learning outcomes]
    |
    v
[32.1 Different languages]
    |
    v
[32.2 Working with legal and privacy]
    |
    v
[32.3 Resolving conflicts]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX094]

Learning outcomes

You will (1) work with legal, finance and operations colleagues on security decisions; (2) translate security into each discipline's language; (3) resolve conflicting priorities.

32.1 Different languages

Lucas finds that each Fernway department hears security differently. The finance manager thinks in costs and losses; the operations manager thinks in throughput and staff time; the co-operative's legal adviser thinks in obligations and liability. When Lucas presented the access proxy in technical terms, nobody engaged. When he described it to finance as reducing the chance of payment fraud, to operations as removing the VPN step that slows store staff, and to legal as supporting data protection duties, each person saw a reason to support it.

32.2 Working with legal and privacy

The legal adviser asks whether the sign-in detection rule from chapter 30 is lawful under data protection rules, since it processes staff location data. Lucas and the adviser document the purpose, the data minimised to country level, the retention period and the staff notice, and they record a legitimate-interest assessment. ISO/IEC 27001:2022 expects such obligations to be identified and met. The work slows the trial by two weeks but makes it defensible. Lucas learns that early legal involvement is cheaper than redesign after an objection.

32.3 Resolving conflicts

Operations wants seasonal staff to start work within an hour of arrival; security wants accounts approved and trained first. Lucas brokers a compromise: seasonal accounts are pre-created with limited till rights, activated on arrival by a store manager, and expire at season end. Training is a five-minute video on the till. Both sides get most of what they need. He records the compromise as a design decision so that it is not reopened every season. Interdisciplinary work is mostly finding designs that serve several goals at once.

Worked example

Lucas translates the access proxy into finance, operations and legal terms, documents a lawful basis for detection and brokers a seasonal account compromise.

Synthetic case. Departments and decisions are synthetic; ISO/IEC 27001:2022 is real.

Errors and limits

Translation can oversell benefits. Compromises need review if conditions change.

Exercises

Synthesis

Security decisions succeed when translated into each discipline's language and designed to serve several goals at once.

Continue studying — chapter 32 of 40

← Chapter 31 (draft) · Course chapter index · Chapter 33 (draft) →

Worked answers

EX094. As reducing the chance of payment fraud.

EX095. The purpose, country-level data, retention, staff notice and a legitimate-interest assessment.

EX096. Pre-created limited till accounts activated by a manager on arrival and expiring at season end.