Επεξεργασία

Κοινή χρήση μέσω

Configure and validate exclusions for Microsoft Defender for Endpoint on macOS

  • Άρθρο

Applies to:

Want to experience Defender for Endpoint? Sign up for a free trial.

This article provides information on how to define exclusions that apply to on-demand scans, and real-time protection and monitoring.

Important

The exclusions described in this article don't apply to other Defender for Endpoint on Mac capabilities, including endpoint detection and response (EDR). Files that you exclude using the methods described in this article can still trigger EDR alerts and other detections.

You can exclude certain files, folders, processes, and process-opened files from Defender for Endpoint on Mac scans.

Exclusions can be useful to avoid incorrect detections on files or software that are unique or customized to your organization. They can also be useful for mitigating performance issues caused by Defender for Endpoint on Mac.

To narrow down which process and/or path and/or extension you need to exclude, use real-time-protection-statistics.

Warning

Defining exclusions lowers the protection offered by Defender for Endpoint on Mac. You should always evaluate the risks that are associated with implementing exclusions, and you should only exclude files that you are confident are not malicious.

Supported exclusion types

The following table shows the exclusion types supported by Defender for Endpoint on Mac.

Exclusion Definition Examples
File extension All files with the extension, anywhere on the machine .test
File A specific file identified by the full path /var/log/test.log

/var/log/*.log

/var/log/install.?.log
Folder All files under the specified folder (recursively) /var/log/

/var/*/
Process A specific process (specified either by the full path or file name) and all files opened by it /bin/cat

cat

c?t

File, folder, and process exclusions support the following wildcards:

Wildcard Description Examples
* Matches any number of any characters including none (note if this wildcard isn't used at the end of the path then it substitutes only one folder) /var/*/tmp includes any file in /var/abc/tmp and its subdirectories, and /var/def/tmp and its subdirectories. It doesn't include /var/abc/log or /var/def/log

/var/*/ includes any file in /var and its subdirectories.
? Matches any single character file?.log includes file1.log and file2.log, but not file123.log

Note

When using the * wildcard at the end of the path, it will match all files and subdirectories under the parent of the wildcard.

The product attempts to resolve firmlinks when evaluating exclusions. Firmlink resolution does not work when the exclusion contains wildcards or the target file (on the Data volume) does not exist.

Best practices for adding antimalware exclusions for Microsoft Defender for Endpoint on macOS.

  1. Write down why an exclusion was added to a central location where only SecOps and/or Security Administrator have access. For example, list the submitter, date, app name, reason, and exclusion information.

  2. Make sure to have an expiration date* for the exclusions

    *except for apps that the ISV stated that there's no other tweaking that could be done to prevent the false positive or higher cpu utilization from occurring.

  3. Avoid migrating non-Microsoft antimalware exclusions since they may no longer be applicable nor applicable to Microsoft Defender for Endpoint on macOS.

  4. Order of exclusions to consider top (more secure) to bottom (least secure):

    1. Indicators - Certificate - allow

      1. Add an extended validation (EV) code signing.

    2. Indicators - File hash - allow

      1. If a process or daemon doesn't change often, for example, the app doesn't have a monthly security update.

    3. Path & Process

    4. Process

    5. Path

    6. Extension

How to configure the list of exclusions

Use the Microsoft Defender for Endpoint Security Settings management console

  1. Sign in to the Microsoft Defender portal.

  2. Go to Configuration management > Endpoint Security Policies > Create new Policy.

    • Select Platform: macOS
    • Select Template: Microsoft Defender Antivirus exclusions

  3. Select Create Policy.

  4. Enter a name and description and select Next.

  5. Expand Antivirus engine, and then select Add.

  6. Select Path or File extension or File name.

  7. Select Configure instance and add the exclusions as needed. Then select Next.

  8. Assign the exclusion to a group and Select Next.

  9. Select Save.

From the management console

For more information on how to configure exclusions from JAMF, Intune, or another management console, see Set preferences for Defender for Endpoint on Mac.

From the user interface

  1. Open the Defender for Endpoint application and navigate to Manage settings > Add or Remove Exclusion..., as shown in the following screenshot:

    The Manage exclusions page

  2. Select the type of exclusion that you wish to add and follow the prompts.

Validate exclusions lists with the EICAR test file

You can validate that your exclusion lists are working by using curl to download a test file.

In the following Bash snippet, replace test.txt with a file that conforms to your exclusion rules. For example, if you have excluded the .testing extension, replace test.txt with test.testing. If you're testing a path, ensure that you run the command within that path.

curl -o test.txt https://secure.eicar.org/eicar.com.txt

If Defender for Endpoint on Mac reports malware, then the rule isn't working. If there's no report of malware, and the downloaded file exists, then the exclusion is working. You can open the file to confirm that the contents are the same as what is described on the EICAR test file website.

If you don't have Internet access, you can create your own EICAR test file. Write the EICAR string to a new text file with the following Bash command:

echo 'X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*' > test.txt

You can also copy the string into a blank text file and attempt to save it with the file name or in the folder you're attempting to exclude.

Allow threats

In addition to excluding certain content from being scanned, you can also configure the product not to detect some classes of threats (identified by the threat name). You should exercise caution when using this functionality, as it can leave your device unprotected.

To add a threat name to the allowed list, execute the following command:

mdatp threat allowed add --name [threat-name]

The threat name associated with a detection on your device can be obtained using the following command:

mdatp threat list

For example, to add EICAR-Test-File (not a virus) (the threat name associated with the EICAR detection) to the allowed list, execute the following command:

mdatp threat allowed add --name "EICAR-Test-File (not a virus)"

Tip

Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: Microsoft Defender for Endpoint Tech Community.