A library system formally accepts residual risk on a legacy catalog server. What validation prevents that acceptance from lasting forever without revisit?
Select an answer to reveal the explanation.
Short Explanation
Acceptance is a timed parking permit, not a forever deed. Put a review date on accepted risks so someone looks again before the world changes. Hiding them from dashboards or zeroing residual is how silent risk piles up.
Full Explanation
Risk acceptance is a governed decision that should include accountable sign-off and a scheduled review. Time-bound review dates ensure accepted risks are reassessed as context changes. Suppressing dashboards, auto-zeroing residual, or treating acceptance as permanent retirement without follow-up violates sound IRM lifecycle control.