| V-273785 | | The RUCKUS ICX device must enforce approved authorizations for controlling the flow of management information within the network device based on information flow control policies. | A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management informati... |
| V-273786 | | The RUCKUS ICX 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. | By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, ... |
| V-273787 | | The RUCKUS ICX device must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the device. | Display of the DOD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is c... |
| V-273788 | | The RUCKUS ICX device must initiate session auditing upon startup. | If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state ... |
| V-273789 | | The RUCKUS ICX device must generate audit records containing the full-text recording of privileged commands. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
Organizations consider lim... |
| V-273799 | | The RUCKUS ICX 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. | Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local da... |
| V-273802 | | The RUCKUS ICX device must enforce password complexity and length requirements. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password ... |
| V-273820 | | The RUCKUS ICX device must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure network devices have a sufficient storage capacity in which to write the audit logs, they must be able to allocate audit record storage capa... |
| V-273821 | | The RUCKUS ICX device must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-273825 | | The RUCKUS ICX device must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC). | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authenticati... |
| V-273826 | | The RUCKUS ICX device must authenticate Network Time Protocol sources using authentication that is cryptographically based. | If Network Time Protocol (NTP) is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrec... |
| V-273829 | | The RUCKUS ICX device must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. | DoS is a condition that occurs when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its ... |
| V-273830 | | Security-relevant firmware updates must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). | Security flaws with firmware are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vu... |
| V-273832 | | The RUCKUS ICX device must off-load audit records onto a different system or media than the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-273838 | | The RUCKUS ICX device must obtain its public key certificates from an appropriate certificate policy through an approved service provider. | For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agenci... |
| V-273848 | | The RUCKUS ICX device must be configured to include only approved trust anchors in trust stores or certificate stores managed by the organization. | Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the inter... |
| V-273850 | | The RUCKUS ICX device must be configured to synchronize system clocks within and between systems or system components. | Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication proc... |
| V-273851 | | The RUCKUS ICX device must be configured to compare the internal system clocks on an organization-defined frequency with two organization-defined authoritative time sources. | Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and ... |
| V-273784 | | The RUCKUS ICX device must be configured to assign appropriate user roles or access levels to authenticated users. | Successful identification and authentication must not automatically give an entity full access to a network device or security domain. The lack of aut... |
| V-273798 | | The RUCKUS ICX device must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-273808 | | The RUCKUS ICX device must use FIPS 140-2/140-3 approved algorithms for authentication to a cryptographic module. | Unapproved mechanisms used for authentication to the cryptographic module are not validated and therefore cannot be relied upon to provide confidentia... |
| V-273809 | | The RUCKUS ICX 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. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management se... |
| V-273835 | | The RUCKUS ICX device must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access. | Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important... |
| V-273839 | | The RUCKUS ICX 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). | 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 stor... |
| V-273840 | | The RUCKUS ICX device must be running an operating system release that is currently supported by the vendor. | RUCKUS ICX devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabi... |
