A critical library catalog finding will not be fixed this quarter due to a vendor dependency. How should that decision be handled?
Select an answer to reveal the explanation.
Short Explanation
Can't fix it yet? Don't ghost the ticket—write an exception with an end date and a revisit. Silent deletes, fake 'fixed' labels, or public forever-accepts are how risk acceptance goes sideways.
Full Explanation
When remediation is deferred, exception handling requires documented risk acceptance with time bounds and scheduled review. Silent suppression, false closure, or open-ended public acceptance without governance fails Domain 6 reporting expectations. Library systems still need traceable treatment of unresolved findings.