{"stig":{"title":"Juniper SRX SG ALG Security Technical Implementation Guide","version":"1","release":"4"},"checks":[{"vulnId":"V-66003","ruleId":"SV-80493r1_rule","severity":"medium","ruleTitle":"For User Role Firewalls, the Juniper SRX Services Gateway Firewall must employ user attribute-based security policies to enforce approved authorizations for logical access to information and system resources.","description":"Successful authentication must not automatically give an entity access to an asset or security boundary. The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. All DoD systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access.\n\nAuthorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset.\n\nThe Juniper Technical Library, Understanding User Role Firewalls, explains this Juniper SRX functionality in detail. This function integrates user-based firewall policies. Administrators can permit or restrict network access of employees, contractors, partners, and other users based on the roles they are assigned. User role firewalls enable greater threat mitigation, provide more informative forensic resources, improve record archiving for regulatory compliance, and enhance routine access provisioning. User role firewalls are more feasible with sites that do not have production workload and are used for employees to access network resources as opposed to large-scale datacenter environments.\n\nUser role firewalls trigger two actions, retrieval of user and/or role information associated with the traffic, and determine the action to take based on six match criteria within the context of the zone pair.\n\nThe source-identity field distinguishes a user role firewall from other types of firewalls. If the source identity is specified in any policy for a particular zone pair, it is a user role firewall. The user and role information must be retrieved before policy lookup occurs. If the source identity is not specified in any policy, user and role lookup is not required.\n\nTo retrieve user and role information, authentication tables are searched for an entry with an IP address corresponding to the traffic. If an entry is found, the user is classified as an authenticated user. If not found, the user is classified as an unauthenticated user.\n\nThe username and roles associated with an authenticated user are retrieved for policy matching. Both the authentication classification and the retrieved user and role information are used to match the source-identity field.\n\nCharacteristics of the traffic are matched to the policy specifications. Within the zone context, the first policy that matches the user or role and the five standard match criteria determines the action to be applied to the traffic.\"","checkContent":"If user-based firewall policies are not used, this is not applicable.\n\nTo verify the existence of user-based firewall policies, view a summary of all policies configured on the firewall.\n\n[edit]\nshow security policies\n\nIf the source identity is not specified in any policy for a particular zone pair, this is a finding.","fixText":"Configure attribute-based security policies to enforce approved authorizations for logical access to information and system resources using the following commands.\n\nTo configure redirection from the SRX Series device to the Access Control Service, from configuration mode, configure the UAC profile for the captive portal <acs-device>.\n\n[edit]\nset services unified-access-control captive-portal <acs-device-name> redirect-traffic unauthenticated\n\nConfigure the redirection URL for the Access Control Service or a default URL for the captive portal.\n\n[edit]\nset services unified-access-control captive-portal acs-device redirect-url https://%ic-url%/?target=%dest-url%&enforcer=%enforcer-id%\n\nThis policy specifies the default target and enforcer variables to be used by the Access Control Service to direct the user back after authentication. This ensures that changes to system specifications will not affect configuration results.\n\nConfigure a user role firewall policy that redirects HTTP traffic from zone trust to zone untrust if the source-identity is unauthenticated-user. The captive portal profile name is specified as the action to be taken for traffic matching this policy. The following is an example only since there the actual policy is dependent on the architecture of the organization's network.\n\n[edit]\nset security policies from-zone trust to-zone untrust policy user-role-fw1 match source-address any\nset security policies from-zone trust to-zone untrust policy user-role-fw1 match destination-address any\nset security policies from-zone trust to-zone untrust policy user-role-fw1 match application http\nset security policies from-zone trust to-zone untrust policy user-role-fw1 match source-identity unauthenticated-user\nset security policies from-zone trust to-zone untrust policy user-role-fw1 then permit app","ccis":[]},{"vulnId":"V-66303","ruleId":"SV-80793r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway must generate log records when firewall filters, security screens and security policies are invoked and the traffic is denied or restricted.","description":"Without generating log records that log usage of objects by subjects and other objects, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.\n\nSecurity objects are data objects which are controlled by security policy and bound to security attributes.\n\nBy default, the Juniper SRX will not forward traffic unless it is explicitly permitted via security policy. Logging for Firewall security-related sources such as screens and security policies must be configured separately. To ensure firewall filters, security screens and security policies send events to a Syslog server and local logs, security logging must be configured one each firewall term.","checkContent":"To verify what is logged in the Syslog, view the Syslog server (Syslog server configuration is out of scope for this STIG); however, the reviewer must also verify that packets are being logged to the local log using the following commands.\n\nFrom operational mode, enter the following command.\n\nshow firewall log\n\nView the Action column; the configured action of the term matches the action taken on the packet: A (accept), D (discard).\n\nIf events in the log do not reflect the action taken on the packet, this is a finding.","fixText":"Include the log and/or syslog action in all term to log packets matching each firewall term to ensure the term results are recorded in the firewall log and Syslog. To get traffic logs from permitted sessions, add \"then log session-close\" to each policy. To get traffic logs from denied sessions, add \"then log session-init\" to the policy.\n\nFirewall filter:\n[edit]\nset firewall family <family name> filter <filter_name> term <term_name> then log\n\nExamples: \nset firewall family inet filter protect_re term tcp-connection then syslog\nset firewall family inet filter protect_re term tcp-connection then log\nset firewall family inet filter ingress-filter-v4 term deny-dscp then log\nset firewall family inet filter ingress-filter-v4 term deny-dscp then syslog\n\nSecurity policy and security screens:\nset security policies from-zone <zone_name> to-zone <zone_name> policy <policy_name> then log\n\nExample:\nset security policies from-zone untrust to-zone trust policy default-deny then log","ccis":[]},{"vulnId":"V-66305","ruleId":"SV-80795r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must generate audit records when unsuccessful attempts to access security zones occur.","description":"Without generating log 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.\n\nAccess for different security levels maintains separation between resources (particularly stored data) of different security domains.\n\nThe Juniper SRX Firewall implements security zones which are configured with different security policies based on risk and trust levels.","checkContent":"To verify what is logged in the Syslog, view the Syslog server (Syslog server configuration is out of scope for this STIG); however, the reviewer must also verify that packets are being logged to the local log using the following commands.\n\nFrom operational mode, enter the following command.\n\nshow firewall log\n\nView the Action column; the configured action of the term matches the action taken on the packet: A (accept), D (discard).\n\nIf events in the log do not reflect the action taken on the packet, this is a finding.","fixText":"Include the log and/or syslog action in all zone configurations to log attempts to access zones. To get traffic logs from permitted sessions, add \"then log session-close\" to the policy. To get traffic logs from denied sessions, add \"then log session-init\" to the policy.\n\nset security policies from-zone <zone_name> to-zone <zone_name> policy <policy_name> then log\n\nExample:\nset security policies from-zone untrust to-zone trust policy default-deny then log","ccis":[]},{"vulnId":"V-66307","ruleId":"SV-80797r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must be configured to support centralized management and configuration of the audit log.","description":"Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack.\n\nThe DoD requires centralized management of all network component audit record content. Network components requiring centralized audit log management must have the capability to support centralized management. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. Ensure at least one Syslog server and local files are configured to support requirements. However, the Syslog itself must also be configured to filter event records so it is not overwhelmed. A best practice when configuring the external Syslog server is to add similar log-prefixes to the log file names to help and researching of central Syslog server. Another best practice is to add a match condition to limit the recorded events to those containing the regular expression (REGEX). This requirement does not apply to audit logs generated on behalf of the device itself (management).\n\nWhile the Juniper SRX inherently has the capability to generate log records, by default only the high facility levels are captured and only to local files.","checkContent":"To verify that traffic logs are being sent to the syslog server, check the syslog server files. \n\nIf traffic logs are not being sent to the syslog server, this is a finding.","fixText":"Logging for security-related sources such as screens and security policies must be configured separately. \n\nThe following example specifies that security log messages in structured-data format (syslog format) are sent from the source <MGT IP address> (e.g., the SRX's loopback or other interface IP address) to an external syslog server.\n\n[edit]\nset security log cache\nset security log format syslog\nset security log source-address <MGT IP Address>\nset security log stream <stream name> host <syslog server IP Address>\n\nTo get traffic logs from permitted sessions, add \"then log session-close\" to the policy.\nTo get traffic logs from denied sessions, add \"then log session-init\" to the policy. Enable Logging on Security Policies:\n\n[edit]\nset security policies from-zone <zone-name> to-zone <zone-name> policy <policy-name> then log <event>\n\nExample to log session init and session close events:\nset security policies from-zone trust to-zone untrust policy default-permit then log session-init\nset security policies from-zone trust to-zone untrust policy default-permit then log session-close","ccis":[]},{"vulnId":"V-66309","ruleId":"SV-80799r1_rule","severity":"medium","ruleTitle":"In the event that communications with the Syslog server is lost, the Juniper SRX Services Gateway must continue to queue traffic log records locally.","description":"It is critical that when the network element is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.\n\nSince availability is an overriding concern given the role of the Juniper SRX in the enterprise, the system must not be configured to shut down in the event of a log processing failure. The system will be configured to log events to local files which will provide a log backup. If communication with the syslog server is lost or the server fails, the network device must continue to queue log records locally. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local log data with the collection server.\n\nBy default, both traffic log and system log events are sent to a local log file named messages. You can create a separate log file that contains only traffic log messages so that you do not need to filter for traffic log messages. This makes it easier to track usage patterns or troubleshoot issues for a specific policy. \n\nA best practice is to add log-prefixes to the log file names to help in researching the events and filters to prevent log overload. Another best practice is to add a match condition to limit the recorded events to those containing the regular expression (REGEX).","checkContent":"Verify logging has been enabled and configured.\n\n[edit] \nshow log <LOG-NAME> match \"RT_FLOW_SESSION\"\n\nIf a local log file or files is not configured to capture \"RT_FLOW_SESSION\" events, this is a finding.","fixText":"The following example commands configure local backup files to capture DoD-defined auditable events. \n\n[edit]\nset system syslog file <LOG-NAME> any info\nset system syslog file <LOG-NAME> match \"RT_FLOW_SESSION \"\n\nExample:\nset system syslog file<LOG-NAME> match \"RT_FLOW_SESSION \"","ccis":[]},{"vulnId":"V-66311","ruleId":"SV-80801r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must disable or remove unnecessary network services and functions that are not used as part of its role in the architecture.","description":"Network devices are capable of providing a wide variety of functions (capabilities or processes) and services. Some of these functions and services are installed and enabled by default. The organization must determine which functions and services are required to perform the content filtering and other necessary core functionality for each component of the SRX. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nServices that may be related security-related, but based on the role of the device in the architecture do not need to be installed. For example, the Juniper SRX can have an Antivirus, Web filter, IDS, or ALG license. However, if these functions are not part of the documented role of the SRX in the enterprise or branch architecture, then these the software and licenses should not be installed on the device. This mitigates the risk of exploitation of unconfigured services or services that are not kept updated with security fixes. If left unsecured, these services may provide a threat vector.\n\nOnly remove unauthorized services. This control is not intended to restrict the use of Juniper SRX devices with multiple authorized roles.","checkContent":"Review the documentation and architecture for the device.\n\n<root> \nshow system license\n\nIf unneeded services and functions are installed on the device, but are not part of the documented role of the device, this is a finding.","fixText":"Remove unnecessary services and functions. From operational mode, display the licenses available to be deleted; enter the following commands.\n\nrequest system license delete license-identifier-list ?\nrequest system license delete <license-identifier>\n\nNote: Only remove unauthorized services. This control is not intended to restrict the use of Juniper SRX devices with multiple authorized roles.","ccis":[]},{"vulnId":"V-66313","ruleId":"SV-80803r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must not be configured as an NTP server since providing this network service is unrelated to the role as a firewall.","description":"Information systems are capable of providing a wide variety of functions (capabilities or processes) and services. Some of these functions and services are installed and enabled by default. The organization must determine which functions and services are required to perform the content filtering and other necessary core functionality for each component of the SRX. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nThe Juniper SRX is a highly configurable platform that can fulfil many roles in the Enterprise or Branch architecture depending on the model installed. Some services are employed for management services; however, these services can often also be provided as a network service on the data plane. Examples of these services are NTP, DNS, and DHCP. Also, as a Next Generation Firewall (NGFW) and Unified Threat Management (UTM) device, the SRX integrate functions which have been traditionally separated. \n\nThe SRX may integrate related content filtering, security services, and analysis services and tools (e.g., IPS, proxy, malware inspection, black/white lists). Depending on licenses purchased, gateways may also include email scanning, decryption, caching, VPN, and DLP services. However, services and capabilities which are unrelated to this primary functionality must not be installed (e.g., DNS, email server, FTP server, or web server).","checkContent":"Check both the zones and the interface stanza to ensure NTP is not configured as a service option.\n\n[edit]\nshow security zones\n\nand, for each interface used, enter:\n\nshow security zones <zone-name> interface <interface-name>\n\nIf NTP is included in any of the zone or interface stanzas, this is a finding.","fixText":"Delete NTP options from zones and interface commands. Re-enter the set security zone command without the \"ntp\" attribute. The exact command entered depends how the zone is configured with the authorized attributes, services, and options.\n\nExamples: \n\n[edit]\nset security zones security-zone <zone-name> interfaces <interface-name> host-inbound-traffic","ccis":[]},{"vulnId":"V-66315","ruleId":"SV-80805r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must not be configured as a DNS proxy since providing this network service is unrelated to the role as a Firewall.","description":"Information systems are capable of providing a wide variety of functions (capabilities or processes) and services. Some of these functions and services are installed and enabled by default. The organization must determine which functions and services are required to perform the content filtering and other necessary core functionality for each component of the SRX. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nThe Juniper SRX is a highly configurable platform that can fulfil many roles in the Enterprise or Branch architecture depending on the model installed. Some services are employed for management services; however, these services can often also be provided as a network service on the data plane. Examples of these services are NTP, DNS, and DHCP. Also, as a Next Generation Firewall (NGFW) and Unified Threat Management (UTM) device, the SRX integrate functions which have been traditionally separated. \n\nThe SRX may integrate related content filtering, security services, and analysis services and tools (e.g., IPS, proxy, malware inspection, black/white lists). Depending on licenses purchased, gateways may also include email scanning, decryption, caching, VPN, and DLP services. However, services and capabilities which are unrelated to this primary functionality must not be installed (e.g., DNS, email server, FTP server, or web server).","checkContent":"Check both the zones and the interface stanza to ensure DNS proxy server services are not configured.\n\n[edit}\nshow system services dns\n\nIf a stanza exists for DNS (e.g., forwarders option), this is a finding.","fixText":"First, remove the DNS stanza. Then re-enter the set security zones and interfaces command without the \"dns\" attribute. The exact command entered depends how the zone is configured with the authorized attributes, services, and options.\n\nExamples: \n\n[edit]\ndelete system services dns\nset security zones security-zone <zone-name> interfaces <interface-name> host-inbound-traffic","ccis":[]},{"vulnId":"V-66317","ruleId":"SV-80807r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must not be configured as a DHCP server since providing this network service is unrelated to the role as a Firewall.","description":"Information systems are capable of providing a wide variety of functions (capabilities or processes) and services. Some of these functions and services are installed and enabled by default. The organization must determine which functions and services are required to perform the content filtering and other necessary core functionality for each component of the SRX. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nThe Juniper SRX is a highly configurable platform that can fulfil many roles in the Enterprise or Branch architecture depending on the model installed. Some services are employed for management services; however, these services can often also be provided as a network service on the data plane. Examples of these services are NTP, DNS, and DHCP. Also, as a Next Generation Firewall (NGFW) and Unified Threat Management (UTM) device, the SRX integrate functions which have been traditionally separated. \n\nThe SRX may integrate related content filtering, security services, and analysis services and tools (e.g., IPS, proxy, malware inspection, black/white lists). Depending on licenses purchased, gateways may also include email scanning, decryption, caching, VPN, and DLP services. However, services and capabilities which are unrelated to this primary functionality must not be installed (e.g., DNS, email server, FTP server, or web server).","checkContent":"Check both the zones and the interface stanza to ensure DHCP proxy server services are not configured.\n\n[edit]\nshow system services dhcp\n\nIf a stanza exists for DHCP (e.g., forwarders option), this is a finding.","fixText":"First, remove the DHCP stanza. Then re-enter the set security zones and interfaces command without the \"dhcp\" attribute. The exact command entered depends how the zone is configured with the authorized attributes, services, and options.\n\nExamples: \n\n[edit]\ndelete system services dhcp\nset security zones security-zone <zone-name> interfaces <interface-name> host-inbound-traffic","ccis":[]},{"vulnId":"V-66319","ruleId":"SV-80809r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must be configured to prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services, as defined in the PPSM CAL, vulnerability assessments.","description":"In order 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 or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nDoD continually assesses the ports, protocols, and services that can be used for network communications. Some ports, protocols or services have known exploits or security weaknesses. Network traffic using these ports, protocols, and services must be prohibited or restricted in accordance with DoD policy. The PPSM CAL and vulnerability assessments provide an authoritative source for ports, protocols, and services that are unauthorized or restricted across boundaries on DoD networks.\n\nThe Juniper SRX must be configured to prevent or restrict the use of prohibited ports, protocols, and services throughout the network by filtering the network traffic and disallowing or redirecting traffic as necessary. Default and updated policy filters from the vendors will disallow older version of protocols and applications and will address most known non-secure ports, protocols, and/or services.","checkContent":"Entering the following commands from the configuration level of the hierarchy.\n\n[edit]\nshow security services\n\nIf functions, ports, protocols, and services identified on the PPSM CAL are not disabled, this is a finding.","fixText":"Ensure functions, ports, protocols, and services identified on the PPSM CAL are not used for system services configuration.\n\n[edit]\nshow security services\n\nCompare the services which are enabled, including the port, services, protocols and functions.\n\nConsult the Juniper knowledge base and configuration guides to determine the commands for disabling each port, protocol, service or function that is not in compliance with the PPSM CAL and vulnerability assessments.","ccis":[]},{"vulnId":"V-66321","ruleId":"SV-80811r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must terminate all communications sessions associated with user traffic after 15 minutes or less of inactivity.","description":"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 terminating an idle session will also free up resources committed by the managed network element.\n\nThis control does not imply that the device terminates all sessions or network access; it only ends the inactive session.\n\nSince many of the inactivity timeouts pre-defined by Junos OS are set to 1800 seconds, an explicit custom setting of 900 must be set for each application used by the DoD implementation. Since a timeout cannot be set directly on the predefined applications, the timeout must be set on the any firewall rule that uses a pre-defined application (i.e., an application that begins with junos-), otherwise the default pre-defined timeout will be used.","checkContent":"Check both the applications and protocols to ensure session inactivity timeout for communications sessions is set to 900 seconds or less.\n\nFirst get a list of security policies, then enter the show details command for each policy-name found.\n\n[edit]\nshow security policies\nshow security policy <policy-name> details\n\nExample:\nApplication: any\n IP protocol: 0, ALG: 0, Inactivity timeout: 0\n\nVerify an activity timeout is configured for either \"any\" application or, at a minimum, the pre-defined applications (i.e., application names starting with junos-).\n\nTo verify locally created applications, first get a list of security policies, then enter the show details command for each policy-name found.\n\n[edit]\nShow applications \nshow applications application <application-name>\n\nIf an inactivity timeout value of 900 seconds or less is not set for each locally created application and pre-defined applications, this is a finding.","fixText":"Add or update the session inactivity timeout for communications sessions to 900 seconds or less.\n\nExamples: \n[edit]\nset applications application <application-name> term 1 protocol udp inactivity-timeout 900\nset applications application junos-http inactivity-timeout 900\n\nOr\n\nCreate a service that matches any TCP/UDP:\n[edit]\nset applications application TCP-ALL source-port 1-65535 destination-port 1-65535 protocol tcp inactivity-timeout 900\n\nNote: When pre-defined applications are used in firewall policies, the timeout value must be set in the policy stanza.","ccis":[]},{"vulnId":"V-66323","ruleId":"SV-80813r2_rule","severity":"high","ruleTitle":"The Juniper SRX Services Gateway Firewall providing content filtering must protect against known and unknown types of Denial of Service (DoS) attacks by implementing statistics-based screens.","description":"If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume/type.\n \nJuniper SRX Firewall DoS protections can be configured by either using a Screen or within the global flow options. Screens, also known as IDS-options, block various layer 3 and 4 attacks. Screen objects are configured with various screen-specific options and then assigned to a zone. The Juniper SRX can be configured with Screens to protect against the following statistics-based DoS attacks: IP sweeps, port scans, and flood attacks.","checkContent":"Run the following command to see the screen options currently configured:\n\n[edit]\nshow security screen ids-option\nshow security zone match \"screen\"\n\nIf security screens are not configured or if the security zone is not configured with screen options, this is a finding.","fixText":"The following example commands configure security screens under a profile named untrust-screen. Screen options, with configurable thresholds may be customized to minimize/prevent operational impact on traffic performance.\n\n[edit]\nset security screen ids-option <zone-name> <screen name> <option name> <value>\n\nBased on 800-53 requirements and vendor recommendations, the following DoS screens are required, at a minimum, for use in DoD configurations.\n\nset security screen ids-option untrust-screen icmp ip-sweep threshold 1000\nset security screen ids-option untrust-screen tcp port-scan threshold 1000\nset security screen ids-option untrust-screen tcp sin-flood alarm-threshold 1000\nset security screen ids-option untrust-screen tcp syn-flood attack-threshold 1100\nset security screen ids-option untrust-screen tcp syn-flood source-threshold 100\nset security screen ids-option untrust-screen tcp syn-flood destination-threshold 2048\nset security screen ids-option untrust-screen tcp syn-flood timeout 20\nset security screen ids-option untrust-screen udp flood threshold 5000\nset security screen ids-option untrust-screen udp udp-sweep threshold 1000\n\nTo enable screen protection, the screen profile must be associated with individual security zones using the following command. Recommend assigning \"untrust-screen\" profile name to the default zone named \"untrust\".\n\n[edit]\nset security zone security-zone <zone-name> screen <screen-profile>\nExample: set security zones security-zone untrust screen untrust-screen","ccis":[]},{"vulnId":"V-66325","ruleId":"SV-80815r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must implement load balancing on the perimeter firewall, at a minimum, to limit the effects of known and unknown types of Denial of Service (DoS) attacks on the network.","description":"If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Load balancing provides service redundancy, which reduces the susceptibility of the ALG to many DoS attacks.\n\nThis requirement applies to the network traffic functionality of the device as it pertains to handling network traffic. Some types of attacks may be specialized to certain network technologies, functions, or services. For each technology, known and potential DoS attacks must be identified and solutions for each type implemented.\n\nThe Juniper SRX provides a number of methods for load balancing the traffic flow. The device can be configured for filter based forwarding, per flow load balancing, per-packet load balancing, or High Availability (HA) using additional hardware. Since the firewall is considered a critical security system, it is imperative that perimeter firewalls, at a minimum, be safeguarded with redundancy measures such as HA.","checkContent":"Since load balancing is a highly complex configuration that can be implemented using a wide variety of configurations, ask the site representative to demonstrate the method used and the configuration.\n\nIf load balancing is not implemented on the perimeter firewall, this is a finding.","fixText":"Consult vendor configuration guides and knowledge base. Implement one or more methods of load balance (e.g., filter based forwarding, per flow load balancing, per-packet load balancing, or High Availability [HA]).","ccis":[]},{"vulnId":"V-66327","ruleId":"SV-80817r2_rule","severity":"high","ruleTitle":"The Juniper SRX Services Gateway Firewall must protect against known types of Denial of Service (DoS) attacks by implementing signature-based screens.","description":"If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks.\n\nJuniper SRX Firewall DoS protections can be configured by either using a Screen or within the global flow options. Screens, also known as IDS-options, block various layer 3 and 4 attacks. Screen objects are configured with various screen-specific options and then assigned to a zone. The Juniper SRX can be configured with Screens to protect against the following signature-based DoS attacks: ICMP based attacks such as ping of death, IP based attacks such as IP spoofing and teardrop, and TCP based attacks such as TCP headers and land.","checkContent":"Run the following command to see the screen options currently configured:\n\n[edit]\nshow security screen ids-option\nshow security zone match \"screen\"\n\nIf security screens are not configured or if the security zone is not configured with screen options, this is a finding.","fixText":"The following example commands configure security screens under a profile named untrust-screen. Screen options with configurable thresholds may be customized to minimize/prevent operational impact on traffic performance.\n\n[edit]\nset security screen ids-option <zone-name> <screen name> <option name> <value>\n\nBased on 800-53 requirements and vendor recommendations, the following signature-based screens are required, at a minimum, for use in DoD configurations.\n\nset security screen ids-option untrust-screen icmp ping-death\nset security screen ids-option untrust-screen ip bad-option\nset security screen ids-option untrust-screen ip record-route-option\nset security screen ids-option untrust-screen ip timestamp-option\nset security screen ids-option untrust-screen ip security-option\nset security screen ids-option untrust-screen ip stream-option\nset security screen ids-option untrust-screen ip spoofing\nset security screen ids-option untrust-screen ip source-route-option\nset security screen ids-option untrust-screen ip unknown-protocol\nset security screen ids-option untrust-screen ip tear-drop\nset security screen ids-option untrust-screen ip ipv6-extension-header hop-by-hop-header\njumbo-payload-option\nset security screen ids-option untrust-screen ip ipv6-extension-header hop-by-hop-header\nrouter-alert-option\nset security screen ids-option untrust-screen ip ipv6-extension-header hop-by-hop-header\nquick-start-option\nset security screen ids-option untrust-screen ip ipv6-extension-header routing-header\nset security screen ids-option untrust-screen ip ipv6-extension-header fragment-header\nset security screen ids-option untrust-screen ip ipv6-extension-header no-next-header\nset security screen ids-option untrust-screen ip ipv6-extension-header shim6-header\nset security screen ids-option untrust-screen ip ipv6-extension-header mobility-header\nset security screen ids-option untrust-screen ip ipv6-malformed-header\nset security screen ids-option untrust-screen tcp syn-fin\nset security screen ids-option untrust-screen tcp fin-no-ack\nset security screen ids-option untrust-screen tcp tcp-no-flag\nset security screen ids-option untrust-screen tcp syn-frag\nset security screen ids-option untrust-screen tcp land\n\nTo enable screen protection, the screen profile must be associated with individual security zones using the following command. Recommend assigning \"untrust-screen\" profile name to the default zone named \"untrust\".\n\n[edit]\nset security zone security-zone <ZONE NAME> screen <SCREEN PROFILE NAME>\nExample: set security zones security-zone untrust screen untrust-screen","ccis":[]},{"vulnId":"V-66329","ruleId":"SV-80819r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must block outbound traffic containing known and unknown DoS attacks to protect against the use of internal information systems to launch any Denial of Service (DoS) attacks against other networks or endpoints.","description":"DoS attacks can take multiple forms but have the common objective of overloading or blocking a network or host to deny or seriously degrade performance. If the network does not provide safeguards against DoS attack, network resources will be unavailable to users. The Juniper SRX must include protection against DoS attacks that originate from inside the enclave, which can affect either internal or external systems. These attacks may use legitimate or rogue endpoints from inside the enclave. These attacks can be simple \"floods\" of traffic to saturate circuits or devices, malware that consumes CPU and memory on a device or causes it to crash, or a configuration issue that disables or impairs the proper function of a device. For example, an accidental or deliberate misconfiguration of a routing table can misdirect traffic for multiple networks.\n\nThe Juniper SRX Firewall uses Screens and Security Policies to detect known DoS attacks with known attack vectors. However, these Screens and policies must be applied to outbound traffic using zones and interface stanzas. \n\nTraffic exits the Juniper SRX by way of interfaces. Security zones are configured for one or more interfaces with the same security requirements for filtering data packets. A security zone implements a security policy for one or multiple network segments. These policies must be applied to inbound traffic as it crosses both the network perimeter and as it crosses internal security domain boundaries.","checkContent":"Obtain and review the list of outbound interfaces and zones. This is usually part of the System Design Specification or Accreditation Package.\n\nReview each of the configured outbound interfaces and zones. Verify zones that communicate outbound have been configured with DoS screens.\n\n[edit]\nshow security zones <security-zone-name>\n\nIf the zone for the security screen has not been applied to all outbound interfaces, this is a finding.","fixText":"To enable screen protection, the screen profile must be associated with individual security zones using the following command. Recommend assigning \"untrust-screen\" profile name.\n\nApply screen to each outbound interface example:\n\nset security zones security-zone untrust interfaces <OUTBOUND-INTERFACE>\nset security zones security-zone trust screen untrust-screen","ccis":[]},{"vulnId":"V-66331","ruleId":"SV-80821r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must only allow inbound communications from organization-defined authorized sources routed to organization-defined authorized destinations.","description":"Unrestricted traffic may contain malicious traffic which poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth and other resources.\n\nTraffic enters the Juniper SRX by way of interfaces. Security zones are configured for one or more interfaces with the same security requirements for filtering data packets. A security zone implements a security policy for one or multiple network segments. These policies must be applied to inbound traffic as it crosses the network perimeter and as it crosses internal security domain boundaries.","checkContent":"Obtain and review the list of authorized sources and destinations. This is usually part of the System Design Specification or Accreditation Package.\n\nReview each of the configured security policies in turn.\n\n[edit]\nshow security policies <security-policy-name>\n\nIf any existing policies allow traffic that is not part of the authorized sources and destinations list, this is a finding.","fixText":"Configure a security policy or screen to each outbound zone to implement continuous monitoring. The following commands configure a security zone called “untrust” that can be used to apply security policy for inbound interfaces that are connected to untrusted networks. This example assumes that interfaces ge-0/0/1 and ge-0/0/2 are connected to untrusted and trusted network segments.\n\nApply security policy a zone example:\n\nset security zones security-zone untrust interfaces ge-0/0/1.0\nset security zones security-zone trust interfaces ge-0/0/2.0\nset security policies from-zone trust to-zone untrust policy default-deny match destination-address any\nset security policies from-zone trust to-zone untrust policy default-deny then deny","ccis":[]},{"vulnId":"V-66333","ruleId":"SV-80823r2_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must be configured to fail securely in the event of an operational failure of the firewall filtering or boundary protection function.","description":"If a boundary protection device fails in an unsecure manner (open), information external to the boundary protection device may enter, or the device may permit unauthorized information release.\n\nSecure failure ensures when a boundary control device fails, all traffic will be subsequently denied.\n\nFail secure is a condition achieved by employing information system mechanisms to ensure in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold.","checkContent":"Request documentation of the architecture and Juniper SRX configuration. Verify the site has configured the SRX to fail closed, thus preventing traffic from flowing through without filtering and inspection.\n\nIf the site has not configured the SRX to fail closed, this is a finding.","fixText":"Implement and configure the Juniper SRX to fail closed, thus preventing traffic from flowing through without filtering and inspection. In case of failure, document a process for the Juniper SRX to be configured to fail closed. Redundancy should be implemented if failing closed has a mission impact.","ccis":[]},{"vulnId":"V-66335","ruleId":"SV-80825r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).","description":"A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed.\n\nAs a managed interface, the ALG must block all inbound and outbound network communications traffic to the application being managed and controlled unless a policy filter is installed to explicitly allow the traffic. The allow policy filters must comply with the site's security policy. A deny all, permit by exception network communications traffic policy ensures that only those connections which are essential and approved, are allowed.\n\nBy default, Junos denies all traffic through an SRX Series device using an implicit default security policy exists that denies all packets. Organizations must configure security policies that permits or redirects traffic in compliance with DoD policies and best practices. Sites must not change the factory-default security policies.","checkContent":"Verify the default-policy has not been changed and is set to deny all traffic.\n\n[edit]\nshow security policies default-policy\n\nIf the default-policy is not set to deny-all, this is a finding.","fixText":"By default, the SRX device will not forward traffic unless it is explicitly permitted via security policy. If the default-policy has been changed, then this must be corrected using the set security policies default-policy command.","ccis":[]},{"vulnId":"V-66337","ruleId":"SV-80827r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must configure ICMP to meet DoD requirements.","description":"Providing too much information in error messages risks compromising the data and security of the application and system.\n\nOrganizations carefully consider the structure/content of error messages. The required information within error messages will vary based on the protocol and error condition. Information that could be exploited by adversaries includes ICMP messages that reveal the use of firewalls or access-control lists.","checkContent":"Verify ICMP messages are configured to meet DoD requirements.\n\n[edit]\nshow firewall family inet\n\nIf ICMP messages are not configured in compliance with DoD requirements, this is a finding.","fixText":"Configure ICMP to meet DoD requirements. The following is an example which uses the filter name \"protect_re\" as the filter name with pre-configured address books (source-prefix-lists).\n\n[edit]\nset firewall family inet filter protect_re term permit-icmp from source-prefix-list ssh-addresses\nset firewall family inet filter protect_re term permit-icmp from source-prefix-list bgp-addresses\nset firewall family inet filter protect_re term permit-icmp from source-prefix-list loopback-addresses\nset firewall family inet filter protect_re term permit-icmp from source-prefix-list local-addresses\nset firewall family inet filter protect_re term permit-icmp from source-prefix-list ixiav4\nset firewall family inet filter protect_re term permit-icmp from icmp-type echo-request\nset firewall family inet filter protect_re term permit-icmp from icmp-type echo-reply\nset firewall family inet filter protect_re term permit-icmp then log\nset firewall family inet filter protect_re term permit-icmp then syslog\nset firewall family inet filter protect_re term permit-icmp then accept\nset firewall family inet6 filter protect_re-v6 term permit-ar from icmp-type neighboradvertisement\nset firewall family inet6 filter protect_re-v6 term permit-ar from icmp-type neighborsolicit\nset firewall family inet6 filter ingress-v6 term permit-ar from icmp-type neighboradvertisement\nset firewall family inet6 filter ingress-v6 term permit-ar from icmp-type neighborsolicit\nset firewall family inet6 filter ingress-v6 term permit-ar from icmp-type 134\nset firewall family inet6 filter ingress-v6 term permit-ar then accept\nset firewall family inet6 filter egress-v6 term permit-lr from icmp-type neighboradvertisement\nset firewall family inet6 filter egress-v6 term permit-lr from icmp-type neighbor-solicit\nset firewall family inet6 filter egress-v6 term permit-lr from icmp-type 134\nset firewall family inet6 filter egress-v6 term permit-lr then accept","ccis":[]},{"vulnId":"V-66339","ruleId":"SV-80829r1_rule","severity":"high","ruleTitle":"The Juniper SRX Services Gateway Firewall must continuously monitor all inbound communications traffic for unusual/unauthorized activities or conditions.","description":"If inbound communications traffic is not continuously monitored, hostile activity may not be detected and prevented. Output from application and traffic monitoring serves as input to continuous monitoring and incident response programs.\n\nThe Juniper SRX is a highly scalable system which, by default, provides stateful or stateless continuous monitoring when placed in the architecture at either the perimeter or internal boundaries. \n\nUnusual/unauthorized activities or conditions may include unusual use of unusual protocols or ports and attempted communications from trusted zones to external addresses. \n\nInterfaces with identical security requirements can be grouped together into a single security zone. By default, once a security policy is applied to a zone, the Juniper SRX continuously monitors the associated zone for unusual/unauthorized activities or conditions based on the firewall filter or screen associated with that zone.","checkContent":"For each inbound zone, verify a firewall screen or security policy is configured.\n\n[edit]\nshow security zone\nshow security policies\n\nIf communications traffic for each inbound zone is not configured with a firewall screen and/or security policy, this is not a finding.","fixText":"Configure a security policy or screen to each inbound zone to implement continuous monitoring. The following commands configure a security zone called “untrust” that can be used to apply security policy for inbound interfaces that are connected to untrusted networks. This example assumes that interfaces ge-0/0/1 and ge-0/0/2 are connected to untrusted and trusted network segments.\n\nApply policy or screen to a zone example:\n\nset security zones security-zone untrust interfaces ge-0/0/1.0\nset security zones security-zone trust interfaces ge-0/0/2.0\nset security zones security-zone untrust screen untrust-screen\nset security policies from-zone untrust to-zone trust policy default-deny match destination-address any\nset security policies from-zone untrust to-zone trust policy default-deny then deny","ccis":[]},{"vulnId":"V-66341","ruleId":"SV-80831r1_rule","severity":"high","ruleTitle":"The Juniper SRX Services Gateway Firewall must continuously monitor outbound communications traffic for unusual/unauthorized activities or conditions.","description":"If outbound communications traffic is not continuously monitored, hostile activity may not be detected and prevented. Output from application and traffic monitoring serves as input to continuous monitoring and incident response programs.\n\nThe Juniper SRX is a highly scalable system which can provide stateful or stateless continuous monitoring when placed in the architecture at either the perimeter or internal boundaries. Unusual/unauthorized activities or conditions may include unusual use of unusual protocols or ports and attempted communications from trusted zones to external addresses.","checkContent":"For each outbound zone, verify a firewall screen or security policy is configured.\n\n[edit]\nshow security zones\nshow security policies\n\nIf communications traffic for each outbound zone is not configured with a firewall screen or security policy, this is not a finding.","fixText":"Configure a security policy or screen to each outbound zone to implement continuous monitoring. The following commands configure a security zone called “untrust” that can be used to apply security policy for inbound interfaces that are connected to untrusted networks. This example assumes that interfaces ge-0/0/1 and ge-0/0/2 are connected to untrusted and trusted network segments.\n\nApply policy or screen to a zone example:\n\nset security zones security-zone untrust interfaces ge-0/0/1.0\nset security zones security-zone trust interfaces ge-0/0/2.0\nset security zones security-zone untrust screen untrust-screen\nset security policies from-zone trust to-zone untrust policy default-deny match destination-address any\nset security policies from-zone trust to-zone untrust policy default-deny then deny","ccis":[]},{"vulnId":"V-66343","ruleId":"SV-80833r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must generate an alert to, at a minimum, the ISSO and ISSM when unusual/unauthorized activities or conditions are detected during continuous monitoring of communications traffic as it traverses inbound or outbound across internal security boundaries.","description":"Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information.\n\nSince these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema.\n\nIn accordance with CCI-001242, the ALG which provides content inspection services is a real-time intrusion detection system. These systems must generate an alert when detection events from real-time monitoring occur as required by CCI-2262 and CCI-2261. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The ALG must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. Alerts must be sent immediately to designated individuals. Alerts may be sent via NMS, SIEM, Syslog configuration, SNMP trap or notice, or manned console message.\n\nUnusual/unauthorized activities or conditions may include large file transfers, long-time persistent connections, unusual protocols and ports in use, and attempted communications with suspected malicious external addresses.","checkContent":"For each zone, verify a log event, SNMP trap, or SNMP notification is generated and sent to be forwarded to, at a minimum, the ISSO and ISSM when unusual/unauthorized activities or conditions are detected during continuous monitoring of communications traffic as it traverses inbound or outbound across internal security boundaries. \n\n[edit]\nshow security zones\nshow security polices\n\nIf each inbound and outbound zone policy does not generate an alert that can be forwarded to, at a minimum, the ISSO and ISSM when unusual/unauthorized activities or conditions are detected during continuous monitoring of communications traffic as it traverses inbound or outbound across internal security boundaries, this is a finding.","fixText":"Configure the Juniper SRX to generate and send a notification or log message immediately that can be forwarded via an event monitoring system (e.g., via Syslog configuration, SNMP trap, manned console message, or other events monitoring system). The NSM, Syslog, or SNMP server must then be configured to send the message.\n\nThe following example configures the zone security policy to include the log and/or syslog action in all terms to log packets matching each firewall term to ensure the term results are recorded in the firewall log and Syslog. To get traffic logs from permitted sessions, add \"then log session-close\" to each policy. To get traffic logs from denied sessions, add \"then log session-init\" to the policy.\n\nSecurity policy and security screens:\nset security policies from-zone <zone_name> to-zone <zone_name> policy <policy_name> then log\n\nExample:\nset security policies from-zone untrust to-zone trust policy default-deny then log session-init","ccis":[]},{"vulnId":"V-66345","ruleId":"SV-80835r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must generate an alert that can be forwarded to, at a minimum, the ISSO and ISSM when threats identified by authoritative sources are detected.","description":"Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information.\n\nThe ALG generates an alert that notifies designated personnel of the Indicators of Compromise (IOCs) which require real-time alerts. These messages should include a severity level indicator or code as an indicator of the criticality of the incident. These indicators reflect the occurrence of a compromise or a potential compromise.\n\nSince these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema.\n\nAlerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The ALG must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. Alerts must be sent immediately to designated individuals. Alerts may be sent via NMS, SIEM, Syslog configuration, SNMP trap or notice, or manned console message.\n\nAuthoritative sources include USSTRATCOM warning and tactical directives/orders including Fragmentary Order (FRAGO), Communications Tasking Orders (CTOs), IA Vulnerability Notices, Network Defense Tasking Message (NDTM), DOD GIG Tasking Message (DGTM), and Operations Order (OPORD).","checkContent":"Obtain the list of threats identified by authoritative sources from the ISSM or ISSO. For each threat, ensure a security policy, screen, or filter that denies or mitigates the threat includes the log or syslog option. Verify a log event, SNMP trap, or SNMP notification is generated and sent to be forwarded to, at a minimum, the ISSO and ISSM when threats identified by authoritative sources are detected.\n\n[edit]\nshow security zones\nshow security polices\n\nIf an alert is not generated that can be forwarded to, at a minimum, the ISSO and ISSM when threats identified by authoritative sources are detected, this is a finding.","fixText":"Configure the Juniper SRX to generate and send a notification or log message that can be forwarded via an event monitoring system (e.g., via Syslog configuration, SNMP trap, manned console message, or other events monitoring system). The NSM, Syslog, or SNMP server must then be configured to send the message.\n\nThe following example configures the zone security policy to include the log and/or syslog action in all terms to log packets matching each firewall term to ensure the term results are recorded in the firewall log and Syslog. To get traffic logs from permitted sessions, add \"then log session-close\" to each policy. To get traffic logs from denied sessions, add \"then log session-init\" to the policy.\n\nSecurity policy and security screens:\nset security policies from-zone <zone_name> to-zone <zone_name> policy <policy_name> then log\n\nExample:\nset security policies from-zone untrust to-zone trust policy default-deny then log session-init","ccis":[]},{"vulnId":"V-66347","ruleId":"SV-80837r1_rule","severity":"medium","ruleTitle":"The Juniper SRX Services Gateway Firewall must generate an alert that can be forwarded to, at a minimum, the ISSO and ISSM when DoS incidents are detected.","description":"Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information.\n\nThe ALG generates an alert that notifies designated personnel of the Indicators of Compromise (IOCs) which require real-time alerts. These messages should include a severity level indicator or code as an indicator of the criticality of the incident. These indicators reflect the occurrence of a compromise or a potential compromise.\n\nSince these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema.\n\nCJCSM 6510.01B, \"Cyber Incident Handling Program\", lists nine Cyber Incident and Reportable Event Categories. DoD has determined that categories identified by CJCSM 6510.01B Major Indicators (category 1, 2, 4, or 7 detection events) will require an alert when an event is detected.\n\nAlerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The ALG must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel.","checkContent":"Verify a security policy with an associated screen that denies or mitigates the threat of DoS attacks includes the log or syslog option. Verify a log event, SNMP trap, or SNMP notification is generated and sent to be forwarded to, at a minimum, the ISSO and ISSM when threats identified by authoritative sources are detected.\n\n[edit]\nshow security zones\nshow security polices\n\nIf an alert is not generated that can be forwarded to, at a minimum, the ISSO and ISSM when DoS incidents are detected, this is a finding.","fixText":"Configure the Juniper SRX to generate for DoS attacks detected in CCI-002385. DoS attacks are detected using screens. The alert sends a notification or log message that can be forwarded via an event monitoring system (e.g., via Syslog configuration, SNMP trap, manned console message, or other events monitoring system). The NSM, Syslog, or SNMP server must then be configured to send the message.\n\nThe following example configures the zone security policy to include the log and/or syslog action in all terms to log packets matching each firewall term to ensure the term results are recorded in the firewall log and Syslog. To get traffic logs from permitted sessions, add \"then log session-close\" to each policy. To get traffic logs from denied sessions, add \"then log session-init\" to the policy.\n\nApply policy or screen to a zone example:\n\nset security zones security-zone trust interfaces ge-0/0/2.0\nset security zones security-zone untrust screen untrust-screen\nset security policies from-zone untrust to-zone trust policy default-deny then log session-init","ccis":[]}]}