February 10, 2026 Release
Juniper Security Director Cloud New Features: February 10, 2026
General
Menu reorganization—You can use the reorganized navigation system in Juniper Security Director Cloud to view the related features under intuitive categories with streamlined menu headers. The new layout reduces clutter, minimizes clicks, and helps you quickly find the required tools. Role-based access controls show only permitted menu items, simplifying your interface. You can quickly search the menu using the dedicated Menu Search text box provided at the top of the menu.
Intelligence
IDP and Screens insights—We have moved IDP and Screens threat details to separate pages. This dedicated view enhances clarity and improves user experience.
[See Insights Overview]
Security
Zone-based or global security policy rule—You can now select the security policy rule scope—either zone-based or global—while creating a rule.
[See Add and Manage Security Policy Rules.]
Support for IPv6—We have extended IPv6 support across the following areas to enhance your network addressing capabilities:
-
IPS Signatures: A new IPv6 tab is now available when you create custom IPS signatures under .
-
IPsec VPNs: IPv6 is supported for Network IP and Tunnel Settings in .
-
Shared Object: You can now enter an IPv6 value in .
-
Security Policies: IPv6 is supported for Source and Destination addresses in .
-
Device Tunnel Status: IPv6 is supported for Device 1 and Device 2 in .
[See Create and Manage IPS Signatures, Create and Manage Route-Based Site-to-Site VPN,Create and Manage Addresses or Address Groups, and Tunnel Status Overview.]
Inventory
Looking Glass—Use the looking glass functionality to view and compare
configurations and runtime data across multiple devices. Run CLI
commands—show, ping, test and
traceroute simultaneously on selected devices to validate the state and
troubleshoot efficiently. As you type, a dynamic suggestion list displays supported
commands from the platform database, ensuring accurate inputs and faster entry. You can
view results in text or table formats and export them in text or CSV format.
[See Looking Glass Overview].
Logical MNHA grouping or ungrouping for existing devices—If Multinode High Availability (MNHA) is already configured using the CLI on devices outside Juniper Security Director Cloud or through templates, you can now select and logically group two already-managed standalone devices in the UI. You can then view the grouped devices as part of the MNHA configuration in the Juniper Security Director Cloud UI. You can also ungroup these devices in the UI if MNHA has been removed or ungrouped outside of Juniper Security Director Cloud. In this case, the devices appear as standalone devices.
Group and Ungroup are UI-only actions that improve visibility and management. Juniper Security Director Cloud does not create, modify, push, or remove any MNHA configuration on the devices.
[See Group MNHA Devices and Ungroup MNHA Pairs].
Configurable routing instance support—You can configure a custom routing instance for management, so devices can reach Juniper Security Director Cloud services through that instance. Provide an input for the routing instance during onboarding or update from . Juniper Security Director Cloud saves the routing instance with interface and applies it to CLIs for outbound SSH, security log streaming, security packages, image staging or file copy, and PKI/Security-Intelligence/AAMW profiles. You can edit or remove the management routing instance. You can use templates to deploy routing instances to PKI/Security-Intelligence/AAMW profiles.
[See Configure and Manage Routing Instance].
Roll back device image—You can now roll back the current image deployed on a device to its preceding version, also known as a backup image. Roll back the image on standalone devices, clusters, or MNHA pair devices that are onboarded and connected to the Juniper Security Director Cloud. You can roll back up to 10 devices at once.
[See Rollback Device Image.]
Proxy server for device connectivity—You can now configure a dynamic or static HTTP proxy server to manage your devices, onboard devices, and for all outbound SSH device traffic.
Devices running Junos OS Release 23.4R1 and later can use proxy servers. You can configure proxy servers in Juniper Security Director Cloud to manage devices running these supported versions of Junos OS.
[See Configure an HTTP Proxy Server for Device Management.]
Automate configuration deployment with API-driven YAML templates—You can now automate consistent configuration deployment using an API-driven system for YAML-based templates. This enhancement reduces errors, accelerates rollouts, and supports scalable, auditable change management across your network.
[See Configuration Templates Overview, Add and Manage Configuration Templates, and Deploy a Configuration Template on to a Device.]
FQDN for IPv6—Fully qualified domain names (FQDNs) for IPv6 addresses are now available across multiple regions.
[See Add Devices.]
Admin
Two-factor authentication—You can now view the authentication key to manually enter it in a mobile authenticator app. This method provides an alternative for entering the authentication key in addition to scanning the QR code.
[See Onboard Your Two-Factor Authenticator App.]
Update to Juniper Security Director Cloud privacy settings—Juniper Security Director Cloud now seeks your consent to analyze the pattern of your interaction with the Juniper Security Director Cloud portal. This analysis enables advanced troubleshooting and is used for product enhancements.
[See About the Organization Page and Create an Organization.]
Support for IPv6—We have extended IPv6 support across the following areas to enhance your network addressing capabilities:
-
Address Pools: IPv6 is supported in Address pool type, Primary DNS Server, and Secondary DNS Server in .
-
Access Profile: IPv6 is supported for RADIUS authentication in .
-
JIMS: IPv6 is supported for Primary JIMS Server in .
[See Create and Manage Address Pools, Create and Manage Access Profiles, and JIMS Identity Management Service Overview.]
Network
Support for IPv6 in NAT Pools—You can now expand your addressing capabilities with IPv6 supported in Pool address and Host Address Base in .
[See Create and Manage NAT Pools.]
Support for IPv6 in NAT Policy Rules—IPv6 is supported for Source and Destination addresses in .
[See Create a NAT Policy Rule.]
Support for Neighbor Discovery Protocol in NAT Policy—Use this feature to have the device respond to NDP requests and translate IPv6 addresses to MAC addresses in .
[See Create a NAT Policy.]
Juniper Security Director Cloud Bug Fixes: February 10, 2026
-
Incorrect install interval value in a remote access VPN—Previously, if you created a remote access VPN without specifying an install interval, the system incorrectly configured the install interval as 0 and added a matching command. This issue is fixed in latest Juniper Security Director Cloud release.
-
Unable to clear OOB configuration changes for device in Juniper Security Director Cloud—Previously, when a configuration rollback was performed directly from device CLI, devices intermittently returning partial configuration. This incomplete configuration caused the Out‑of‑Band (OOB) synchronization process to hang and lead to timeout errors. This issue is now resolved.
-
Infected Host dashboard displays no data—Previously, Infected Hosts dashboard appeared empty even though active infected‑host entries existed under ATP. This issue is now resolved.
-
Unable to import address-object with CSV file—Previously, when importing address‑objects using a CSV file, the job status was showing success even for the objects that were not imported successfully. This issue is now resolved.
-
Incorrect log configuration placement affecting external SIEM—Previously, Juniper Security Director Cloud used to push the sd-syslog configuration outside the associated security log stream. This misplacement could cause conflicts or unexpected behavior when your device is forwarding logs to external SIEM solutions. This issue is now resolved.
-
Cannot add multiple interfaces in Proxy ARP—Previously, there was no option to add multiple interfaces for the network range in Proxy ARP. This issue is resolved now.