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 Release 22.1R1.

• Application visibility enhancements—Starting in Junos Space Security Director Release 22.1R1, you can:

  • View the applications, users, and source IP address details on the same landing page.

  • Use the query builder in the chart view to create search criteria based on options such as user, application, source IP address, and destination IP address. Enter the filter criteria, and click Save to save the filter. Click the filter icon and select Show Saved Filters to view the filters that you created.

  • View the aggregate count of applications, content (content filter), source IP addresses, and destination IP addresses in the insight bar. The aggregate count changes based on the applied filter values. When you click a count link, you navigate to the All Events page with valid filters applied.

  • View the standard and nonstandard port, firewall rule, and status details in the application grid view columns. The status indicates whether the application is blocked or not.

• Manage threat prevention policy without Policy Enforcer—Starting in Junos Space Security Director Release 21.3R1 Hot Patch V1, you can manage threat prevention policies even if you haven’t configured Policy Enforcer. If you create and associate a threat prevention policy or profile with the firewall policy using the device CLI or J-Web without configuring Policy Enforcer, then Security Director doesn’t delete the threat prevention policy or profile when you preview or update the firewall policy. Therefore, you don't have to reconfigure the threat prevention policy or profile, and reassociate it with the firewall policies in the device.

  Note

  This feature is applicable only when you create a threat prevention policy and associate it to existing rules using the device CLI or J-Web.

• Legacy log collector and Security Director Insights log collector support for event viewer—Starting in Junos Space Security Director Release 21.3R1 Hot Patch V1, you can add both the legacy log collector node and the Security Director Insights VM on the Logging Nodes page in Security Director. We've added read-only log collector support to enable you to view existing data. This support provides a smooth transition from the legacy log collector to the Security Director Insights VM as the log collector.

  Note

  You cannot add same type of log collector nodes on the Logging Nodes page.

  The Legacy Node check box appears on all the Events & Logs pages after you add the legacy log collector node. Select the Legacy Node check box to view only the existing log collector data. New logs should point to Security Director Insights VM as the log collector. You see the Security Director Insights log collector data after you clear the Legacy Node check box.

For new features and enhancements in Policy Enforcer, see Policy Enforcer Release Notes.

Supported Managed Devices

Security Director Release 22.1R1 manages the following devices:

• SRX100

• SRX110

• SRX210

• SRX220

• SRX240

• SRX240H

• SRX300

• SRX320

• SRX320-POE

• SRX340

• SRX345

• SRX380

• SRX550

• SRX550M

• SRX650

• SRX1400

• SRX1500

• SRX3400

• SRX3600

• SRX4100

• SRX4200

• SRX5400

• SRX5600

• SRX5800

• SRX4600

• vSRX

• MX240

• MX480

• MX960

• MX2010

• MX2020

• LN1000-V

• LN2600

Supported Log Collection Systems

The following log collection systems are supported:

• Log Collector 22.1 (Security Director Insights VM)

• Juniper Networks® Secure Analytics (JSA) Series Virtual Appliance 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 22.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.3

• 19.4

• 20.1

• 20.2

• 20.3

• 20.4

• 21.1

• 21.2

• 21.3

• 21.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® Advanced Threat Prevention (ATP) Cloud Releases

Table 1 shows the supported Policy Enforcer and Juniper ATP Cloud releases.

Supported Browsers

Security Director Release 22.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 22.1R1

Installing and Upgrading Security Director Release 22.1R1

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

• 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 and Log Collector 22.1 (Security Director Insights VM), 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 18.4R1.8 version is not available, then Junos Space chooses the nearest lower version of DMI schema installed.

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 nearest lower version of DMI schema installed, 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 18.4R1.x versions are not available, then Junos Space chooses the nearest lower version of DMI schema installed.

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 the nearest lower version of DMI schema installed, 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 22.1R1.

• To discover the tenant devices in Security Director Release 21.2R1, we recommend the schema to be greater than or equal to 20.1R1. You must install the schema before Security Director discovers a tenant device.

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

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

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

• After upgrade, you cannot edit profiles with predefined proposals because the profiles in Security Director Release 20.1R1 and later support only custom proposals.

• In Security Director Release 19.4R1 and earlier, if you configure a VPN with static routing or a traffic selector with protected network as the zone or interface, you must perform the following tasks:

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

  In Security Director Release 20.1R1 and later, we support only address objects in protected networks for static routing and traffic selector.

• You must enable the Enable preview and import device change option, which is disabled by default:

  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 that you 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 through CSV, a new address object is created by appending a_1 to the address object name if the address object already exists in Security Director.

Known Issues

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

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

• A policy analysis report with more than 20000 rules cannot be generated. PR1708393

• SSL certificate error is displayed while analyzing threat prevention policy. PR1648734

• When you use Security Director Insights as a log collector, device selection on Monitor page does not work when a logical system or a tenant system device is selected. PR1621052

• Security Director displays device lookup failed error during preview. PR1617742

  Workaround:

  1. Move the device to RMA state. Navigate to Junos Space Network Management Platform. Select Devices > Device Management. Select a device, right-click and select Device Operations and then select Put in RMA State.
  2. Reactivate the device from RMA state. Navigate to Junos Space Network Management Platform. Select Devices > Device Management. Select a device, right-click and select Device Operations and then select Reactivate from RMA.

• Primary cluster displays the status as DOWN while both devices in the device cluster displays the status as UP. PR1616993

  Workaround:

  1. Move the device to RMA state. Navigate to Junos Space Network Management Platform. Select Devices > Device Management. Select a device, right-click and select Device Operations and then select Put in RMA State.
  2. Reactivate the device from RMA state. Navigate to Junos Space Network Management Platform. Select Devices > Device Management. Select a device, right-click and select Device Operations and then select Reactivate from RMA.

• Security Director does not clear uncommitted logical system or tenant system device management configuration in case of job failure, which causes subsequent updates to fail. You must clear the configuration from space node before proceeding with next update. PR1603146

  Workaround: Navigate to Junos Space Network Management Platform > Devices > Device Management > Modify Configuration > Deploy > Reject Changes.

• Security Director fails to import policies when custom dynamic-applications are configured at root-level and referred in logical system or tenant system policies. PR1602677

• 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. PR1484953

  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.

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

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

• 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 device, a job is created for the root device along with the logical system device, although changes are made only in the logical system 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 the 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 22.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 import address objects from a CSV file. PR1623265

• The user is unable to export shared service objects to a CSV file. PR1633147

• The NAT policy import with the compressed IPv6 format fails. PR1628535

• The firewall policy update fails. PR1646550

• The user is unable to push licenses from Security Director to an SRX Series device in the multinode setup. PR1636657

• There are auto policy sync job issues. PR1638876

• The Disable option in the NAT rule does not work as expected. PR1648031

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

Hot Patch Releases

This section describes the installation procedure, features, and resolved issues in Junos Space Security Director Release 22.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 22.1R1 Patch vX from the download site.

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

2. Copy the SD22.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 SD22.1R1-hotpatch-vX.tgz.

4. Extract the SD22.1R1-hotptach-vX.tgz file:

   tar -zxvf SD22.1R1-hotpatch-vX.tgz

5. Change the directory to SD22.1R1-hotpatch-vX.

   cd SD22.1R1-hotpatch-vX

6. Execute the patchme.sh script from the SD22.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/.SD22.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 22.1R1 hot patch includes the following enhancements:

• Polymorphic address support in source and destination address for NAT rules— Starting in Security Director Release 22.1R1 hot patch V1, while creating NAT rules for group policies you can select polymorphic addresses as source or destination address. The rule points to default address if the device IP address does not match any of the context values in the polymorphic address. If there is a match, the address corresponding to the context value is considered in the source or destination address of the rule.

  Note

  Polymorphic address is not supported for static NAT destination address.

• Support for disabling service offload in Security Director— Starting in Security Director Release 22.1R1 hot patch V1, we’ve provided an option to disable service offload on the Edit Profile page of a rule for standard and unified firewall policies. This feature is supported both on logical systems and tenant systems. You can select from the following options:

  • None: Select to delete the configured service on the device.

  • Enable: Select to enable service offload. When services-offload is enabled, only the first packets of a session go to the Services Processing Unit (SPU), rest of packets in services-offload mode does not go to SPU, therefore some security features such as stateful screen are not supported. Only TCP and UDP packets can be services offloaded.

  • Disable: Select to disable service offload.

• Support to terminate CLI/J-Web edit mode user session— tarting in Security Director Release 22.1R1 hot patch V1, when you retry the update job on failed devices caused due to device lock failures, you can log the user (edit mode user) out who locked the configuration database, from the device CLI. Navigate to Monitor > Job Management. Select the job, and then from the More list select Retry on Failed Devices. On the Retry Update Failed Devices page, enable Evict CLI/J-Web edit mode users option.

Resolved Issues in Hot Patches

Table 6 lists the resolved issues in the Security Director Release 22.1R1 hot patch.