Редагувати

Поділитися через

Migrate File Integrity Monitoring from previous versions

  • Стаття

Microsoft Defender for Servers Plan 2 now offers a new File Integrity Monitoring (FIM) solution powered by Microsoft Defender for Endpoint.

If you don't use the previous versions of FIM, you can onboard directly to the new FIM solution. For more information, see Enable File Integrity Monitoring with Microsoft Defender for Endpoint.

Migrate from FIM over AMA

If you use File Integrity Monitoring (FIM) over Azure Monitor Agent (AMA), you can migrate to the new FIM solution powered by Microsoft Defender for Endpoint. Follow these steps:

  1. Since onboarding new subscriptions or servers to File Integrity Monitoring based on AMA and the Change Tracking extension, as well as viewing changes, will no longer be available through the Defender for Cloud portal, you need to adjust your processes accordingly.

  2. If you wish to continue consuming File Integrity Monitoring events collected by AMA, you can manually connect to the relevant workspace and view changes in the Change Tracking table using the following query:

    ConfigurationChange  
| where TimeGenerated > ago(14d)  
| where ConfigChangeType in ('Registry', 'Files')  
| summarize count() by Computer, ConfigChangeType

  3. If you want to continue onboarding new scopes or configuring monitoring rules, you can manually use Data Collection Rules to configure or customize various aspects of data collection.

Disable FIM over AMA

We recommend that you disable FIM over AMA and use the new FIM solution powered by Microsoft Defender for Endpoint. To disable FIM over AMA, follow these steps:

  1. Remove the Azure Change Tracking solution. For more information, see Remove ChangeTracking solution.
  2. Alternatively, you can remove the related file change tracking Data Collection Rules (DCR). For more information, see the instructions in Remove-AzDataCollectionRuleAssociation and Remove-AzDataCollectionRule.
  3. After you disable the file events collections by the Change Tracking extension over AMA using one of the previously mentioned methods, new events will stop being collected on the selected scopes. Historical events that already were collected, remain stored in the relevant workspace under the table ConfigurationChange under the Change Tracking section. These events will remain available in the relevant workspace according to the retention period defined in this workspace. For more information, see Manage data retention in a Log Analytics workspace.

Migrate from FIM over MMA

If you use File Integrity Monitoring (FIM) over Microsoft Monitoring Agent (MMA), you can migrate to the new FIM solution powered by Microsoft Defender for Endpoint. Follow these steps:

To disable FIM over MMA, remove the Azure Change Tracking solution. For more information, see Remove ChangeTracking solution.

After you disable the file events collections by the Change Tracking extension over AMA using one of the previously mentioned methods, new events will stop being collected on the selected scopes. Historical events that already were collected, remain stored in the relevant workspace under the table ConfigurationChange under the Change Tracking section. These events will remain available in the relevant workspace according to the retention period defined in this workspace. For more information, see Manage data retention in a Log Analytics workspace.

Note

If you no longer need the legacy Log Analytics agent, make sure you remove it from your environments. For this purpose, be sure to disable the agent's auto provisioning from the subscription settings, then use the Azure Monitor utility to discover and remove the Log Analytics agent from your machines.

Next steps