(L1) Ensure the Common Attachment Types Filter is enabled (Only Checks Default Policy)
Part of CIS · Defender · Anti-malware · All checks
Invoke-Maester -TestId CIS.M365.2.1.2Overview
Section titled “Overview”2.1.2 (L1) Ensure the Common Attachment Types Filter is enabled
The Common Attachment Types Filter lets a user block known and custom malicious file types from being attached to emails.
Rationale
Section titled “Rationale”Blocking known malicious file types can help prevent malware-infested files from infecting a host.
Impact
Section titled “Impact”Blocking common malicious file types should not cause an impact in modern computing environments.
The audit also verifies that the FileTypes property contains at least the default list of 53 file types below.
Remediation action
Section titled “Remediation action”To enable the Common Attachment Types Filter:
- Navigate to Microsoft 365 Defender.
- Click to expand Email & collaboration select Policies & rules.
- On the Policies & rules page select Threat policies.
- Under policies select Anti-malware and click on the Default (Default) policy.
- On the Policy page that appears on the right-hand pane scroll to the bottom and click on Edit protection settings, check the Enable the common attachments filter.
- If any of the default file types are missing, click Select file types and add the missing file types in.
- Click Save.
PowerShell
Section titled “PowerShell”- Connect to Exchange Online using
Connect-ExchangeOnline. - Run the following Exchange Online PowerShell command:
Set-MalwareFilterPolicy -Identity Default -EnableFileFilter $true- Use
Set-MalwareFilterPolicy -Identity Defaultwith the-FileTypesparameter to add any missing file types from the default list below. Retrieve the existing list first usingGet-MalwareFilterPolicyand append any missing file types before updating the policy.
Default extensions:
ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe,hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi,msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe,vbs, vxd, wsc, wsf, wsh, xll, xz, z, aceNote: Audit and Remediation guidance may focus on the Default policy however, if a Custom Policy exists in the organization’s tenant, then ensure the setting is set as outlined in the highest priority policy listed.
Related links
Section titled “Related links”- Microsoft 365 Defender
- Get-MalwareFilterPolicy
- Configure anti-malware policies for cloud mailboxes
- CIS Microsoft 365 Foundations Benchmark v7.0.0 - Page 84
Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | CIS.M365.2.1.2 |
| Severity | Medium |
| Suite | CIS |
| Product | Defender |
| Related products | Exchange Online |
| Feature | Anti-malware |
| Area | Email and collaboration protection |
| Resource type | Tenant |
| User impact | Low |
| Implementation cost | Low |
| MITRE ATT&CK | T1566.001 Spearphishing Attachment, T1204.002 Malicious File |
| Supports benchmark | CIS Microsoft 365 Foundations Benchmark (version 7.0.0), requirement 2.1.2 |
| Benchmark level | L1 |
| Benchmark profiles | E3 Level 1 |
| Supports controls | cis-m365:2.1.2, nist-800-53-r5:SI-3 |
| PowerShell test | Test-MtCisAttachmentFilter |
| Services | ExchangeOnline |
Source
Section titled “Source”- Test:
tests/cis/Test.CIS.M365.2.1.2.ps1 - Documentation:
tests/cis/Test.CIS.M365.2.1.2.md
About this check
- Severity
- Medium
- Effort to fix
- Low
- Impact on users
- Low
- Product
- Defender
- Feature
- Anti-malware
- Area
- Email and collaboration protection
- Suite
- CIS