STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to DBN-6300 NDM Security Technical Implementation Guide

V-255549

CAT II (Medium)

The DBN-6300 must use multifactor authentication for network access (remote and nonlocal) to privileged accounts.

Rule ID

SV-255549r960972_rule

STIG

DBN-6300 NDM Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000765

Discussion

Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) something a user is (e.g., biometric). Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., LAN, WAN, or the Internet). DoD has mandated the use of the Common Access Card (CAC) token/credential to support identity management and personal authentication for systems covered under HSPD 12. DoD recommended architecture for network devices is for system administrators to authenticate using an authentication server using the DoD CAC credential with DoD-approved PKI. This requirement also applies to the account of last resort and the root account only if non-local access via the network is enabled for these accounts (not recommended). This control does not apply to the account of last resort or root account. DoD prohibits local user accounts on the device, except for an account of last resort and (where applicable) a root account.

Check Content

Multifactor authentication is managed through the LDAP server. Verify that LDAP (remote authentication) is enabled.

Navigate to Settings >> Initial Configuration >> Authentication.

Verify that LDAP server information is correctly entered and enabled.

Verify that "Native takes precedence" is disabled.

If LDAP server is not connected, or if "Native takes precedence" is not disabled, this is a finding.

Fix Text

Configure the LDAP server to be connected correctly and disable "Native takes precedence".

Navigate to Settings >> Initial Configuration >> Authentication.

Enter the correct LDAP server information and press the "Enable" button.

Press the "Native takes precedence" "Disable" button (if it is not already disabled).