Network Devices Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1800
- Vuln IDs
-
- V-3008
- Rule IDs
-
- SV-3008r1_rule
Checks: C-3837r1_chk
Have the SA display the configuration settings that enable this feature. Review the network topology diagram, and review VPN concentrators. Determine if tunnel mode is being used by reviewing the configuration. Examples: In CISCO Router(config)# crypto ipsec transform-set transform-set-name transform1 Router(cfg-crypto-tran)# mode tunnel OR in Junos edit security ipsec security-association sa-name] mode tunnel
Fix: F-3033r1_fix
Establish the VPN as a tunneled VPN. Terminate the tunneled VPN outside of the firewall. Ensure all host-to-host VPN are established between trusted known hosts.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0230
- Vuln IDs
-
- V-3012
- Rule IDs
-
- SV-3012r2_rule
Checks: C-3456r3_chk
Review the network element configuration to determine if administrative access to the device requires some form of authentication—at a minimum a password is required.
Fix: F-3037r5_fix
Configure the network element so it will require a password to gain administrative access to the device.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0340
- Vuln IDs
-
- V-3013
- Rule IDs
-
- SV-3013r2_rule
Checks: C-3474r8_chk
Review the device configuration or request that the administrator login to the device and observe the terminal. Verify either Option A or Option B (for systems with character limitations) of the Standard Mandatory DoD Notice and Consent Banner is displayed at logon. The required banner verbiage follows and must be displayed verbatim: Option A 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. Option B If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't.”
Fix: F-3038r6_fix
Configure all management interfaces to the network device to display the DoD mandated warning banner verbiage at login regardless of the means of connection or communication. The required banner verbiage that must be displayed verbatim is as follows: Option A 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. Option B If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't.”
- RMF Control
- Severity
- M
- CCI
- Version
- NET1639
- Vuln IDs
-
- V-3014
- Rule IDs
-
- SV-3014r2_rule
Checks: C-3540r4_chk
Review the management connection for administrative access and verify the network element is configured to time-out the connection after 10 minutes or less of inactivity.
Fix: F-3039r4_fix
Configure the network element to ensure the timeout for unattended administrative access connections is no longer than 10 minutes.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1027
- Vuln IDs
-
- V-3031
- Rule IDs
-
- SV-3031r1_rule
Checks: C-3955r1_chk
Review the syslog server configuration to ensure that it is collecting syslog messages levels 0 through 6 for the appropriate facilities.
Fix: F-3056r1_fix
The administrator will configure the syslog server to collect syslog messages levels 0 through 6.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1710
- Vuln IDs
-
- V-3046
- Rule IDs
-
- SV-3046r1_rule
Checks: C-3826r1_chk
Request that the network engineer demonstrate the alert capabilities.
Fix: F-3071r1_fix
The NSO will ensure that the NMS is configured, at a minimum, to alarm on the following security violations: integrity, operational, physical, security mechanism, and time domain violation.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1720
- Vuln IDs
-
- V-3047
- Rule IDs
-
- SV-3047r1_rule
Checks: C-3827r1_chk
Request that the network engineer demonstrate the alert capabilities.
Fix: F-3072r1_fix
The NSO will ensure that the NMS security alarm severity levels are configured as critical, major, minor, warning and indeterminate.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1750
- Vuln IDs
-
- V-3050
- Rule IDs
-
- SV-3050r1_rule
Checks: C-3830r1_chk
Review the NMS configuration and logs
Fix: F-3075r1_fix
The NSO will ensure that the NMS records all logons and transactions on the management station. The log will include at a minimum: time logged in and out, devices that were accessed and modified, and other activities performed. The audit will be stored online for a minimum of 30 days and offline for at least one year.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1760
- Vuln IDs
-
- V-3051
- Rule IDs
-
- SV-3051r1_rule
Checks: C-3831r1_chk
Review the NMS configuration to verify compliancy.
Fix: F-3076r1_fix
The NOC will ensure that access to the NMS is available only to authorized users with appropriate userids and passwords.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0460
- Vuln IDs
-
- V-3056
- Rule IDs
-
- SV-3056r5_rule
Checks: C-3503r9_chk
Review the network device configuration and validate there are no group accounts configured for access.
Fix: F-3081r9_fix
Configure individual user accounts for each authorized person then remove any group accounts.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0465
- Vuln IDs
-
- V-3057
- Rule IDs
-
- SV-3057r3_rule
Checks: C-3504r6_chk
Review the accounts authorized for access to the network device. Determine if the accounts are assigned the lowest privilege level necessary to perform assigned duties. User accounts must be set to a specific privilege level which can be mapped to specific commands or a group of commands. Authorized accounts should have the greatest privilege level unless deemed necessary for assigned duties. If it is determined that authorized accounts are assigned to greater privileges than necessary, this is a finding.
Fix: F-3082r5_fix
Configure authorized accounts with the least privilege rule. Each user will have access to only the privileges they require to perform their assigned duties.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0470
- Vuln IDs
-
- V-3058
- Rule IDs
-
- SV-3058r3_rule
Checks: C-3505r4_chk
Review the organization's responsibilities list and reconcile the list of authorized account with those accounts defined for access to the network device. If an unauthorized account is configured for access to the device, this is a finding.
Fix: F-3083r5_fix
Remove any account configured for access to the network device that is not defined in the organization's responsibilities list.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1638
- Vuln IDs
-
- V-3069
- Rule IDs
-
- SV-3069r3_rule
Checks: C-3532r7_chk
Review the network device configuration to verify only secure protocols using FIPS 140-2 validated cryptographic modules are used for any administrative access. Some of the secure protocols used for administrative and management access are listed below. This list is not all inclusive and represents a sample selection of secure protocols. -SSHv2 -SCP -HTTPS -SSL -TLS If management connections are established using protocols without FIPS 140-2 validated cryptographic modules, this is a finding.
Fix: F-3094r5_fix
Configure the network device to use secure protocols with FIPS 140-2 validated cryptographic modules.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1640
- Vuln IDs
-
- V-3070
- Rule IDs
-
- SV-3070r2_rule
Checks: C-3542r4_chk
Review the configuration to verify all attempts to access the device via management connection are logged.
Fix: F-3095r3_fix
Configure the device to log all access attempts to the device to establish a management connection for administrative access.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0240
- Vuln IDs
-
- V-3143
- Rule IDs
-
- SV-3143r2_rule
Checks: C-40236r1_chk
Review the network element configuration to determine if the vendor default password is active.
Fix: F-35391r2_fix
Remove any vendor default passwords from the network element configuration.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0700
- Vuln IDs
-
- V-3160
- Rule IDs
-
- SV-3160r2_rule
Checks: C-3549r2_chk
Have the administrator display the OS version in operation. The OS must be current with related IAVMs addressed.
Fix: F-3185r2_fix
Update operating system and address all related IAVMs.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1636
- Vuln IDs
-
- V-3175
- Rule IDs
-
- SV-3175r3_rule
Checks: C-3516r7_chk
Review the network device configuration to verify all management connections for administrative access require authentication.
Fix: F-3200r3_fix
Configure authentication for all management connections.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1780
- Vuln IDs
-
- V-3184
- Rule IDs
-
- SV-3184r1_rule
Checks: C-3834r1_chk
Review the user database to determine compliance.
Fix: F-3209r1_fix
Have the NSO ensure that accounts are created with the lowest privilege necessary to perform their duties.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1660
- Vuln IDs
-
- V-3196
- Rule IDs
-
- SV-3196r2_rule
Checks: C-3820r5_chk
Review the device configuration to verify it is configured to use SNMPv3 with both SHA authentication and privacy using AES encryption. If the site is using Version 1 or Version 2 with all of the appropriate patches and has developed a migration plan to implement the Version 3 Security Model, this finding can be downgraded to a Category II. To verify the appropriate patches on CISCO devices: Check the following IAVMs associated with SNMPv1: 1. 2001-B-0001 (V0005809) Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability 2. 2002-A-SNMP-001 (V0005835) Multiple Simple Network Management Protocol Vulnerabilities in Perimeter Devices (Cisco Security Advisory: Malformed SNMP Message-Handling Vulnerabilities) To verify the appropriate patches on other vendors refer to this web site: http://www.cert.org/advisories/CA-2002-03.html. If the targeted asset is running SNMPv3 and does not support SHA or AES, but the device is configured to use MD5 authentication and DES or 3DES encryption, then the finding can be downgraded to a Category III. If the site is using Version 1 or Version 2 and has installed all of the appropriate patches or upgrades to mitigate any known security vulnerabilities, this finding can be downgraded to a Category II. In addition, if the device does not support SNMPv3, this finding can be downgraded to a Category III provided all of the appropriate patches to mitigate any known security vulnerabilities have been applied and has developed a migration plan that includes the device upgrade to support Version 3 and the implementation of the Version 3 Security Model.
Fix: F-3221r3_fix
If SNMP is enabled, configure the network element to use SNMP Version 3 Security Model with FIPS 140-2 validated cryptography (i.e., SHA authentication and AES encryption).
- RMF Control
- Severity
- H
- CCI
- Version
- NET1665
- Vuln IDs
-
- V-3210
- Rule IDs
-
- SV-3210r2_rule
Checks: C-3822r5_chk
Review the network element configuration and verify if either of the SNMP community strings “public” or “private” is being used.
Fix: F-3235r4_fix
Configure unique SNMP community strings replacing the default community strings.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0440
- Vuln IDs
-
- V-3966
- Rule IDs
-
- SV-3966r3_rule
Checks: C-3502r4_chk
Review the network device configuration to determine if an authentication server is defined for gaining administrative access. If so, there must be only one account configured locally for an emergency. Verify the username and password for the emergency account is contained within a sealed envelope kept in a safe.
Fix: F-3899r4_fix
Configure the device to only allow one local account for emergency access and store the credentials in a secret manner.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1624
- Vuln IDs
-
- V-3967
- Rule IDs
-
- SV-3967r2_rule
Checks: C-3511r3_chk
Review the configuration and verify a session using the console port will time out after 10 minutes or less of inactivity.
Fix: F-3900r4_fix
Configure the timeout for idle console connection to 10 minutes or less.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-TUNL-013
- Vuln IDs
-
- V-3982
- Rule IDs
-
- SV-3982r2_rule
Checks: C-3800r3_chk
Review the network topology diagram, and review VPN concentrators. Verify that L2TP is not permitted into the enclave's private network. L2TP uses TCP and UDP ports 1701. See the PPS Vulnerability Assessment for additional protocol guidance and reference the Backbone Transport STIG for exceptions.
Fix: F-3915r3_fix
Terminate L2TP tunnels at the enclave perimeter, either in the DMZ or a service network for filtering and content inspection before passing traffic to the enclave's private network.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1623
- Vuln IDs
-
- V-4582
- Rule IDs
-
- SV-4582r3_rule
Checks: C-3510r4_chk
Review the network device's configuration and verify authentication is required for console access.
Fix: F-4515r4_fix
Configure authentication for console access on the network device.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1762
- Vuln IDs
-
- V-4613
- Rule IDs
-
- SV-4613r2_rule
Checks: C-3832r2_chk
Inspect the NMS configuration to validate in-band management access is using an approved FIPS 140-2 encryption and hashing algorithm.
Fix: F-4546r2_fix
Implement and configure an approved FIPs 140-2 encryption and hashing algorithm for in-band management to the NMS.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1637
- Vuln IDs
-
- V-5611
- Rule IDs
-
- SV-5611r2_rule
Checks: C-3527r4_chk
Review the configuration and verify management access to the device is allowed only from hosts within the management network.
Fix: F-5522r3_fix
Configure an ACL or filter to restrict management access to the device from only the management network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1645
- Vuln IDs
-
- V-5612
- Rule IDs
-
- SV-5612r2_rule
Checks: C-3534r4_chk
Review the configuration and verify the timeout is set for 60 seconds or less. The SSH service terminates the connection if protocol negotiation (that includes user authentication) is not complete within this timeout period.
Fix: F-5523r4_fix
Configure the network element so it will require a secure shell timeout of 60 seconds or less.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1646
- Vuln IDs
-
- V-5613
- Rule IDs
-
- SV-5613r2_rule
Checks: C-3538r4_chk
Review the configuration and verify the number of unsuccessful SSH login attempts is set at 3.
Fix: F-5524r7_fix
Configure the network element to require a maximum number of unsuccessful SSH login attempts at 3.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1071
- Vuln IDs
-
- V-5644
- Rule IDs
-
- SV-5644r2_rule
Checks: C-3657r2_chk
Review the layer 2 and layer 3 network topology to determine what network the TFTP server is connected to. Verify that the server has been configured or assigned an IP address that belongs to the management network.
Fix: F-5555r2_fix
Connect the TFTP server only to the management network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0965
- Vuln IDs
-
- V-5646
- Rule IDs
-
- SV-5646r4_rule
Checks: C-3604r8_chk
Review the device configuration to determine if threshold filters or timeout periods are set for dropping excessive half-open TCP connections. For timeout periods, the time should be set to 10 seconds or less. If the device can not be configured for 10 seconds or less, it should be set to the least amount of time allowable in the configuration. Threshold filters will need to be determined by the organization for optimal filtering.
Fix: F-5557r6_fix
Configure the device to drop half-open TCP connections through threshold filtering or timeout periods.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1629
- Vuln IDs
-
- V-7011
- Rule IDs
-
- SV-7365r2_rule
Checks: C-3513r3_chk
Review the configuration and verify the auxiliary port is disabled unless a secured modem providing encryption and authentication is connected.
Fix: F-6614r3_fix
Disable the auxiliary port. If used for out-of-band administrative access, the port must be connected to a secured modem providing encryption and authentication.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-NAC-010
- Vuln IDs
-
- V-7542
- Rule IDs
-
- SV-8011r1_rule
Checks: C-5960r1_chk
Verify that the authentication server is configured to use a strong EAP such as EAP-TLS, EAP-TTLS or PEAP
Fix: F-6892r1_fix
Confiugre the authentication server to use a strong EAP such as EAP-TLS, EAP-TTLS or PEAP.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0386
- Vuln IDs
-
- V-14646
- Rule IDs
-
- SV-15272r2_rule
Checks: C-13714r3_chk
Review the network device or syslog server to determine whether alerts are configured to automatically generate and notify the administrator when seventy-five percent or more of the storage capacity has been reached with log data.
Fix: F-14748r3_fix
Configure the network device or syslog server to automatically generate and notify the administrator when seventy-five percent or more of the storage capacity has been reached with log data.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0813
- Vuln IDs
-
- V-14671
- Rule IDs
-
- SV-15327r2_rule
Checks: C-12793r5_chk
Review the device configuration and verify it is authenticating the NTP messages received from the NTP server or peer. Authentication must be performed using either PKI (supported in NTP v4) or SHA-1 hashing algorithm. If SHA-1 is not supported by both the NTP client and server, then MD5 can be used.
Fix: F-14132r1_fix
Configure the device to authenticate all received NTP messages using either PKI (supported in NTP v4) or SHA-1 hashing algorithm. If SHA-1 is not supported by this client or the NTP peer or server, then MD5 can be used.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1647
- Vuln IDs
-
- V-14717
- Rule IDs
-
- SV-15459r2_rule
Checks: C-12924r6_chk
Review the configuration and verify SSH Version 1 is not being used for administrative access.
Fix: F-14184r3_fix
Configure the network element to use SSH version 2.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0434
- Vuln IDs
-
- V-15433
- Rule IDs
-
- SV-16260r1_rule
Checks: C-14440r1_chk
Review the AAA server configuration. Attempt to identify suspicious group profile definitions that do not meet the accounts user-id naming convention. Example:supr-user. Below is an example of what an SA profile may be associated. Group Profile Information group = rtr_super{ profile_id = 40 profile_cycle = 1 service=shell { default cmd=permit cmd=debug { deny all permit .* } } } Below is an example of the user definition that should be assigned with a valid ID, (not rtr-geek). Look for group accounts here: user = rtr-geek{ profile_id = 45 profile_cycle = 1 member = rtr_super password = des "********" }
Fix: F-15097r1_fix
Remove all group profiles from the AAA server.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0441
- Vuln IDs
-
- V-15434
- Rule IDs
-
- SV-16261r2_rule
Checks: C-14441r3_chk
Review the emergency account configured on the network element and verify that it has been assigned to a privilege level that will enable the administrator to perform necessary administrative functions when the authentication server is not online.
Fix: F-15098r6_fix
Assign a privilege level to the emergency account to allow the administrator to perform necessary administrative functions when the authentication server is not online.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0991
- Vuln IDs
-
- V-17821
- Rule IDs
-
- SV-19075r2_rule
Checks: C-19238r3_chk
The managed network element’s OOBM interface must be configured with an IP address from the address space belonging to the OOBM network. After determining which interface is connected to the OOBM access switch, review the managed device configuration and verify the interface has been assigned an address from the local management address block.
Fix: F-17736r1_fix
Configure the managed network element’s OOBM interface with an IP address from the address space belonging to the OOBM network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0992
- Vuln IDs
-
- V-17822
- Rule IDs
-
- SV-19076r2_rule
Checks: C-19239r4_chk
Step 1: Verify the managed interface has an inbound and outbound ACL or filter. Step 2: Verify the ingress ACL blocks all transit traffic—that is, any traffic not destined to the router itself. In addition, traffic accessing the managed elements should be originated at the NOC. Step 3: Verify the egress ACL blocks any traffic not originated by the managed element.
Fix: F-17737r1_fix
If the management interface is a routed interface, it must be configured with both an ingress and egress ACL. The ingress ACL should block any transit traffic, while the egress ACL should block any traffic that was not originated by the managed network elements.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1615
- Vuln IDs
-
- V-17840
- Rule IDs
-
- SV-19115r1_rule
Checks: C-19324r1_chk
Step 1: Issue the show line command to see the AUX port tty numbering for the communications server. The numbering varies based on the router model and modules installed. Step 2: Review the communications server configuration and verify that CHAP is used for PPP authentication. Assuming that line 4 is bound to the AUX port, the configuration would look similar to the example shown below: interface async 4 encapsulation ppp ppp authentication chap
Fix: F-17767r1_fix
Configure the communications server to use PPP encapsulation and PPP authentication CHAP for the async or AUX port used for dial in.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1616
- Vuln IDs
-
- V-17841
- Rule IDs
-
- SV-19116r1_rule
Checks: C-19325r1_chk
Review the communications server configuration and verify that PPP connections require AAA authentication using a RADIUS or TACACS+ authentication server. aaa new-model aaa authentication ppp list-name tacacs+ local .. tacacs-server host 200.200.2.2 tacacs-server host 300.300.3.3 Upon verifying that an AAA server is used for authenticating dial-up connections to the communications server, review the AAA server to ensure two-factor is used.
Fix: F-17768r1_fix
Configure the communications server to use an AAA server to authenticate all administrators authorized for dial-up access using 2-factor authentication.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1617
- Vuln IDs
-
- V-17842
- Rule IDs
-
- SV-19117r1_rule
Checks: C-19326r1_chk
Review the configuration of the communications server. The following example configuration would enable a secured call back on a Cisco network access server: interface s0/1 physical-layer async ip address 192.168.8.1 255.255.255.252 encapsulation ppp async mode dedicated ppp authentication chap ppp callback accept dialer callback-secure dialer map ip 192.168.8.2 name Dean class dial-back-admin 1112223333 dialer map ip 192.168.8.3 name Dana class dial-back-admin 1113334444 ! map-class dialer dial-back-admin dialer callback-server username dialer hold-queue timeout 60 The call-back numbers used for each authorized user must be defined within the communications server local database or the AAA server. In the example above, the username identifies the return call by looking up the authenticated host name in a dialer map command. Do not allow the client to supply the callback number such as, pre-configuring a null dial string for an authorized dial-up user in the access server database or the AAA. An alternative to the communication server and AAA server implementation is an integrated solution that includes the following: 1. a secured modem using FIPS 140-2 compliant encryption for the connection 2. an integrated RSA Secure ID server for 2-factor authentication 3. OOB connectivity to the managed device via console port access granted after the administrator has been authenticated
Fix: F-17774r1_fix
The communications server must be configured to accept a callback request. In addition, it must be configured in a secured mode so that it will not callback an unauthorized user.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0436
- Vuln IDs
-
- V-17843
- Rule IDs
-
- SV-19118r1_rule
Checks: C-19334r1_chk
Interview the IAO and administrator to determine if the server is compliant with respective OS STIG.
Fix: F-17778r1_fix
Configure the platforms hosting the AAA server in accordance with the appropriate OS STIG.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0437
- Vuln IDs
-
- V-17844
- Rule IDs
-
- SV-19119r1_rule
Checks: C-19335r1_chk
Interview the IAO and administrator to determine if unique keys have been configured.
Fix: F-17781r1_fix
Configure each AAA server with a unique key to be used for communication (i.e. RADIUS, TACACS+) with any client requesting authentication services.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0438
- Vuln IDs
-
- V-17845
- Rule IDs
-
- SV-19120r1_rule
Checks: C-19336r1_chk
Interview the IAO and AAA administrator to determine if the server is compliant. Have the administrator provide a demonstration of the HIDS capability to ensure that it is configured and in operation.
Fix: F-17782r1_fix
Implement an HIDS on the AAA server.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0815
- Vuln IDs
-
- V-17848
- Rule IDs
-
- SV-19123r1_rule
Checks: C-19349r1_chk
Interview the IAO and administrator to determine if the server is compliant with respective OS STIG.
Fix: F-17785r1_fix
If the NTP server is not an appliance, configure the platform hosting the NTP server in accordance with the appropriate OS STIG.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0816
- Vuln IDs
-
- V-17849
- Rule IDs
-
- SV-19124r1_rule
Checks:
Fix: F-17786r1_fix
Implement an HIDS on the NTP server
- RMF Control
- Severity
- L
- CCI
- Version
- NET0817
- Vuln IDs
-
- V-17850
- Rule IDs
-
- SV-19125r1_rule
Checks: C-19351r1_chk
Review both NTP server configurations to determine that they are referencing two different reference clocks and that the NTP servers are peering with each other. An alternative configuration for management networks that have a gateway would be to implement two stratum-2 servers peering with each other and each referencing a different trusted external stratum 1 server. This is a less expensive solution that still provides redundancy, but not quite the same accuracy.
Fix: F-17787r1_fix
Use at least two independent sources of time reference. The best practice is to deploy two stratum 1 servers, each connected to a different reference clock (GPS, NIST WWVB) and both peering with each other for redundancy.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0819
- Vuln IDs
-
- V-17852
- Rule IDs
-
- SV-19127r1_rule
Checks: C-19353r1_chk
Interview the IAO and administrator to determine if unique keys have been configured.
Fix: F-17789r1_fix
If a hashing algorithm is being used, all servers must be configured with a symmetric key that is unique from any key configured on any other NTP server.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1731
- Vuln IDs
-
- V-17854
- Rule IDs
-
- SV-19129r1_rule
Checks: C-19355r1_chk
Interview the IAO and administrator to determine if the SNMP manager is compliant with respective OS STIG.
Fix: F-17791r1_fix
Configure the SNMP manager to be compliant with the appropriate OS STIG
- RMF Control
- Severity
- L
- CCI
- Version
- NET1732
- Vuln IDs
-
- V-17855
- Rule IDs
-
- SV-19130r1_rule
Checks: C-19356r1_chk
Interview the IAO and the administrator to determine if the SNMP manager is compliant. Have the administrator provide a demonstration of the HIDS capability to ensure that it is configured and in operation
Fix: F-17792r1_fix
Implement an HIDS to provide access control for the SNMP data as well as provide the necessary protection against unauthorized modifications and access.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1733
- Vuln IDs
-
- V-17856
- Rule IDs
-
- SV-19131r1_rule
Checks: C-19358r1_chk
Review the network topology to determine what network the network manager is connected to. Verify that it is not dual-homed by physically inspecting the device’s LAN connection.
Fix: F-17793r1_fix
Connect the SNMP manager only to the management network.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1734
- Vuln IDs
-
- V-17857
- Rule IDs
-
- SV-19132r1_rule
Checks: C-19359r1_chk
Review network management station configuration to determine if SNMP messages are stored for a minimum of 30 days and then archived. Interview the network administrator to verify if they are stored offline for a minimum of one year.
Fix: F-17795r1_fix
Configure the SNMP manager to store SNMP messages for a minimum of 30 days and then stored offline for one year.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-NAC-001
- Vuln IDs
-
- V-18555
- Rule IDs
-
- SV-20099r1_rule
Checks: C-21582r1_chk
Review the AAA server configuration. Have the SA display the policy groups. Have the SA display the vlan configuration. VLANs will be defined under Tunnel-Pvt-Group-ID with a tunnel type of VLAN. The dynamic VLAN definitions will have a IP pool assignment. Ensure the Production VLAN does not share the same AAA IP pool . Then verify the subnets used in other pools are not the same as the production.
Fix: F-19171r1_fix
Build different IP pools. Use different IP subnets for each pool.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-NAC-004
- Vuln IDs
-
- V-18558
- Rule IDs
-
- SV-20102r1_rule
Checks: C-21584r1_chk
Review the AAA server configuration. If the SA has created a dynamic Unauthorized VLAN, definitions should not have a IP pool assignment. Ensure the Unauthorized VLAN is configured without IP or a Guest VLAN is defined with limited access.
Fix: F-19173r1_fix
Implement a NAC solution where the device remains without IP assignment if authentication fails or create a dynamic Unauthorized VLAN / Guest VLAN with limited access in AAA server. If a Guest VLAN is built, it should not have access to production data.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0812
- Vuln IDs
-
- V-23747
- Rule IDs
-
- SV-28651r2_rule
Checks: C-3581r3_chk
Review the configuration and verify two NTP servers have been defined.
Fix: F-3044r1_fix
Specify two NTP server IP addresses on the device to be used to request time from.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1022
- Vuln IDs
-
- V-23749
- Rule IDs
-
- SV-28655r1_rule
Checks: C-12944r1_chk
Physically inspect the syslog server and its LAN connection as well as review the network topology diagram to verify compliance.
Fix: F-14191r1_fix
Ensure the syslog server is only connected to the management network
- RMF Control
- Severity
- M
- CCI
- Version
- NET1023
- Vuln IDs
-
- V-23750
- Rule IDs
-
- SV-28656r1_rule
Checks: C-12945r1_chk
Interview the IAO and syslog administrator to determine if the server is compliant with respective OS STIG.
Fix: F-14192r1_fix
Ensure that the syslog server is compliant with the appropriate OS STIG
- RMF Control
- Severity
- M
- CCI
- Version
- NET0814
- Vuln IDs
-
- V-25883
- Rule IDs
-
- SV-32243r1_rule
Checks: C-32705r1_chk
Review the layer 2 and layer 3 network topology to determine what network the NTP server is connected to. Verify that the server has been configured or assigned an IP address that belongs to the management network.
Fix: F-28796r1_fix
Connect the NTP server only to the management network.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0431
- Vuln IDs
-
- V-25894
- Rule IDs
-
- SV-32516r1_rule
Checks: C-32825r1_chk
Have the administrator discuss their implementation. A typical AAA process includes the device being authenticated to direct authentication request directly to a 2-facor server (i.e. ACE) or to an AAA server via RADIUS or TACACS+ which redirects the 'authentication' request to the 2-facor server. Request the administrator to demonstrate the implementation.
Fix: F-28936r1_fix
The IAO will implement a 2-factor authentication solution for granting administrative access to all network elements.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0432
- Vuln IDs
-
- V-25895
- Rule IDs
-
- SV-32517r1_rule
Checks: C-32826r1_chk
Review the AAA server implemented and determine if user profiles are members of a group. Determine if the groups have different privileges and the users are in the appropriate groups. In the following TACACS example the user (rtr-test) is a member of the group “rtr-basic”. <CSUserver>$/opt/ciscosecure/CLI/ViewProfile -p 9900 -u rtr_test User Profile Information user = rtr_test{ profile_id = 66 profile_cycle = 1 member = rtr_basic password = des "********" } Below is an example of CiscoSecure TACACS+ server defining the privilege level. user = junior-engineer1 { password = clear "xxxxx" service = shell { set priv-lvl = 7 } }
Fix: F-28937r1_fix
The administrator will configure the authentication server with standard accounts and assign them to privilege levels that meet their job description
- RMF Control
- Severity
- M
- CCI
- Version
- NET0435
- Vuln IDs
-
- V-25896
- Rule IDs
-
- SV-32518r1_rule
Checks: C-32827r1_chk
Review the network topology to determine what network they are connected to. Verify that they are not dual-homed by physically inspecting the device’s LAN connection
Fix: F-28938r1_fix
Connect the authentication servers to only the management network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0405
- Vuln IDs
-
- V-28784
- Rule IDs
-
- SV-36774r2_rule
Checks: C-35853r2_chk
Verify the call home service or feature is disabled on the device.
Fix: F-31103r1_fix
Configure the network device to disable the call home service or feature.