All courses / The Transformed Security Architect / Module 2 / Chapter 9
Learning objectives
After the lesson the participant can:
- Explain which three connections the architect owns in the catalogue and where that ownership stops.
- Write a complete control entry with a falsifiable objective, an implemented_by path, a test, evidence with a fail condition and reviewed mappings.
- Classify controls as verified, declared or failed by rule and open a finding for every status other than verified.
- Describe how a catalogue as code changes the work of the auditor while preserving independence.
Key concepts
- Falsifiable objective
- One sentence that a test can disprove, such as: an agent cannot call a tool that its manifest does not name. A sentence such as 'access is appropriately managed' cannot be tested and so cannot be verified.
- Assure once, comply many
- A control is written once and mapped to every obligation it serves, each mapping with its relation, reviewer and date. Written four times it would drift into four controls; mapped four times it is tested once and the result serves every column.
- Fail condition and maximum age
- The fail condition names the observation that would prove failure, since a query that describes success invites confirmation. The maximum age turns a control declared the day its evidence expires, which also catches a collector that silently stops.
- Verified, declared, failed
- Verified: test passed within cadence and machine-generated evidence within its maximum age. Declared: no recent passing test, stale evidence or attestation only. Failed: the last test failed or the evidence query returned its fail condition. There is no amber.
- Shared dependency
- Two controls that depend on the same tool gateway or model provider fail together, so the coverage view counts controls with a common dependency as one. Counting controls is not the same as counting protection.
Interactive exercises
Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.
Interactive exercise 1 · Sort
Verified, declared or failed
Apply the chapter's classification rule to each control and sort it under its status.
Interactive exercise 2 · Scenario
A status typed by hand
Apply the chapter's rule on who sets a control's status.
Teaching plan
| 15 min | Lecture on why the catalogue is the architect's artefact and where the ownership stops, using Figure 9.1 and the fields of a control entry. |
| 15 min | Read CTRL-AGT-002 together: participants locate the objective, the fail condition, the maximum ages, the mappings and the pending-review mappings owned by local security officers. |
| 15 min | Classify Nordvik's first ten entries before revealing the statuses, then discuss why supplier-held controls start as declared and what the failed entry is used for. |
| 35 min | Exercise: participants convert three spreadsheet rows into control entries and derive a status for each, opening findings where needed. |
| 10 min | Debrief on the architect and the auditor: read-only access, tests that can be re-run and reasoning written in pull requests. |
Discussion
- A declared entry is a known gap, not an error. How would your management review react to a first report in which most controls are declared, and how would you prepare it?
- The chapter says evidence a system produces about itself is weaker than evidence from outside it. Which of your current evidence sources would fail that test?
- Hansa brings the United Kingdom and Swiss mappings into the catalogue as entries the local security officers own. Why does the chapter keep authorship with them?
Written exercise
Exercise · 35 minutes
From spreadsheet row to control entry
Take three rows from your organisation's ISO/IEC 27001 Annex A spreadsheet or statement of applicability, or three supplier-held controls of the kind in Nordvik Region's catalogue. Remember that a row is a requirement and an entry is a control. For each, write an entry with a stable identifier, one falsifiable objective, the owner and the architect, the threats it answers, an implemented_by path to a real configuration, policy rule or contract clause, a test with its cadence, an evidence source with a fail condition and maximum age, and the obligations it maps to with relation and reviewer. Apply the classification rule to each and open a dated finding with an owner and a re-test for every declared or failed control.
Deliverable: Three control entries in the form of CTRL-AGT-002, each with a derived status, and a findings list for every entry that is not verified.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
Who or what sets the status of a control in the chapter's design?
Show the answer
A. A rule applied in the pipeline, owned by the architect and reviewed by the CISO
A rule owned by the architect and reviewed by the CISO applies the status in the pipeline, so no control owner can type it in. The evidence-collection agent refreshes evidence but cannot alter the rule, the tests or the exceptions.In the first report from Nordvik's catalogue, why is CTRL-LOG-001 classified as failed?
Show the answer
C. A replay found the managed security service provider's detections cover only some Region scenarios
The replay found that the managed security service provider's detections cover only some of the Region's scenarios, so the control did not work as its objective states. The finding goes to the CISO for the contract discussion.What does the coverage view say about CTRL-AGT-002 enforcing three agents' permission manifests through the same tool gateway?
Show the answer
B. That the gateway is one point of failure, leading to a second independent control or an accepted risk
Each agent has its own manifest, but the same tool gateway enforces all three, which is one point of failure. The finding leads to a second, independent control or to an accepted risk with an expiring exception.