IA-2 (6) - Access to Accounts — Separate Device
Control requirements
IA-2 (6) (a)
Implement multi-factor authentication for [IBM Assignment: local, network and remote] access to [IBM Assignment: privileged accounts; non-privileged accounts] such that: One of the factors is provided by a device separate from the system gaining access.
IA-2 (6) (b)
Implement multi-factor authentication for [IBM Assignment: local, network and remote] access to [IBM Assignment: privileged accounts; non-privileged accounts] such that: The device meets [IBM Assignment: FIPS 140-2 level 2 capable or above or equivalent].
NIST supplemental guidance
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.