Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

December, 2018 Release

New and Changed Features: December, 2018

Whitelist Command and Control Servers

You can now whitelist C&C servers by entering an IP address or hostname in the Configure > Whitelist > C&C Server page. This information is then sent to the SRX Series device to be excluded from any security intelligence blacklists or C&C feeds (both Juniper’s global threat feed and third party feeds). You can also whitelist C&C servers directly from the C&C Monitoring page details view.

[See Creating Allowlists and Blocklists.]

Resolved Issues

September 2020

There are no resolved issues in this release for Juniper ATP Cloud.

June 2020

  • SATP-473 – Since Ransomware Tracker is deprecated, ransomware tracker IP feeds are not supported on Juniper Sky ATP. The option to enable these feeds has been removed from Juniper Sky ATP UI. If you had enabled the Ransomware Tracker feed earlier, you might stop receiving this feed.

  • SATP-117 – Unable to search devices on Realm Management page.

September 2019

  • PR 1457400 and PR 1456736 – Host in infected hosts feed was being auto-resolved and removed from feed with no manual intervention.

July 2019

  • PR1352313 – The Juniper Sky ATP Web Portal does not display the OS version and device name for vSRX

December 2018

  • PR1402190 – IPv6 addresses were not being correctly added to blacklist feeds.

  • PR1351544 – Tool tips for third party feeds were not appearing when clicking on the “?” in the Sky ATP Web UI.

  • PR1356443 – The modify profile screen contained errors in the file categories description.

  • PR1380649 – The command and control server details page duplicated the threat summary, total hits, protocols & ports fields when clicking on the time range links.

November 2018

  • PR1383886 – In some instances, malicious SMTP attachments were not detected correctly.

  • PR1367466 – With X-Forwarded-For (XFF) enabled on the proxy server, Sky ATP populated the portal with the proxy IP address instead of the host IP address.