A transit authority’s appetite breaches currently live only in a shared spreadsheet footnote. Which architecture should replace that pattern?
Select an answer to reveal the explanation.
Short Explanation
A spreadsheet footnote is a sticky note on a moving train—easy to miss. Put appetite breaches into IRM workflow with an owner, a due date, and a trail so leadership actually sees the breach.
Full Explanation
Risk appetite and tolerance only govern behavior when breaches create accountable work. Architecture should systematize breach handling inside IRM with workflow, ownership, and history rather than informal notes. Offline PDFs, delayed audit-only discovery, or personal files hide breaches from operating management.