A standard revision publishes and several authority-document sections change. What should the GRC team do in IRM?
Select an answer to reveal the explanation.
Short Explanation
When the standard's pages turn, update the authority docs and re-hook the objectives to the new citations. Keeping zombies or burning down the app are the bad extremes.
Full Explanation
When a standard revision publishes and authority-document sections change, the GRC team should update the authority documents and remap affected control objectives to the revised citations. Living standards require living mappings so tests still prove the current obligation text for civic programs. Remapping is maintenance, not optional cleanup.
Leaving obsolete citations active forever to avoid remapping work misleads testing against dead text. Deleting the entire Policy and Compliance application and rebuilding from blank tables is destructive overkill. Converting revised standards into SIR security incidents one-for-one confuses regulatory text updates with security incidents.
Exam caveat: update authority docs + remap objectives; do not keep zombie citations or burn down the app.
Operational check: ingest the revised standard sections; deactivate or supersede obsolete citations; remap objectives; re-run a sample control test against the new citation links.
After remapping, sample control tests to confirm they reference revised citations, and communicate obsolete citation retirement to testers. Avoid application teardown or SIR incident creation as responses to routine standard revisions.