Chapter 32 — Cloud and container security: interdisciplinary interfaces
Lesson map
Lesson 32 published. Map, example, EX094.
flowchart TD
N0["Learning outcomes"]
N1["32.1 Legal and privacy"]
N2["32.2 Finance"]
N3["32.3 Teaching staff"]
N4["32.4 Students"]
N5["32.5 Translating"]
N6["32.6 Decisions"]
N7["Governance group"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX094"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["32.1 Legal and privacy"]
N2["32.2 Finance"]
N3["32.3 Teaching staff"]
N4["32.4 Students"]
N5["32.5 Translating"]
N6["32.6 Decisions"]
N7["Governance group"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX094"]
[Learning outcomes]
|
v
[32.1 Legal and privacy]
|
v
[32.2 Finance]
|
v
[32.3 Teaching staff]
|
v
[32.4 Students]
|
v
[32.5 Translating]
|
v
[32.6 Decisions]
|
v
[Governance group]
|
v
[Worked example] --> [Exercise EX094]
Learning outcomes
You will (1) work with law, finance, teaching staff and students on cloud security decisions; (2) translate between disciplines; (3) balance competing needs.
32.1 Legal and privacy
The data protection officer needs to know where student data is stored and how breaches would be detected. Samuel provides the data map and logging coverage.
The data map shows where each kind of student data lives and in which region; logging coverage shows whether a breach in each place would be noticed. With both, the DPO can judge whether Westmere could meet its notification duties. After the opening case, logging coverage was the figure the DPO asked about first.
32.2 Finance
Cloud costs are visible per account. Security controls such as logging have costs; Samuel estimates log storage cost and shows retention choices that balance cost and evidence.
Longer log retention costs more, but too short a period may leave investigations without evidence. Samuel's estimate showed that keeping audit logs for a year cost little compared with StudyHub's overall cloud bill, while application logs were the larger cost. That supported the existing retention rules and helped finance see logging as a known, modest expense.
32.3 Teaching staff
Lecturers want research sandboxes with freedom to experiment. Guardrails protect against public data exposure without blocking experiments.
Lecturers worried that guardrails would stop experiments in the research sandbox. In practice, the main guardrails block public storage and disabled logging, which few experiments need. Where an experiment does need an exception, the documented route allows it with a time limit, so research continues without opening permanent gaps. Samuel met two lecturers who ran sandbox projects to explain the guardrails and listen to their needs. One asked for a larger machine type that the guardrails had blocked by region, and the governance group approved a time-limited exception.
32.4 Students
Students expect StudyHub to be available during deadlines. Changes are scheduled away from submission peaks.
Submission deadlines cluster at the ends of terms, so the cloud team keeps a calendar of peaks and avoids changes in the days before them. Urgent security fixes are still applied, but with extra testing and a rollback ready. Students rarely notice security work when it is scheduled this way. The calendar is shared with the student union, whose representatives can flag events the team might not know about, such as a large resubmission window after a system outage. Planned maintenance notices go out a week ahead through StudyHub itself.
32.5 Translating
Each audience gets the same facts in its own terms: risk to students, legal duty, cost, teaching impact.
For the open registry, the DPO hears about potential exposure of personal data and the logging gap; finance hears about the small cost of central logging; lecturers hear that research images now go to a separate registry; students hear that StudyHub's images are private. The facts are the same in every version. Samuel checks each version with someone from that audience before it goes out, which twice caught terms he had assumed everyone knew.
32.6 Decisions
Conflicts, such as a research group wanting public datasets, go to a small governance group with a documented decision.
Sending conflicts to a group with members from each discipline means no single team decides alone on a trade-off that affects others. Documented decisions also prevent the same debate from recurring each term. The public-dataset request described below is an example of a decision that satisfied both research and security needs. Each decision record names the trade-off, the options, the choice, who agreed and when it will be reviewed. The records are kept with the governance group's papers, so later members can understand past choices.
Governance group
The governance group meets monthly with the cloud lead, the data protection officer, a finance representative, an academic and a student representative. It decides exceptions and trade-offs that cross disciplines, records each decision with its reasons, and reviews earlier decisions when circumstances change. Samuel attends as an observer and drafts the papers for two meetings, learning how to present technical options to non-technical members in plain terms with clear choices.
Plain language
Papers use plain language, with technical terms defined once.
Worked example
A research group asks for a public bucket to share an open dataset. The governance group approves a dedicated account for public data, with only the open dataset in it and a review of contents before publishing, keeping public data separate from everything else.
Synthetic case. People and decisions are synthetic.
Errors and limits
Translating risk across disciplines can lose nuance; check understanding.
Exercises
- EX094 — DPO needs. What does the DPO need? Rubric: 3 = data location and breach detection; 2 = partial; 1 = vague; 0 = none.
- EX095 — Scheduling. How are student needs respected? Rubric: 3 = changes away from deadline peaks; 2 = partial; 1 = vague; 0 = none.
- EX096 — Public dataset. How was the public dataset request handled? Rubric: 3 = dedicated public-data account with review; 2 = partial; 1 = vague; 0 = none.
Synthesis
Cloud security decisions involve many disciplines; translate carefully.
Continue studying — chapter 32 of 40
← Chapter 31 (draft) · Course chapter index · Chapter 33 (draft) →