<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b244bd2a074a4784828e40d09fa0afe2&quot; frameborder=&quot;0&quot; width=&quot;1304&quot; height=&quot;978&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>978</height><width>1304</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>978</thumbnail_height><thumbnail_width>1304</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b244bd2a074a4784828e40d09fa0afe2-ec2205564ea775a3.gif</thumbnail_url><duration>508.191</duration><title>Vendor Engagements in TPRM</title><description>This Loom announces TPRM’s Vendor Engagements feature, which lets customers nest products and services as engagements under a vendor instead of reassessing the same vendor repeatedly. It explains that customers managing Atlassian as a flat vendor must assess Atlassian for each new product, but with engagements they assess Atlassian once and then assess only the specific engagement such as Bitbucket or Jira each time. The video shows how the vendor list will display Atlassian with expandable engagements, each with its own inherent risk score, owners, and assessment status, and how to add engagements via a modal. It notes this first release adds UI support for managing engagements, with an agent to triage and nest vendors coming soon, plus planned rollups for parent vendor inherent risk and reusable parent-level evidence.</description></oembed>