Network Device Management SRG
Network Device Management Security Requirements Guide. Version v4 r3, released June 7, 2023.
SRG-APP-000164-NDM-000252: The network device must enforce a minimum 15-character password length.
Determine if the network device or its associated authentication server enforces a minimum 15-character password length. This requirement may be verified by demonstration or configuration review. If the network device or its associated authentication server does not enforce a minimum 15-character password length, this is a finding.
Discussion
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. The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.
Fix
Configure the network device or its associated authentication server to enforce a minimum 15-character password length.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000122-NDM-000239: The network device must protect audit tools from unauthorized modification.
If the network device provides audit tools, check the device to determine if it protects audit tools from unauthorized modification. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not protect its audit tools from unauthorized modification, this is a finding.
Discussion
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Network devices providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Fix
Configure the network device to protect audit tools from unauthorized modification.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000340: The network device must be configured to conduct backups of system level information contained in the information system when changes occur.
Review the network device configuration to determine if the device is configured to conduct backups of system-level information contained in the information system when changes occur. If the network device is not configured to conduct backups of system-level data when changes occur, this is a finding.
Discussion
System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the execution and operation of the device. Information system backup is a critical step in ensuring system integrity and availability. If the system fails and there is no backup of the system-level information, a denial of service condition is possible for all who utilize this critical network component. This control requires the network device to support the organizational central backup process for system-level information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups.
Fix
Configure the network device to conduct backups of system-level information contained in the information system when changes occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000100-NDM-000230: The network device must generate audit records containing information that establishes the identity of any individual or process associated with the event.
Determine if the network device generates audit records containing information that establishes the identity of any individual or process associated with the event. This requirement may be verified by demonstration or validated test results. If the network device does not generate audit records containing information that establishes the identity of any individual or process associated with the event, this is a finding.
Discussion
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.
Fix
Configure the network device to generate audit records containing information that establishes the identity of any individual or process associated with the event.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000357-NDM-000293: The network device must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
Determine if the network device allocates audit record storage capacity in accordance with organization-defined audit record storage requirements. This requirement may be verified by configuration review or vendor-provided information. This requirement may be met through use of a properly configured syslog server if the device is configured to use the syslog server. If audit record store capacity is not allocated in accordance with organization-defined audit record storage requirements, this is a finding.
Discussion
In order to ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. The value for the organization-defined audit record storage requirement will depend on the amount of storage available on the network device, the anticipated volume of logs, the frequency of transfer from the network device to centralized log servers, and other factors.
Fix
Configure the network device to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000231-NDM-000271: The network device must only allow authorized administrators to view or change the device configuration, system files, and other files stored either in the device or on removable media (such as a flash drive).
List the contents of the network device’s local storage, including any drives supporting removable media (such as flash drives or CDs) and check the file permissions of all files on those drives. If any files allow read or write access by accounts not specifically authorized access or by non-privileged accounts, this is a finding.
Discussion
This requirement is intended to address the confidentiality and integrity of system information at rest (e.g., network device rule sets) when it is located on a storage device within the network device or as a component of the network device. This protection is required to prevent unauthorized alteration, corruption, or disclosure of information when not stored directly on the network device. Files on the network device or on removable media used by the device must have their permissions set to allow read or write access to those accounts that are specifically authorized to access or change them. Note that different administrative accounts or roles will have varying levels of access. File permissions must be set so that only authorized administrators can read or change their contents. Whenever files are written to removable media and the media removed from the device, the media must be handled appropriately for the classification and sensitivity of the data stored on the device.
Fix
Set the file permissions on files on the network device or on removable media used by the device so that only authorized administrators can read or change their contents.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000395-NDM-000310: The network device must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
Review the network device configuration to verify SNMP messages are authenticated using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC). If the network device is not configured to authenticate SNMP messages using a FIPS-validated HMAC, this is a finding.
Discussion
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
Fix
Configure the network device to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000033-NDM-000212: The network device must be configured to assign appropriate user roles or access levels to authenticated users.
If the network device is configured to use a AAA service account, and the AAA broker is configured to assign authorization levels based on centralized user account group memberships on behalf of the network device, that will satisfy this objective. Because the responsibility for meeting this objective is transferred to the AAA broker, this requirement is not applicable for the local network device. This requirement may be verified by demonstration or configuration review. Verify the network device is configured to assign appropriate user roles or access levels to authenticated users. This requirement may be verified by demonstration or configuration review. If the network device does not enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level, this is a finding.
Discussion
Successful identification and authentication must not automatically give an entity full access to a network device or security domain. The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. All DoD systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset or set of resources. Information systems use access control policies and enforcement mechanisms to implement this requirement. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Some network devices are pre-configured with security groups. Other network devices enable operators to create custom security groups with custom permissions. For example, an ISSM may require read-only access to audit the network device. Operators may create an audit security group, define permissions and access levels for members of the group, and then assign the ISSM’s user persona to the audit security group. This is still considered privileged access, but the ISSM’s security group is more restrictive than the network administrator’s security group. Network devices that rely on AAA brokers for authentication and authorization services may need to identify the available security groups or access levels available on the network devices and convey that information to the AAA operator. Once the AAA broker identifies the user persona on the centralized directory service, the user’s security group memberships can be retrieved. The AAA operator may need to create a mapping that links target security groups from the directory service to the appropriate security groups or access levels on the network device. Once these mappings are configured, authorizations can happen dynamically, based on each user’s directory service group membership.
Fix
Configure the network device to assign appropriate user roles or access levels to authenticated users, or configure the network device to leverage an AAA solution that will satisfy this objective.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000516-NDM-000335: The network device must enforce access restrictions associated with changes to the system components.
Check the network device to determine if only authorized administrators have permissions for changes, deletions and updates on the network device. Inspect the maintenance log to verify changes are being made only by the system administrators. If unauthorized users are allowed to change the hardware or software, this is a finding.
Discussion
Changes to the hardware or software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals should be allowed administrative access to the network device for implementing any changes or upgrades. This requirement applies to updates of the application files, configuration, ACLs, and policy filters.
Fix
Configure the network device to enforce access restrictions associated with changes to the system components.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000400-NDM-000313: The network device must prohibit the use of cached authenticators after an organization-defined time period.
Review the network device configuration to determine if the network device or its associated authentication server prohibits the use of cached authenticators after an organization-defined time period. If cached authenticators are used after an organization-defined time period, this is a finding.
Discussion
Some authentication implementations can be configured to use cached authenticators. If cached authentication information is out-of-date, the validity of the authentication information may be questionable. The organization-defined time period should be established for each device depending on the nature of the device; for example, a device with just a few administrators in a facility with spotty network connectivity may merit a longer caching time period than a device with many administrators.
Fix
Configure the network device or its associated authentication server to prohibit the use of cached authenticators after an organization-defined time period.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000319-NDM-000283: The network device must automatically audit account enabling actions.
Determine if the network device automatically audits account enabling actions. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If account enabling actions are not automatically audited, this is a finding.
Discussion
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 which documents the creation of application user accounts and notifies administrators and Information Assurance Officers (IAO). Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.
Fix
Configure the network device or its associated authentication server to automatically audit account enabling actions.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000177-NDM-000263: The network device, for PKI-based authentication, must be configured to map validated certificates to unique user accounts.
If PKI-based authentication is not used as the MFA solution for interactive logins, this requirement is not applicable. If the network device is configured to use a AAA service account, and the AAA broker is configured to map validated certificates to centralized user accounts on behalf of the network device, that will satisfy this objective. Because the responsibility for meeting this objective is transferred to the AAA broker, this requirement is not applicable for the local network device. This requirement may be verified by demonstration or configuration review. Verify the network device is configured to map each validated certificate to a unique, centralized user account for all interactive users. If the network device is not configured to map each validated certificate to a unique, centralized user account for all interactive users, this is a finding. Note: If local user accounts are used on the device, this requirement cannot be met in its entirety and it is a permanent finding. This may be the case if AO’s choose to accept the risk of using local accounts on network devices for small, isolated environments where centralized directory services are not available in the infrastructure or where they are not cost effective to implement and maintain. In such cases, this requirement can be mitigated to a CAT III if the network device is configured to map each validated certificate to a unique, local user account for all interactive users. Note: This requirement is not applicable to the emergency account of last resort nor for service accounts (non-interactive users). Examples of service accounts include remote service brokers such as AAA, syslog, etc.
Discussion
Without mapping the PKI certificate to a unique user account, the ability to determine the identities of individuals or the status of their non-repudiation is considerably impacted during forensic analysis. A strength of using PKI as MFA is that it can help ensure only the assigned individual is using their associated user account. This can only be accomplished if the network device is configured to enforce the relationship which binds PKI certificates to unique user accounts. Local accounts (accounts created, stored, and maintained locally on the network device) should be avoided in lieu of using a centrally managed directory service. Local accounts empower the same workgroup who will be operating the network infrastructure to also control and manipulate access methods, thus creating operational autonomy. This undesirable approach breaks the concept of separation of duties. Additionally, local accounts are susceptible to poor cyber hygiene because they create another user database that must be maintained by the operator, whose primary focus is on running the network. Such examples of poor hygiene include dormant accounts that are not disabled or deleted, employees who have left the organization but whose accounts are still present, periodic password and hash rotation, password complexity shortcomings, increased exposure to insider threat, etc. For reasons such as this, local users on network devices are frequently the targets of cyber-attacks. Instead, organizations should explore examples of centrally managed account services. These examples include the implementation of AAA concepts like the use of external RADIUS and LDAP directory service brokers.
Fix
Configure the network device to use a AAA service account whereby the remote AAA broker will map the validated certificate used for PKI-based authentication to a centrally managed, interactive user account. Alternatively, for organizations who choose to accept the risk and permanent finding, configure the network device to map the validated certificate used for PKI-based authentication to a unique, local, interactive user account.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000506-NDM-000323: The network device must generate audit records when concurrent logons from different workstations occur.
Determine if the network device generates audit records when concurrent logons from different workstations occur. If the network device does not generate audit records when concurrent logons from different workstations occur, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records when concurrent logons from different workstations occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000296-NDM-000280: The network device must be configured to provide a logout mechanism for administrator-initiated communication sessions.
Review the network device configuration to determine if it is configured to enable a logout for administrator-initiated communication sessions. If the network device is not configured to provide a logout mechanism for these sessions, this is a finding.
Discussion
If an administrator cannot explicitly end a device management session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session.
Fix
Configure the network device to provide a logout capability for administrator-initiated communication sessions.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000499-NDM-000319: The network device must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.
Determine if the network device generates audit records when successful/unsuccessful attempts to delete administrator privileges occur. If the network device does not generate audit records when successful/unsuccessful attempts to delete administrator privileges occur, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000097-NDM-000227: The network device must produce audit records containing information to establish where the events occurred.
Determine if the network device is configured to produce audit records containing information to establish where the events occurred. If the network device does not produce audit records containing information to establish where the events occurred, this is a finding.
Discussion
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. Associating information about where the event occurred within the network device provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured device.
Fix
Configure the network device to produce audit records containing information to establish where the events occurred.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000101-NDM-000231: The network device must generate audit records containing the full-text recording of privileged commands.
Determine if the network device generates audit records containing the full-text recording of privileged commands. If such audit records are not being generated, this is a finding.
Discussion
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 within 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.
Fix
Configure the network device to generate audit records containing the full-text recording of privileged commands.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000224-NDM-000270: The network device must generate unique session identifiers using a FIPS 140-2 approved random number generator.
If the network device uses a web interface for device management, determine if it generates unique session identifiers using a FIPS 140-2 approved random number generator. This requirement may be verified by validated NIST certification and vendor documentation. If the network device does not use unique session identifiers for its web interface for device management, this is a finding.
Discussion
Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force attacks to determine future session identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. This requirement is applicable to devices that use a web interface for device management.
Fix
Configure the network device to generate unique session identifiers using a FIPS 140-2 approved random number generator.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000190-NDM-000267: The network device must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after five minutes of inactivity except to fulfill documented and validated mission requirements.
Determine if the network device terminates the connection associated with a device management session at the end of the session or after five minutes of inactivity. This requirement may be verified by demonstration or configuration review. If the network device does not terminate the connection associated with a device management session at the end of the session or after five minutes of inactivity, this is a finding.
Discussion
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, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating 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.
Fix
Configure the network device to terminate the connection associated with a device management session at the end of the session or after five minutes of inactivity.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000119-NDM-000236: The network device must protect audit information from unauthorized modification.
Determine if the network device protects audit information from any type of unauthorized modification with such methods as ensuring log files receive the proper file system permissions, limiting log data locations and leveraging user permissions and roles to identify the user accessing the data and the corresponding rights that the user enjoys. This requirement may be verified by demonstration, configuration, or validated test results. If the network device does not protect audit information from unauthorized modification, this is a finding.
Discussion
Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit network device activity. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the network device must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions and limiting log data locations. Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data.
Fix
Configure the network device to protect audit information from unauthorized modification.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000099-NDM-000229: The network device must produce audit records that contain information to establish the outcome of the event.
Determine if the network device is configured to produce audit records that contain information to establish the outcome of the event. If the network device does not produce audit records that contain information to establish the outcome of the event, this is a finding.
Discussion
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.
Fix
Configure the network device to produce audit records that contain information to establish the outcome of the event.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000503-NDM-000320: The network device must generate audit records when successful/unsuccessful logon attempts occur.
Determine if the network device generates audit records when successful/unsuccessful logon attempts occur. If it does not generate audit records when successful/unsuccessful logon attempts occur, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records when successful/unsuccessful logon attempts occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000166-NDM-000254: The network device must enforce password complexity by requiring that at least one upper-case character be used.
Where passwords are used, confirm that the network device and associated authentication server enforces password complexity by requiring that at least one upper-case character be used. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device and associated authentication server does not require that at least one upper-case character be used in each password, this is a finding.
Discussion
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. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Fix
Configure the network device and associated authentication server to enforce password complexity by requiring that at least one upper-case character be used.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000131-NDM-000243: The network device must prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.
Determine if the network device prevents the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization, this is a finding.
Discussion
Changes to any software components can have significant effects on the overall security of the network device. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the software has not been tampered with and has been provided by a trusted vendor. Accordingly, patches, service packs, or application components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The device should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.
Fix
Configure the network device to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000350: The network device must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).
Verify that the network device is configured to send log data to at least two central log servers. If the network device is not configured to send log data to at least two central log servers, this is a finding.
Discussion
The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, are important in showing whether someone is an internal employee or an outside threat.
Fix
Configure the network device to send log data to at least two central log servers.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000220-NDM-000268: The network device must invalidate session identifiers upon administrator logout or other session termination.
If the network device uses a web interface for device management, determine if the network device invalidates session identifiers upon administrator logout or other session termination. This requirement may be verified by validated test results. If the network device does not invalidate session identifiers upon administrator logout or other session termination, this is a finding.
Discussion
Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and to continue to employ previously valid session IDs. This requirement is applicable to devices that use a web interface for device management. Session IDs are tokens generated by web applications to uniquely identify an application user's session. Applications will make application decisions and execute business logic based on the session ID. Unique session identifiers or IDs are the opposite of sequentially generated session IDs which can be easily guessed by an attacker. Unique session IDs help to reduce predictability of said identifiers. If a device uses a web interface for device management, when an administrator logs out, or when any other session termination event occurs, the device management web application must invalidate the session identifier to minimize the potential for an attacker to hijack that particular management session.
Fix
Configure the network device to invalidate session identifiers upon administrator logout or other session termination.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000297-NDM-000281: The network device must display an explicit logout message to administrators indicating the reliable termination of authenticated communications sessions.
This requirement may be verified by demonstration. If an explicit logoff message is not displayed, or provides clear evidence that the session has been terminated, this is a finding.
Discussion
If an explicit logout message is not displayed and the administrator does not expect to see one, the administrator may inadvertently leave a management session un-terminated. The session may remain open and be exploited by an attacker; this is referred to as a zombie session. Administrators need to be aware of whether or not the session has been terminated. A prompt for new logon is an acceptable indication of previous session termination. If the device takes the user back to the logon page or prompt after selecting the logoff button, it is considered an explicit logout message. In the case of terminal sessions (such as SSH), an explicit logoff message is displayed by the client application. Usually this is a message such as "connect closed by remote host" displayed by the client. For a terminal connected to the console port of a network device, either a logoff message is displayed or the device takes the user back to the logon prompt.
Fix
Configure the network device to display an explicit logoff message to administrators indicating the reliable termination of authenticated communications sessions. This may be a capability the device is inherently capable of.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000149-NDM-000247: The network device must be configured to use DoD PKI as multi-factor authentication (MFA) for interactive logins.
Verify the network device is configured to use DoD PKI as MFA for interactive logins. Evidence of successful configuration is usually indicated by a prompt for the user to insert a smartcard. If the smartcard is already inserted, the network device will prompt the user to enter the corresponding PIN which unlocks the certificate keystore on the smartcard. If the network device is not configured to use DoD PKI as MFA for interactive logins, this is a finding. If the PKI authenticated user is not mapped to the effective local user account this is a finding . Note: Alternative MFA solutions for network devices with basic user interfaces (e.g., L2 switch with only SSH access) have been evaluated by the DoD Privileged User Working Group (PUWG). Current alternatives include RSA SecureID tokens and YubiKey One Time Password (OTP) tokens. To use an alternative MFA solution, a business case and risk assessment must be presented to the Authorizing Official (AO) for review and acceptance. AOs may choose to accept the risk of using one of these alternatives in a target environment based on the business case that was presented. If so, it is the responsibility of the AO to determine if the risk should be downgraded to a CAT II or a CAT III based on the risk assessment of the target environment. If DoD PKI is not used but the network device makes use of an alternative FIPS 140-2 compliant, Cryptographic Module Validation Program (CMVP) validated OTP password solution, then this requirement can be downgraded to a CAT III. Note: Other mitigation strategies which have not been evaluated by the DoD PUWG may include the use of one or more industry solutions. One-time password/PIN/passcodes (OTP), one-time URLs, time-based tokens, and biometrics are examples of such solutions. While AOs may choose to accept the risk of using these alternatives on a case-by-case basis, for DoD the risk of using these alternatives should never be mitigated below a CAT II. Note: This requirement is not applicable to the emergency account of last resort nor for service accounts (non-interactive users). Examples of service accounts include remote service brokers such as AAA, syslog, etc.
Discussion
Multi-factor authentication (MFA) is when two or more factors are used to confirm the identity of an individual who is requesting access to digital information resources. Valid factors include something the individual knows (e.g., username and password), something the individual has (e.g., a smartcard or token), or something the individual is (e.g., a fingerprint or biometric). Legacy information system environments only use a single factor for authentication, typically a username and password combination. Although two pieces of data are used in a username and password combination, this is still considered single factor because an attacker can obtain access simply by learning what the user knows. Common attacks against single-factor authentication are attacks on user passwords. These attacks include brute force password guessing, password spraying, and password credential stuffing. MFA, along with strong user account hygiene, helps mitigate against the threat of having account passwords discovered by an attacker. Even in the event of a password compromise, with MFA implemented and required for interactive login, the attacker still needs to acquire something the user has or replicate a piece of user’s biometric digital presence. Private industry recognizes and uses a wide variety of MFA solutions. However, DoD public key infrastructure (PKI) is the only prescribed method approved for DoD organizations to implement MFA. For authentication purposes, centralized DoD certificate authorities (CA) issue PKI certificate key pairs (public and private) to individuals using the prescribed x.509 format. The private certificates that have been generated by the issuing CA are downloaded and saved to smartcards which, within DoD, are referred to as common access cards (CAC) or personal identity verification (PIV) cards. This happens at designated DoD badge facilities. The CA maintains a record of the corresponding public keys for use with PKI-enabled environments. Privileged user smartcards, or “alternate tokens”, function in the same manner, so this requirement applies to all interactive user sessions (authorized and privileged users). Note: This requirement is used in conjunction with the use of a centralized authentication server (e.g., AAA, RADIUS, LDAP), a separate but equally important requirement. The MFA configuration of this requirement provides identification and the first phase of authentication (the challenge and validated response, thereby confirming the PKI certificate that was presented by the user). The centralized authentication server will provide the second phase of authentication (the digital presence of the PKI ID as a valid user in the requested security domain) and authorization. The centralized authentication server will map validated PKI identities to valid user accounts and determine access levels for authenticated users based on security group membership and role. In cases where the centralized authentication server is not utilized by the network device for user authorization, the network device must map the authenticated identity to the user account for PKI-based authentication.
Fix
Configure the network device to use DoD PKI as MFA for interactive logins.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000169-NDM-000257: The network device must enforce password complexity by requiring that at least one special character be used.
Where passwords are used, confirm that the network device and associated authentication server enforces password complexity by requiring that at least one special character be used. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device and associated authentication server does not require that at least one special character be used in each password, this is a finding.
Discussion
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. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Fix
Configure the network device and associated authentication server to enforce password complexity by requiring that at least one special character be used.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000412-NDM-000331: The network device must be configured to implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions
Review the network device configuration to determine if cryptographic mechanisms are implemented using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions If the network device is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm, this is a finding.
Discussion
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.
Fix
Configure the network device to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000170-NDM-000329: The network device must require that when a password is changed, the characters are changed in at least eight of the positions within the password.
Where passwords are used, confirm the characters are changed in at least eight of the positions within the password. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device and associated authentication server does not require that when a password is changed, the characters are changed in at least eight of the positions within the password, this is a finding.
Discussion
: If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Fix
Configure the network device and associated authentication server to require that when a password is changed, the characters are changed in at least eight of the positions within the password.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000004-NDM-000203: The network device must be configured to enable network administrators to directly initiate a session lock.
Directly observe the management application or the console; if an administrator cannot directly initiate a session lock from either the management application or the console, this is a finding.
Discussion
A session lock is a temporary network device or administrator-initiated action taken when the administrator stops work but does not log out of the network device. Rather than being forced to wait for a period of time to expire before the management session can be locked, network management consoles need to provide administrators with the ability to manually invoke a session lock so they may secure their management session should the need arise for them to temporarily vacate the immediate physical vicinity of the management workstation. Once invoked, the session lock shall remain in place until the administrator re-authenticates. No other system activity aside from re-authentication shall unlock the management session. The session lock is implemented at the point where session activity can be determined. This is typically at the operating system-level, but may be at the application-level. The session lock is initiated and controlled by either the client application or the workstation being used to access a network element. Many terminal emulation clients implement this capability through software flow control or XOFF/XON flow control. If this capability is not available, administrators must terminate all management sessions before leaving their management console or workstation. This includes closing any views or windows from those sessions.
Fix
This is an intrinsic capability of the client application or the console. Many terminal emulation clients implement this capability through software flow control or XOFF/XON flow control.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000092-NDM-000224: The network device must initiate session auditing upon startup.
Determine if the network device initiates session auditing upon startup. This requirement may be verified by validated test results. If the network device does not initiate session auditing upon startup, this is a finding.
Discussion
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.
Fix
Configure the network device to initiate session auditing upon startup.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000038-NDM-000213: The network device must enforce approved authorizations for controlling the flow of management information within the network device based on information flow control policies.
Review the network device configuration to determine if it enforces approved authorizations for controlling the flow of management information within the network device based on information flow control policies. If it does not enforce these approved authorizations, this is a finding.
Discussion
A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management information flow is not enforced based on approved authorizations, the network device may become compromised. Information flow control regulates where management information is allowed to travel within a network device. The flow of all management information must be monitored and controlled so it does not introduce any unacceptable risk to the network device or data. Application-specific examples of enforcement occur in systems that employ rule sets or establish configuration settings that restrict information system services or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of management information within the system in accordance with applicable policy.
Fix
Configure the network device to enforce approved authorizations for controlling the flow of management information within the network device based on information flow control policies.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000317-NDM-000282: The network device must terminate shared/group account credentials when members leave the group.
Determine if the network device terminates shared/group account credentials when members leave the group. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. This requirement is not applicable if the device does not support shared/group credentials. If the network device does not terminate shared/group credentials when members leave the group, this is a finding.
Discussion
A shared/group account credential is a shared form of authentication that allows multiple individuals to access the network device using a single account. If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even though they are no longer authorized. There may also be instances when specific user actions need to be performed on the network device without unique administrator identification or authentication. Examples of credentials include passwords and group membership certificates.
Fix
Configure the network device to terminate shared/group account credentials when members leave the group.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000005-NDM-000204: The network device must retain the session lock until the administrator reestablishes access using established identification and authentication procedures.
Review the network device configuration to determine if the device retains session lock until the administrator re-authenticates. This may be verified by configuration check, demonstration, or other validation test results. If the device does not require re-authentication before releasing the session lock, this is a finding.
Discussion
A session lock is a temporary network device or administrator-initiated action taken when the administrator stops work but does not log out of the network device. Once invoked, the session lock shall remain in place until the administrator re-authenticates. No other system activity aside from re-authentication shall unlock the management session.
Fix
Configure the network device to retain session lock until the administrator re-authenticates.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000133-NDM-000244: The network device must limit privileges to change the software resident within software libraries.
Determine if the network device limits privileges to change the software resident within software libraries. If it does not limit privileges to change the software resident within software libraries, this is a finding.
Discussion
Changes to any software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals should be allowed administrative access to the network device for implementing any changes or upgrades. If the network device were to enable non-authorized users to make changes to software libraries, those changes could be implemented without undergoing testing, validation, and approval.
Fix
Configure the network device to limit privileges to change the software resident within software libraries.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000091-NDM-000223: The network device must generate audit records when successful/unsuccessful attempts to access privileges occur.
Determine if the network device generates audit records when successful/unsuccessful attempts to access privileges occur. If the network device does not generate audit records when successful/unsuccessful attempts to access privileges occur, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records when successful/unsuccessful attempts to access privileges occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000505-NDM-000322: The network device must generate audit records showing starting and ending time for administrator access to the system.
Determine if the network device generates audit records showing starting and ending time for administrator access to the system. If the network device does not generate audit records showing starting and ending time for administrator access to the system, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records showing starting and ending time for administrator access to the system.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000374-NDM-000299: The network device must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
Determine if the network device records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). This requirement may be verified by demonstration or configuration review. If the network device does not record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT), this is a finding.
Discussion
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
Fix
Configure the network device to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000121-NDM-000238: The network device must protect audit tools from unauthorized access.
If the network device provides audit tools, check the device to determine if it protects audit tools from unauthorized access. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not protect its audit tools from unauthorized access, this is a finding.
Discussion
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Network devices providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Fix
Configure the network device to protect audit tools from unauthorized access.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000343-NDM-000289: The network device must audit the execution of privileged functions.
Determine if the network device audits the execution of privileged functions. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not audit the execution of privileged functions, this is a finding.
Discussion
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.
Fix
Configure the network device to audit the execution of privileged functions.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000495-NDM-000318: The network device must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.
Determine if the network device generates audit records when successful/unsuccessful attempts to modify administrator privileges occur. If the network device does not generate audit records when successful/unsuccessful attempts to modify administrator privileges occur, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000360-NDM-000295: The network device must generate an immediate real-time alert of all audit failure events requiring real-time alerts.
Determine if the network device generates an immediate alert of all audit failure events requiring real-time alerts. This requirement may be verified by configuration review or validated test results. If an immediate alert of all audit failure events requiring real-time alerts is not generated, this is a finding.
Discussion
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).
Fix
Configure the network device to generate an immediate real-time alert of all audit failure events requiring real-time alerts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000120-NDM-000237: The network device must protect audit information from unauthorized deletion.
Determine if the network device protects audit information from any type of unauthorized deletion with such methods as ensuring log files receive the proper file system permissions utilizing file system protections, restricting access to log data and backing up log data to ensure log data is retained, and leveraging user permissions and roles to identify the user accessing the data and the corresponding rights the user enjoys. This requirement may be verified by demonstration, configuration, or validated test results. If the network device does not protect audit information from unauthorized deletion, this is a finding.
Discussion
Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the network device must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files receive the proper file system permissions utilizing file system protections, restricting access, and backing up log data to ensure log data is retained. Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order to make access decisions regarding the deletion of audit data.
Fix
Configure the network device to protect audit information from unauthorized deletion.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000178-NDM-000264: The network device must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
Determine if the network device obscures feedback of authentication information during the authentication process. This requirement may be verified by demonstration. If the network device does not obscure feedback of authentication information during the authentication process, this is a finding.
Discussion
To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the network device must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. For example, displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.
Fix
Configure the network device to obscure feedback of authentication information during the authentication process.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000029-NDM-000211: The network device must automatically audit account removal actions.
Check the network device to determine if account removal actions are automatically audited. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If account removal actions are not automatically audited, this is a finding.
Discussion
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.
Fix
Configure the network device or its associated authentication server to automatically audit the removal of accounts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000515-NDM-000325: The network device must off-load audit records onto a different system or media than the system being audited.
Check the network device configuration to determine if the device off-loads audit records onto a different system or media than the system being audited. If the device does not off-load audit records onto a different system or media, this is a finding.
Discussion
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity.
Fix
Configure the network device to off-load audit records onto a different system or media than the system being audited.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000336: The network device must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access.
Review the network device configuration to verify that the device is configured to use at least two authentication servers as primary source for authentication. If the network device is not configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access, this is a finding.
Discussion
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.
Fix
Step 1: Configure the network device to use at least two authentication servers. Step 2: Configure the authentication order to use the authentication servers as primary source for authentication. Step 3: Configure all network connections associated with a device management to use the authentication servers for the purpose of login authentication.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000153-NDM-000249: The network device must be configured to authenticate each administrator prior to authorizing privileges based on assignment of group or role.
Determine if the network device ensures that administrators are authenticated with an individual authenticator prior to using a group authenticator. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not authenticate administrators with an individual authenticator prior to using a group authenticator, this is a finding.
Discussion
To assure individual accountability and prevent unauthorized access, administrators must be individually identified and authenticated. Individual accountability mandates that each administrator is uniquely identified. A group authenticator is a shared account or some other form of authentication that allows multiple unique individuals to access the network device using a single account. If a device allows or provides for group authenticators, it must first individually authenticate administrators prior to implementing group authenticator functionality. Some devices may not have the need to provide a group authenticator; this is considered a matter of device design. In those instances where the device design includes the use of a group authenticator, this requirement will apply. This requirement applies to accounts created and managed on or by the network device.
Fix
Configure the network device to ensure administrators are authenticated with an individual authenticator prior to using a group authenticator.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000026-NDM-000208: The network device must automatically audit account creation.
Review the network device configuration to determine if it automatically audits account creation or is configured to use an authentication server which would perform this function. If account creation is not automatically audited, this is a finding.
Discussion
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. Notification of account creation helps to mitigate this risk. Auditing account creation provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes.
Fix
Configure the network device or its associated authentication server to automatically audit the creation of accounts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000001-NDM-000200: The network device must limit the number of concurrent sessions to an organization-defined number for each administrator account and/or administrator account type.
Review the network device configuration to see if the device limits the number of concurrent sessions to an organization-defined number for all administrator accounts and/or administrator account types. If the network device does not limit the number of concurrent sessions to an organization-defined number for each administrator account and/or administrator account type, this is a finding.
Discussion
Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to DoS attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions.
Fix
Configure the network device to limit the number of concurrent sessions to an organization-defined number for all administrator accounts and/or administrator account types.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000504-NDM-000321: The network device must generate audit records for privileged activities or other system-level access.
Determine if the network device generates audit records for privileged activities or other system-level access. If the network device does not generate audit records for privileged activities or other system-level access, this is a finding.
Discussion
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).
Fix
Configure the network device to generate audit records for privileged activities or other system-level access.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000098-NDM-000228: The network device must produce audit log records containing information to establish the source of events.
Determine if the network device is configured to produce audit records containing information to establish the source (apparent cause) of the event. If the network device does not produce audit records containing information to establish the source of the event, this is a finding.
Discussion
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. Associating information about where the source of the event occurred provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured device.
Fix
Configure the network device to produce audit records containing information to establish the source of the event.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000167-NDM-000255: The network device must enforce password complexity by requiring that at least one lower-case character be used.
Where passwords are used, confirm that the network device and associated authentication server enforces password complexity by requiring that at least one lower-case character be used. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device and associated authentication server does not require that at least one lower-case character be used in each password, this is a finding.
Discussion
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. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Fix
Configure the network device and associated authentication server to enforce password complexity by requiring that at least one lower-case character be used.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000351: The network device must be running an operating system release that is currently supported by the vendor.
Verify that the network device is in compliance with this requirement. If the network device is not running an operating system release that is currently supported by the vendor, this is a finding.
Discussion
Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.
Fix
Upgrade the network device to an operating system that is supported by the vendor.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000516-NDM-000341: The network device must support organizational requirements to conduct backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner.
Review the network device backup configuration to determine if the network device backs up the information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner. If the network device does not backup the information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner, this is a finding.
Discussion
Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system configuration and security settings. If this information were not backed up, and a system failure were to occur, the security settings would be difficult to reconfigure quickly and accurately. Maintaining a backup of information system and security-related documentation provides for a quicker recovery time when system outages occur. This control requires the network device to support the organizational central backup process for user account information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups.
Fix
Configure the network device to conduct backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000408-NDM-000314: Network devices performing maintenance functions must restrict use of these functions to authorized personnel only.
Determine if the network device restricts the use of maintenance functions to authorized personnel only. If other personnel can use maintenance functions on the network device, this is a finding.
Discussion
There are security-related issues arising from software brought into the network device specifically for diagnostic and repair actions (e.g., a software packet sniffer installed on a device in order to troubleshoot system traffic, or a vendor installing or running a diagnostic application in order to troubleshoot an issue with a vendor-supported device). If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. This requirement addresses security-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational network devices. Maintenance tools can include hardware, software, and firmware items. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into organizational information systems. Maintenance tools can include, for example, hardware/software diagnostic test equipment and hardware/software packet sniffers. This requirement does not cover hardware/software components that may support information system maintenance yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
Fix
Configure the network device to restrict use of maintenance functions to authorized personnel only.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000168-NDM-000256: The network device must enforce password complexity by requiring that at least one numeric character be used.
Where passwords are used, confirm that the network device and associated authentication server enforces password complexity by requiring that at least one numeric character be used. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device and associated authentication server does not require that at least one numeric character be used in each password, this is a finding.
Discussion
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. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Fix
Configure the network device and associated authentication server to enforce password complexity by requiring that at least one numeric character be used.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000080-NDM-000345: The network device must not have any default manufacturer passwords when deployed.
Review the configuration of the network device to determine if the vendor default password is present. This may involve showing the passwords configured on the device in the clear.
Discussion
Network devices not protected with strong password schemes provide the opportunity for anyone to crack the password and gain access to the device, which can result in loss of availability, confidentiality, or integrity of network traffic. Many default vendor passwords are well known or are easily guessed; therefore, not removing them prior to deploying the network device into production provides an opportunity for a malicious user to gain unauthorized access to the device.
Fix
Remove any vendor default passwords from the network device configuration.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000340-NDM-000288: The network device must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
Determine if the network device prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not prevent non-privileged users from executing privileged functions, this is a finding.
Discussion
Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations.
Fix
Configure the network device to prevent non-privileged users from executing privileged functions.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000028-NDM-000210: The network device must automatically audit account disabling actions.
Check the network device to determine if account disabling actions are automatically audited. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If account disabling actions are not audited, this is a finding.
Discussion
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 disabling actions will support account management procedures. When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.
Fix
Configure the network device or its associated authentication server to automatically audit the disabling of accounts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000381-NDM-000305: The network device must audit the enforcement actions used to restrict access associated with changes to the device.
Determine if the network device audits the enforcement actions used to restrict access associated with changes to the device. This requirement may be verified by demonstration, configuration review or validated test results. If the network device does not audit the enforcement actions used to restrict access associated with changes to the device, this is a finding.
Discussion
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.
Fix
Configure the network device to audit the enforcement actions used to restrict access associated with changes to the device.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000411-NDM-000330: The network devices must use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications.
Verify the network device uses FIPS-validated HMAC to protect the integrity of nonlocal maintenance and diagnostic communications. If the network device does not use FIPS-validated HMAC to protect the integrity of nonlocal maintenance and diagnostic communications, this is a finding.
Discussion
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Currently, HMAC is the only FIPS-approved algorithm for generating and verifying message/data authentication codes in accordance with FIPS 198-1. Products that are FIPS 140-2 validated will have an HMAC that meets specification; however, the option must be configured for use as the only message authentication code used for authentication to cryptographic modules. Separate requirements for configuring applications and protocols used by each application (e.g., SNMPv3, SSHv2, NTP, HTTPS, and other protocols and applications that require server/client authentication) are required to implement this requirement. Where SSH is used, the SSHv2 protocol suite is required because it includes Layer 7 protocols such as SCP and SFTP, which can be used for secure file transfers.
Fix
Configure the network device to use FIPS-validated HMAC to protect the integrity of nonlocal maintenance and diagnostic communications.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000123-NDM-000240: The network device must protect audit tools from unauthorized deletion.
If the network device provides audit tools, check to see that the network device protects audit tools from unauthorized deletion. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device does not protect its audit tools from unauthorized deletion, this is a finding.
Discussion
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit data. Network devices providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Fix
Configure the network device to protect audit tools from unauthorized deletion.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000027-NDM-000209: The network device must automatically audit account modification.
Check the network device to determine if account modification actions are automatically audited. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If account modification is not automatically audited, this is a finding.
Discussion
Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel with the appropriate and necessary privileges. Auditing account modification along with an automatic notification to appropriate individuals will provide the necessary reconciliation that account management procedures are being followed. If modifications to management accounts are not audited, reconciliation of account management procedures cannot be tracked.
Fix
Configure the network device or its associated authentication server to automatically audit the modification of accounts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000171-NDM-000258: The network device must only store cryptographic representations of passwords.
Review the network device’s files using a text editor or a database tool that allows viewing data stored in database tables. Determine if password strings are readable/discernable. Determine if the network device, and any associated authentication servers, enforce only storing cryptographic representations of passwords. Verify that databases, configuration files, and log files have encrypted representations of all passwords, and that no password strings are readable/discernable. Potential locations include the local file system where configurations and events are stored, or in a network device related database table. Also identify if the network device uses the MD5 hashing algorithm to create password hashes. If the network device, or any associated authentication servers, stores unencrypted (clear text) representations of passwords, this is a finding. If the network device uses MD5 hashing algorithm to create password hashes, this is a finding.
Discussion
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Network devices must enforce cryptographic representations of passwords when storing passwords in databases, configuration files, and log files. Passwords must be protected at all times; using a strong one-way hashing encryption algorithm with a salt is the standard method for providing a means to validate a password without having to store the actual password. Performance and time required to access are factors that must be considered, and the one way hash is the most feasible means of securing the password and providing an acceptable measure of password security. If passwords are stored in clear text, they can be plainly read and easily compromised. In many instances, verifying the user knows a password is performed using a password verifier. In its simplest form, a password verifier is a computational function that is capable of creating a hash of a password and determining if the value provided by the user matches the stored hash.
Fix
Configure the network device, and any associated authentication servers, to store all passwords using cryptographic representations. Configure all associated databases, configuration files, and log files to use only encrypted representations of passwords, and that no password strings are readable/discernable. Potential locations include the local file system where configurations and events are stored, or in a network device-related database table.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000156-NDM-000250: The network device must implement replay-resistant authentication mechanisms for network access to privileged accounts.
Determine if the network device implements replay-resistant authentication mechanisms for network access to privileged accounts. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If the network device does not implement replay-resistant authentication mechanisms for network access to privileged accounts, this is a finding.
Discussion
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.
Fix
Configure the network device to implement replay-resistant authentication mechanisms for network access to privileged accounts.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000491-NDM-000316: If the network device uses mandatory access control, the network device must enforce organization-defined mandatory access control policies over all subjects and objects.
Check the network device to determine if organization-defined mandatory access control policies are enforced over all subjects and objects. If it does not use mandatory access control, this is not a finding. If organization-defined mandatory access control policies are not enforced over all subjects and objects, this is a finding.
Discussion
Mandatory access control policies constrain what actions subjects can take with information obtained from data objects for which they have already been granted access, thus preventing the subjects from passing the information to unauthorized subjects and objects. This class of mandatory access control policies also constrains what actions subjects can take with respect to the propagation of access control privileges; that is, a subject with a privilege cannot pass that privilege to other subjects. Enforcement of mandatory access control is typically provided via an implementation that meets the reference monitor concept. The reference monitor enforces (mediates) access relationships between all subjects and objects based on privilege and need to know. The mandatory access control policies are defined uniquely for each network device, so they cannot be specified in the requirement. An example of where mandatory access control may be needed is to prevent administrators from tampering with audit objects.
Fix
Configure the network device to enforce organization-defined mandatory access control policies over all subjects and objects.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000142-NDM-000245: The network device must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services
Determine if the network device prohibits the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services. If any unnecessary or nonsecure functions are permitted, this is a finding.
Discussion
In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused or unnecessary physical and logical ports/protocols on information systems. Network devices are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the network device must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved. Some network devices have capabilities enabled by default; if these capabilities are not necessary, they must be disabled. If a particular capability is used, then it must be documented and approved.
Fix
Configure the network device to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000175-NDM-000262: The network device must be configured to use DoD approved OCSP responders or CRLs to validate certificates used for PKI-based authentication.
Verify the network device is configured to validate certificates used for PKI-based authentication using DoD approved OCSP or CRL resources. If the network device is not configured to validate certificates used for PKI-based authentication using DoD approved OCSP or CRL sources, this is a finding. Note: This requirement may be not applicable if the network device is not configured to use DoD PKI as multi-factor authentication for interactive logins. In that scenario, this requirement should be included as part of the business case and discussion with the AO who is required to accept the risk of the alternative solution. However, if alternative DoD or AO approved solutions are employed which still rely on some form of PKI (digital certificates), this requirement should be tailored to configure certificate validation of the accepted solution. An example may be the reinforcement of a list of explicitly allowed, unique per user, session certificates that are both configured on the devices and documented with the ISSO and ISSM (implying that all other certificates are also explicitly forbidden).
Discussion
Once issued by a DoD certificate authority (CA), public key infrastructure (PKI) certificates are typically valid for 3 years or shorter within the DoD. However, there are many reasons a certificate may become invalid before the prescribed expiration date. For example, an employee may leave or be terminated and still possess the smartcard on which the PKI certificates were stored. Another example is that a smartcard containing PKI certificates may become lost or stolen. A more serious issue could be that the CA or server which issued the PKI certificates has become compromised, thereby jeopardizing every certificate keypair that was issued by the CA. These examples of revocation use cases and many more can be researched further using Internet cybersecurity resources. PKI user certificates presented as part of the identification and authentication criteria (e.g., DoD PKI as multi-factor authentication [MFA]) must be checked for validity by network devices. For example, valid PKI certificates are digitally signed by a trusted DoD certificate authority (CA). Additionally, valid PKI certificates are not expired, and valid certificates have not been revoked by a DoD CA. Network devices can verify the validity of PKI certificates by checking with an authoritative CA. One method of checking the status of PKI certificates is to query databases referred to as certificate revocation lists (CRL). These are lists which are published, updated, and maintained by authoritative DoD CAs. For example, once certificates are expired or revoked, issuing CAs place the certificates on a certificate revocation list (CRL). Organizations can download these lists periodically (i.e. daily or weekly) and store them locally on the devices themselves or even onto another nearby local enclave resource. Storing them locally ensures revocation status can be checked even if Internet connectivity is severed at the enclave’s point of presence (PoP). However, CRLs can be rather large in storage size and further, the use of CRLs can be rather taxing on some computing resources. Another method of validating certificate status is to use the online certificate status protocol (OCSP). Using OCSP, a requestor (i.e. the network device which the user is trying to authenticate to) sends a request to an authoritative CA challenging the validity of a certificate that has been presented for identification and authentication. The CA receives the request and sends a digitally signed response indicating the status of the user’s certificate as valid, revoked, or unknown. Network devices should only allow access for responses that indicate the certificates presented by the user were considered valid by an approved DoD CA. OCSP is the preferred method because it is fast, provides the most current status, and is lightweight.
Fix
Configure the network device to validate certificates used for PKI-based authentication using DoD approved OCSP or CRL sources.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000435-NDM-000315: The network device must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
Determine if the network device protects against or limits the effects of all known types of DoS attacks by employing organization-defined security safeguards. If the network device does not protect against or limit the effects of all known types of DoS attacks by employing organization-defined security safeguards, this is a finding.
Discussion
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. The security safeguards cannot be defined at the DoD level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (for example, firewalls performing packet filtering to block DoS attacks).
Fix
Configure the network device to protect against or limit the effects of all known types of DoS attacks by employing organization-defined security safeguards.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000148-NDM-000346: The network device must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.
Review the network device configuration to determine if an account of last resort is configured. Verify default admin and other vendor-provided accounts are disabled, removed, or renamed where possible. Verify the username and password for the account of last resort is contained within a sealed envelope and kept in a safe. If one local account does not exist for use as the account of last resort, this is a finding.
Discussion
Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.
Fix
Configure the device to only allow one local account for use as the account of last resort.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000065-NDM-000214: The network device must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
Review the device configuration to verify that it enforces the limit of three consecutive invalid logon attempts. If the device is not configured to enforce the limit of three consecutive invalid logon attempts, this is a finding.
Discussion
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced.
Fix
Configure the network device to enforce the limit of three consecutive invalid logon attempts during a 15-minute time period.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000395-NDM-000347: The network device must authenticate Network Time Protocol sources using authentication that is cryptographically based.
Review the network device configuration to determine if the network device authenticates NTP endpoints before establishing a local, remote, or network connection using authentication that is cryptographically based. If the network device does not authenticate Network Time Protocol sources using authentication that is cryptographically based, this is a finding.
Discussion
If Network Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.
Fix
Configure the network device to authenticate Network Time Protocol sources using authentication that is cryptographically based.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000334: The network device must generate log records for a locally developed list of auditable events
Determine if the network device generates audit log events for a locally developed list of auditable events. If the network device is not configured to generate audit log events for a locally developed list of auditable events, this is a finding.
Discussion
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.
Fix
Configure the network device to generate audit log events for a locally developed list of auditable events.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000373-NDM-000298: The network device must be configured to synchronize internal information system clocks using redundant authoritative time sources.
Determine if the network device is configured to synchronize internal information system clocks with the primary and secondary time sources. If the network device is not configured to synchronize internal information system clocks with the primary and secondary time sources, this is a finding.
Discussion
The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions. Multiple time sources provide redundancy by including a secondary source. Time synchronization is usually a hierarchy; clients synchronize time to a local source while that source synchronizes its time to a more accurate source. The network device must utilize an authoritative time server and/or be configured to use redundant authoritative time sources. This requirement is related to the comparison done in CCI-001891. DoD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DoD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source.
Fix
Configure the network device to synchronize internal information system clocks with the primary and secondary time sources.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000068-NDM-000215: The network device must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.
Determine if the network device is configured to present a DoD-approved banner that is formatted in accordance with DTM-08-060. If such a banner is not presented, this is a finding. Use the following verbiage for applications that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."
Discussion
Display of the DoD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users.
Fix
Configure the network device to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000344: The network device must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
Determine if the network device obtains public key certificates from an appropriate certificate policy through an approved service provider. If the network device does not obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.
Discussion
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.
Fix
Configure the network device to obtain its public key certificates from an appropriate certificate policy through an approved service provider.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000328-NDM-000286: If the network device uses discretionary access control, the network device must enforce organization-defined discretionary access control policies over defined subjects and objects.
Check the network device to determine if organization-defined discretionary access control policies are enforced over defined subjects and objects. If it does not use discretionary access control, this is not a finding. If organization-defined discretionary access control policies are not enforced over defined subjects and objects, this is a finding.
Discussion
Discretionary Access Control (DAC) is based on the notion that individual network administrators are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. The discretionary access control policies and the subjects and objects are defined uniquely for each network device, so they cannot be specified in the requirement.
Fix
Configure the network device to enforce organization-defined discretionary access control policies over defined subjects and objects.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000096-NDM-000226: The network device must produce audit records containing information to establish when (date and time) the events occurred.
Determine if the network device is configured to produce audit records containing information to establish when (date and time) the events occurred. If the network device does not produce audit records containing information to establish when the events occurred, this is a finding.
Discussion
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.
Fix
Configure the network device to produce audit records containing information to establish when (date and time) the events occurred.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000069-NDM-000216: The network device must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access.
Determine if the network device is configured to retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access. If the network device does not retain the banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access, this is a finding.
Discussion
The banner must be acknowledged by the administrator prior to the device allowing the administrator access to the network device. This provides assurance that the administrator has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the administrator, DoD will not be in compliance with system use notifications required by law. To establish acceptance of the network administration policy, a click-through banner at management session logon is required. The device must prevent further activity until the administrator executes a positive action to manifest agreement. In the case of CLI access using a terminal client, entering the username and password when the banner is presented is considered an explicit action of acknowledgement. Entering the username, viewing the banner, then entering the password is also acceptable.
Fix
Configure the network device to retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000116-NDM-000234: The network device must use internal system clocks to generate time stamps for audit records.
Determine if the network device uses internal system clocks to generate time stamps for audit records. This requirement may be verified by demonstration, configuration, or validated test results. If the network device does not use internal system clocks to generate time stamps for audit records, this is a finding.
Discussion
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.)
Fix
Configure the network device to use internal system clocks to generate time stamps for audit records.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000002-NDM-000201: The network device must conceal, via the session lock, information previously visible on the display with a publicly viewable image.
Review the network device configuration to see if the device conceals information previously visible on the display with a publicly viewable image during the session lock. This can be demonstrated by the network administrator. If previously visible information is not concealed with a publicly viewable image by the session lock, this is a finding.
Discussion
A session lock is a temporary network device or administrator-initiated action taken when the administrator stops work but does not log out of the network device. The network management session lock event must include an obfuscation of the display screen to prevent other users from reading what was previously displayed. Permitted publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, or a blank screen, with the additional caveat that none of the images convey sensitive information.
Fix
Configure the network device to conceal information previously visible on the display with a publicly viewable image during the session lock.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000380-NDM-000304: The network device must enforce access restrictions associated with changes to device configuration.
Determine if the network device enforces access restrictions associated with changes to device configuration. If the network device does not enforce such access restrictions, this is a finding.
Discussion
Failure to provide logical access restrictions associated with changes to device configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the device can potentially have significant effects on the overall security of the device. Accordingly, only qualified and authorized individuals should be allowed to obtain access to device components for the purposes of initiating changes, including upgrades and modifications. Logical access restrictions include, for example, controls that restrict access to workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).
Fix
Configure the network device to enforce access restrictions associated with changes to device configuration.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000179-NDM-000265: The network device must use FIPS 140-2 approved algorithms for authentication to a cryptographic module.
Determine if the network device uses FIPS 140-2 approved algorithms for authentication to a cryptographic module. If the network device is not configured to use a FIPS-approved authentication algorithm to a cryptographic module, this is a finding.
Discussion
Unapproved mechanisms that are used for authentication to the cryptographic module are not validated and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised. Network devices utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. However, authentication algorithms must configure security processes to use only FIPS-approved and NIST-recommended authentication algorithms.
Fix
Configure the network device to use FIPS 140-2 approved algorithms for authentication to a cryptographic module.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000172-NDM-000259: The network device must transmit only encrypted representations of passwords.
Determine if the network device or its associated authentication server transmits only encrypted representations of passwords. This requirement may be verified by demonstration or configuration review. If the network device or the associated authentication server transmits unencrypted representations of passwords, this is a finding.
Discussion
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Network devices can accomplish this by making direct function calls to encryption modules or by leveraging operating system encryption capabilities.
Fix
Configure the network device or its associated authentication server to transmit only encrypted representations of passwords.
Rating Info
DISA Cat I. NIST impact 4.
Expert Comment
None
SRG-APP-000080-NDM-000220: The network device 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.
Determine if the network device protects 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 requires logging all administrator access and configuration activity. This requirement may be verified by demonstration or configuration review. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. (Note that two-factor authentication of administrator access is needed to support this requirement.) If the network device does not 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 is a finding.
Discussion
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.
Fix
Configure the network device or its associated authentication server to 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. Examples that support this include configuring the audit log to capture administration login events and configuration changes to the network device.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000223-NDM-000269: The network device must recognize only system-generated session identifiers.
If the network device uses a web interface for device management, determine if it recognizes only system-generated session identifiers. This requirement may be verified by demonstration, configuration review, or validated test results. If the network device recognizes other session identifiers than the system-generated ones, this is a finding.
Discussion
Network device management web interfaces utilize sessions and session identifiers to control management interface behavior and administrator access. If an attacker can guess the session identifier or can inject or manually insert session information, the session may be compromised. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions.
Fix
Configure the network device to recognize only system-generated session identifiers.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000375-NDM-000300: The network device must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
Determine if the network device records time stamps for audit records that meet a granularity of one second for a minimum degree of precision. This requirement may be verified by demonstration or configuration. If the network device does not record time stamps for audit records that meet a granularity of one second for a minimum degree of precision, this is a finding.
Discussion
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.
Fix
Configure the network device to record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000378-NDM-000302: The network device must prohibit installation of software without explicit privileged status.
Determine if the network device prohibits installation of software without explicit privileged status. This requirement may be verified by demonstration or configuration review. If installation of software is not prohibited without explicit privileged status, this is a finding.
Discussion
Allowing anyone to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. This requirement applies to code changes and upgrades for all network devices.
Fix
Configure the network device to prohibit installation of software without explicit privileged status.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000186-NDM-000266: The network device must terminate all sessions and network connections when nonlocal device maintenance is completed.
Determine if the network device terminates all sessions and network connections when nonlocal device maintenance is completed. This requirement may be verified by demonstration or validated test results. If the network device does not terminate all sessions and network connections when nonlocal device maintenance is complete, this is a finding.
Discussion
If a device management session or connection remains open after management is completed, it may be hijacked by an attacker and used to compromise or damage the network device. Nonlocal device management and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. In the event the remote node has abnormally terminated or an upstream link from the managed device is down, the management session will be terminated, thereby freeing device resources and eliminating any possibility of an unauthorized user being orphaned to an open idle session of the managed device.
Fix
Configure the network device to terminate all sessions and network connections when nonlocal device maintenance is completed.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000095-NDM-000225: The network device must produce audit log records containing sufficient information to establish what type of event occurred.
Determine if the network device produces audit log records containing sufficient information to establish what type of event occurred. If the network device does not produce audit log records containing sufficient information to establish what type of event occurred, this is a finding.
Discussion
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.
Fix
Configure the network device to produce audit log records containing sufficient information to establish what type of event occurred.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000329-NDM-000287: If the network device uses role-based access control, the network device must enforce organization-defined role-based access control policies over defined subjects and objects.
Determine if the network device enforces role-based access control policy over defined subjects and objects. This requirement may be verified by demonstration, configuration review, or validated test results. This requirement may be met through use of a properly configured authentication server if the device is configured to use the authentication server. If role-based access control policy is not enforced over defined subjects and objects, this is a finding.
Discussion
Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the organization-defined roles. When administrators are assigned to the organizational roles, they inherit the authorizations or privileges defined for those roles. RBAC simplifies privilege administration for organizations because privileges are not assigned directly to every administrator (which can be a significant number of individuals for mid- to large-size organizations) but are instead acquired through role assignments. RBAC can be implemented either as a mandatory or discretionary form of access control. The RBAC policies and the subjects and objects are defined uniquely for each network device, so they cannot be specified in the requirement.
Fix
Configure the network device or its associated authentication server to enforce role-based access control policy over defined subjects and objects.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000003-NDM-000202: The network device must initiate a session lock after a 15-minute period of inactivity.
Review the network device configuration to see if it initiates a session lock after a 15-minute period of inactivity. This may be verified by configuration check or demonstration. If a session lock is not initiated after a 15-minute period of inactivity, this is a finding.
Discussion
A session lock is a temporary network device or administrator-initiated action taken when the administrator stops work but does not log out of the network device. Rather than relying on the user to manually lock their management session prior to vacating the vicinity, network devices need to be able to identify when a management session has idled and take action to initiate the session lock. Once invoked, the session lock shall remain in place until the administrator re-authenticates. No other system activity aside from re-authentication shall unlock the management session. Note that CCI-001133 requires that administrative network sessions be disconnected after 10 minutes of idle time. So this requirement may only apply to local administrative sessions.
Fix
Configure the network device to initiate a session lock after a 15-minute period of inactivity.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000516-NDM-000317: The network device must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
Determine if the network device is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not configured in accordance with the designated security configuration settings, this is a finding.
Discussion
Configuring the network device to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the network device. Security-related parameters are those parameters impacting the security state of the network device, including the parameters required to satisfy other security control requirements.
Fix
Configure the network device to be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None
SRG-APP-000457-NDM-000352: The application must install security-relevant firmware updates within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
Obtain evidence that firmware updates are consistently applied to the network device within the time frame defined for each patch. If such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding. If the network device does not install security-relevant updates within the time period directed by the authoritative source, this is a finding.
Discussion
Security flaws with firmware are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant firmware updates. Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install firmware patches across the enclave (e.g., mobile device management solutions). Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant firmware updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant firmware updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
Fix
Institute and adhere to policies and procedures to ensure that patches are consistently applied to the network device within the time allowed.
Rating Info
DISA Cat II. NIST impact 3.
Expert Comment
None