Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

DBN-6300 NDM Security Technical Implementation Guide

V1R2 · · · Released 24 Jul 2024 · 59 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
Supporting documents DISA companion ZIP · 1.3 MB 4 PDFs

Bundled by DISA alongside this STIG release: overview, revision history, and readme files. Download the full archive or open an individual PDF.

Download full ZIP U_DBN-6300_Y24M07_STIG.zip
Digest of Updates vs. V1R1 · 12 Sep 2017 +59 −58

Comparison against the immediately-prior release (V1R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 59

  • V-255529 High The DBN-6300 must provide automated support for account management functions.
  • V-255530 Medium The DBN-6300 must automatically audit account creation.
  • V-255531 Medium The DBN-6300 must automatically audit account modification.
  • V-255532 Medium The DBN-6300 must automatically audit account removal actions.
  • V-255533 Medium The DBN-6300 must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
  • V-255534 Low The DBN-6300 must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.
  • V-255535 Medium The DBN-6300 must provide audit record generation capability for DoD-defined auditable events within the DBN-6300.
  • V-255536 Low The DBN-6300 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the audit log.
  • V-255537 Medium The DBN-6300 must generate log records when successful attempts to access privileges occur.
  • V-255538 Low The DBN-6300 must initiate session auditing upon startup.
  • V-255539 Low The DBN-6300 must produce audit log records containing sufficient information to establish what type of event occurred.
  • V-255540 Low The DBN-6300 must produce audit records containing information to establish when (date and time) the events occurred.
  • V-255541 Low The DBN-6300 must produce audit records containing information to establish where the events occurred.
  • V-255542 Low The DBN-6300 must produce audit log records containing information to establish the source of events.
  • V-255543 Low The DBN-6300 must produce audit records that contain information to establish the outcome of the event.
  • V-255544 Low The DBN-6300 must generate audit records containing information that establishes the identity of any individual or process associated with the event.
  • V-255545 Low The DBN-6300 must generate audit records containing the full-text recording of privileged commands.
  • V-255546 Medium The DBN-6300 must use internal system clocks to generate time stamps for audit records.
  • V-255547 Low The DBN-6300 must back up audit records at least every seven days onto a different system or system component than the system or component being audited.
  • V-255548 High The DBN-6300 must uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators).
  • V-255549 Medium The DBN-6300 must use multifactor authentication for network access (remote and nonlocal) to privileged accounts.
  • V-255550 Medium The DBN-6300 must use multifactor authentication for local access to privileged accounts.
  • V-255551 Medium The DBN-6300 must implement replay-resistant authentication mechanisms for network access to privileged accounts.
  • V-255552 Medium The DBN-6300 must enforce a minimum 15-character password length.
  • V-255553 Medium The DBN-6300 must prohibit password reuse for a minimum of five generations.
  • V-255554 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one upper-case character be used.
  • V-255555 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one lower-case character be used.
  • V-255556 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one numeric character be used.
  • V-255557 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one special character be used.
  • V-255558 Medium The DBN-6300 must enforce 24 hours/1 day as the minimum password lifetime.
  • V-255559 Medium The DBN-6300 must enforce a 60-day maximum password lifetime restriction.
  • V-255560 High The DBN-6300 must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements.
  • V-255561 Medium The DBN-6300 must reveal error messages only to authorized individuals (ISSO, ISSM, and SA).
  • V-255562 Medium The DBN-6300 must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.
  • V-255563 Medium The DBN-6300 must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.
  • V-255564 Medium The DBN-6300 must automatically audit account enabling actions.
  • V-255565 Medium The DBN-6300 must be compliant with at least one IETF Internet standard authentication protocol.
  • V-255566 Medium The DBN-6300 must audit the execution of privileged functions.
  • V-255567 Low The DBN-6300 must provide the capability for organization-identified individuals or roles to change the auditing to be performed based on all selectable event criteria within near real time.
  • V-255568 Medium The DBN-6300 must compare internal information system clocks at least every 24 hours with an authoritative time server.
  • V-255569 Medium The DBN-6300 must synchronize its internal system clock to the NTP server when the time difference is greater than one second.
  • V-255570 Medium The DBN-6300 must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).
  • V-255571 Medium The DBN-6300 must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
  • V-255572 Medium The DBN-6300 must audit the enforcement actions used to restrict access associated with changes to the device.
  • V-255573 Medium Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications.
  • V-255574 Medium Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.
  • V-255575 Medium The DBN-6300 must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.
  • V-255576 Medium The DBN-6300 must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.
  • V-255577 Medium The DBN-6300 must generate audit records when successful/unsuccessful logon attempts occur.
  • V-255578 Medium The DBN-6300 must generate audit records for privileged activities or other system-level access.
  • V-255579 Medium The DBN-6300 must generate audit records showing starting and ending time for administrator access to the system.
  • V-255580 Medium The DBN-6300 must generate audit records when concurrent logons from different workstations occur.
  • V-255581 Medium The DBN-6300 must generate audit records for all account creation, modification, disabling, and termination events.
  • V-255582 Medium The DBN-6300 must off-load audit records onto a different system or media than the system being audited.
  • V-255583 Medium The DBN-6300 must generate audit log events for a locally developed list of auditable events.
  • V-255584 Medium Accounts for device management must be configured on the authentication server and not the network device itself, except for the account of last resort.
  • V-255585 Medium The DBN-6300 must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
  • V-255586 High The DBN-6300 must be configured to send log data to a syslog server for the purpose of forwarding alerts to the administrators and the ISSO.
  • V-264431 High The DBN-6300 NDM must be using a version supported by the vendor.

Removed rules 58

  • V-64975 High The DBN-6300 must provide automated support for account management functions.
  • V-64983 Medium The DBN-6300 must automatically audit account creation.
  • V-64985 Medium The DBN-6300 must automatically audit account modification.
  • V-64987 Medium The DBN-6300 must be compliant with at least one IETF Internet standard authentication protocol.
  • V-64989 Medium The DBN-6300 must automatically audit account removal actions.
  • V-64991 Medium The DBN-6300 must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
  • V-64993 Low The DBN-6300 must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.
  • V-64995 Medium The DBN-6300 must generate audit log events for a locally developed list of auditable events.
  • V-64997 Medium The DBN-6300 must provide audit record generation capability for DoD-defined auditable events within the DBN-6300.
  • V-76927 Low The DBN-6300 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the audit log.
  • V-76929 Medium The DBN-6300 must generate log records when successful attempts to access privileges occur.
  • V-76931 Low The DBN-6300 must initiate session auditing upon startup.
  • V-76933 Low The DBN-6300 must produce audit log records containing sufficient information to establish what type of event occurred.
  • V-76935 Low The DBN-6300 must produce audit records containing information to establish when (date and time) the events occurred.
  • V-76937 Low The DBN-6300 must produce audit records containing information to establish where the events occurred.
  • V-76939 Low The DBN-6300 must produce audit log records containing information to establish the source of events.
  • V-76941 Low The DBN-6300 must produce audit records that contain information to establish the outcome of the event.
  • V-76943 Low The DBN-6300 must generate audit records containing information that establishes the identity of any individual or process associated with the event.
  • V-76945 Low The DBN-6300 must generate audit records containing the full-text recording of privileged commands.
  • V-76947 Medium The DBN-6300 must use internal system clocks to generate time stamps for audit records.
  • V-76949 Low The DBN-6300 must back up audit records at least every seven days onto a different system or system component than the system or component being audited.
  • V-76951 High The DBN-6300 must uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators).
  • V-76953 Medium The DBN-6300 must use multifactor authentication for network access (remote and nonlocal) to privileged accounts.
  • V-76955 Medium The DBN-6300 must use multifactor authentication for local access to privileged accounts.
  • V-76957 Medium The DBN-6300 must implement replay-resistant authentication mechanisms for network access to privileged accounts.
  • V-76959 Medium The DBN-6300 must enforce a minimum 15-character password length.
  • V-76961 Medium The DBN-6300 must prohibit password reuse for a minimum of five generations.
  • V-76963 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one upper-case character be used.
  • V-76965 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one lower-case character be used.
  • V-76967 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one numeric character be used.
  • V-76969 Medium If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one special character be used.
  • V-76971 Medium The DBN-6300 must enforce 24 hours/1 day as the minimum password lifetime.
  • V-76973 Medium The DBN-6300 must enforce a 60-day maximum password lifetime restriction.
  • V-76975 High The DBN-6300 must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements.
  • V-76977 Medium The DBN-6300 must reveal error messages only to authorized individuals (ISSO, ISSM, and SA).
  • V-76979 Medium The DBN-6300 must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.
  • V-76981 Medium The DBN-6300 must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.
  • V-76983 Medium The DBN-6300 must automatically audit account enabling actions.
  • V-76985 Medium The DBN-6300 must audit the execution of privileged functions.
  • V-76987 Low The DBN-6300 must provide the capability for organization-identified individuals or roles to change the auditing to be performed based on all selectable event criteria within near real time.
  • V-76989 Medium The DBN-6300 must compare internal information system clocks at least every 24 hours with an authoritative time server.
  • V-76991 Medium The DBN-6300 must synchronize its internal system clock to the NTP server when the time difference is greater than one second.
  • V-76993 Medium The DBN-6300 must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).
  • V-76995 Medium The DBN-6300 must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
  • V-76997 Medium The DBN-6300 must audit the enforcement actions used to restrict access associated with changes to the device.
  • V-76999 Medium Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications.
  • V-77001 Medium Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.
  • V-77003 Medium The DBN-6300 must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.
  • V-77005 Medium The DBN-6300 must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.
  • V-77007 Medium The DBN-6300 must generate audit records when successful/unsuccessful logon attempts occur.
  • V-77009 Medium The DBN-6300 must generate audit records for privileged activities or other system-level access.
  • V-77011 Medium The DBN-6300 must generate audit records showing starting and ending time for administrator access to the system.
  • V-77013 Medium The DBN-6300 must generate audit records when concurrent logons from different workstations occur.
  • V-77015 Medium The DBN-6300 must generate audit records for all account creation, modification, disabling, and termination events.
  • V-77017 Medium The DBN-6300 must off-load audit records onto a different system or media than the system being audited.
  • V-77019 High The DBN-6300 must be configured to send log data to a syslog server for the purpose of forwarding alerts to the administrators and the ISSO.
  • V-77021 Medium Accounts for device management must be configured on the authentication server and not the network device itself, except for the account of last resort.
  • V-77023 Medium The DBN-6300 must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
Sort by
c
The DBN-6300 must provide automated support for account management functions.
AC-2 - High - CCI-000015 - V-255529 - SV-255529r961863_rule
RMF Control
AC-2
Severity
H
CCI
CCI-000015
Version
DBNW-DM-000006
Vuln IDs
  • V-255529
  • V-64975
Rule IDs
  • SV-255529r961863_rule
  • SV-79465
If account management functions are not automatically enforced, an attacker could gain privileged access to a vital element of the network security architecture.
Checks: C-59202r873041_chk

Verify that the LDAP authentication server is configured correctly. Navigate to Settings >> Initial Configuration >> Authentication. Verify that the LDAP server entry is correct and that the button for "LDAP Based Authentication" is enabled. Verify that the "Native takes precedence" button is set to "Disabled". If the LDAP server entry is not present and enabled, and the "Native takes precedence" button is not set to "Disabled", this is a finding.

Fix: F-59145r873042_fix

Navigate to Settings >> Initial Configuration >> Authentication. Enter the correct LDAP server entry. Press the button for "LDAP Based Authentication" so that it is enabled. If necessary, press the "Disabled" button for "Native takes precedence". Press the "Commit" button.

b
The DBN-6300 must automatically audit account creation.
AC-2 - Medium - CCI-000018 - V-255530 - SV-255530r960777_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000018
Version
DBNW-DM-000009
Vuln IDs
  • V-255530
  • V-64983
Rule IDs
  • SV-255530r960777_rule
  • SV-79473
Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. 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. With the DB-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59203r873044_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account creation. Confirm the presence of a syslog message on the syslog server containing the information for successful account creation. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a successful account creation has just occurred is not there, this is a finding.

Fix: F-59146r873045_fix

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account creation. Confirm the presence of a syslog message on the syslog server containing the information for successful account creation.

b
The DBN-6300 must automatically audit account modification.
AC-2 - Medium - CCI-001403 - V-255531 - SV-255531r960780_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001403
Version
DBNW-DM-000010
Vuln IDs
  • V-255531
  • V-64985
Rule IDs
  • SV-255531r960780_rule
  • SV-79475
Upon gaining access to a network device, an attacker will often attempt to create a persistent method of reestablishing access. One way to accomplish this is to modify an account. 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. Account management functions include assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59204r873047_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account modification. Confirm the presence of a syslog message on the syslog server containing the information for successful account modification. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a successful account modification has just occurred is not there, this is a finding.

Fix: F-59147r873048_fix

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account modification. Confirm the presence of a syslog message on the syslog server containing the information for successful account modification.

b
The DBN-6300 must automatically audit account removal actions.
AC-2 - Medium - CCI-001405 - V-255532 - SV-255532r960786_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001405
Version
DBNW-DM-000012
Vuln IDs
  • V-255532
  • V-64989
Rule IDs
  • SV-255532r960786_rule
  • SV-79479
Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will support account management procedures. When device management accounts are terminated, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59205r873050_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account removal. Confirm the presence of a syslog message on the syslog server containing the information for successful account removal. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a successful account removal has just occurred is not there, this is a finding.

Fix: F-59148r873051_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
AC-7 - Medium - CCI-000044 - V-255533 - SV-255533r960840_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
DBNW-DM-000015
Vuln IDs
  • V-255533
  • V-64991
Rule IDs
  • SV-255533r960840_rule
  • SV-79481
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. It is possible to set a time-to-retry variable, as well as number of retries during that lockout timeout variable, within the DBN-6300.
Checks: C-59206r873053_chk

To see if the system will lock out the user if three failed logon attempts occur within 15 minutes, attempt to log on as a user three times in succession and deliberately fail (by entering the wrong password). After the third attempt, the user will be locked out from retrying until the oldest attempt (by time) ages out past the 15-minute mark and then will be allowed to try again. If the user is not locked out after three failed logon attempts within 15 minutes, this is a finding.

Fix: F-59149r873054_fix

Set a time-to-retry variable, as well as number of retries during that lockout timeout variable, within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": { "local": { "policies": { "passwordFail": { "enable": true, "threshold": 3, "windowSeconds": 60 }}}}}

a
The DBN-6300 must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.
AU-10 - Low - CCI-000166 - V-255534 - SV-255534r960864_rule
RMF Control
AU-10
Severity
L
CCI
CCI-000166
Version
DBNW-DM-000021
Vuln IDs
  • V-255534
  • V-64993
Rule IDs
  • SV-255534r960864_rule
  • SV-79483
This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration management process. All configuration changes to the network device are logged, and administrators authenticate with two-factor authentication before gaining administrative access. Together, these processes will ensure the administrators can be held accountable for the configuration changes they implement. To meet this requirement, the network device must log administrator access and activity. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59207r873056_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any account function. Confirm the presence of a syslog message on the syslog server containing the information for whatever that account function represented. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information for the account action that took place is not present, this is a finding.

Fix: F-59150r873057_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must provide audit record generation capability for DoD-defined auditable events within the DBN-6300.
AU-12 - Medium - CCI-000169 - V-255535 - SV-255535r961863_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
DBNW-DM-000023
Vuln IDs
  • V-255535
  • V-64997
Rule IDs
  • SV-255535r961863_rule
  • SV-79487
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., process, module). Certain specific device functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the device will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and (iii) All account creation, modification, disabling, and termination actions. With the DB-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59208r873059_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any account function. Confirm the presence of a syslog message on the syslog server containing the information for whatever that account function represented. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information for the account action that took place is not present, this is a finding.

Fix: F-59151r873060_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the audit log.
AU-12 - Low - CCI-000171 - V-255536 - SV-255536r961863_rule
RMF Control
AU-12
Severity
L
CCI
CCI-000171
Version
DBNW-DM-000024
Vuln IDs
  • V-255536
  • V-76927
Rule IDs
  • SV-255536r961863_rule
  • SV-91623
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Checks: C-59209r873062_chk

Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories can be checked in accordance with the role assigned. For an administrator, the admin role should allow all categories to be checked for Audit Log, Syslog, and Audit Console. Log off, log on again, and attempt to repeat the process logged on as a "lesser" user that does not have privileges to configure audit. Attempt to modify the audit log categories. This should fail. Following this verification, if it is possible for a non-privileged user with no audit log modification privileges to modify log functions, this is a finding.

Fix: F-59152r873063_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate log records when successful attempts to access privileges occur.
AU-12 - Medium - CCI-000172 - V-255537 - SV-255537r960885_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000025
Vuln IDs
  • V-255537
  • V-76929
Rule IDs
  • SV-255537r960885_rule
  • SV-91625
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). It is not possible to perform unsuccessful commands in the UI web management interface since it is a GUI interface. Unauthorized menu items/commands are not visible.
Checks: C-59210r873065_chk

Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and that the Audit Configuration Categories can be checked in accordance with the role assigned. For an administrator, the admin role should allow all categories to be checked for Audit Log, Syslog, and Audit Console. Log off, log on again, and attempt to repeat the process logged on as a "lesser" user that does not have privileges to configure audit. Attempt to modify the audit log categories. This should fail. Following this verification, if it is possible for a non-privileged user with no audit log modification privileges to modify log functions, this is a finding.

Fix: F-59153r873066_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must initiate session auditing upon startup.
AU-14 - Low - CCI-001464 - V-255538 - SV-255538r960888_rule
RMF Control
AU-14
Severity
L
CCI
CCI-001464
Version
DBNW-DM-000026
Vuln IDs
  • V-255538
  • V-76931
Rule IDs
  • SV-255538r960888_rule
  • SV-91627
If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.
Checks: C-59211r873068_chk

Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories can be checked in accordance with the role assigned. For an administrator, the admin role should allow all categories to be checked for Audit Log, Syslog, and Audit Console. Log off and log on to the system again. Examine the message at the syslog server. If there is no message, or no information in the message containing data showing the logon, this is a finding.

Fix: F-59154r873069_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must produce audit log records containing sufficient information to establish what type of event occurred.
AU-3 - Low - CCI-000130 - V-255539 - SV-255539r960891_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000130
Version
DBNW-DM-000027
Vuln IDs
  • V-255539
  • V-76933
Rule IDs
  • SV-255539r960891_rule
  • SV-91629
It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Associating event types with detected events in the application and audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network device. Without this capability, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59212r873071_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the DBN-6300 is not connected to the syslog server, this is a finding.

Fix: F-59155r873072_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must produce audit records containing information to establish when (date and time) the events occurred.
AU-3 - Low - CCI-000131 - V-255540 - SV-255540r960894_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000131
Version
DBNW-DM-000028
Vuln IDs
  • V-255540
  • V-76935
Rule IDs
  • SV-255540r960894_rule
  • SV-91631
It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Logging the date and time of each detected event provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network device. In order to establish and correlate the series of events leading up to an outage or attack, it is imperative the date and time are recorded in all log records.
Checks: C-59213r873074_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing date and time information for when the event occurred. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain date and time information, this is a finding.

Fix: F-59156r873075_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must produce audit records containing information to establish where the events occurred.
AU-3 - Low - CCI-000132 - V-255541 - SV-255541r960897_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000132
Version
DBNW-DM-000029
Vuln IDs
  • V-255541
  • V-76937
Rule IDs
  • SV-255541r960897_rule
  • SV-91633
In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as device hardware components, device software modules, session identifiers, filenames, host names, and functionality. Location of events includes hardware components, device software module, session identifiers, filenames, host names, and functionality.
Checks: C-59214r873077_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing information to establish where the event occurred. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain information to establish where the event occurred, this is a finding.

Fix: F-59157r873078_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must produce audit log records containing information to establish the source of events.
AU-3 - Low - CCI-000133 - V-255542 - SV-255542r960900_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000133
Version
DBNW-DM-000030
Vuln IDs
  • V-255542
  • V-76939
Rule IDs
  • SV-255542r960900_rule
  • SV-91635
In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the source of the event. The source may be a component, module, or process within the device or an external session, administrator, or device. Location of events includes hardware components, device software module, processes within the device or external session, administrator ID, or device.
Checks: C-59215r873080_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing information to establish the source of events. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain information to establish the source of events, this is a finding.

Fix: F-59158r873081_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must produce audit records that contain information to establish the outcome of the event.
AU-3 - Low - CCI-000134 - V-255543 - SV-255543r960903_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000134
Version
DBNW-DM-000031
Vuln IDs
  • V-255543
  • V-76941
Rule IDs
  • SV-255543r960903_rule
  • SV-91637
Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the device after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.
Checks: C-59216r873083_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing information to establish the outcome of the event. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain information to establish the outcome of the event, this is a finding.

Fix: F-59159r873084_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must generate audit records containing information that establishes the identity of any individual or process associated with the event.
AU-3 - Low - CCI-001487 - V-255544 - SV-255544r960906_rule
RMF Control
AU-3
Severity
L
CCI
CCI-001487
Version
DBNW-DM-000032
Vuln IDs
  • V-255544
  • V-76943
Rule IDs
  • SV-255544r960906_rule
  • SV-91639
Without information that establishes the identity of the subjects (i.e., administrators or processes acting on behalf of administrators) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Event identifiers (if authenticated or otherwise known) include but are not limited to user database tables, primary key values, user names, or process identifiers.
Checks: C-59217r873086_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing information to establish the identity of any individual or process associated with the event. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain information to establish the identity of any individual or process associated with the event, this is a finding.

Fix: F-59160r873087_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must generate audit records containing the full-text recording of privileged commands.
AU-3 - Low - CCI-000135 - V-255545 - SV-255545r960909_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000135
Version
DBNW-DM-000033
Vuln IDs
  • V-255545
  • V-76945
Rule IDs
  • SV-255545r960909_rule
  • SV-91641
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the data and the environment in which it resides). At a minimum, the organization must audit full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
Checks: C-59218r873089_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an auditable action. Confirm the presence of a syslog message on the syslog server containing the full-text recording of privileged commands. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message for the event does not contain the full-text recording of privileged commands, this is a finding.

Fix: F-59161r873090_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must use internal system clocks to generate time stamps for audit records.
AU-8 - Medium - CCI-000159 - V-255546 - SV-255546r960927_rule
RMF Control
AU-8
Severity
M
CCI
CCI-000159
Version
DBNW-DM-000036
Vuln IDs
  • V-255546
  • V-76947
Rule IDs
  • SV-255546r960927_rule
  • SV-91643
In order to determine what is happening within the network infrastructure or to resolve and trace an attack, the network device must support the organization's capability to correlate the audit log data from multiple network devices to acquire a clear understanding of events. In order to correlate auditable events, time stamps are needed on all of the log records. If the internal clock is not used, the system may not be able to provide time stamps for log messages. Additionally, externally generated time stamps may not be accurate. Applications can use the capability of an operating system or purpose-built module for this purpose. (Note that the internal clock is required to be synchronized with authoritative time sources by other requirements.)
Checks: C-59219r873092_chk

Verify the configuration of the NTP server. Navigate to Settings >> Initial Configuration >> Time. View the "Time" settings window. If an NTP server address is not configured, this is a finding.

Fix: F-59162r873093_fix

Configure the NTP server on the device. The time difference is part of the NTP protocol and is not configurable. Navigate to Settings >> Initial Configuration >> Time. In the "Time" settings window, select the "NTP" button and enter the NTP server address. Click on "Commit".

a
The DBN-6300 must back up audit records at least every seven days onto a different system or system component than the system or component being audited.
AU-9 - Low - CCI-001348 - V-255547 - SV-255547r961863_rule
RMF Control
AU-9
Severity
L
CCI
CCI-001348
Version
DBNW-DM-000043
Vuln IDs
  • V-255547
  • V-76949
Rule IDs
  • SV-255547r961863_rule
  • SV-91645
Protection of log data includes assuring log data is not accidentally lost or deleted. Regularly backing up audit records to a different system or onto separate media than the system being audited helps to ensure that, in the event of a catastrophic system failure, the audit records will be retained. Backup of audit records helps to ensure that a compromise of the information system being audited does not also result in a compromise of the audit records. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59220r873095_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process a logon. Confirm the presence of a syslog message on the syslog server containing the date and time of this last logon. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a logon had just occurred is not there, this is a finding.

Fix: F-59163r873096_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog.

c
The DBN-6300 must uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators).
AC-2 - High - CCI-001358 - V-255548 - SV-255548r960969_rule
RMF Control
AC-2
Severity
H
CCI
CCI-001358
Version
DBNW-DM-000049
Vuln IDs
  • V-255548
  • V-76951
Rule IDs
  • SV-255548r960969_rule
  • SV-91647
To ensure accountability and prevent unauthenticated access, organizational administrators must be uniquely identified and authenticated for all network management accesses to prevent potential misuse and compromise of the system.
Checks: C-59221r873098_chk

Verify that there is one local account configured on the DBN-6300. Navigate to Settings >> User Management. Verify that there is one account on the system and that this account has unrestricted privileges. If no local account is configured in this way, or more than one account is configured locally, this is a finding.

Fix: F-59164r873099_fix

Verify that there is one local account configured on the DBN-6300. Navigate to Settings >> User Management. Verify that there is one account on the system, and that this account has unrestricted privileges. If there is more than one local account, delete the additional accounts by clicking on the trashcan icon on the far right of the account(s) in question, until all accounts are deleted except for one administrative account with unlimited privileges. If there is no local account with administrative or unlimited privileges, create one using the following steps: Navigate to Settings >> User Management >> Users. Click on the New User button. Enter a username for Username, a name (optional), a 15-character (minimum) complex password, and the role of either Admin or Unrestricted. After all entries are filled, click "Save".

b
The DBN-6300 must use multifactor authentication for network access (remote and nonlocal) to privileged accounts.
IA-2 - Medium - CCI-000765 - V-255549 - SV-255549r960972_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000765
Version
DBNW-DM-000050
Vuln IDs
  • V-255549
  • V-76953
Rule IDs
  • SV-255549r960972_rule
  • SV-91649
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.
Checks: C-59222r873101_chk

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: F-59165r873102_fix

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).

b
The DBN-6300 must use multifactor authentication for local access to privileged accounts.
IA-2 - Medium - CCI-000767 - V-255550 - SV-255550r961863_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000767
Version
DBNW-DM-000051
Vuln IDs
  • V-255550
  • V-76955
Rule IDs
  • SV-255550r961863_rule
  • SV-91651
Multifactor authentication is defined as 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). To ensure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Applications integrating with the DoD Active Directory and utilizing the DoD CAC are examples of compliant multifactor authentication solutions. 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.
Checks: C-59223r873104_chk

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: F-59166r873105_fix

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).

b
The DBN-6300 must implement replay-resistant authentication mechanisms for network access to privileged accounts.
IA-2 - Medium - CCI-001941 - V-255551 - SV-255551r960993_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001941
Version
DBNW-DM-000053
Vuln IDs
  • V-255551
  • V-76957
Rule IDs
  • SV-255551r960993_rule
  • SV-91653
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.
Checks: C-59224r873107_chk

Verify SSL is configured to use SSL for the web management tool. Navigate to Settings >> Initial Configuration >> Security. If the check box for "Enforce secure communications (SSL) for user interface access" is not checked, this is a finding.

Fix: F-59167r873108_fix

Enable SSL for use with the web management tool. Navigate to Settings >> Initial Configuration >> Security. Select the check box for "Enforce secure communications (SSL) for user interface access". Click on "Commit".

b
The DBN-6300 must enforce a minimum 15-character password length.
IA-5 - Medium - CCI-000205 - V-255552 - SV-255552r984092_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000205
Version
DBNW-DM-000055
Vuln IDs
  • V-255552
  • V-76959
Rule IDs
  • SV-255552r984092_rule
  • SV-91655
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Since the device cannot be configured for password complexity, not having a strong password can result in the success of a brute force attack, which would give immediate access to a privileged system.
Checks: C-59225r873110_chk

Verify the minimum password length is set to "15". Navigate to Settings >> Initial Configuration >> Authentication. If the "Minimum User Password Length" is not set to "15", this is a finding.

Fix: F-59168r873111_fix

Configure the minimum password length to "15". Navigate to Settings >> Initial Configuration >> Authentication. Enter "15" in the "Minimum User Password Length". Click on "Commit".

b
The DBN-6300 must prohibit password reuse for a minimum of five generations.
IA-5 - Medium - CCI-000200 - V-255553 - SV-255553r961863_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000200
Version
DBNW-DM-000056
Vuln IDs
  • V-255553
  • V-76961
Rule IDs
  • SV-255553r961863_rule
  • SV-91657
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. To meet password policy requirements, passwords need to be changed at specific policy-based intervals. If the network device allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.
Checks: C-59226r873113_chk

To see if the system prohibits password reuse attempt to change the users password deliberately reusing the last passwords used. The user should fail to update their password for the last five passwords that their account has used. If the user is able to reuse their password before using five different password, this is a finding.

Fix: F-59169r873114_fix

Set a password-reuse variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordReuse": {"check": true,"numberToKeep": 5 }}}}}

b
If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one upper-case character be used.
IA-5 - Medium - CCI-000192 - V-255554 - SV-255554r984095_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000192
Version
DBNW-DM-000057
Vuln IDs
  • V-255554
  • V-76963
Rule IDs
  • SV-255554r984095_rule
  • SV-91659
Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-59227r873116_chk

To see if the system requires password complexity attempt to change your password to a non-conforming password. If the user is able to change their password without meeting the requirement, this is a finding.

Fix: F-59170r873117_fix

Set the password-complexity variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordQuality": {"owasp": {"enable": true,"allowPassphrases": false }}}}}}

b
If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one lower-case character be used.
IA-5 - Medium - CCI-000193 - V-255555 - SV-255555r984098_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000193
Version
DBNW-DM-000058
Vuln IDs
  • V-255555
  • V-76965
Rule IDs
  • SV-255555r984098_rule
  • SV-91661
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-59228r873119_chk

To see if the system requires password complexity attempt to change your password to a non-conforming password. If the user is able to change their password without meeting the requirement, this is a finding.

Fix: F-59171r873120_fix

Set the password-complexity variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordQuality": {"owasp": {"enable": true,"allowPassphrases": false }}}}}}

b
If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one numeric character be used.
IA-5 - Medium - CCI-000194 - V-255556 - SV-255556r984099_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000194
Version
DBNW-DM-000059
Vuln IDs
  • V-255556
  • V-76967
Rule IDs
  • SV-255556r984099_rule
  • SV-91663
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-59229r873122_chk

To see if the system requires password complexity attempt to change your password to a non-conforming password. If the user is able to change their password without meeting the requirement, this is a finding.

Fix: F-59172r873123_fix

Set the password-complexity variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordQuality": {"owasp": {"enable": true,"allowPassphrases": false }}}}}}

b
If multifactor authentication is not supported and passwords must be used, the DBN-6300 must enforce password complexity by requiring that at least one special character be used.
IA-5 - Medium - CCI-001619 - V-255557 - SV-255557r984100_rule
RMF Control
IA-5
Severity
M
CCI
CCI-001619
Version
DBNW-DM-000060
Vuln IDs
  • V-255557
  • V-76969
Rule IDs
  • SV-255557r984100_rule
  • SV-91665
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-59230r873125_chk

To see if the system requires password complexity attempt to change your password to a non-conforming password. If the user is able to change their password without meeting the requirement, this is a finding.

Fix: F-59173r873126_fix

Set the password-complexity variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordQuality": {"owasp": {"enable": true,"allowPassphrases": false }}}}}}

b
The DBN-6300 must enforce 24 hours/1 day as the minimum password lifetime.
IA-5 - Medium - CCI-000198 - V-255558 - SV-255558r961863_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000198
Version
DBNW-DM-000064
Vuln IDs
  • V-255558
  • V-76971
Rule IDs
  • SV-255558r961863_rule
  • SV-91667
Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. Restricting this setting limits the user's ability to change their password. Passwords need to be changed at specific policy-based intervals; however, if the network device allows the user to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.
Checks: C-59231r873128_chk

To see if the system requires a minimum password lifetime attempt to change your password two times quickly. If the user is able to change their password the second time, this is a finding.

Fix: F-59174r873129_fix

Set the password-minAge variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordReuse": {"check": true, "minAge": 3600 }}}}}

b
The DBN-6300 must enforce a 60-day maximum password lifetime restriction.
IA-5 - Medium - CCI-000199 - V-255559 - SV-255559r961863_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000199
Version
DBNW-DM-000065
Vuln IDs
  • V-255559
  • V-76973
Rule IDs
  • SV-255559r961863_rule
  • SV-91669
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the network device does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the passwords could be compromised. This requirement does not include emergency administration accounts which are meant for access to the network device in case of failure. These accounts are not required to have maximum password lifetime restrictions.
Checks: C-59232r873131_chk

To see if the system requires a maximum password lifetime attempt to login with a user who has had their password set longer then password lifetime setting. If a user is able to log in successfully, this is a finding.

Fix: F-59175r873132_fix

Set the password-maxAge variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: reg set /sysconfig/auth/01 {"stores": {"local": {"policies": {"passwordExpire": {"maxAge": 216000,"action": "reject"}}}}}

c
The DBN-6300 must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements.
SC-10 - High - CCI-001133 - V-255560 - SV-255560r961068_rule
RMF Control
SC-10
Severity
H
CCI
CCI-001133
Version
DBNW-DM-000071
Vuln IDs
  • V-255560
  • V-76975
Rule IDs
  • SV-255560r961068_rule
  • SV-91671
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level or deallocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Checks: C-59233r873134_chk

Verify administrator accounts are configured with a 10-minute timeout setting. Navigate to Settings >> Users. Click on the wrench for an existing user. View each user defined on the device since there is no setting for a global value. If a timeout value of "600" is not set for each administrator account configured on the device, this is a finding.

Fix: F-59176r873135_fix

Configure administrator accounts with a timeout setting. Navigate to Settings >> Users. Click on the wrench for an existing user. In the "Edit User" popup box, enter a timeout value of "600". Click on "Commit".

b
The DBN-6300 must reveal error messages only to authorized individuals (ISSO, ISSM, and SA).
SI-11 - Medium - CCI-001314 - V-255561 - SV-255561r961863_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001314
Version
DBNW-DM-000077
Vuln IDs
  • V-255561
  • V-76977
Rule IDs
  • SV-255561r961863_rule
  • SV-91673
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state. Additionally, sensitive account information must not be revealed through error messages to unauthorized personnel or their designated representatives. The DBN-6300 will reveal error messages only to authorized individuals (ISSO, ISSM, and SA). Only privileged users have visibility into any error messages. The audit log requires authorized users to log on to obtain visibility. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59234r873137_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any account function. Confirm the presence of a syslog message on the syslog server containing the information for whatever that account function represented. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information for the account action that took place is not present, this is a finding.

Fix: F-59177r873138_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.
CM-6 - Medium - CCI-000366 - V-255562 - SV-255562r961863_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
DBNW-DM-000078
Vuln IDs
  • V-255562
  • V-76979
Rule IDs
  • SV-255562r961863_rule
  • SV-91675
Predictable failure prevention requires organizational planning to address device failure issues. If components key to maintaining the device's security fail to function, the device could continue operating in a nonsecure state. If appropriate actions are not taken when a network device failure occurs, a denial-of-service condition may occur that could result in mission failure because the network would be operating without a critical security monitoring and prevention function. Upon detecting a failure of network device security components, the network device must activate a system alert message, send an alarm, or shut down. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59235r873140_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and that the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any account function. Confirm the presence of a syslog message on the syslog server containing the information for whatever that account function represented. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information for the account action that took place is not present, this is a finding.

Fix: F-59178r873141_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.
AC-12 - Medium - CCI-002361 - V-255563 - SV-255563r961863_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
DBNW-DM-000083
Vuln IDs
  • V-255563
  • V-76981
Rule IDs
  • SV-255563r961863_rule
  • SV-91677
Automatic session termination addresses the termination of administrator-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever an administrator (or process acting on behalf of a user) accesses a network device. Such administrator sessions can be terminated (and thus terminate network administrator access) without terminating network sessions. Session termination terminates all processes associated with an administrator's logical session except those processes that are specifically created by the administrator (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. These conditions will vary across environments and network device types.
Checks: C-59236r873143_chk

Verify administrator accounts are configured with a 10 minute timeout setting. Navigate to Settings >> Users. Click on the wrench for an existing user. View each user defined on the device since there is no setting for a global value. If a timeout value of "600" is not set for each administrator account configured on the device, this is a finding.

Fix: F-59179r873144_fix

Configure administrator accounts with a timeout setting. Navigate to Settings >> Users. Click on the wrench for an existing user. In the "Edit User" popup box, enter a timeout value of "600".

b
The DBN-6300 must automatically audit account enabling actions.
AC-2 - Medium - CCI-002130 - V-255564 - SV-255564r961290_rule
RMF Control
AC-2
Severity
M
CCI
CCI-002130
Version
DBNW-DM-000087
Vuln IDs
  • V-255564
  • V-76983
Rule IDs
  • SV-255564r961290_rule
  • SV-91679
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of application user accounts and notifies administrators and ISSOs. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59237r873146_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, enable an account. Confirm the presence of a syslog message on the syslog server containing the date and time of this last logon. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that an account has been enabled is not there, this is a finding.

Fix: F-59180r873147_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must be compliant with at least one IETF Internet standard authentication protocol.
CM-6 - Medium - CCI-000366 - V-255565 - SV-255565r961863_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
DBNW-DM-000089
Vuln IDs
  • V-255565
  • V-64987
Rule IDs
  • SV-255565r961863_rule
  • SV-79477
Protecting access authorization information (i.e., access control decisions) ensures that authorization information cannot be altered, spoofed, or otherwise compromised during transmission. In distributed information systems, authorization processes and access control decisions may occur in separate parts of the systems. In such instances, authorization information is transmitted securely so timely access control decisions can be enforced at the appropriate locations. To support the access control decisions, it may be necessary to transmit, as part of the access authorization information, supporting security attributes. This is because, in distributed information systems, there are various access control decisions that need to be made, and different entities (e.g., services) make these decisions in a serial fashion, each requiring some security attributes to make the decisions.
Checks: C-59238r873149_chk

Verify that the LDAP authentication server is configured correctly. Navigate to Settings >> Initial Configuration >> Authentication. Verify that the LDAP server entry is correct and the button for "LDAP Based Authentication" is enabled. Verify that the "Native takes precedence" button is set to "Disabled". If the LDAP server entry is not present and enabled, and the "Native takes precedence" button is not set to "Disabled", this is a finding.

Fix: F-59181r873150_fix

Navigate to Settings >> Initial Configuration >> Authentication. Enter the correct LDAP server entry. Press the button for "LDAP Based Authentication" so that it is enabled. If necessary, press the "Disabled" button for "Native takes precedence". Press the "Commit" button.

b
The DBN-6300 must audit the execution of privileged functions.
AC-6 - Medium - CCI-002234 - V-255566 - SV-255566r961362_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002234
Version
DBNW-DM-000093
Vuln IDs
  • V-255566
  • V-76985
Rule IDs
  • SV-255566r961362_rule
  • SV-91681
Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59239r873152_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process a privileged function. Confirm the presence of a syslog message on the syslog server containing the privileged function. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that the privileged function that just occurred is not there, this is a finding.

Fix: F-59182r873153_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

a
The DBN-6300 must provide the capability for organization-identified individuals or roles to change the auditing to be performed based on all selectable event criteria within near real time.
AU-12 - Low - CCI-001914 - V-255567 - SV-255567r961863_rule
RMF Control
AU-12
Severity
L
CCI
CCI-001914
Version
DBNW-DM-000096
Vuln IDs
  • V-255567
  • V-76987
Rule IDs
  • SV-255567r961863_rule
  • SV-91683
If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed, for example, near-real-time, within minutes, or within hours. The individuals or roles to change the auditing are dependent on the security configuration of the network device. For example, it may be configured to allow only some administrators to change the auditing, while other administrators can review audit logs but not reconfigure auditing. Because this capability is so powerful, organizations should be extremely cautious about only granting this capability to fully authorized security personnel. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59240r873155_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are able to be selected based on selectable event criteria for Audit Log, Syslog, and Audit Console. If, after navigating to Settings >> Advanced >> Audit Log, there is no facility to change the auditing to be performed within the system log based on selectable event criteria, this is a finding.

Fix: F-59183r873156_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must compare internal information system clocks at least every 24 hours with an authoritative time server.
AU-8 - Medium - CCI-001891 - V-255568 - SV-255568r961863_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001891
Version
DBNW-DM-000100
Vuln IDs
  • V-255568
  • V-76989
Rule IDs
  • SV-255568r961863_rule
  • SV-91685
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside of the configured acceptable allowance (drift) may be inaccurate. Additionally, unnecessary synchronization may have an adverse impact on system performance and may indicate malicious activity. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.
Checks: C-59241r873158_chk

Verify the configuration of the NTP server. Navigate to Settings >> Initial Configuration >> Time. View the "Time" settings window. If an NTP server address is not configured, this is a finding.

Fix: F-59184r873159_fix

Configure the NTP server on the device. The time difference is part of the NTP protocol and is not configurable. Navigate to Settings >> Initial Configuration >> Time. In the "Time" settings window, select the "NTP" button and enter the NTP server address. Click on "Commit".

b
The DBN-6300 must synchronize its internal system clock to the NTP server when the time difference is greater than one second.
AU-8 - Medium - CCI-002046 - V-255569 - SV-255569r961863_rule
RMF Control
AU-8
Severity
M
CCI
CCI-002046
Version
DBNW-DM-000101
Vuln IDs
  • V-255569
  • V-76991
Rule IDs
  • SV-255569r961863_rule
  • SV-91687
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems). Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in CCI-001891 because a comparison must be done in order to determine the time difference. The organization-defined time period will depend on multiple factors, most notably the granularity of time stamps in audit logs. For example, if time stamps only show to the nearest second, there is no need to have accuracy of a tenth of a second in clocks.
Checks: C-59242r873161_chk

Verify the configuration of the NTP server. Navigate to Settings >> Initial Configuration >> Time. View the "Time" settings window. If an NTP server address is not configured, this is a finding.

Fix: F-59185r873162_fix

Configure the NTP server on the device. The time difference is part of the NTP protocol and is not configurable. Navigate to Settings >> Initial Configuration >> Time. In the "Time" settings window, select the "NTP" button and enter the NTP server address. Click on "Commit".

b
The DBN-6300 must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).
AU-8 - Medium - CCI-001890 - V-255570 - SV-255570r961443_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
DBNW-DM-000103
Vuln IDs
  • V-255570
  • V-76993
Rule IDs
  • SV-255570r961443_rule
  • SV-91689
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Checks: C-59243r873164_chk

Verify the time zone is configured for "UTC". Navigate to Settings >> Initial Configuration >> Time. View the "Time Zone" box. If the Time Zone is not set to "UTC", this is a finding.

Fix: F-59186r873165_fix

Configure the time zone to "UTC". Navigate to Settings >> Initial Configuration >> Time and click on "NTP". Click on the drop-down box next to the "Time Zone" label. Select "UTC" underneath the "Etc" category. Click on "Commit".

b
The DBN-6300 must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
AU-8 - Medium - CCI-001889 - V-255571 - SV-255571r961446_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001889
Version
DBNW-DM-000104
Vuln IDs
  • V-255571
  • V-76995
Rule IDs
  • SV-255571r961446_rule
  • SV-91691
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks.
Checks: C-59244r873167_chk

Verify the configuration of the NTP server. Navigate to Settings >> Initial Configuration >> Time. View the "Time" settings window. If an NTP server address is not configured, this is a finding.

Fix: F-59187r873168_fix

Configure the NTP server on the device. The time difference is part of the NTP protocol and is not configurable. Navigate to Settings >> Initial Configuration >> Time. In the "Time" settings window, select the "NTP" button and enter the NTP server address. Click on "Commit".

b
The DBN-6300 must audit the enforcement actions used to restrict access associated with changes to the device.
CM-5 - Medium - CCI-001814 - V-255572 - SV-255572r984111_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001814
Version
DBNW-DM-000108
Vuln IDs
  • V-255572
  • V-76997
Rule IDs
  • SV-255572r984111_rule
  • SV-91693
Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59245r873170_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account removal. Confirm the presence of a syslog message on the syslog server containing the date and time of this last logon. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a logon just occurred is not there, this is a finding.

Fix: F-59188r873171_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications.
MA-4 - Medium - CCI-002890 - V-255573 - SV-255573r961554_rule
RMF Control
MA-4
Severity
M
CCI
CCI-002890
Version
DBNW-DM-000117
Vuln IDs
  • V-255573
  • V-76999
Rule IDs
  • SV-255573r961554_rule
  • SV-91695
This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents of those sessions will be susceptible to manipulation, potentially allowing alteration and hijacking of maintenance sessions.
Checks: C-59246r873173_chk

Verify SSL is configured to use SSL for the web management tool. Navigate to Settings >> Initial Configuration >> Security. If the check box for "Enforce secure communications (SSL) for user interface access" is not checked, this is a finding.

Fix: F-59189r873174_fix

Configure the User Interface (UI) web management tool to use HTTPS for communications. Navigate to Settings >> Initial Configuration >> Security. Select the check box for "Enforce secure communications (SSL) for user interface access". Click on "Commit".

b
Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.
MA-4 - Medium - CCI-003123 - V-255574 - SV-255574r961557_rule
RMF Control
MA-4
Severity
M
CCI
CCI-003123
Version
DBNW-DM-000118
Vuln IDs
  • V-255574
  • V-77001
Rule IDs
  • SV-255574r961557_rule
  • SV-91697
This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents of those sessions will be susceptible to eavesdropping, potentially putting sensitive data (including administrator passwords) at risk of compromise and potentially allowing hijacking of maintenance sessions.
Checks: C-59247r873176_chk

Verify SSL is configured to use SSL for the web management tool. Navigate to Settings >> Initial Configuration >> Security. If the check box for "Enforce secure communications (SSL) for user interface access" is not checked, this is a finding.

Fix: F-59190r873177_fix

Configure the User Interface (UI) web management tool to use HTTPS for communications. Navigate to Settings >> Initial Configuration >> Security. Select the check box for "Enforce secure communications (SSL) for user interface access". Click on "Commit".

b
The DBN-6300 must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.
AU-12 - Medium - CCI-000172 - V-255575 - SV-255575r961800_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000121
Vuln IDs
  • V-255575
  • V-77003
Rule IDs
  • SV-255575r961800_rule
  • SV-91699
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). Administrative roles cannot be changed on the device console; thus, this only applies to the User Interface (UI) web management tool. All account activities (creation, modification, disabling, and removal, and other account activities, including successful/unsuccessful attempts to modify administrator privileges) on the DBN-6300 are written out to an audit log. This log carries a wealth of information that provides valuable forensic help, including the origin IP and port and destination and port where the event occurred, as well as the type of event and when it occurred. This data is all used to help establish the identity of any individual or process associated with the event. This can be verified by accessing the audit logs remotely by downloading the System State Report. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59248r873179_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account administrator privilege modification. Confirm the presence of a syslog message on the syslog server containing the account administrator privilege modification. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that an account administrator privilege modification has occurred is not there, this is a finding.

Fix: F-59191r873180_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.
AU-12 - Medium - CCI-000172 - V-255576 - SV-255576r961812_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000122
Vuln IDs
  • V-255576
  • V-77005
Rule IDs
  • SV-255576r961812_rule
  • SV-91701
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59249r873182_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account administrator privilege modification. Confirm the presence of a syslog message on the syslog server containing the deletion of account administrator privileges. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the deletion of account administrator privileges is not there, this is a finding.

Fix: F-59192r873183_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes". If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit". Verify that the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If any of the Configuration Categories are not checked, cycle the top buttons until every category is completely checked. Click on "Commit".

b
The DBN-6300 must generate audit records when successful/unsuccessful logon attempts occur.
AU-12 - Medium - CCI-000172 - V-255577 - SV-255577r961824_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000123
Vuln IDs
  • V-255577
  • V-77007
Rule IDs
  • SV-255577r961824_rule
  • SV-91703
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300 Audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59250r873185_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process an account administrator privilege modification. Confirm the presence of a syslog message on the syslog server containing information pertinent to successful or unsuccessful logon attempts. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing information pertinent to successful or unsuccessful logon attempts is not there, this is a finding.

Fix: F-59193r873186_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit records for privileged activities or other system-level access.
AU-12 - Medium - CCI-000172 - V-255578 - SV-255578r961827_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000124
Vuln IDs
  • V-255578
  • V-77009
Rule IDs
  • SV-255578r961827_rule
  • SV-91705
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59251r873188_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any kind of privileged activity or any type of system-level access. Confirm the presence of a syslog message on the syslog server containing information pertinent to any kind of privileged activity or any type of system-level access. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information pertinent to any kind of privileged activity or any type of system-level access that was processed is not there, this is a finding.

Fix: F-59194r873189_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit records showing starting and ending time for administrator access to the system.
AU-12 - Medium - CCI-000172 - V-255579 - SV-255579r961830_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000125
Vuln IDs
  • V-255579
  • V-77011
Rule IDs
  • SV-255579r961830_rule
  • SV-91707
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59252r873191_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, process any function using administrator access. Confirm the presence of a syslog message on the syslog server containing information pertinent to an event using administrator access that was processed. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information pertinent to any kind of administrator access is not there, this is a finding.

Fix: F-59195r873192_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and he Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit records when concurrent logons from different workstations occur.
AU-12 - Medium - CCI-000172 - V-255580 - SV-255580r961833_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000126
Vuln IDs
  • V-255580
  • V-77013
Rule IDs
  • SV-255580r961833_rule
  • SV-91709
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59253r873194_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, a user should log on from two different workstations. Confirm the presence of a syslog message on the syslog server containing logon information pertinent to logons from the same user from two different workstations. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information pertinent to a user logging on concurrently from two different workstations is not there, this is a finding.

Fix: F-59196r873195_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit records for all account creation, modification, disabling, and termination events.
AU-12 - Medium - CCI-000172 - V-255581 - SV-255581r961863_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
DBNW-DM-000127
Vuln IDs
  • V-255581
  • V-77015
Rule IDs
  • SV-255581r961863_rule
  • SV-91711
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter). With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59254r873197_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. Following this verification, execute four processes: account creation, account modification, account termination, and account disabling. Confirm the presence of a syslog message on the syslog server containing information pertinent to account creation, account modification, account termination, and account disabling. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing information pertinent to the account creation, account modification, account termination, and account disabling is not there, this is a finding.

Fix: F-59197r873198_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must off-load audit records onto a different system or media than the system being audited.
AU-4 - Medium - CCI-001851 - V-255582 - SV-255582r961860_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001851
Version
DBNW-DM-000128
Vuln IDs
  • V-255582
  • V-77017
Rule IDs
  • SV-255582r961860_rule
  • SV-91713
Off-loading ensures audit information does not get overwritten if the limited audit storage capacity is reached and also protects the audit record in case the system/component being audited is compromised. The intent of this control is to ensure that log information does not get overwritten if the limited log storage capacity is reached and also to protect the log records in general if the system/component being logged is compromised (hence the notion of off-loading onto a different system or media) but the intent is not to hold the information in more than one or multiple locations. This requirement is intended to address the primary repository, which is on the centralized Syslog server. This requirement is only applicable to the server used as the Syslog server. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59255r873200_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the DBN-6300 is not connected to the syslog server, this is a finding.

Fix: F-59198r873201_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
The DBN-6300 must generate audit log events for a locally developed list of auditable events.
CM-6 - Medium - CCI-000366 - V-255583 - SV-255583r961863_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
DBNW-DM-000132
Vuln IDs
  • V-255583
  • V-64995
Rule IDs
  • SV-255583r961863_rule
  • SV-79485
Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured network device. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59256r873203_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", that the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes"; the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console; and the items for any locally developed list of auditable events is checked. Following this verification, process an account removal. Confirm the presence of a syslog message on the syslog server containing the date and time of this last logon. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a logon has just occurred is not there, this is a finding.

Fix: F-59199r873204_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

b
Accounts for device management must be configured on the authentication server and not the network device itself, except for the account of last resort.
CM-6 - Medium - CCI-000366 - V-255584 - SV-255584r961863_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
DBNW-DM-000134
Vuln IDs
  • V-255584
  • V-77021
Rule IDs
  • SV-255584r961863_rule
  • SV-91717
Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important protection against the insider threat. With robust centralized management, audit records for administrator account access to the organization's network devices can be more readily analyzed for trends and anomalies. The alternative method of defining administrator accounts on each device exposes the device configuration to remote access authentication attacks and system administrators with multiple authenticators for each network device.
Checks: C-59257r873206_chk

Verify that the LDAP authentication server is configured correctly. Navigate to Settings >> Initial Configuration >> Authentication. Verify that the LDAP server entry is correct and the button for "LDAP Based Authentication" is enabled. Verify that the "Native takes precedence" button is set to "Disabled". If the LDAP server entry is not present and enabled, and the "Native takes precedence" button is not set to "Disabled", this is a finding.

Fix: F-59200r873207_fix

Navigate to Settings >> Initial Configuration >> Authentication. Enter the correct LDAP server entry. Press the button for "LDAP Based Authentication" so that it is enabled. If necessary, press the "Disabled" button for "Native takes precedence". Press the "Commit" button.

b
The DBN-6300 must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
CM-6 - Medium - CCI-000366 - V-255585 - SV-255585r961863_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
DBNW-DM-000141
Vuln IDs
  • V-255585
  • V-77023
Rule IDs
  • SV-255585r961863_rule
  • SV-91719
For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice. Self-signed certificates are not allowed.
Checks: C-59258r873209_chk

Verify that the Public Key Certificate is installed and has been obtained from an appropriate certificate policy through an approved service provider. Navigate to CLI and verify that there is a registry entry similar to below: Reg set /sysconfig/tls/trustedcas EOF (enter/paste certificate here) EOF If an entry is not found in the registry with the appropriate certificate, this is a finding.

Fix: F-59201r873210_fix

Verify that the Public Key Certificate is installed and has been obtained from an appropriate certificate policy through an approved service provider. Set the trusted-ca variable within the DBN-6300 through the CLI. This value is set with the following registry entry in the CLI: Reg set /sysconfig/tls/trustedcas EOF (enter/paste certificate here) EOF

c
The DBN-6300 must be configured to send log data to a syslog server for the purpose of forwarding alerts to the administrators and the ISSO.
CM-6 - High - CCI-000366 - V-255586 - SV-255586r961863_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000366
Version
DBNW-DM-000142
Vuln IDs
  • V-255586
  • V-77019
Rule IDs
  • SV-255586r961863_rule
  • SV-91715
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of accounts and notifies administrators and ISSOs. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. With the DBN-6300, audit records are automatically backed up on a real-time basis via syslog when enabled.
Checks: C-59259r873212_chk

Verify the DBN-6300 is connected to the syslog server. Navigate to Settings >> Advanced >> Syslog. Verify that the syslog services are set to "on", the syslog server information is valid, and the syslog server has connected. Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes"; the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console; and the items for any locally developed list of auditable events is checked. Following this verification, process any type of account management activity. Confirm the presence of a syslog message on the syslog server containing the information regarding the account management function that was used. If the DBN-6300 is not connected to the syslog server, or if the syslog server is connected but the message containing the information that a logon has just occurred is not there, this is a finding.

Fix: F-59202r873213_fix

Configure the DBN-6300 to be connected to the syslog server. Also configure the DBN-6300 to include audit records in the syslog message feed. Navigate to Settings >> Advanced >> Syslog. Enter the syslog connection information (port and IP address) and push the "enabled" button for both "TCP" and "enable". Navigate to Settings >> Advanced >> Audit Log. Verify that the Audit Syslog, "Use System Syslog" button is set to "Yes" and the Audit Configuration Categories are all checked for Audit Log, Syslog, and Audit Console. If the "Use System Syslog" button is not set to "Yes", press the "Yes" button. Click on "Commit".

c
The DBN-6300 NDM must be using a version supported by the vendor.
CM-6 - High - CCI-000366 - V-264431 - SV-264431r992090_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000366
Version
DBNW-DM-000150
Vuln IDs
  • V-264431
Rule IDs
  • SV-264431r992090_rule
Systems running an unsupported software/firmware version lack current security fixes required to mitigate the risks associated with recent vulnerabilities.
Checks: C-68345r992088_chk

This STIG is sunset and no longer updated. Compare the version running to the supported version by the vendor. If the system is using an unsupported version from the vendor, this is a finding.

Fix: F-68253r992089_fix

Upgrade to a version supported by the vendor.