DBN-6300 NDM Security Technical Implementation Guide

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: [email protected]

Details

Version / Release: V1R1

Published: 2017-09-15

Updated At: 2018-09-23 19:12:47

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-79465r1_rule DBNW-DM-000006 CCI-000015 HIGH The DBN-6300 must provide automated support for account management functions. If account management functions are not automatically enforced, an attacker could gain privileged access to a vital element of the network security architecture.
    SV-79473r1_rule DBNW-DM-000009 CCI-000018 MEDIUM The DBN-6300 must automatically audit account creation. 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
    SV-79475r1_rule DBNW-DM-000010 CCI-001403 MEDIUM The DBN-6300 must automatically audit account modification. 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.
    SV-79477r1_rule DBNW-DM-000089 CCI-000366 MEDIUM The DBN-6300 must be compliant with at least one IETF Internet standard authentication protocol. 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
    SV-79479r1_rule DBNW-DM-000012 CCI-001405 MEDIUM The DBN-6300 must automatically audit account removal actions. 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 managemen
    SV-79481r1_rule DBNW-DM-000015 CCI-000044 MEDIUM The DBN-6300 must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. 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 loc
    SV-79483r1_rule DBNW-DM-000021 CCI-000166 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. 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 authe
    SV-79485r1_rule DBNW-DM-000132 CCI-000366 MEDIUM The DBN-6300 must generate audit log events for a locally developed list of auditable events. 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 netwo
    SV-79487r1_rule DBNW-DM-000023 CCI-000169 MEDIUM The DBN-6300 must provide audit record generation capability for DoD-defined auditable events within the DBN-6300. 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
    SV-91623r1_rule DBNW-DM-000024 CCI-000171 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. 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 th
    SV-91625r1_rule DBNW-DM-000025 CCI-000172 MEDIUM The DBN-6300 must generate log records when successful attempts to access privileges occur. 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 reco
    SV-91627r1_rule DBNW-DM-000026 CCI-001464 LOW The DBN-6300 must initiate session auditing upon startup. 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.
    SV-91629r1_rule DBNW-DM-000027 CCI-000130 LOW The DBN-6300 must produce audit log records containing sufficient information to establish what type of event occurred. 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 applic
    SV-91631r1_rule DBNW-DM-000028 CCI-000131 LOW The DBN-6300 must produce audit records containing information to establish when (date and time) the events occurred. 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
    SV-91633r1_rule DBNW-DM-000029 CCI-000132 LOW The DBN-6300 must produce audit records containing information to establish where the events occurred. 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, a
    SV-91635r1_rule DBNW-DM-000030 CCI-000133 LOW The DBN-6300 must produce audit log records containing information to establish the source of events. 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, administrato
    SV-91637r1_rule DBNW-DM-000031 CCI-000134 LOW The DBN-6300 must produce audit records that contain information to establish the outcome of the event. 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 succ
    SV-91639r1_rule DBNW-DM-000032 CCI-001487 LOW The DBN-6300 must generate audit records containing information that establishes the identity of any individual or process associated with the event. 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. Eve
    SV-91641r1_rule DBNW-DM-000033 CCI-000135 LOW The DBN-6300 must generate audit records containing the full-text recording of privileged commands. 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 requi
    SV-91643r1_rule DBNW-DM-000036 CCI-000159 MEDIUM The DBN-6300 must use internal system clocks to generate time stamps for audit records. 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 und
    SV-91645r1_rule DBNW-DM-000043 CCI-001348 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. 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 syste
    SV-91647r1_rule DBNW-DM-000049 CCI-001358 HIGH The DBN-6300 must uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators). 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.
    SV-91649r1_rule DBNW-DM-000050 CCI-000765 MEDIUM The DBN-6300 must use multifactor authentication for network access (remote and nonlocal) to privileged accounts. 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
    SV-91651r1_rule DBNW-DM-000051 CCI-000767 MEDIUM The DBN-6300 must use multifactor authentication for local access to privileged accounts. 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) Some
    SV-91653r1_rule DBNW-DM-000053 CCI-001941 MEDIUM The DBN-6300 must implement replay-resistant authentication mechanisms for network access to privileged accounts. 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
    SV-91655r1_rule DBNW-DM-000055 CCI-000205 MEDIUM The DBN-6300 must enforce a minimum 15-character password length. 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 passwor
    SV-91657r1_rule DBNW-DM-000056 CCI-000200 MEDIUM The DBN-6300 must prohibit password reuse for a minimum of five generations. 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
    SV-91659r1_rule DBNW-DM-000057 CCI-000192 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. 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. Passwor
    SV-91661r1_rule DBNW-DM-000058 CCI-000193 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. 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
    SV-91663r1_rule DBNW-DM-000059 CCI-000194 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. 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
    SV-91665r1_rule DBNW-DM-000060 CCI-001619 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. 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
    SV-91667r1_rule DBNW-DM-000064 CCI-000198 MEDIUM The DBN-6300 must enforce 24 hours/1 day as the minimum password lifetime. 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 sp
    SV-91669r1_rule DBNW-DM-000065 CCI-000199 MEDIUM The DBN-6300 must enforce a 60-day maximum password lifetime restriction. 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 li
    SV-91671r1_rule DBNW-DM-000071 CCI-001133 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. 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 terminat
    SV-91673r1_rule DBNW-DM-000077 CCI-001314 MEDIUM The DBN-6300 must reveal error messages only to authorized individuals (ISSO, ISSM, and SA). 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 unauthori
    SV-91675r1_rule DBNW-DM-000078 CCI-000366 MEDIUM The DBN-6300 must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected. 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
    SV-91677r1_rule DBNW-DM-000083 CCI-002361 MEDIUM The DBN-6300 must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect. 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 l
    SV-91679r1_rule DBNW-DM-000087 CCI-002130 MEDIUM The DBN-6300 must automatically audit account enabling actions. 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
    SV-91681r1_rule DBNW-DM-000093 CCI-002234 MEDIUM The DBN-6300 must audit the execution of privileged functions. 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
    SV-91683r1_rule DBNW-DM-000096 CCI-001914 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. 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 enable
    SV-91685r1_rule DBNW-DM-000100 CCI-001891 MEDIUM The DBN-6300 must compare internal information system clocks at least every 24 hours with an authoritative time server. 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. S
    SV-91687r1_rule DBNW-DM-000101 CCI-002046 MEDIUM The DBN-6300 must synchronize its internal system clock to the NTP server when the time difference is greater than one second. 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.
    SV-91689r1_rule DBNW-DM-000103 CCI-001890 MEDIUM The DBN-6300 must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC). If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
    SV-91691r1_rule DBNW-DM-000104 CCI-001889 MEDIUM The DBN-6300 must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. 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 synchron
    SV-91693r1_rule DBNW-DM-000108 CCI-001814 MEDIUM The DBN-6300 must audit the enforcement actions used to restrict access associated with changes to the device. 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. Enfo
    SV-91695r1_rule DBNW-DM-000117 CCI-002890 MEDIUM Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications. 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
    SV-91697r1_rule DBNW-DM-000118 CCI-003123 MEDIUM Applications used for nonlocal maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications. 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
    SV-91699r1_rule DBNW-DM-000121 CCI-000172 MEDIUM The DBN-6300 must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur. 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 reco
    SV-91701r1_rule DBNW-DM-000122 CCI-000172 MEDIUM The DBN-6300 must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur. 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 reco
    SV-91703r1_rule DBNW-DM-000123 CCI-000172 MEDIUM The DBN-6300 must generate audit records when successful/unsuccessful logon attempts occur. 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 recor
    SV-91705r1_rule DBNW-DM-000124 CCI-000172 MEDIUM The DBN-6300 must generate audit records for privileged activities or other system-level access. 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 reco
    SV-91707r1_rule DBNW-DM-000125 CCI-000172 MEDIUM The DBN-6300 must generate audit records showing starting and ending time for administrator access to the system. 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 recor
    SV-91709r1_rule DBNW-DM-000126 CCI-000172 MEDIUM The DBN-6300 must generate audit records when concurrent logons from different workstations occur. 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 reco
    SV-91711r1_rule DBNW-DM-000127 CCI-000172 MEDIUM The DBN-6300 must generate audit records for all account creation, modification, disabling, and termination events. 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 reco
    SV-91713r1_rule DBNW-DM-000128 CCI-001851 MEDIUM The DBN-6300 must off-load audit records onto a different system or media than the system being audited. 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
    SV-91715r1_rule DBNW-DM-000142 CCI-000366 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. 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 m
    SV-91717r1_rule DBNW-DM-000134 CCI-000366 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. 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 administra
    SV-91719r1_rule DBNW-DM-000141 CCI-000366 MEDIUM The DBN-6300 must obtain its public key certificates from an appropriate certificate policy through an approved service provider. 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 Aut