Release Notes for Junos Space Security Director

New and Changed Features

This section describes the new features and enhancements to existing features in Junos Space Security Director and Policy Enforcer Release 21.1R1.

• Secure Web Proxy setting for firewall policy— Starting in Junos Space Security Director Release 21.1R1, you can use secure Web proxy to enable traffic for the selected dynamic applications to bypass the external proxy server and sent directly to a webserver.

  You must define a Web proxy profile by specifying external proxy server details and dynamic application. You can associate this secure Web proxy profile with standard firewall policy rule for advanced security. The traffic matching the firewall rule is sent to the configured external proxy server on the rule, unless the selected dynamic application matches.

• Application visibility and threat map support for unified firewall policies— Starting in Junos Space Security Director Release 21.1, when unified policy rules permit the traffic, selecting block action creates block rules in the appropriate unified policy.

• LSYS support for log collector— Starting in Junos Space Security Director Release 21.1, we’ve provided the support for source type for security logging configuration.

• Inline address support for IPS policies— Starting in Junos Space Security Director Release 21.1, you can import a valid source or destination inline address for an IPS Policy from an SRX Series device to Security Director. In the case of an inline address, the address object can be assigned in the device without creating the address object in the address-book. After import of inline address, you can edit the inline address in shared object. You can edit the name and IP address listed on the Addresses page. This is applicable for devices with Junos OS release 18.1 or later.

• Support for NSX-T North-South traffic— VMware NSX-T is the latest generation of VMware’s network virtualization product series. NSX-T is the successor to NSX-V. VMware NSX-T provides framework to integrate the advanced security services as North-South at Edge Gateway. vSRX runs as a service virtual machine and provides advanced services such as L4 to L7 services. To deploy the advanced security features of the vSRX Virtual Services Gateway in the VMware NSX-T environment, the Junos Space Security Director, vSRX, and NSX-T Manager operate together as a solution to fully automate the provisioning and deployment of the vSRX to protect applications and data from advanced cyberattacks.

Supported Managed Devices

Security Director Release 21.1R1 manages the following devices:

• SRX100

• SRX110

• SRX210

• SRX220

• SRX240

• SRX240H

• SRX300

• SRX320

• SRX320-POE

• SRX340

• SRX345

• SRX550

• SRX550M

• SRX650

• SRX1400

• SRX1500

• SRX3400

• SRX3600

• SRX4100

• SRX4200

• SRX5400

• SRX5600

• SRX5800

• SRX4600

• vSRX

• MX240

• MX480

• MX960

• MX2010

• MX2020

• LN1000-V

• LN2600

• Security Director Log Collector

• Juniper Secure Analytics (JSA) as Log Collector on JSA Release 2014.8.R4 and later

• QRadar as Log Collector on QRadar Release 7.2.8 and later

Supported Junos OS Releases

Security Director Release 21.1R1 supports the following Junos OS releases:

• 10.4

• 11.4

• 12.1

• 12.1X44

• 12.1X45

• 12.1X46

• 12.1X47

• 12.3X48

• 15.1X49

• vSRX 15.1X49

• 16.1R3-S1.3

• 15.1X49-D110

• 17.3

• 17.4

• 18.1

• 18.1R2.6

• 18.2

• 18.2R3.4

• 18.3

• 18.4

• 18.4R3.3

• 19.1

• 19.2

• 19.2R3.5

• 19.3

• 19.4

• 19.4R3.11

• 20.1R1.11

• 20.2R2.11

• 20.3R1.8

• 20.4

SRX Series devices require Junos OS Release 12.1 or later to synchronize the Security Director description field with the device.

The logical systems feature is supported only on devices running Junos OS Release 11.4 or later.

Supported Policy Enforcer and Juniper Sky ATP Releases

Table 1 shows the supported Policy Enforcer and Juniper Sky Advanced Threat Prevention (Juniper Sky ATP) releases.

Supported Browsers

Security Director Release 21.1R1 is best viewed on the following browsers:

• Mozilla Firefox

• Google Chrome

• Microsoft Internet Explorer 11

Installation and Upgrade Instructions

• Installing and Upgrading Security Director Release 21.1R1

• Adding Security Director Log Collector Node in Security Director Release 17.2R1 and Later

Installing and Upgrading Security Director Release 21.1R1

Junos Space Security Director Release 21.1R1 is supported only on Junos Space Network Management Platform Release 21.1R1 that can run on the following devices:

• JA2500

• Junos Space virtual appliance

• Kernel-based virtual machine (KVM) server installed on CentOS Release 7.2.1511

For more information about installing and upgrading Security Director Release 21.1R1, see Security Director Installation and Upgrade Guide.

Adding Security Director Log Collector Node in Security Director Release 17.2R1 and Later

For distributed Log Collector deployment, you must add only a Log Receiver node. You can add the node directly to Security Director using admin credentials, as in the case of the JSA node. For security reasons, non-root credentials are used to add a node.

Figure 1: Change Password

For JSA, provide the admin credentials that are used to log in to the JSA console.

For information about how to add the Log Collector node to Security Director, see Security Director Installation and Upgrade Guide.

Loading Junos OS Schema for SRX Series Devices

You must download and install correct Junos OS schema to manage SRX Series devices. To download the correct schema, from the Network Management Platform list, select Administration > DMI Schema, and click Update Schema. See Updating a DMI Schema.

DMI Schema Compatibility for Junos OS Service Releases

The following tables explain how the Junos Space Network Management Platform chooses Device Management Interface (DMI) schemas for devices running Junos OS Service Releases.

If a Junos OS Service Release is installed on your device with a major release version of a DMI schema installed on Junos Space Network Management Platform, then Junos Space chooses the latest corresponding major release of DMI schemas, as shown in Table 2.

If a Junos OS Service Release is installed on your device without a matching DMI schema version in Junos Space Network Management Platform, then Junos Space chooses the default DMI schema version, as shown in Table 3.

If more than one version of the DMI schemas are installed in Junos Space Platform for a single Junos OS Service Release version, Junos Space chooses the latest version of the DMI schema, as shown in Table 4.

If a Junos OS Service Release is installed on your device without a corresponding DMI schema version in Junos Space Network Management Platform, then Junos Space chooses a default DMI schema version, as shown in Table 5.

For information about Junos OS compatibility, see Junos OS Releases Supported in Junos Space Network Management Platform.

Management Scalability

• By default, monitor polling is set to 15 minutes and resource usage polling is set to 10 minutes. This polling time changes to 30 minutes for a large-scale data center setup such as one for 200 SRX Series devices managed in Security Director.

  Note

  You can manually configure the monitor polling on the Administration>Monitor Settings page.

• Security Director supports up to 15,000 SRX Series devices with a six-node Junos Space fabric. In a setup with 15,000 SRX Series devices, all settings for monitor polling must be set to 60 minutes. If monitoring is not required, disable it to improve the performance of your publish and update jobs.

• To enhance the performance further, increase the number of update subjobs thread in the database. To increase the update subjobs thread in the database, run the following command:

  Note

  For mysql username and password, contact Juniper Support.

Known Behavior

This section contains the known behavior and limitations in Junos Space Security Director Release 21.1R1.

• If VPN is configured in Security Director Release earlier to 19.4 and upgraded to Security Director Release 20.1R1 and later, IKE ID is displayed blank if IKE ID is defined as Default.

• Security Director does not generate delete CLIs if VPN already exist in the device and same device is used for creating another VPN from Security Director.

• In Junos Space Security Director Release 20.1R1 and later, you must configure tunnel IP address for dynamic routing protocols. In Junos Space Security Director Release 19.4R1 and earlier, if you have configured VPN as unnumbered with dynamic routing protocol, you will be prompted to provide tunnel IP address while editing the VPN after upgrading to Junos Space Security Director Release 20.1R1 and later.

• After upgrade you will not be allowed to edit profiles with predefined proposals because profiles in Junos Space Security Director Release 20.1R1 and later supports only custom proposals.

• In Junos Space Security Director Release 19.4R1 and earlier, if you have configured VPN with static routing or traffic selector with protected network as zone or interface, perform the following:

  1. Before you upgrade, update the configuration to device, and delete the VPN Policy from Security Director.
  2. After you upgrade to Junos Space Security Director Release 20.1R1 and later, you must import the VPN configuration.
  Note

  In Junos Space Security Director Release 20.1R1 and later, only address objects is supported in protected networks for static routing and traffic selector.

• You must disable OpenNMS before installing the integrated Log Collector.

  To disable OpenNMS:

  1. Select Network Management Platform > Administration > Applications.
  2. Right-click Network Management Platform, and select Manage Services.
  3. Select Network Monitoring, and click the Stop Service icon.

     The network monitoring service is stopped, and the status of OpenNMS is changed to Disabled.

  Note

  You must ensure that Junos Space Network Management Platform and Security Director are already installed on a JA2500 appliance or Junos Space virtual appliance.

• The Enable preview and import device change option is disabled by default.

  To enable this option:

  1. Select Network Management Platform > Administration > Applications.
  2. Right-click Security Director, and select Modify Application Settings.
  3. From Update Device, select the Enable preview and import device change option.

• If you restart the JBoss application servers manually in a six-node setup one-by-one, the Junos Space Network Management Platform and Security Director user interfaces are launched within 20 minutes, and the devices reconnect to Junos Space Network Management Platform. You can then edit and publish the policies. When the connection status and the configuration status of all devices are UP and IN SYNC, respectively, click Update Changes to update all security-specific configurations or pending services on SRX Series devices.

• To generate reports in the local time zone of the server, you must modify /etc/sysconfig/clock to configure the time zone. Changing the time zone on the server by modifying /etc/localtime does not generate reports in the local time zone.

• If the vSRX VMs in NSX Manager are managed in Security Director Release 17.1R1 and Policy Enforcer Release 17.1R1, then after upgrading to Security Director Release 20.3R1 and Policy Enforcer Release 20.3R1, we recommend you to migrate the existing vSRX VMs in NSX Manager from Policy Enforcer Release 17.1R1 to Release 20.3R1.

  To migrate the existing vSRX VMs:

  1. Log in to the Policy Enforcer server by using SSH.
  2. Run the following commands:

     cd /var/lib/nsxmicro

     ./migrate_devices.sh

• If the NSX Server SSL certificate has expired or changed, communication between Security Director and NSX Manager fails, thereby impacting the functionality of NSX Manager, such as sync NSX inventory and security group update.

  To refresh the NSX SSL certificate:

  1. Log in to Policy Enforcer by using SSH.
  2. Run the following command:

     nsxmicro_refresh_ssl --server <<NSX IP ADDRESS>>--port 443

     This script fetches the latest NSX SSL certificate and stores it for communication between Security Director and NSX Manager.

• In a setup where other applications are installed in Junos Space Network Management Platform along with Security Director, the JBoss PermSize must be increased from 512m to 1024m in the /usr/local/jboss/domain/configuration/host.xml.slave file. Under <jvm name="platform">, change the following values in the <jvm-options> tag:

  <option value="-XX:PermSize=1024m"/>

  <option value="-XX:MaxPermSize=1024m"/>

• When you import addresses via CSV, a new address object is created by appending a_1 to the address object name if the address object is already present in Security Director.

Known Issues

This section lists the known issues in Junos Space Security Director Release 21.1R1.

For the most complete and latest information about known Security Director defects, use the Juniper Networks online Junos Problem Report Search application.

• Integrated Log Collector node failed to add in Security Director. PR1587916

  Workaround: Perform the following after installing integrated Log Collector script: Integrated-Log-Collector-20.1R1v.130

  1. Log in to Junos Space console.
  2. Update Dir permission.

     chmod -R 777 /var/run/

  3. Restart ElasticSearch service:

     systemctl restart elasticsearch

     systemctl status elasticsearch

  4. Update eth0 IP in /opt/jIngest/config/config.properties:

     bindIp=<Junos Space eth0 IP>

  5. Restart the JIngest service:

     service jingest restart

     service jingest status

  6. Run the following commands to add Log Collector in Security Director:
     1. ip=$(ifconfig eth0 | grep "inet" | awk '{print $2}')
     2. curl -X POST -k -H 'Accept: application/json' -H 'Content-Type: application/json' -i 'http://localhost:8080/api/juniper/ecm/log-collector-nodes/' --data '{"log-collector-credential":{"user-name":"admin","ip-address":"'"$ip"'","password":"juniper_123","name":"Integrated","node-type":"Integrated"}}'
  7. Log in to Security Director and check the Log Collector details.

• An icon showing out-of-band changes is seen for firewall and IPS policies, although the corresponding policy changes are not made on the device.

  Workaround: Clear the out-of-band icon on the policies when changes are not made on the device. Navigate to the corresponding policy and right-click the policy. Select View Device Policy Changes and reject all changes, and then click OK. PR1484953

• Deployment of cipher list CLI works only when you perform Save or Save and Deploy.

  Workaround: You must save or deploy the selected Cipher list before you view the preview changes. PR1485949

• An object conflict occurs when you import Web filter profiles with duplicate names, although the values are the same. PR1420341

  Workaround: Select either Overwrite with Imported Value or Keep Existing Object to avoid duplicate objects.

• Junos Space Security Director does not support routing instances and proxy profiles in an antivirus pattern update for the unified threat management (UTM) default configuration. PR1462331

• When you import out-of-band changes to a logical system (LSYS) device, a job is created for the root device along with the LSYS device, although changes are made only in the LSYS device. PR1448667

• Import fails when a device is imported only with UTM custom objects without a UTM policy. PR1447779

  Workaround: Delete the UTM custom objects if they are not used in a policy or assign a UTM policy.

• Update fails for unified policies when an SSL proxy profile that is set as global in a device is not used in any policy for that device. PR1407389

• A policy analysis report with a large number of rules cannot be generated. PR1418125

• When a column filter is used, the Deselect all and Clear all options do not clear selected items occasionally. PR1424112

• The Show Unused option is not available for URL categories. PR1431345

• Restart of a single JBoss node does not recover system even if the issue is present on a single node. PR1478804

  Workaround: Restart all JBoss nodes.

For known issues in Policy Enforcer, see Policy Enforcer Release Notes.

Resolved Issues

This section lists the issues fixed in Junos Space Security Director and Policy Enforcer Release 21.1R1:

For the most complete and latest information about resolved issues, use the Juniper Networks online Junos Problem Report Search application.

• The user is unable to export events to CSV for logs from Log collector. PR1552582

• In the Security Director UI, Create Exempt rule option does not work in Monitor > Events & logs > IPS > IPS events. PR1555362

• SRX imports get failed after adding a new dynamic address that is being called in a global policy. PR1555848

• Security Director pushes incorrect configuration for the external IP-Addresses that are configured in VPN. PR1562130

• Publish/Update of Threat Prevention Policy fails when Policy Enforcement Group (PEG) is changed from Location type to IP Address/Subnet type. PR1572517

• The custom feeds downloaded from remote server through HTTPS does not work. PR1576467

• Policy Enforcer does not allow the creation of custom feeds with a URL or domain. You can only create IP-based custom feeds. PR1522841

• The country codes available in the Security Director GeoIP feed does not match with SRX CLI GeoIP. PR1582766

• An issue with GeoIP country code for Serbia / Montenegro. PR1569964

• In Security Director UI, finish button for Add Sky ATP Realm/Modify Sky ATP Realm does not work in Configure > Threat Prevention > Feed Sources from Firefox 83.0 onward. PR1564456

Hot Patch Releases

This section describes the installation procedure, features, and resolved issues in Junos Space Security Director Release 21.1R1 hot patch.

During hot patch installation, the script performs the following operations:

• Blocks the device communication.

• Stops JBoss, JBoss Domain Controller (JBoss-dc), and jmp-watchdog services.

• Backs up existing configuration files and EAR files.

• Updates the Red Hat Package Manager (RPM) files.

• Restarts the watchdog process, which restarts JBoss and JBoss-dc services.

• Unblocks device communication after restarting the watchdog process for device load balancing.

Installation Instructions

1. Download the Security Director 21.1R1 Patch vX from the download site.

   Here, X is the hot patch version. For example, v1, v2, and so on.

2. Copy the SD-21.1R1-hotpatch-vX.tgz file to the /home/admin location of the VIP node.
3. Verify the checksum of the hot patch for data integrity:

   md5sum SD-21.1R1-hotpatch-vX.tgz.

4. Extract the SD-21.1R1-hotptach-vX.tgz file:

   tar -zxvf SD-21.1R1-hotpatch-vX.tgz

5. Change the directory to SD-21.1R1-hotpatch-vX.

   cd SD-21.1R1-hotpatch-vX

6. Execute the patchme.sh script from the SD-21.1R1-hotpatch-vX folder:

   sh patchme.sh

   The script detects whether the deployment is a standalone deployment or a cluster deployment and installs the patch accordingly.

A marker file, /etc/.SD-21.1R1-hotpatch-vX, is created with the list of Red-hat Package Manager (RPM) details in the hot patch.

New and Enhanced Features in the Hot Patch

Junos Space Security Director Release 21.1R1 hot patch includes the following enhancement:

• Log Director configuration changes—Starting in Junos Space Security Director Release 21.1R1 V1 hot patch, when you add Security Director Insights as a log collector, you must enable the Enable SDI Log Collector Query Format option in Junos Space Network Management Platform.

  To enable the option:

  1. Log in to Junos Space Network Management Platform.
  2. Select Administration > Applications.
  3. Right-click Log Director and select Modify Application Settings.
  4. Enable the Enable SDI Log Collector Query Format check box.

Resolved Issues in the Hot Patches

Table 6 lists the resolved issues in Security Director Release 21.1R1 hot patches.