<?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/2b2665e8408247118681af7d3a1b81d3&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/2b2665e8408247118681af7d3a1b81d3-66abf43f240c9468.gif</thumbnail_url><duration>453.266667</duration><title>Fatem JSM Integration for Automated CMDB Sync</title><description>Today I walked you through the new Fatem JSM integration. Fatem continuously discovers your hybrid infrastructure and automatically syncs live discovery data into Jira Service Management on a configurable schedule, so your CMDB stays accurate. I showed the setup flow, install the app from the Atlassian Marketplace, create an Assets schema with a Fatem import type, then add the webhook URL and authentication token and run the first manual sync, which takes about 20 to 30 seconds for object creation and about 30 seconds for the first sync. After syncing, JSM shows servers, dependencies, risk score, and a link back to Phantom. I recommend you set a schedule for ongoing freshness.</description></oembed>