Chapter 7 — Security architecture and engineering: organizational integration | Postgraduate 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 7 — Security architecture and engineering: organizational integration

Lesson map

Lesson 07 published. Map, example, EX031.

flowchart TD
  N0["Learning outcomes"]
  N1["7.1 Architecture and governance"]
  N2["7.2 A review board that works"]
  N3["7.3 Connecting to other functions"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX031"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["7.1 Architecture and governance"]
  N2["7.2 A review board that works"]
  N3["7.3 Connecting to other functions"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX031"]

[Learning outcomes]
    |
    v
[7.1 Architecture and governance]
    |
    v
[7.2 A review board that works]
    |
    v
[7.3 Connecting to other functions]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX031]

Learning outcomes

You will (1) embed architecture into Corvane's governance; (2) connect architecture to the management system; (3) design an architecture review board that works.

7.1 Architecture and governance

Priya's designs only last if they become part of how Corvane runs. She links architecture to the information security management system required by ISO/IEC 27001:2022: risk assessment, statement of applicability, internal audit and management review. Each architecture decision record now references the risks it treats and the controls it implements. When the internal auditor tests a control, they can trace it back to a design decision and its reasons, closing the gap between architecture documents and audit evidence. This also shortens audit preparation.

7.2 A review board that works

Corvane's old architecture review board met monthly, reviewed every project and became a bottleneck that teams avoided. Priya redesigns it. Projects answer a short triage form; only those that add suppliers, patient data flows, clinical device connections or internet exposure come to the board. The board meets weekly for thirty minutes, publishes decisions within two days and uses a standard template. Within a quarter, more projects come forward voluntarily because the process is quick and predictable rather than a source of delay.

7.3 Connecting to other functions

Priya maps where architecture touches procurement, clinical engineering, privacy and finance. Procurement adds security questions to tenders; clinical engineering joins the board for device projects; the privacy officer reviews any new patient data flow; finance sees architecture costs early. She uses the control families of NIST SP 800-53 Rev. 5 to make sure no area is left without an owner. Integration works when each function sees architecture as helping its own goals, not as an extra approval imposed from outside. Each interface has a named contact.

Worked example

Priya links decision records to ISO/IEC 27001 processes, redesigns the review board with triage and weekly short meetings, and maps four interfaces with owners.

Synthetic case. Corvane's governance is synthetic; ISO/IEC 27001:2022 and SP 800-53 Rev. 5 are real.

Errors and limits

Triage can miss risky projects that answer no. Fast boards can become rubber stamps.

Exercises

EX031 — Audit traceability. How did linking records to the ISMS help auditors? Rubric: 3 = they can trace a control back to its design decision;; 2 = traceability;; 1 = vague;; 0 = none.
EX032 — Old board problem. What was wrong with the old review board? Rubric: 3 = it reviewed everything monthly and became a bottleneck;; 2 = bottleneck;; 1 = too fast;; 0 = none.
EX033 — Triage triggers. Which project features trigger board review? Rubric: 3 = suppliers, patient data flows, clinical devices, internet exposure;; 2 = two;; 1 = all projects;; 0 = none.
EX034 — Board effect. What changed within a quarter of the redesign? Rubric: 3 = more projects came forward voluntarily;; 2 = voluntary;; 1 = vague;; 0 = none.
EX035 — Integration principle. When does integration with other functions work? Rubric: 3 = when each function sees architecture helping its own goals;; 2 = shared goals;; 1 = mandates;; 0 = none.

Synthesis

Architecture lasts when it is embedded in the management system and a fast, predictable review process.

Continue studying — chapter 07 of 12

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