OpenCyber Academy
Postgraduate · Chapter 9 · English
Course code: OCA-157Chapter 09: OCA-157-C009

Chapter 9 — Leadership and assurance

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 09 published. Map, example, EX041.

flowchart TD
  N0["Learning outcomes"]
  N1["9.1 Assurance language"]
  N2["9.2 Linter in CI"]
  N3["9.3 Leadership behaviours"]
  N4["9.4 Coaching refusal"]
  N5["9.5 Board education"]
  N6["9.6 Succession"]
  N7["9.7 Narrative"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
  N7 --> EX["Worked example"]
  EX --> Q["Exercise EX041"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["9.1 Assurance language"]
  N2["9.2 Linter in CI"]
  N3["9.3 Leadership behaviours"]
  N4["9.4 Coaching refusal"]
  N5["9.5 Board education"]
  N6["9.6 Succession"]
  N7["9.7 Narrative"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX041"]
[Learning outcomes]
    |
    v
[9.1 Assurance language]
    |
    v
[9.2 Linter in CI]
    |
    v
[9.3 Leadership behaviours]
    |
    v
[9.4 Coaching refusal]
    |
    v
[9.5 Board education]
    |
    v
[9.6 Succession]
    |
    v
[9.7 Narrative]
    |
    v
[Worked example] --> [Exercise EX041]

Learning outcomes

You will (1) write assurance statements that survive audit; (2) lead without theatre; (3) coach refusal skills; (4) validate statements with a linter lab.

9.1 Assurance language

Assurance language at Meridian Clearing House is time-bounded, scope-bounded and method-bounded. Forbidden: fully secure, guaranteed, hack-proof, 100% coverage.

"""Lab 9: validate a synthetic assurance statement against a forbidden-phrase list."""
forbidden = ["fully secure", "guaranteed", "hack-proof", "100% coverage"]
text = "Quarterly web tests and a 2025 threat-led exercise provide time-bounded assurance; SWIFT remains excluded from ordinary tests."
hits = [f for f in forbidden if f in text.lower()]
print("CLEAN" if not hits else "FORBIDDEN: " + ", ".join(hits))
print("chars", len(text))

Run with python3 lab_assurance.py. Verified output:

CLEAN
chars 126

lab_assurance checks a synthetic statement against those four forbidden phrases and prints CLEAN with chars 126 for the wording about quarterly web tests and a 2025 threat-led exercise. Amira runs the same check on every board pack export, so forbidden phrases never leave in a pack. A statement that fails is rewritten with its time, scope and method bounds stated, then checked again before the export continues.

9.2 Linter in CI

The linter is small on purpose, so deputies can run lab_assurance without Amira and the check does not depend on one person before a pack leaves. It sits in CI before the board-portal upload, and the pack cannot be uploaded until the export job reports CLEAN. A vendor paste once introduced "hack-proof" into a draft pack and CI blocked it. Amira keeps that block as the teaching case for why the check runs before a pack leaves rather than after a director has already read it.

9.3 Leadership behaviours

Leadership behaviours shape what juniors chase. Amira praises early stops, funded negative results and clean catalogues more than dramatic finds; at quarterly review she names one early stop and one funded negative result before mentioning any finding. Students who stopped the tabletop at the simulated settlement delay are praised in the same meeting as the quarter's best finding. A culture that only celebrates fireworks will bury pauses and refuse negative results, which is how unsafe exercises continue for applause at an organisation like Meridian Clearing House.

9.4 Coaching refusal

Monthly role-play puts pressure on a specialist to soften wording. Amira wants both calm tone and firm refusal, so the score sheet rates tone and refusal separately, from zero to three each, with sample phrases for every level. They are scored separately on purpose, because a learner can be calm without holding the boundary. Soft panic and angry collapse both fail. The sheet is shared in advance, so people know what good looks like before the next real pressure email arrives.

9.5 Board education

Directors must learn what ordinary tests cannot claim, above all that they do not cover SWIFT-adjacent systems. Amira's board education pack uses the catalogue cannot-claim lines and the rewritten CBEST-inspired slide. Teaching happens before exam season, not during a finding argument, and the rewritten slide is part of the education pack rather than an emergency handout in the middle of a dispute. Directors who learn the cannot-claim lines in advance do not argue findings from SWIFT myths when a real finding reaches them.

9.6 Succession

Amira documents decisions so a successor can continue without folklore. Documented decisions such as DEC-14 and the two-year calendar beat hallway advice. Succession folders hold three CLEAN statements and three FORBIDDEN counterexamples with explanations, so deputies learn by contrast and wording rules travel with the decisions. The CLEAN examples include the lab statement that printed CLEAN at 126 characters, with its time and scope bounds marked. Amira answers questions during transfer but keeps no secret side rules. Each explanation names the bound that the FORBIDDEN version broke.

9.7 Narrative

The forbidden-phrase linter runs on every board pack export. When CI blocked "hack-proof" from a vendor paste, Amira forwarded the raw CI log to the vendor without scolding. Succession folders keep the CLEAN and FORBIDDEN pairs; each FORBIDDEN example uses one banned phrase, such as "fully secure" or "100% coverage", with corrected wording beside it. Deputies who study the pairs can explain why a sentence fails before they run the linter on it. Amira treats that skill, not the linter's output, as the real goal of the folder.

9.8 Vendor warning letters

Vendor warning letters enclose the forbidden list as Appendix A, with the four phrases exactly as the linter matches them: fully secure, guaranteed, hack-proof and 100% coverage. Attaching the list makes the warning specific: the vendor sees exactly which claims the team will not accept, whereas a vague "please be careful" letter changes nothing. Some vendors have updated their marketing decks after receiving it. Amira's seminar on quiet influence uses one such before-and-after deck pair as its main example. Each letter is filed in the vendor's catalogue entry.

9.9 Quiet influence

The CI log Amira forwarded showed the matched phrase and the line of pasted vendor text, which was all the explanation the vendor needed. The vendor's next deck used time-bounded assurance, and the change arrived without a meeting. She keeps that before-and-after pair for leadership seminars on quiet influence and refuses to tell the story as a victory over the vendor. In seminars she shows the CI log first and the new deck second, leaving deputies to draw the conclusion themselves.

9.10 Influence records

Before-and-after vendor decks are stored as evidence of influence, not of mockery. Both decks are filed, dated, with the CI log and the warning letter in that vendor's catalogue entry. Keeping both versions shows auditors that the warning changed vendor claims, which is the point of sending it. Amira can produce the pair when asked how Meridian Clearing House handles assurance language from suppliers. Influence with a record is assurance work; influence without a record is only a story. The file also notes the date the new deck was first seen.

Worked example (synthetic MCH)

lab_assurance prints CLEAN for Amira's statement; a draft with "fully secure" would fail.

Synthetic case — Meridian Clearing House (MCH). The clearing organisation, Amira Hassan and all figures are invented for teaching.

Errors and limits

Threat-led and clearing-system tests require specialised legal authorization. This book uses synthetic scenarios only and never supplies exploit code or live targeting advice for market infrastructures.

Exercises

  • EX041 — Forbidden list. Name three forbidden assurance phrases.
    Show marking criteria
    Rubric: 3 = three of fully secure, guaranteed, hack-proof, 100% coverage; 2 = two; 1 = one; 0 = none.
  • EX042 — Lab result. What does the lab print for the sample statement?
    Show marking criteria
    Rubric: 3 = CLEAN; 2 = forbidden; 1 = error; 0 = none.
  • EX043 — Praise targets. Name two behaviours Amira praises.
    Show marking criteria
    Rubric: 3 = two of early stops, negative results, clean catalogues; 2 = one; 1 = drama only; 0 = none.
  • EX044 — Board lesson. What must directors learn about SWIFT-adjacent systems?
    Show marking criteria
    Rubric: 3 = ordinary tests do not cover them; 2 = partial; 1 = fully covered; 0 = none.
  • EX045 — If forbidden present. What would lab print if "fully secure" appeared?
    Show marking criteria
    Rubric: 3 = FORBIDDEN: fully secure; 2 = CLEAN; 1 = vague; 0 = none.

Synthesis

Leadership is honest assurance language, coached refusal and praise for restraint.

Continue studying — chapter 09 of 12

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

Worked answers

EX041. Fully secure, guaranteed and hack-proof (100% coverage also).

EX042. CLEAN

EX043. Early stops and funded negative results (clean catalogues also).

EX044. That ordinary tests do not cover SWIFT-adjacent systems.

EX045. FORBIDDEN: fully secure