Quiz: Building a Complete Security Program

A 26-question self-check synthesizing the capstone and the book. Because Chapter 38 integrates everything, several questions reach back into earlier material. Questions tagged [Sec+] map to CompTIA Security+ domains and [CISSP] to (ISC)² CISSP domains (especially Security & Risk Management and Security Architecture). Answers and one-line explanations are at the end — try the whole quiz first.


Section 1 — Multiple choice (1 pt each)

1. [CISSP] What primarily distinguishes a security program from a collection of security controls? A. the number of tools B. coherence — a spine, structure, and strategy tying the parts together C. the size of the budget D. having a CISO

2. [Sec+] Meridian organizes its program around the six functions Govern, Identify, Protect, Detect, Respond, Recover. This structure comes from: A. ISO 27001 B. the NIST Cybersecurity Framework (CSF) 2.0 C. PCI-DSS D. MITRE ATT&CK

3. The "spine" of Meridian's security program — the organizing logic everything hangs from — is: A. the firewall ruleset B. compliance C. risk D. the org chart

4. [CISSP] A roadmap should sequence initiatives primarily by: A. raw risk score, highest first B. lowest cost first C. risk-reduction per cost, adjusted for dependencies and obligations D. vendor recommendation

5. Which can legitimately override the risk-per-cost ranking when prioritizing a roadmap? A. a hard dependency or a non-negotiable compliance obligation B. a louder stakeholder C. a newer technology D. nothing — the ratio is absolute

6. [Sec+] ALE, the engine of the business case, is computed as: A. likelihood × impact B. SLE × ARO C. CVSS × EPSS D. MTTD × MTTR

7. A board presentation should lead with: A. the network architecture B. the threat-intelligence feed C. the ask (the decision requested) D. a list of tools deployed

8. [CISSP] A board of directors provides __, not management, of the security program. A. funding only B. oversight C. engineering D. incident response

9. Presenting the program's gaps and residual risk to the board tends to: A. erode confidence and should be avoided B. build confidence by proving clear sight and honest management C. trigger an audit D. violate policy

10. [Sec+] Which metric belongs on a board (executive) slide rather than an operational SOC dashboard? A. alerts per analyst per day B. SIEM rule false-positive rate C. mean time to detect (MTTD) trend D. raw count of brute-force alerts

11. The capstone's program_dashboard(state) integrates outputs from which modules? A. only riskcalc B. riskcalc (risk/ALE) and metrics (MTTD/MTTR/coverage) C. netfilter and siem D. none — it is standalone

12. [CISSP] "The board wants to know if the plane will land, not how the engine works" is a principle about: A. encryption B. translating technical work into executive risk language C. aircraft security D. availability

13. The original Meridian phishing attack is now met by defense in depth. Which set best illustrates the independent layers involved? A. one firewall B. email auth + awareness + phishing-resistant MFA + least privilege + segmentation + detection/response C. antivirus only D. a longer password policy

14. [Sec+] A compliance obligation such as PCI-DSS CDE segmentation is best described in the business case as: A. optional risk reduction B. the non-negotiable floor the organization is legally required to meet C. a vanity metric D. a Phase 3 nice-to-have


Section 2 — True / False with justification (1 pt each)

For each, mark T or F and give a one-sentence reason.

15. "A program that has every control in this book is, by definition, a mature security program."

16. [Sec+] "The scariest, highest-impact risk should always be the first item on the roadmap."

17. "Inflating risk numbers to win a budget is a reasonable tactic if the program genuinely needs the money."

18. [CISSP] "Owning the program's gaps in front of the board undermines the CISO's credibility."

19. "Operational SOC metrics, such as alert volume and tuning rates, are important and therefore belong in the board deck."

20. "Every roadmap item should trace to a specific risk-register entry."


Section 3 — Fill in the blank (1 pt each)

21. A multi-year, sequenced, costed plan from current state to target state is the security __.

22. [Sec+] The four parts of a business case are: the cost of the _ _, the investment and the risk it buys down, the compliance _, and the alternatives ending in a specific _.

23. The three capstone tracks are SOC (Detect–Respond–Recover), Engineer (_ architecture and sequencing), and _ (Govern–Identify and the full synthesis).


Section 4 — Short answer (2 pts each)

24. [CISSP] Explain why "always do the highest-risk item next" is a flawed prioritization rule, and name the ranking that fixes it.

25. A board asks, "Are we spending the right amount on security?" Describe, in two or three sentences, how the Govern layer (risk appetite + risk assessment) answers this question.


Section 5 — Applied scenario (5 pts)

26. [Sec+] Meridian carries roughly $6M in annualized cyber risk (from its top three untreated risks). A proposed $1.7M investment in Phases 1–2 is projected to reduce this to ~$0.9M; the board's risk appetite is $1.0M. (a) State the business case in one sentence in the board's language. (b) Is the projected residual within appetite, and what does that let the CISO tell the board? (c) Name two of the four things a board cares about that this case addresses, and the deck slide that carries each.


Answer Key

Click to reveal answers and explanations 1. **B** — coherence (spine + structure + strategy) is what makes a program, not tool count or budget. 2. **B** — Govern/Identify/Protect/Detect/Respond/Recover are the NIST CSF 2.0 functions. 3. **C** — risk is the spine; every control, roadmap item, and dollar maps to a risk. 4. **C** — sequence by risk-reduction per cost, adjusted for dependencies and obligations. 5. **A** — hard dependencies and non-negotiable compliance obligations are the only legitimate overrides. 6. **B** — ALE = SLE × ARO (Ch.27). 7. **C** — lead with the ask; boards read the conclusion first. 8. **B** — boards provide oversight, assuring risk is within the appetite they set. 9. **B** — owning gaps proves clear sight and builds trust. 10. **C** — MTTD trend is a board KRI; the others are operational. 11. **B** — it integrates `riskcalc` and `metrics`. 12. **B** — translating technical work into executive risk language. 13. **B** — multiple independent layers are defense in depth. 14. **B** — the non-negotiable compliance floor. 15. **F** — a program is *coherence* (spine, structure, strategy), not a complete control inventory; controls without coherence are a pile, not a program. 16. **F** — that ignores cost and dependencies and can burn the budget for little total risk reduction; rank by risk-per-cost. 17. **F** — inflating numbers is dishonest and, beyond one budget cycle, self-defeating, because lost credibility discounts every future ask. 18. **F** — owning gaps *builds* credibility; a gapless presentation signals concealment. 19. **F** — operational metrics matter but answer questions no director asked and signal lost forest-for- trees; the board sees only risk-trending KRIs. 20. **T** — traceability to a named risk is what makes each item defensible. 21. roadmap. 22. status quo; obligations; ask. 23. Protect; GRC. 24. It ignores cost and dependencies, so a single expensive, slow megaproject can consume the budget while cheaper fixes that remove more total risk wait, producing little measurable burndown; ranking by risk-reduction-per-cost (adjusted for dependencies/obligations) fixes it. 25. The risk-appetite statement says how much risk the board has decided the bank will tolerate, the risk assessment says how much it currently holds, and the gap between them — translated to dollars — is the answer: you are spending correctly if the program is closing that gap efficiently and residual risk is trending toward appetite. 26. (a) "We propose investing $1.7M to remove ~$5.1M of annualized cyber risk, taking residual risk from ~$6M to ~$0.9M." (b) Yes — $0.9M is below the $1.0M appetite, so the CISO can tell the board that the proposed program drives residual risk *within the appetite they set* (a decision they can own). (c) Any two of: *are we exposed?* (risk-story slide), *are we competent?* (what-we've-built / metrics slides), *are we compliant?* (business-case obligations slide), *what do you need?* (ask/decision slides). **Topics to review by question:** missed 1, 3, 15 → §38.1; 2 → §38.2 (CSF); 4, 5, 16, 24 → §38.3; 6, 14, 17, 22, 26 → §38.4; 7, 8, 9, 10, 12, 13, 18, 19, 23 → §38.5; 11 → Project Checkpoint; 20, 21 → §38.3/38.7.