Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Issues

This section lists the known issues in hardware and software in Policy Enforcer version 17.1R1.

  • Enrolling devices to Sky ATP through Policy Enforcer takes an average of four minutes to complete. Enrolling devices are done serially, not in parallel. [1222713]
  • The first time you open the Monitoring pages, you will receive an Error occurred while requesting the data message. This also happens the first time you open the Top Compromised Host dashboard widget. As a workaround, click your browser refresh button to refresh the page and display the information. [1239956]
  • The top compromised hosts widget in the dashboard does not list all the realms. As a workaround, drag and drop another top compromised host widget to the dashboard to display all realms. [1262410]
  • Connectors assigned to a site cannot be deleted. You must first unassign it from the site and then go to the Connectors window (Administration > Policy Enforcer > Connectors) to delete it.
  • If a vSRX is properly enrolled in Sky ATP and you create a site within Policy Enforcer with that vSRX and a connector, the secure fabric page for that site shows the vSRX enroll status as failed. [1284258]
  • An infected host can be blocked using a custom feed, however there is no UI to indicate that the host is blocked. To unblock the infected host, remove it’s IP address from the custom feed. [1292394]
  • If a site is created with a CPPM connector, the site can be created only based on a location-based policy enforcement group. It cannot be created with an IP-based policy enforcement group. [1288247]
  • You can configure only one Radius server as a controller for a connector. [1287908]
  • Moving the C&C Threat Score slider in the Threat Prevention Policy window (Configure > Threat Prevention > Policy), for example from 10 to 8, may cause the Actions dropdown menu to appear empty. Click the arrow in the Actions menu to see the options. [1296098]
  • Removing a site from a realm may remove the SRX Series device from the Secure Fabric site. As a workaround, re-add the device to the site. [1295460]
  • When an SRX Series device is used as a Layer 3 gateway for a given host or subnet and a switch is part of the Secure Fabric, the block and unblock actions may fail when the PEG is created with the location group type. As a workaround, create the PEG with the IP/Subnet group type and associate that PEG to the threat prevention policy. [1296535]
  • Even when a device is unavailable (for example, the device is down), the removal of the device or site from the realm may state it as a successful dis-enroll.
  • Create a threat prevention policy with the following options and save the policy:
    • Include malware in policy
    • HTTP file download enabled
    • SMTP attachments enabled
    • Threat score set to Permit 1-10

    When you edit this same policy, the threat score now shows Permit 1-9 and Block 10. As a workaround, change the threat score to Permit 1-10 before you save. [1297962]

Modified: 2017-08-02