

Tampering events are logged in: “Library/Logs/Microsoft/mdatp/microsoft_defender_core*.log”Īdmins can leverage the audit mode to get familiar with how the feature detections possible tampering actions.


The logs can also be found locally on the device. Look for the tamper_protection field, it will display “audit”, “block” or “disabled” according to your configuration. If you want to check the status of the feature on a single device, you can run the command “mdatp health”. | where ActionType contains “TamperingAttempt” To observe tampering events in the portal, you can use the following query in Advanced Hunting: Here’s more from Microsoft’s blog about how to observe tampering events in the portal: No tampering alerts are raised in the Security Center while in Audit model, and alerts are raised in the portal only in block mode. While in Audit mode, TP signals can be viewed via Advanced Hunting and in local on-device logs, the company says.
