STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 6 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Juniper SRX SG NDM Security Technical Implementation Guide

Archived

Version

V1R3

Release Date

Jul 26, 2019

SCAP Benchmark ID

S-db52020ecf6f80aa15e2d982b2fcecfcc9108a80

Total Checks

72

Tags

network
CAT I: 5CAT II: 49CAT III: 18

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 e-mail to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (72)

V-66015MEDIUMIf the loopback interface is used, the Juniper SRX Services Gateway must protect the loopback interface with firewall filters for known attacks that may exploit this interface.V-66443MEDIUMFor local accounts, the Juniper SRX Services Gateway must generate an alert message to the management console and generate a log event record that can be forwarded to the ISSO and designated system administrators when local accounts are created.V-66445MEDIUMThe Juniper SRX Services Gateway must generate an alert message to the management console and generate a log event record that can be forwarded to the ISSO and designated system administrators when the local accounts (i.e., the account of last resort or root account) are modified.V-66447MEDIUMThe Juniper SRX Services Gateway must generate alerts to the management console and generate a log record that can be forwarded to the ISSO and designated system administrators when the local accounts (i.e., the account of last resort or root account) are deleted.V-66449HIGHThe Juniper SRX Services Gateway must be configured to use a centralized authentication server to authenticate privileged users for remote and nonlocal access for device management.V-66451HIGHIf SNMP is enabled, the Juniper SRX Services Gateway must use and securely configure SNMPv3.V-66453HIGHFor nonlocal maintenance sessions using SNMP, the Juniper SRX Services Gateway must use and securely configure SNMPv3 with SHA to protect the integrity of maintenance and diagnostic communications.V-66455HIGHFor nonlocal maintenance sessions using SNMP, the Juniper SRX Services Gateway must securely configure SNMPv3 with privacy options to protect the confidentiality of maintenance and diagnostic communications for nonlocal maintenance sessions.V-66457MEDIUMThe Juniper SRX Services Gateway must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.V-66459MEDIUMFor local accounts created on the device, the Juniper SRX Services Gateway must automatically generate log records for account creation events.V-66461MEDIUMFor local accounts created on the device, the Juniper SRX Services Gateway must automatically generate log records for account modification events.V-66463MEDIUMFor local accounts created on the device, the Juniper SRX Services Gateway must automatically generate log records for account disabling events.V-66465MEDIUMFor local accounts created on the device, the Juniper SRX Services Gateway must automatically generate log records for account removal events.V-66467MEDIUMThe Juniper SRX Services Gateway must generate an alert message to the management console and generate a log event record that can be forwarded to the ISSO and designated system administrators when accounts are disabled.V-66469MEDIUMThe Juniper SRX Services Gateway must automatically generate a log event when accounts are enabled.V-66471MEDIUMThe Juniper SRX Services Gateway must generate an immediate alert message to the management console for account enabling actions.V-66473MEDIUMThe Juniper SRX Services Gateway must enforce the assigned privilege level for each administrator and authorizations for access to all commands by assigning a login class to all AAA-authenticated users.V-66475MEDIUMThe Juniper SRX Services Gateway must enable log record generation for DoD-defined auditable events within the Juniper SRX Service Gateway.V-66477MEDIUMFor local log files, the Juniper SRX Services Gateway must allocate log storage capacity in accordance with organization-defined log record storage requirements so that the log files do not grow to a size that causes operational issues.V-66479MEDIUMThe Juniper SRX Services Gateway must generate an immediate system alert message to the management console when a log processing failure is detected.V-66481MEDIUMIn the event that communications with the events server is lost, the Juniper SRX Services Gateway must continue to queue log records locally.V-66483MEDIUMThe Juniper SRX Services Gateway must record time stamps for log records using Coordinated Universal Time (UTC).V-66485MEDIUMThe Juniper SRX Services Gateway must implement logon roles to ensure only authorized roles are allowed to install software and updates.V-66487MEDIUMThe Juniper SRX Services Gateway must be configured to synchronize internal information system clocks with the primary and secondary NTP servers for the network.V-66489MEDIUMThe Juniper SRX Services Gateway must be configured to use an authentication server to centrally manage authentication and logon settings for remote and nonlocal access.V-66491MEDIUMThe Juniper SRX Services Gateway must be configured to use an authentication server to centrally apply authentication and logon settings for remote and nonlocal access for device management.V-66493MEDIUMThe Juniper SRX Services Gateway must use DoD-approved PKI rather than proprietary or self-signed device certificates.V-66495MEDIUMThe Juniper SRX Services Gateway must generate an alarm or send an alert message to the management console when a component failure is detected.V-66497MEDIUMThe Juniper SRX Services Gateway must be configured to prohibit the use of unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.V-66499MEDIUMFor nonlocal maintenance sessions, the Juniper SRX Services Gateway must remove or explicitly deny the use of nonsecure protocols.V-66501MEDIUMThe Juniper SRX Services Gateway must authenticate NTP servers before establishing a network connection using bidirectional authentication that is cryptographically based.V-66503MEDIUMThe Juniper SRX Services Gateway must ensure SSH is disabled for root user logon to prevent remote access using the root account.V-66507MEDIUMThe Juniper SRX Services Gateway must ensure access to start a UNIX-level shell is restricted to only the root account.V-66509MEDIUMThe Juniper SRX Services Gateway must ensure TCP forwarding is disabled for SSH to prevent unauthorized access.V-66511MEDIUMThe Juniper SRX Services Gateway must be configured with only one local user account to be used as the account of last resort.V-66513MEDIUMThe Juniper SRX Services Gateway must implement replay-resistant authentication mechanisms for network access to privileged accounts.V-66515MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce a minimum 15-character password length.V-66517MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce password complexity by setting the password change type to character sets.V-66519MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce password complexity by requiring at least one upper-case character be used.V-66521MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce password complexity by requiring at least one lower-case character be used.V-66523MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce password complexity by requiring at least one numeric character be used.V-66525MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort), the Juniper SRX Services Gateway must enforce password complexity by requiring at least one special character be used.V-66527MEDIUMFor local accounts using password authentication (i.e., the root account and the account of last resort) the Juniper SRX Services Gateway must use the SHA1 or later protocol for password authentication.V-66529MEDIUMFor nonlocal maintenance sessions using SSH, the Juniper SRX Services Gateway must securely configure SSHv2 Message Authentication Code (MAC) algorithms to protect the integrity of maintenance and diagnostic communications.V-66531MEDIUMFor nonlocal maintenance sessions using SSH, the Juniper SRX Services Gateway must securely configured SSHv2 with privacy options to protect the confidentiality of maintenance and diagnostic communications for nonlocal maintenance sessions.V-66533MEDIUMFor nonlocal maintenance sessions, the Juniper SRX Services Gateway must ensure only zones where management functionality is desired have host-inbound-traffic system-services configured.V-66535MEDIUMThe Juniper SRX Services Gateway must immediately terminate SSH network connections when the user logs off, the session abnormally terminates, or an upstream link from the managed device goes down.V-66537MEDIUMThe Juniper SRX Services Gateway must terminate a device management session after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.V-66539MEDIUMThe Juniper SRX Services Gateway must terminate a device management session if the keep-alive count is exceeded.V-66541MEDIUMThe Juniper SRX Services Gateway must configure the control plane to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself by configuring applicable system options and internet-options.V-66543MEDIUMThe Juniper SRX Services Gateway must limit the number of sessions per minute to an organization-defined number for SSH to protect remote access management from unauthorized access.V-66545MEDIUMThe Juniper SRX Services Gateway must reveal log messages or management console alerts only to the ISSO, ISSM, and SA roles).V-66547MEDIUMThe Juniper SRX Services Gateway must be configured to use Junos 12.1 X46 or later to meet the minimum required version for DoD.V-66549LOWThe Juniper SRX Services Gateway must limit the number of concurrent sessions to a maximum of 10 or less for remote access using SSH.V-66551LOWThe Juniper SRX Services Gateway must generate a log event when privileged commands are executed.V-66553LOWFor local accounts created on the device, the Juniper SRX Services Gateway must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.V-66555LOWThe Juniper SRX Services Gateway must display the Standard Mandatory DoD Notice and Consent Banner before granting access.V-66557LOWThe Juniper SRX Services Gateway must allow only the ISSM (or administrators/roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the syslog and/or local logs.V-66559LOWThe Juniper SRX Services Gateway must generate log records when successful attempts to configure the device and use commands occur.V-66561LOWThe Juniper SRX Services Gateway must generate log records when changes are made to administrator privileges.V-66563LOWThe Juniper SRX Services Gateway must generate log records when administrator privileges are deleted.V-66565LOWThe Juniper SRX Services Gateway must generate log records when logon events occur.V-66567LOWThe Juniper SRX Services Gateway must generate log records when privileged commands are executed.V-66569LOWThe Juniper SRX Services Gateway must generate log records when concurrent logons from different workstations occur.V-66571LOWThe Juniper SRX Services Gateway must generate log records containing the full-text recording of privileged commands.V-66573LOWFor local logging, the Juniper SRX Services Gateway must generate a message to the system management console when a log processing failure occurs.V-66595LOWThe Juniper SRX Services Gateway must have the number of rollbacks set to 5 or more.V-66597LOWThe Juniper SRX Services Gateway must specify the order in which authentication servers are used.V-66599LOWThe Juniper SRX Services Gateway must detect the addition of components and issue a priority 1 alert to the ISSM and SA, at a minimum.V-66601LOWThe Juniper SRX Services Gateway must terminate the console session when the serial cable connected to the console port is unplugged.V-66603LOWThe Juniper SRX Services Gateway must implement service redundancy to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself.V-66605HIGHFor nonlocal maintenance sessions, the Juniper SRX Services Gateway must explicitly deny the use of J-Web.