Third-party risk tasks are stored in the table sn_vdr_risk_asmt_task. The table records follow-up work connected to assessments and issues, such as obtaining additional evidence or confirming a remediation step, and it extends the Planned Task table, so tasks inherit planning features such as scheduling and assignment. The table is part of the same scoped family as the assessment and issue tables, which share the sn_vdr_risk_asmt prefix.
The remaining names are not the delivered table. A table named for an activity, a table using a shortened sn_vdr_risk_task prefix, and a table carrying a longer assessment_task name resemble the real one but do not correspond to the application's data model. Using any of them in a report, import or script would fail or yield no data.
Knowing the exact table name is useful in several practical scenarios. Reports on overdue remediation work, access control rules, and integrations that create tasks all reference it. When exposing tasks to third-party contacts through the portal, the portal widgets and access controls also operate against this table, so any customization must respect those controls to keep each third party limited to its own tasks.
[Reference: Study Guide – Third-party Supporting Processes: Third-party Risk Tasks and Data Model.]
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