The Third-party Risk Issue lifecycle contains states that govern internal analysis and external collaboration. Two of them, Submitted to Third-party and Finalize with Third-party, exist solely to move the issue to the third-party contact for response and then to conclude it with that party. When an issue is intended for internal use only, no external exchange occurs, so those two states can be skipped.
The remaining states carry no such exemption. New is the entry state at which the issue is created, and it cannot be bypassed because every issue must begin there. Analyze is where the assessor evaluates the finding, determines severity and decides on the treatment, which applies equally to internal and shared issues; internal matters still require analysis before being resolved or accepted.
This design allows a single issue model to serve two purposes. Issues relating to internal controls or sensitive observations stay within the risk team, while issues that require evidence or action from the third party flow through the portal. Marking an issue as internal-only at creation determines which path it follows, and it should be set deliberately, since an issue exposed to the third party cannot be recalled in practice.
[Reference: Study Guide – Third-party Supporting Processes: Issue Lifecycle and States.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit