| Finding ID |
Severity |
Title |
Description |
|
V-265352
|
High |
The NSX Manager must be running a release that is currently supported by the vendor. |
Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities. |
|
V-265348
|
High |
The NSX Manager must be configured to send logs to a central log server. |
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.
Satisfies: SRG-APP-000515-NDM-000325, SRG-APP-000357-NDM-000293, SRG-APP-000516-NDM-000350 |
|
V-265327
|
High |
The NSX Manager must terminate all network connections associated with a session after five minutes of inactivity. |
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take immediate 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... |
|
V-265315
|
High |
The NSX Manager must only enable TLS 1.2 or greater. |
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. Configuration of TLS on the NSX also ensures that passwords are not transmitted in the clear.... |
|
V-265296
|
High |
The NSX Manager must be configured to integrate with an identity provider that supports multifactor authentication (MFA). |
Common attacks against single-factor authentication are attacks on user passwords. These attacks include brute force password guessing, password spraying, and password credential stuffing. This requirement also supports nonrepudiation of actions taken by an administrator.
This requirement ensures the NSX Manager is configured to use a centralized authentication services to authenticate... |
|
V-265292
|
High |
The NSX Manager must assign users/accounts to organization-defined roles configured with approved authorizations. |
The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. Users must be assigned to roles which are configured with approved authorizations and access permissions. The NSX Manager must be configured granularly based on organization requirements to only allow authorized administrators to... |
|
V-265359
|
Medium |
The NSX Managers must be deployed on separate physical hosts. |
SDN relies heavily on control messages between a controller and the forwarding devices for network convergence. The controller uses node and link state discovery information to calculate and determine optimum pathing within the SDN network infrastructure based on application, business, and security policies. Operating in the proactive flow instantiation mode,... |
|
V-265358
|
Medium |
The NSX Manager must be configured as a cluster. |
Failure in a known state can address safety or security in accordance with the mission needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the SDN controller. Preserving network element state information helps... |
|
V-265355
|
Medium |
The NSX Manager must enable the global FIPS compliance mode for load balancers. |
If unsecured protocols (lacking cryptographic mechanisms) are used for load balancing, the contents of those sessions will be susceptible to eavesdropping, potentially putting sensitive data at risk of compromise. |
|
V-265354
|
Medium |
The NSX Manager must disable SNMP v2. |
SNMPv3 supports commercial-grade security, including authentication, authorization, access control, and privacy. Previous versions of the protocol contained well-known security weaknesses that were easily exploited. As such, SNMPv1/2 receivers must be disabled. |
|
V-265353
|
Medium |
The NSX Manager must disable SSH. |
The NSX shell provides temporary access to commands essential for server maintenance. Intended primarily for use in break-fix scenarios, the NSX shell is well suited for checking and modifying configuration details, not always generally accessible, using the web interface. The NSX shell is accessible remotely using SSH. Under normal operating... |
|
V-265351
|
Medium |
The NSX Manager 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 Office of Management and Budget (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. |
|
V-265350
|
Medium |
The NSX Manager must be configured to conduct backups on an organizationally defined schedule. |
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... |
|
V-265346
|
Medium |
The NSX Manager must be configured to protect against denial-of-service (DoS) attacks by limit the number of concurrent sessions to an organization-defined number. |
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.
Limiting the number of concurrent open sessions helps limit the risk of DoS attacks.
Organizations may define the maximum number of... |
|
V-265339
|
Medium |
The NSX Manager must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC). |
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
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... |
|
V-265338
|
Medium |
The NSX Manager must be configured to synchronize internal information system clocks using redundant authoritative time sources. |
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... |
|
V-265321
|
Medium |
The NSX Manager must require that when a password is changed, the characters are changed in at least eight of the positions within the password. |
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... |
|
V-265320
|
Medium |
The NSX Manager must enforce password complexity by requiring that at least one special character be used for local accounts. |
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... |
|
V-265319
|
Medium |
The NSX Manager must enforce password complexity by requiring that at least one numeric character be used for local accounts. |
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... |
|
V-265318
|
Medium |
The NSX Manager must enforce password complexity by requiring that at least one lowercase character be used for local accounts. |
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... |
|
V-265317
|
Medium |
The NSX Manager must enforce password complexity by requiring that at least one uppercase character be used for local accounts. |
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... |
|
V-265316
|
Medium |
The NSX Manager must enforce a minimum 15-character password length for local accounts. |
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... |
|
V-265313
|
Medium |
The NSX Manager 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 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... |
|
V-265295
|
Medium |
The NSX Manager 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. |
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... |
|
V-265294
|
Medium |
The NSX Manager must display the Standard Mandatory DOD Notice and Consent Banner before granting access. |
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. |
|
V-265293
|
Medium |
The NSX Manager 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, is reduced. |
|
V-265289
|
Medium |
The NSX Manager must configure logging levels for services to ensure audit records are generated. |
Without generating audit records 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... |
|
V-265349
|
Low |
The NSX Manager must not provide environment information to third parties. |
Providing technical details about an environment's infrastructure to third parties could unknowingly expose sensitive information to bad actors if intercepted. |