← IA-2
IA-2(6) IA · Identification and Authentication

Access to Accounts —separate Device

LOW MODERATE HIGH
1 Overlay 1 Related Control
Graph
Export ▾

Requirements NIST SOURCE

Implement multi-factor authentication for [one of: local; network; remote] access to [one of: privileged accounts; non-privileged accounts] such that:

Discussion (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.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for IA-2(6) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. one or more of the following PARAMETER VALUES is/are selected: {local; network; remote};
  2. one or more of the following PARAMETER VALUES is/are selected: {privileged accounts; non-privileged accounts};
  3. the strength of mechanism requirements to be enforced by a device separate from the system gaining access to accounts is defined;
  4. multi-factor authentication is implemented for <IA-02(06)_ODP[01] SELECTED PARAMETER VALUES> access to <IA-02(06)_ODP[02] SELECTED PARAMETER VALUES> such that one of the factors is provided by a device separate from the system gaining access;
  5. multi-factor authentication is implemented for <IA-02(06)_ODP[01] SELECTED PARAMETER VALUES> access to <IA-02(06)_ODP[02] SELECTED PARAMETER VALUES> such that the device meets <IA-02(06)_ODP[03] strength of mechanism requirements>.

Examine

[SELECT FROM: Identification and authentication policy; system security plan; procedures addressing user identification and authentication; system design documentation; system configuration settings and associated documentation; system audit records; list of system accounts; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with system operations responsibilities; organizational personnel with account management responsibilities; organizational personnel with information security responsibilities; system/network administrators; system developers].

Test

[SELECT FROM: Mechanisms supporting and/or implementing multi-factor authentication capability].

Overlays

Showing the OT/ICS overlay for the parent control IA-2 — see the IA-2(6) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (8) (12)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (8) (12)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (5) (8) (12)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for IA-2(6). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • Identification and authentication policy
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • Mechanisms supporting and/or implementing multi-factor authentication capability

Other Records

  • procedures addressing user identification and authentication
  • system audit records
  • list of system accounts
  • other relevant documents or records