R82.10 Jumbo Hotfix Take 6

NEW: Added support for nested groups with host/range/network objects for split tunnel on exclusion/inclusion options. Refer to R82.10 Remote Access VPN Administration Guide.

UPDATE: SmartEvent now supports the "system alert" log type for URL Filtering and Application Control Software Blades.

UPDATE: Added Take 210, Take 223 of CPotelcol (OpenTelemetry Collector) Release Updates. Refer to sk180522.

UPDATE: Added Take 52, Take 53 of CPquid (QUID) Release Updates. Refer to sk181458.

UPDATE: Added Take 80, Take 82, Take 87 of Policy Insights Release Updates. Refer to sk183421.

UPDATE: Added Update 4 of Server-Side Change Report Generator Release Updates. Refer to sk179508.

UPDATE: Added Update 28 of Autonomous Threat Prevention Management Integration Release. Refer to sk167109.

Hitcount of NAT Rule Base fails after Security Management Server upgrade. Refer to sk184336.

On Multi-Domain Security Management Servers, custom Compliance Software Blade Best Practices may differ between the Multi-Domain Security Management level and the Domain level.

In some scenarios, exporting logs to CSV in SmartView fails and the LOG_INDEXER process unexpectedly exits. Refer to sk184475.

In some scenarios, incorrect values are shown in the "Total Bytes" field in the logs.

In a rare scenario, the FWK process may restart unexpectedly when the Security Gateway processes accelerated connections.

In scenarios where a network connection is closed before the Anti-Virus ThreatCloud emulation or scanning response is received, the affected session may experience connectivity instability.

In some scenarios, External Risk Management (ERM) enrichment for SSH connections may be incomplete, resulting in only partial contextual data or risk insights associated with the SSH session.

File downloads may get stuck at 100% completion when either the Anti-Virus or Threat Emulation Software Blade is actively scanning the file.

When the Packet Tagging feature is enabled on the Full Identity Agent, new user and machine identity sessions reported to the Identity Awareness Gateway may not be assigned the correct Access Roles. As a result, traffic from these sessions may not match Access Control Policy rules that use Access Roles with Packet Tagging enabled.

False threat alerts may appear in Anti-Virus logs for benign traffic (action: accept). This is a cosmetic issue with no security impact.

Running the "show cp-trusted-ca-certificate" Management API with invalid validFrom/validTo values in the database causes an error and blocks the Trusted Certificates view.

In rare scenarios, Mobile Access SmartConsole Logs may not match views/queries, including the "MAC address" or "Methods" field names.

Permanently disabling the "cphwd_enable_ecmp" global parameter on a VSX Gateway using the "-f" option of the "fwl ctl set" command may fail.

The CX4 firmware does not update automatically as expected, and there is no error message indicating that the firmware is not the latest version.

SNMP monitoring systems may report format errors related to the structure of the chkpnt.mib file.

When integrating SNMP monitoring systems with Gaia OS, compilation of the GaiaTrapsMIB.mib file with the CHECKPOINT-MIB (chkpnt.mib) may fail. SNMP management stations or MIB browsers (such as HP OpenView, CA Spectrum, or HP Network Node Manager) return errors like "File GaiaTrapsMIB.mib failed to parse" or "ERROR : Cannot find symbol file://GaiaTrapsMIB.mib:Line XX:Column XX:multiDiskName".

If multiple snapshots are stored on the Gateway server, creating a new snapshot fails with the "Cannot create snapshot, insufficient space in /boot" error, even though there is enough unpartitioned space.

During interface reallocation between Virtual Systems (VSs) on a VSX Gateway, Management access (SSH/Gaia Portal) to VS0 may be disrupted after the interface move. Returning the interface to its original VS does not recover connectivity.

Creating a large number of Virtual Systems (VSs) simultaneously may intermittently fail.

Three out of four Virtual Systems (VS) on a single site may show a "Problem" Health status in the output of the "asg stat vs all" test. This is a cosmetic issue.

When a new Cloud Firewall Gateway is added to the Security Management Server, and a security policy is installed, the Security Gateway may not appear in the Central License Tool (vsec_lic_cli). As a result, the Security Gateway fails to receive a central license.

When adding a subordinate to an LACP bond, a member may go down, which triggers a site failover.

These actions applied through the Gaia Portal are not applied to all Security Group members, but only to the SMO:

• create/delete/edit scheduled backup

• edit mail-address/notification-level for mailing

• delete backup

Using a unique IP address with the Same VMAC feature enabled may cause connections to the Standby unique IP address to fail.