IA-2(6) Access to Accounts —separate Device
Control enhancement of IA-2 Identification and Authentication (Organizational Users)
Control
Implement multi-factor authentication for [Assignment: Selection (one-or-more): local | network | remote] access to [Assignment: Selection (one-or-more): privileged accounts | non-privileged accounts] such that:
One of the factors is provided by a device separate from the system gaining access; and
The device meets [Assignment: strength of mechanism requirements].
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.
Related controls
Need IA-2(6) implemented and evidenced?
We assess where you stand against this control, document the gap, and build the remediation plan your auditor and your board will both accept.
Control catalog and framework text on this page is reproduced from official NIST publications — a public-domain work of the U.S. Government (17 U.S.C. §105). Maverc commentary, groupings, and readiness guidance are our own and are not part of any NIST publication.