Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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 21.3R1.

  • Onboard devices to Juniper® Security Director Cloud—Starting in Security Director Release 21.3R1, you can add Security Director managed devices to Juniper Security Director Cloud. You can add only root devices or the primary root device in a cluster device. Juniper Security Director Cloud automatically discovers the secondary device in a cluster. You cannot add MX Series, cSRX, logical system, and tenant system devices to Juniper Security Director Cloud.

  • Root certificates—Starting in Security Director Release 21.3R1, you can configure multiple certificates in the SSL proxy profile.

  • Action for out-of-band policy changes—Starting in Security Director Release 21.3R1, during automatic synchronization of out-of-band firewall, intrusion prevention system (IPS), and NAT policy changes from a device to Security Director, you can choose from rename object, keep existing value, or overwrite with imported value. By default, Rename Object is selected.

  • RT_FLOW_SESSION logs support—Security Director does not use AppTrack logs, instead it retrieves the data from RT_FLOW_SESSION logs. For application visibility feature to function and to view application data in Security Director, session-close log should be enabled at rule level.

    For example: set security policies from-zone untrustZone to-zone trustZone policy policy13 then log session-close

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

Supported Managed Devices

Security Director Release 21.3R1 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 21.3 (Security Director Insights VM)

  • Integrated Log Collector 20.1R1

  • 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

Note

Starting in Security Director Release 20.2R1 onward, we’re not supporting standalone Log Collector.

Supported Junos OS Releases

Security Director Release 21.3R1 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

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.

Note

To manage an SRX Series device by using Security Director, we recommend that you install the matching Junos OS schema on the Junos Space Network Management Platform. If the Junos OS schemas do not match, a warning message is displayed during the publish preview workflow.

Supported Policy Enforcer and Juniper® Advanced Threat Prevention (ATP) Cloud Releases

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

Table 1: Supported Policy Enforcer and Juniper ATP Cloud Releases

Security Director Release

Compatible Policy Enforcer Release

Junos OS Release (Juniper ATP Cloud supported devices)

16.1R1

16.1R1

Junos OS Release 15.1X49-D60 and later

16.2R1

16.2R1

Junos OS Release 15.1X49-D80 and later

17.1R1

17.1R1

Junos OS Release 15.1X49-D80 and later

17.1R2

17.1R2

Junos OS Release 15.1X49-D80 and later

17.2R1

17.2R1

Junos OS Release 15.1X49-D110 and later

17.2R2

17.2R2

Junos OS Release 15.1X49-D110 and later

18.1R1

18.1R1

Junos OS Release 15.1X49-D110 and later

18.1R2

18.1R2

Junos OS Release 15.1X49-D110 and later

18.2R1

18.2R1

Junos OS Release 15.1X49-D110 and later

18.3R1

18.3R1

Junos OS Release 15.1X49-D110 and later

18.4R1

18.4R1

Junos OS Release 15.1X49-D110 and later

19.1R1

19.1R1

Junos OS Release 15.1X49-D110 and later

19.2R1

19.2R1

Junos OS Release 15.1X49-D120 and later

19.3R1

19.3R1

Junos OS Release 15.1X49-D120 and later

19.4R1

19.4R1

Junos OS Release 15.1X49-D120 and later

20.1R1

20.1R1

Junos OS Release 15.1X49-D120 and later

20.3R1

20.3R1

Junos OS Release 15.1X49-D120 or Junos OS Release 17.3R1 and later

21.1R1

21.1R1

Junos OS Release 15.1X49-D120 or Junos OS Release 17.3R1 and later

21.2R1

21.2R1

Junos OS Release 15.1X49-D120 or Junos OS Release 17.3R1 and later

21.3R1

21.3R1

Junos OS Release 15.1X49-D120 or Junos OS Release 17.3R1 and later

Note

For Policy Enforcer details, see Policy Enforcer Release Notes.

Supported Browsers

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

  • Mozilla Firefox

  • Google Chrome

  • Microsoft Internet Explorer 11

Installation and Upgrade Instructions

This section describes how you can install and upgrade Junos Space Security Director and Log Collector.

Installing and Upgrading Security Director Release 21.3R1

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

  • Juniper Networks® JA2500 Junos Space® Appliance

  • Junos Space virtual appliance

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

Note

For more information about installing and upgrading Security Director and Log Collector 21.3 (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.

Table 2: Device with Service Release and Junos Space with FRS Release

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1-S1

18.4R1.8

18.3R1.1

18.2R1.1

18.2R1.1

18.4R1.8

If 18.4R1.8 version is not available, then Junos Space chooses the nearest lower version of DMI schema installed.

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1-S1

18.3R1.1

18.2R1.1

18.2R1.1

18.3R1.1

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.

Table 3: Device with Service Release and Junos Space without matching DMI Schema

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1-S1

18.5R1.1

18.3R1.1

18.2R1.1

18.2R1.1

18.3R1.1

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.

Table 4: Device with Service Release and Junos Space with more than one DMI Schemas

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1-S1

18.4R1.8

18.4R1.7

18.4R1.6

18.3R1.1

18.3R1.1

18.4R1.8

If 18.4R1.x versions are not available, then Junos Space chooses the nearest lower version of DMI schema installed.

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1-S1

18.3R1.1

18.2R1.1

18.2R1.1

18.3R1.1

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.

Table 5: Device with Service Release and Junos Space without more DMI Schemas

Junos OS Version on Device

Junos Space DMI Schemas Installed

Junos Space Default Version

Junos Space Version Chosen for Platform

18.4R1.1

18.5R1.1

18.3R1.1

18.2R1.1

18.2R1.1

18.3R1.1

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

Management Scalability

The following management scalability features are supported in Junos Space Security Director:

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

Note

If you use a database dedicated setup (SSD hard disk VMs), the performance of publish and update is better compared to the performance in a normal two-node Junos Space fabric setup.

Known Behavior

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

  • 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 21.3R1.

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

  • In a multi node setup, user is unable to push license from Security Director to an SRX Series device. PR1636657

  • 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

  • Integrated Log Collector node is not added in Security Director. PR1587916

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

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

      chmod -R 777 /var/run/

    3. Restart the ElasticSearch service:

      systemctl restart elasticsearch

      systemctl status elasticsearch

    4. Update the eth0 IP address 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 verify 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. 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 21.3R1:

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

  • There are issues with top-talker and top source IPs by bandwidth reports. PR1587200

  • Proxy ARP delete commands are generated though the proxy ARP setting is enabled. PR1598341

  • There are issues with policy update after you rename objects. PR1601704

  • Policy update to cluster devices fails without any error message. PR1602370

  • When the application name is Any, there is a dynamic application name mismatch between SRX Series device and Security Director. PR1603010

  • There is an issue with the SRX Series device packet capture timestamp. PR1603617

  • Network Management Platform causes MySQL packet.db tables to increase over 17 GB and create issues on node replication. PR1607509

  • There is an error while calculating rules to publish. PR1608285

  • The SRX Series device import fails. PR1609767

  • VPN monitoring does not work as expected. PR1611051

  • Multiple auto policy sync jobs are generated for a single commit. PR1613144

  • Deletion of all devices from the top check box in Security Director does not work. PR1618523

  • Security Director does not import addresses from a CSV file. PR1623570

  • Security Director sets antispam and web-filtering CLIs after import. PR1619077

  • Address object import from a CSV file fails. PR1623265

  • Security Director does not fetch user details from Juniper® Identity Management Service (JIMS). PR1621785

  • If you are using a device running Junos OS Release 21.1R1 and later, due to apptrack changes, you are unable to view application data in Security Director. PR1502587