If a Third-party Risk Issue is intended for internal use only, which states can be skipped? Choose two
Options:
A.
Analyze
B.
Finalize with Third-party
C.
New
D.
Submitted to Third-party
Answer:
B, D
Explanation:
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.]
Question 18
When the GRC: Policy and Compliance Management application is installed, which GRC related list appears on a Third-party Risk Issue record?
Options:
A.
Policies
B.
Policy Exceptions
C.
Configuration baseline
D.
Citations
Answer:
A
Explanation:
When GRC: Policy and Compliance Management is installed alongside Third-party Risk Management, the Third-party Risk Issue record gains a Policies related list. This allows an issue to be associated with the internal policies that the finding relates to, so that a deficiency identified at a third party can be traced to the policy requirement it affects.
The other lists are not the ones added by this integration. Policy Exceptions track approved deviations from policy and are managed within the policy application's own exception process; they are not the related list displayed on the issue. Configuration baseline belongs to configuration compliance for technical assets. Citations are references to authoritative content such as regulatory requirements, and they sit within the compliance content model rather than being displayed as a related list on a third-party issue.
The practical benefit is traceability. A risk team can show an auditor which policies are implicated by a third party's failure to meet an expectation, and policy owners can see external findings that bear on their policies. Implementers should confirm that the plugin is active and that the related list is configured on the issue form for the relevant roles.
[Reference: Study Guide – Other Application Relationships: Policy and Compliance Management Integration., ]