Third parties interact with the application through the Third-party Portal, where they have direct access to update and respond to issues and tasks assigned to their organization, in addition to completing questionnaires and document requests. The portal exposes a controlled subset of records so that remediation can be coordinated without exchanging email attachments.
Viewing other third parties' assessment responses, issues or tasks is prohibited. Isolation between third parties is a fundamental confidentiality requirement, and access is scoped by the contact's association with a specific third party record. Modifying the issue remediation workflow is likewise not available to external contacts. Workflow definition and state design are administrative functions held by internal roles, and contacts operate within the workflow as participants.
This boundary has practical implications for design. Because contacts can respond to issues, the content of issues shared with them must be written for an external audience, and internal analysis notes should be kept in fields or issues that are not exposed. Reviewers should also confirm that tasks assigned to contacts have clear instructions and due dates, since the contact's only view into the work is what the portal displays.
[Reference: Study Guide – Third-party Risk Management Fundamentals and Review: Third-party Access and Data Isolation.]
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