A new software workflow goes live for vendor access, but the access-revocation procedure still describes only the retired legacy system. What tech-change maintenance step was skipped?
Select an answer to reveal the explanation.
Short Explanation
New software with an old kill-switch recipe leaves orphan accounts hanging around. When the workflow changes, the revocation procedure has to change with it. Tech go-lives are procedure maintenance events—not just IT parties.
Full Explanation
System implementations alter how controls such as access provisioning and revocation are performed. Procedure maintenance must update steps, owners, evidence, and tools to match the live workflow; otherwise staff may fail to remove access correctly. Technology change is a standard trigger alongside regulatory and process changes. Aligning documentation and training at go-live reduces residual information and personnel risk.