Release Notes for Junos Space Security Director

Supported Managed Devices

Security Director Release 18.1R2 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 or later

• QRadar as Log Collector on QRadar Release 7.2.8 or later

Supported Junos OS Releases

• Security Director Release 18.1R2 supports the following Junos OS branches:

  • 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

• 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 on devices running Junos OS Release 11.4 or later.

Supported Policy Enforcer and Sky ATP Releases

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

Supported Browsers

Security Director Release 18.1R2 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 18.1R2

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

Installing and Upgrading Security Director Release 18.1R2

Junos Space Security Director Release 18.1R2 is supported only on Junos Space Network Management Platform Release 18.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

In Junos Space Security Director Release 18.1R2, a single image installs Security Director, Log Director, and the Security Director Logging and Reporting modules. All three applications are installed when you install the Security Director Release 18.1R2 image.

For more information about installing and upgrading Security Director Release 18.1R2, 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 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 is used to login 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 Releases

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

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 your publish or update job performance.

• To enhance the performance further, increase the update subjobs thread number 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.

Table 2 shows the supported firewall rules per policy processed concurrently.

New and Changed Features

There are no new features or enhancements to existing features in Junos Space Security Director Release 18.1R2.

Known Behavior

This section contains the known behavior and limitations in Junos Space Security Director Release 18.1R2.

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

  To disable OpenNMS:

  1. Select Network Management Platform > Administration > Applications.

     The Applications page appears.

  2. Right-click Network Management Platform and select Manage Services.

     The Manage Services page appears.

  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 the Junos Space Network Management Platform and Security Director are already installed on a JA2500 or virtual machine.

• The Enable preview and import device change option is disabled by default. To enable this option, select Network Management Platform > Administration > Applications. Right-click Security Director and select Modify Application Settings. Under 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 the Security Director user interfaces are launched within 20 minutes, and the devices reconnects to the 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 is not sufficient.

• If 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 18.1R1 and Policy Enforcer Release 18.1R1, log in to the Policy Enforcer server by using SSH and run the following command:

  cd /var/lib/nsxmicro

  ./migrate_devices.sh

  This script migrates the existing Release 17.1R1 vSRX VMs in NSX Manager into the currently compatible Release 18.1R1.

• If the NSX server SSL certificate has expired or changed, communication between Security Director and NSX Manager does not work, thereby impacting the functionality of the NSX Manager, such as sync NSX inventory, security group update, and so on.

  You must refresh the NSX SSL certificate by performing the following steps:

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

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

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

Known Issues

This section lists the known issues in Security Director Release 18.1R2.

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

• Grid column filter does not work for Internet Explorer 11. PR1161079

• Cluster devices are discovered in different domains. PR1162407

• After you upgrade Security Director, the custom column is not visible in the firewall rule grid. PR1256789

• You must manually synchronize NSX with the vCenter server to view the latest restart or power off status. PR1285312

• The global search for a dynamic address group does not work as expected. PR1285893

• Any Service Groups notification sent from NSX to Security Director triggers an RPC update job for each vSRX device, instead of a single job with all the related vSRX devices. PR1288407

• If there is a change in the login password of NSX Manager, vCenter, or Junos Space, then use the Edit NSX Manager page in Security Director to modify the login password information. Otherwise, synchronization of NSX Manager and dynamic address groups update fails.PR1291965

• If NSX is integrated with Security Director, several login and logout entries are observed in the audit log. PR1291972

• If you delete an NSX service, the associated firewall or IPS policies created by Security Director are also deleted. If you need a copy of the NSX-created group firewall or IPS policies, you must clone them manually before deleting the NSX service. PR1291974

• As Security Director is not aware of the IDP licenses installed on the NSX Manager with vSRX VM, you must perform the full probe during the installation of the IDP signature. PR1291977

• If the Policy Enforcer VM is down or the NSX services are down when there is a change in the service group membership in NSX, you cannot trigger an event to vSRX to poll for the latest service group members from the feed server. PR1295882

  Workaround: Perform one of the following actions to trigger events to vSRX instances:

  • Modify the description of the service group when the services or Policy Enforcer VM is down.

  • Log in to the vSRX device by using the SSH command and execute the following command:

    request security dynamic-address update address-name Dynamic-Address-Name

• Application firewall OCR fails when the OVER WRITE option is selected.

  Workaround: You can choose the RE_NAME option and proceed with the rollback or import. PR1324941

• When you try to add device-specific values for child domains in variable addresses or zones, the changes are not saved in the user interface. PR1330389

• NAT pool is not shown in the OCR screen if the used address has conflicts. PR1330392

• While upgrading log collector from Security Director Release 17.2R2 to Security Director Release 18.1R1 using a log collector upgrade script, if log collector reboots during the upgrade, then the Security Director node addition procedure fails. PR1350341

• Importing variables from CSV is not working as expected. PR1350890

• Dashboard widget preferences are not retained after upgrading log collector from Security Director Release 17.1R1 to Security Director Release 18.1R1. PR1350292

• In the Job Management page, Date and Time filter for columns is not working as expected. PR1350906

• When an SRX Series device is managed directly by Juniper Sky ATP for Advanced Threat Prevention, and is used in Security Director without integrating Policy Enforcer, then Security Director should not manage the threat prevention configuration. For example, security-intelligence policy and advanced-anti-malware policy. However, currently Security Director manages threat prevention configuration and tries to modify the configuration incorrectly. PR1403904

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

Resolved Issues

This section lists the issues fixed in Security Director Release 18.1R2.

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

• While upgrading or downgrading IPS signature package from 3054 or 3057 to 3058 or latest version, parsing job is failing in Security Director. PR1356787