Juniper EX Series Switches Network Device Management Security Technical Implementation Guide
Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected].
Details
Version / Release: V1R3
Published: 2023-03-23
Updated At: 2023-05-04 00:35:03
Compare/View Releases
Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Actions
Download
Filter
Findings
| Severity | Open | Not Reviewed | Not Applicable | Not a Finding |
|---|---|---|---|---|
| Overall | 0 | 0 | 0 | 0 |
| Low | 0 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 | 0 |
| High | 0 | 0 | 0 | 0 |
Drop CKL or SCAP (XCCDF) results here.
| Vuln | Rule | Version | CCI | Severity | Title | Description | Status | Finding Details | Comments |
|---|---|---|---|---|---|---|---|---|---|
| SV-253878r879511_rule | JUEX-NM-000010 | CCI-000054 | MEDIUM | The Juniper EX switch must be configured to limit the number of concurrent management sessions to 10 or less. | 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 helpfu | ||||
| SV-253879r879525_rule | JUEX-NM-000020 | CCI-000018 | MEDIUM | The Juniper EX switch must be configured to automatically audit account creation. | Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. Notification of account creation helps to mitigate this risk. Audi | ||||
| SV-253880r879526_rule | JUEX-NM-000030 | CCI-001403 | MEDIUM | The Juniper EX switch must be configured to automatically audit account modification. | Because 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 i | ||||
| SV-253881r879527_rule | JUEX-NM-000040 | CCI-001404 | MEDIUM | The Juniper EX switch must be configured to automatically audit account disabling actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account disabling actions will support account management procedures. When device managem | ||||
| SV-253882r879528_rule | JUEX-NM-000050 | CCI-001405 | MEDIUM | The Juniper EX switch must be configured to automatically audit account removal actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will support account management procedures. When device managemen | ||||
| SV-253883r879530_rule | JUEX-NM-000060 | CCI-000213 | HIGH | The Juniper EX switch 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 authorization-based access control could result in the immediate compromise and unauthorized access to sensi | ||||
| SV-253884r879533_rule | JUEX-NM-000070 | CCI-001368 | MEDIUM | The Juniper EX switch must be configured to 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 information flow is not enforced based on approved authorizations, the network device may become compromised. Info | ||||
| SV-253885r879546_rule | JUEX-NM-000080 | CCI-000044 | MEDIUM | The Juniper EX switch must be configured to enforce the limit of three consecutive invalid logon attempts for any given user, after which time it must block any login attempt for that user 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. Introducing a lockout period significantly increases the time required for each brute-force a | ||||
| SV-253886r879547_rule | JUEX-NM-000090 | CCI-000048 | MEDIUM | The Juniper EX switch must be configured to 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 consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, a | ||||
| SV-253887r879554_rule | JUEX-NM-000100 | CCI-000166 | MEDIUM | The Juniper EX switch must be configured to protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by nonrepudiation. | This requirement supports nonrepudiation 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 authen | ||||
| SV-253888r879561_rule | JUEX-NM-000110 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records for executed commands. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit reco | ||||
| SV-253889r879563_rule | JUEX-NM-000120 | CCI-000130 | MEDIUM | The Juniper device must be configured to produce audit log records containing sufficient information to establish what type of event occurred. | It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done to compile an accurate risk assessment. Associating event types with detected events in the application and | ||||
| SV-253890r879564_rule | JUEX-NM-000130 | CCI-000131 | MEDIUM | The Juniper EX switch must be configured to produce audit records containing information to establish when (date and time) the events occurred. | It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Logging the date and time of each detected event provides | ||||
| SV-253891r879565_rule | JUEX-NM-000140 | CCI-000132 | MEDIUM | The Juniper EX switch must be configured to produce audit records containing information to establish where the events occurred. | 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 functi | ||||
| SV-253892r879566_rule | JUEX-NM-000150 | CCI-000133 | MEDIUM | The Juniper EX switch must be configured to produce audit log records containing information to establish the source of events. | 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 dev | ||||
| SV-253893r879567_rule | JUEX-NM-000160 | CCI-000134 | MEDIUM | The Juniper EX switch must be configured to produce audit records that contain information to establish the outcome of the event. | Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event succ | ||||
| SV-253894r879568_rule | JUEX-NM-000170 | CCI-001487 | MEDIUM | The Juniper EX switch must be configured to generate audit records containing information that establishes the identity of any individual or process associated with the event. | Without information that establishes the identity of the subjects (i.e., administrators or processes acting on behalf of administrators) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Eve | ||||
| SV-253895r879569_rule | JUEX-NM-000180 | CCI-000135 | MEDIUM | The Juniper EX switch must be configured to generate audit records containing the full-text recording of privileged commands. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requ | ||||
| SV-253896r879577_rule | JUEX-NM-000190 | CCI-000163 | MEDIUM | The Juniper EX switch must be configured to protect audit information from unauthorized modification. | 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 | ||||
| SV-253897r879578_rule | JUEX-NM-000200 | CCI-000164 | MEDIUM | The Juniper EX switch must be configured to protect audit information from unauthorized deletion. | 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 sourc | ||||
| SV-253898r879579_rule | JUEX-NM-000210 | CCI-001493 | MEDIUM | The Juniper EX switch must be configured to protect audit tools from unauthorized access. | 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 wi | ||||
| SV-253899r879586_rule | JUEX-NM-000220 | CCI-001499 | MEDIUM | The Juniper EX switch must be configured to limit privileges to change the software resident within software libraries. | 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 implementi | ||||
| SV-253900r879588_rule | JUEX-NM-000230 | CCI-000382 | HIGH | The Juniper EX switch 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 data types), organizations must disable unused or unnecessary physical and logical ports/protocols on info | ||||
| SV-253901r879589_rule | JUEX-NM-000240 | CCI-001358 | MEDIUM | The Juniper EX switch 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 is created on the device's local database for use when the authentication server is down or connectivity between the device and the authenticati | ||||
| SV-253902r879590_rule | JUEX-NM-000250 | CCI-000765 | HIGH | The Juniper EX switch must be configured to use DoD PKI as multifactor authentication (MFA) for interactive logins. | 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 ( | ||||
| SV-253903r879597_rule | JUEX-NM-000260 | CCI-001941 | MEDIUM | The Juniper EX switch must be configured to implement replay-resistant authentication mechanisms for network access to privileged accounts. | A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process | ||||
| SV-253904r879601_rule | JUEX-NM-000270 | CCI-000205 | MEDIUM | The Juniper EX switch must be configured to enforce a minimum 15-character password length. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a passwor | ||||
| SV-253905r879603_rule | JUEX-NM-000280 | CCI-000192 | MEDIUM | The Juniper EX switch must be configured to enforce password complexity by requiring that at least one uppercase character be used. | Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-253906r879604_rule | JUEX-NM-000290 | CCI-000193 | MEDIUM | The Juniper EX switch must be configured to enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-253907r879605_rule | JUEX-NM-000300 | CCI-000194 | MEDIUM | The Juniper EX switch must be configured to enforce password complexity by requiring that at least one numeric character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-253908r879606_rule | JUEX-NM-000310 | CCI-001619 | MEDIUM | The Juniper EX switch must be configured to enforce password complexity by requiring that at least one punctuation (special) character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-253909r879607_rule | JUEX-NM-000320 | CCI-000195 | MEDIUM | The Juniper EX switch must be configured to 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 c | ||||
| SV-253910r879608_rule | JUEX-NM-000330 | CCI-000196 | HIGH | The Juniper EX switch must be configured to only store cryptographic representations of passwords. | 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 re | ||||
| SV-253911r879616_rule | JUEX-NM-000340 | CCI-000803 | HIGH | The Juniper EX switch must be configured to use FIPS 140-2 approved algorithms for authentication to a cryptographic module. | 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 re | ||||
| SV-253912r879621_rule | JUEX-NM-000350 | CCI-000879 | MEDIUM | The Juniper EX switch must be configured to terminate all sessions and network connections when nonlocal device maintenance is completed. | 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 cond | ||||
| SV-253913r879622_rule | JUEX-NM-000360 | CCI-001133 | HIGH | The Juniper EX switch must be configured to end all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill mission requirements. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminat | ||||
| SV-253914r879642_rule | JUEX-NM-000370 | CCI-001199 | HIGH | The Juniper device must be configured to 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). | 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 protect | ||||
| SV-253915r879696_rule | JUEX-NM-000380 | CCI-002130 | MEDIUM | The Juniper EX switch must be configured to automatically audit account enabling actions. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account | ||||
| SV-253916r879706_rule | JUEX-NM-000390 | CCI-000366 | MEDIUM | The Juniper EX switch must be configured to enforce organization-defined role-based access control policies over defined subjects and objects. | 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 | ||||
| SV-253917r879720_rule | JUEX-NM-000400 | CCI-002234 | MEDIUM | The Juniper EX switch must be configured to audit the execution of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts | ||||
| SV-253918r879730_rule | JUEX-NM-000410 | CCI-001849 | MEDIUM | The Juniper EX switch must be configured to 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 need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device | ||||
| SV-253919r879733_rule | JUEX-NM-000420 | CCI-001858 | MEDIUM | The Juniper EX switch must be configured to generate an immediate real-time alert of all audit failure events requiring real-time alerts. | 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 | ||||
| SV-253920r879746_rule | JUEX-NM-000430 | CCI-000366 | MEDIUM | The Juniper EX switch 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 i | ||||
| SV-253921r879747_rule | JUEX-NM-000440 | CCI-001890 | MEDIUM | The Juniper EX switch must be configured to 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 generated by the application include date and time. Time is commonly expressed in UTC, a modern continuation of G | ||||
| SV-253922r879751_rule | JUEX-NM-000450 | CCI-001812 | MEDIUM | The Juniper EX switch must be configured to prohibit installation of software without explicit privileged status. | 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. | ||||
| SV-253923r879753_rule | JUEX-NM-000460 | CCI-001813 | MEDIUM | The Juniper EX switch must be configured to enforce access restrictions associated with changes to device configuration. | 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 tha | ||||
| SV-253924r879754_rule | JUEX-NM-000470 | CCI-001814 | MEDIUM | The Juniper EX switch must be configured to audit the enforcement actions used to restrict access associated with changes to the device. | Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions. Enfo | ||||
| SV-253925r879768_rule | JUEX-NM-000480 | CCI-001967 | HIGH | The Juniper EX switch 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 authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre | ||||
| SV-253926r904442_rule | JUEX-NM-000490 | CCI-001967 | LOW | The Juniper EX switch must use an an NTP service that is hosted by a trusted source or a DOD-compliant enterprise or local NTP server. | If a trusted time source is not used, 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 which may hide attacks or result in ina | ||||
| SV-253927r879773_rule | JUEX-NM-000500 | CCI-002007 | MEDIUM | The Juniper EX switch must be configured to prohibit the use of cached authenticators after an organization-defined time period. | 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 e | ||||
| SV-253928r904432_rule | JUEX-NM-000510 | CCI-002890 | HIGH | The Juniper EX switches must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications. | 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 activiti | ||||
| SV-253929r904433_rule | JUEX-NM-000520 | CCI-003123 | HIGH | The Juniper EX switch must be configured to implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions. | This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents | ||||
| SV-253930r879806_rule | JUEX-NM-000530 | CCI-002385 | MEDIUM | The Juniper EX switch must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. | 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 mit | ||||
| SV-253931r879866_rule | JUEX-NM-000540 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records when modifying administrator privileges. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-253932r879870_rule | JUEX-NM-000550 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records when deleting administrator privileges. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-253933r879874_rule | JUEX-NM-000560 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records when successful/unsuccessful logon attempts occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-253934r879875_rule | JUEX-NM-000570 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records for privileged activities or other system-level access. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-253935r879876_rule | JUEX-NM-000580 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records showing starting and ending time for administrator access to the system. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit reco | ||||
| SV-253936r879877_rule | JUEX-NM-000590 | CCI-000172 | MEDIUM | The Juniper EX switch must be configured to generate audit records when concurrent logons from different workstations occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-253937r879886_rule | JUEX-NM-000600 | CCI-001851 | MEDIUM | The Juniper EX switch must be configured to offload 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. Offloading is a common process in information systems with limited audit storage capacity. | ||||
| SV-253938r879887_rule | JUEX-NM-000610 | CCI-000366 | MEDIUM | The Juniper EX switch 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. | 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 securit | ||||
| SV-253939r879887_rule | JUEX-NM-000620 | CCI-000169 | MEDIUM | The Juniper EX switch must be configured to generate log records for a locally developed list of auditable events. | Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured netwo | ||||
| SV-253940r879887_rule | JUEX-NM-000630 | CCI-000345 | MEDIUM | The Juniper EX switch must be configured to enforce access restrictions associated with changes to the system components. | 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 fo | ||||
| SV-253941r879887_rule | JUEX-NM-000640 | CCI-000366 | HIGH | The Juniper EX switch must be configured to use an authentication server 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 protection against the insider threat. With robust centralized management, audit records for administrat | ||||
| SV-253942r879887_rule | JUEX-NM-000650 | CCI-000366 | MEDIUM | The Juniper EX switch must be configured to conduct backups of system level information contained in the information system when changes occur. | System-level information includes default and customized settings and security attributes, including firewall filters that relate to the network device configuration, as well as software required for the execution and operation of the device. Information | ||||
| SV-253943r879887_rule | JUEX-NM-000660 | CCI-000366 | MEDIUM | The Juniper EX switch must be configured to obtain its public key certificates from an appropriate certificate policy through an approved service provider. | For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Aut | ||||
| SV-253944r879887_rule | JUEX-NM-000670 | CCI-002605 | HIGH | The Juniper EX switch must be configured to send log data to a central log server for the purpose of forwarding alerts to the administrators and the 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 stored log data can used to detect weaknesses in security that enable the network IA team to find and address | ||||
| SV-253945r879887_rule | JUEX-NM-000680 | CCI-000366 | HIGH | The Juniper EX switch must be configured with an operating system 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. | ||||
| SV-253946r879694_rule | JUEX-NM-000910 | CCI-002142 | MEDIUM | The Juniper EX switch must change credentials for account of last resort when administrators who know the credential leave the organization. | 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 th | ||||
| SV-253947r879717_rule | JUEX-NM-000930 | CCI-002235 | HIGH | The Juniper EX switch must prevent nonprivileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged 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, | ||||