CIS Controls v8
CIS Control 6: Access Control Management

CIS Controls v8 CIS-6.5: Require MFA for Administrative Access

Where supported, require MFA on every account with administrative access, on every enterprise asset, whether the asset is managed on site or by a third-party provider.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 59 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 6 controls

  • 8.3.1 8.3.1 Access authenticated with at least one factor
  • 8.3.3 8.3.3 Identity verified before factor changes
  • 8.4.1 8.4.1 MFA for non-console administrative CDE access
  • 8.5.1 8.5.1 MFA system resistant to replay and bypass
  • 9.2.3 9.2.3 Physical protection of network hardware and lines
  • 9.4.4 9.4.4 Management approval for media leaving facility

FedRAMP High · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(7) Privileged User Accounts
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(8) Access to Accounts Replay Resistant

FedRAMP Moderate · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(7) Privileged User Accounts
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(8) Access to Accounts Replay Resistant

CMMC 2.0 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • ASBv3-IM-2 Protect identity and authentication systems
  • IM-6 Use strong authentication controls
  • PA-2 Avoid standing access for user accounts and permissions

ISO 27002:2022 · 3 controls

  • 5.16 Identity management
  • 8.2 Privileged access rights
  • 8.5 Secure authentication

NIST SP 800-53 Rev 5 · 3 controls

  • NIST800-IA-1 IA-1 Policy and Procedures
  • NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)
  • SP800-53-IA Identification and Authentication Family

C5 (Germany) · 2 controls

ISO 27001:2022 · 2 controls

  • 8.2 Privileged access rights
  • 8.5 Secure authentication

ISO 27701:2019 · 2 controls

  • 6.6.2 User access management
  • 6.6.4 System and application access control

NIST SP 800-171 Rev 3 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.7 MFA for Administrative Accounts
  • CE-SC.6 Multi-Factor Authentication for Cloud Services
  • E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2
  • ASD37-20 Multi-factor authentication (Essential)
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment
  • ISM-1173 Multi-factor authentication for privileged users

CIS Controls v8.1 · 1 control

  • 6.5 Require MFA for Administrative Access

HIPAA Security Rule · 1 control

  • 164.312(d) Person or Entity Authentication (Standard)

NIS2 Directive · 1 control

  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications

NIST SP 800-172 · 1 control

  • 3.5.3e Prohibit Connection of Unknown or Unverified System Components
  • 164.312(d) Person or Entity Authentication (Standard)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CIS Control 6: Access Control Management

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-6.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 59 it maps to, and the evidence behind each claim, over MCP and REST.