IA-2 (06)—Identification and Authentication (organizational Users) | Access to Accounts --separate Device

Moderate

High

>Control Description

Implement multi-factor authentication for [Selection (one or more): local; network; remote] access to [Selection (one or more): privileged accounts; non-privileged accounts] such that: (a) One of the factors is provided by a device separate from the system gaining access; and (b) The device meets ⚙organization-defined strength of mechanism requirements.

>FedRAMP Baseline Requirements

Parameter Values

Additional Requirements and Guidance

IA-2 (6) Guidance: PIV=separate device. Please refer to NIST SP 800-157 Guidelines for Derived Personal Identity Verification (PIV) Credentials. IA-2 (6) Guidance: See SC-13 Guidance for more information on FIPS-validated or NSA-approved cryptography.

>Discussion

The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multi-factor authentication is to reduce the likelihood of compromising authenticators or credentials stored on the system. Adversaries may be able to compromise such authenticators or credentials and subsequently impersonate authorized users. Implementing one of the factors on a separate device (e.g., a hardware token), provides a greater strength of mechanism and an increased level of assurance in the authentication process.

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

•What formal policies and procedures govern the implementation of IA-2(6) (Access To Accounts --Separate Device)?
•Who are the designated roles responsible for implementing, maintaining, and monitoring IA-2(6)?
•How frequently is the IA-2(6) policy reviewed and updated, and what triggers policy changes?
•What governance structure ensures IA-2(6) requirements are consistently applied across all systems?

Technical Implementation:

•Describe the specific technical mechanisms or controls used to enforce IA-2(6) requirements.
•What automated tools, systems, or technologies are deployed to implement IA-2(6)?
•How is IA-2(6) integrated into your system architecture and overall security posture?
•What configuration settings, parameters, or technical specifications enforce IA-2(6) requirements?

Evidence & Documentation:

•What documentation demonstrates the complete implementation of IA-2(6)?
•What audit logs, records, reports, or monitoring data validate IA-2(6) compliance?
•Can you provide evidence of periodic reviews, assessments, or testing of IA-2(6) effectiveness?
•What artifacts would you present during a FedRAMP assessment to demonstrate IA-2(6) compliance?

Ask AI

Configure your API key to use AI features.