6.3
IG1 IG2 IG3

Require MFA for Externally>Exposed Applications

Asset Type: Users
Security Function: Protect

Description

Require all externally-exposed enterprise or third-party applications to enforce MFA, where supported. Enforcing MFA through a directory service or SSO provider is a satisfactory implementation of this Safeguard.

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
Identify systems requiring multi-factor authentication
7
Select and deploy MFA solution
8
Enroll users and distribute authentication factors
9
Test MFA across all identified systems
10
Inventory all third-party service providers
11
Classify third parties by risk level
12
Conduct security assessments of critical vendors
13
Include security requirements in contracts

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Credential Stuffing Against External Applications

Confidentiality

Attackers use leaked credential databases to perform automated login attempts against externally-exposed applications that rely solely on passwords without MFA.

Phished Credentials Used to Access External Portals

Confidentiality

An employee's credentials stolen through a phishing campaign provide immediate access to externally-exposed applications because no second factor is required for authentication.

Brute-Force Attack on Internet-Facing Login Portal

Availability

Attackers perform sustained brute-force attacks against internet-facing login pages where single-factor authentication allows unlimited credential guessing at scale.

Vulnerabilities (When Safeguard Absent)

Single-Factor Authentication on External Applications

Externally-exposed applications protected only by passwords are vulnerable to credential theft, stuffing, spraying, and brute-force attacks from anywhere on the internet.

No MFA Enforcement for Third-Party SaaS Applications

Third-party applications used by the enterprise lack MFA requirements, meaning a compromised password grants full access to potentially sensitive cloud-hosted data.

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 MFA enrollment status and enforcement configuration Reviewed monthly
Record Third-party risk assessment reports and scorecards Annually per vendor
Document Vendor contracts with security requirements Per contract cycle
Document Governing policy document (current, approved, communicated) Reviewed annually