A county GRC admin notices retired clinic applications still spawning new generated risks every week. What configuration change stops that noise without deleting historical risk history?
Select an answer to reveal the explanation.
Short Explanation
Retired apps are closed stores — stop printing new risk labels for them. Filter generation so retired entities are excluded while old risk history can stay for the archive. Nuke-all or hope-and-pray moves make a mess.
Full Explanation
Automatic risk generation should respect entity lifecycle. Excluding retired or inactive entities from generation filters prevents clutter without erasing historical risk records needed for audit trail. Global disable or destructive deletes are overly broad; unrelated CMDB moves do not replace generation criteria.