CIS Controls v8 6.4 — Require MFA for Remote Network Access

What this control requires

Require MFA for remote network access.

In plain English

Require MFA for remote network access. In practice, this means you can prove you require network-level controls on a defined cadence.

Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within Protect, the assessor will trace your implementation back to the catalogue reference (Control 6.4) and look for objective evidence on the latest two assessment cycles.

How to implement

Cloud Posture

CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

Network Security

AWS. VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation.

Azure. NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift.

GCP. VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services.

Operational checklist

• Require. Document the trigger, the owner and the cadence.
• Protect. Document the trigger, the owner and the cadence.
• Scope: network, mfa, identity management.

Evidence to collect

• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.
• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Require MFA for Remote Network Access.

Common pitfalls

• Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.
• Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• ISO/IEC 27701:2025 A.3.8 — Identity management
• ISO/IEC 27001:2022 A.8.21 — Security of network services
• BSI C5:2020 AM-05 — Commitment to Permissible Use, Safe Handling and Return of Assets
• SOC 2 (2017 TSC) CC1.5 — Accountability for Internal Control Responsibilities
• NIST SP 800-53 Rev. 5 AC-6(3) — Network Access To Privileged Commands

Related controls in CIS Controls v8

• Control 12.5 — Centralize Network Authentication, Authorization, and Auditing (AAA)
• Control 12.7 — Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure
• Control 13.9 — Deploy Port-Level Access Control
• Control 9.2 — Use DNS Filtering Services
• Control 5.2 — Use Unique Passwords
• Control 6.5 — Require MFA for Administrative Access

References

• Center for Internet Security — CIS Controls v8
• Catalogue identifier: Control 6.4

Topics: identity accessnetwork securitycloud postureidentity managementaccess review