9.1
IG1 IG2 IG3

Ensure Use of Only Fully Supported Browsers and Email Clients

Asset Type: Applications
Security Function: Protect

Description

Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.

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
9
Inventory all third-party service providers
10
Classify third parties by risk level
11
Conduct security assessments of critical vendors
12
Include security requirements in contracts

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Browser-Based Exploit Kit Delivery

Confidentiality

Outdated or unsupported browsers contain known vulnerabilities that exploit kits target to deliver malware through malicious advertisements, compromised websites, or watering hole attacks without requiring any user interaction beyond visiting a page.

Email Client Vulnerability Exploitation for Initial Access

Integrity

Unsupported email clients with known rendering or parsing vulnerabilities are exploited to execute malicious code when users preview or open specially crafted emails, bypassing attachment-based security controls.

Session Hijacking via Outdated Browser TLS Implementation

Confidentiality

Outdated browsers supporting deprecated TLS versions or weak cipher suites allow man-in-the-middle attackers to intercept and decrypt sensitive web sessions, including banking, email, and enterprise application traffic.

Vulnerabilities (When Safeguard Absent)

Unsupported Browser Versions in Production Use

Enterprise assets run end-of-life browser versions that no longer receive security patches from vendors, accumulating exploitable vulnerabilities with each new disclosure while remaining the primary interface to web applications.

No Browser Version Enforcement Policy

The organization has no technical controls (GPO, MDM, or configuration management) to enforce minimum browser versions or prevent the use of unsupported browsers, allowing users to operate with dangerously outdated software.

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