When an integration imports assets into ControlMap, removing an asset from the source system does not automatically remove it from ControlMap. ControlMap retains synced asset records to support historical data requirements for compliance frameworks.

If you no longer want the imported assets in ControlMap, follow the steps below.

Who can use this feature?

• Super Admins and Compliance Managers.

What you’ll need

• Access to the ControlMap MSP Portal or the tenant where the integration is connected.

• Access to the integration settings in ControlMap.

• The unwanted assets removed from the integration’s source system.

Remove assets synced from an integration

1. Remove the unwanted assets from the source system, if you haven’t already.

2. In ControlMap, open the Integrations area at the MSP or tenant level where the integration is connected.

3. Delete the integration that imported the assets.

   Caution: Deleting an integration resets its integration history and removes previously synced data for that integration. Confirm that you want to remove the integration before continuing.

4. Reconnect the integration in ControlMap.

5. Allow the integration to complete a new sync.

ControlMap imports the assets that still exist in the source system. Assets that you removed from the source system don’t return after the fresh sync.

Why this happens

ControlMap retains assets that an integration previously synced, even when those assets are no longer present in the source system. This behavior preserves historical asset information that some compliance frameworks require.

To identify an asset that is no longer being detected by an integration, check its Last Seen field. If the date stops updating, the source system is no longer returning the asset during syncs.

Deleting individual assets in ControlMap while the integration remains connected might not resolve the issue. The integration can sync those assets again during a future sync.