FedRAMP High IA-2(1): MFA to Privileged Accounts

What else in your programme already covers this

This control maps to 35 controls across 24 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 · 3 controls

8.4.1 8.4.1 MFA for non-console administrative CDE access
8.4.3 8.4.3 MFA for remote access that could reach CDE
8.5.1 8.5.1 MFA system resistant to replay and bypass

SOC 2 · 3 controls

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

UK Cyber Essentials · 3 controls

CE-AC.7 MFA for Administrative Accounts
CE-AC.8 Passwordless Authentication
CE-SC.6 Multi-Factor Authentication for Cloud Services

ACSC Essential Eight · 2 controls

E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2
E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP02 Secure account root user and properties
SEC02-BP01 Use strong sign-in mechanisms

Azure Security Benchmark · 2 controls

ASBv3-IM-2 Protect identity and authentication systems
IM-6 Use strong authentication controls

CIS Controls v8 · 2 controls

CIS-6.4 Require MFA for Remote Network Access
CIS-6.5 Require MFA for Administrative Access

CMMC 2.0 · 2 controls

IA.L2-3.5.3 Multifactor Authentication
MA.L2-3.7.5 Nonlocal Maintenance

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-13 Prefer Strong Authentication Where Possible

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-20 Multi-factor authentication (Essential)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

C5 (Germany) · 1 control

C5-IDM-09 Authentication mechanisms

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-IAM-14 Strong Authentication

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-171 Rev 3 · 1 control

03.05.03 Multi-Factor Authentication

NIST SP 800-172 · 1 control

3.5.3e Prohibit Connection of Unknown or Unverified System Components

NIST SP 800-53 Rev 5 · 1 control

NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)

NIST SP 800-53 Rev 5 HIGH · 1 control

IA-2(1) IA-2(1) Identification and Authentication (Organizational Users) | Multi-factor Authentication to Privileged Accounts

NIST SP 800-53 Rev 5 LOW · 1 control

IA-2(1) IA-2(1) Identification and Authentication (Organizational Users) | Multi-factor Authentication to Privileged Accounts

NIST SP 800-53 Rev 5 MODERATE · 1 control

IA-2(1) IA-2(1) Identification and Authentication (Organizational Users) | Multi-factor Authentication to Privileged Accounts

NIST SP 800-66 Rev 2 · 1 control

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.

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High IA-2(1) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

If you hold C5 (Germany)29% covered · 291 gaps

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. 6 were rejected on the C5 (Germany) pair alone.

See the released pairs, $299 each Browse the graph free