9.6
IG2 IG3

Block Unnecessary File Types

Asset Type: Network
Security Function: Protect

Description

Block unnecessary file types attempting to enter the enterprise’s email gateway.

Implementation Checklist

1
Assess current protection controls in place
2
Configure and deploy required security controls
3
Test control effectiveness in non-production environment
4
Deploy to production and verify functionality
5
Document configuration and operational procedures
6
Configure email authentication (SPF, DKIM, DMARC)
7
Deploy email security gateway with filtering
8
Configure attachment and URL scanning

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Malware Delivery via Executable Email Attachments

Integrity

Attackers deliver ransomware, trojans, and backdoors through email attachments using dangerous file types (.exe, .scr, .js, .vbs, .hta, .iso) that are not blocked at the email gateway, relying on users to execute them.

Macro-Enabled Document Exploitation

Confidentiality

Weaponized Office documents with malicious macros (.docm, .xlsm) or legacy formats (.doc, .xls) pass through the email gateway without file type restrictions, enabling initial access when users enable macros as instructed by social engineering.

Archive-Based Evasion of Security Controls

Integrity

Attackers wrap malicious payloads in nested archives (.zip, .rar, .7z, .iso) or password-protected containers to bypass email scanning, and without file type blocking at the gateway these containers reach user inboxes.

Vulnerabilities (When Safeguard Absent)

No File Type Restrictions at Email Gateway

The email gateway permits all file types as attachments, including executable files, script files, disk image files, and other dangerous formats commonly used as malware delivery vectors.

Incomplete Dangerous File Type Block List

The email gateway blocks some obvious file types (.exe) but misses other dangerous formats such as .iso, .img, .vhd, .js, .jse, .wsf, .hta, .lnk, and .one files that attackers actively use to deliver malware.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Configuration screenshots or exports showing protection controls enabled Captured quarterly
Document Procedure documentation for protection measures Reviewed annually
Technical Email security configuration (SPF, DKIM, DMARC records) Verified quarterly
Document Governing policy document (current, approved, communicated) Reviewed annually