Add Maintenance Controller to Middleware.

Threat hunting middleware upgrade from v5.0.2 to v5.0.3 fails due to incorrect storage validation.

A very slow restart of an environment with many organizations due to slow Threat Hunting Repository registration.

Case of Core attempting to archive EDRv2 Database.

Unable to export cloud core logs in Central Manager.

Executive summary report contains only EDRV1 repositories.

A case of high memory usage.

Upgrade step failure.

Change registration of VDI Collectors to be based on the vdi hostname.

Audit error when moving a Collector to an expired group.

Optimistic locking during security events handling.

Occurrence of events ״handled by״ username display issue.

A rare issue with registering a Collector.

An issue with selecting all groups on assigning security policies.

Offloading load from the Central Manager.

"When created by" field in exception is inactive.

Issue of moving expired Collectors between groups/organizations.

Improve logs in applications learning flow.

Disable AV signatures in Nginx.

A case of registration failure.

A case of rollback during handling of search requests.

Failure in deleting an empty Collector group.

Optimistic locking during security events handling

A case where a wrong OS family value leads to rollbacks.

Failure in opening specific events in the Forensics tab.

Optimization during security events and IoT deep scans.

Log JSON content in case invalid event is received.

Hardening – limit exposure of internal services.

Upgrading to version 5.0.3.823 fails.

Repeating system events on a migrated Collector that failed to register in the destination environment.

Event wrongly shown as covered by exception due to miscalculation related to User field.

Hardening of interfaces.

Exception covering query "Listen on Port Attempt" causing exception to be shown as fully covered when it's actually partially covered.

Custom Connectors: new action cannot be added.

Playbook is now included in default Organization import/export.

Classification rules are not updated when content is uploaded unless a Management restart is performed, which might cause an exception on later content updates.

Exception Covering Query "Listen on Port Attempt" causing partially-covered exceptions to be shown as fully covered.

Accommodate Microsoft SCCM’s default behavior with Powershell scripts within FortiEDR Security Policies.

REST API method unable to retrieve list of collectors that are in running state within a time range.

Manager out-of-memory failure.

Slow loading of Security Events screen with Unhandled filter.

Failure in creating, deleting, or editing organizations due to Threat Hunting Repository allocations.

Drilling down from Forensics to Threat Hunting by PID doesn't always yield results.

Duplicate users columns in Events Excel report.

AV Scan of specific Collectors/Collector Groups is not working.

Security events are repeatedly reclassified after being handled.

LDAP authentication failures.

Inaccurate tooltip for process path in the Exception window.

Exporting a large number of Events to Excel is stuck.

Exceptions with URL are sometimes not sent to Collectors.

Creating Exception fails with "System Busy" Error on UI.

Custom integration script is populated with the wrong device IP.

Incorrect hash value is displayed for an event.

Rest API Collector sorting by lastSeenTime does not work as expected.

Events RDI paging button doesn't work.

VDI device registration doesn't work well when device ID is considered.

Error while filtering Communication Control events.

Collectors degraded due to an error in the configuration related to communication control decision.

Cannot list events when there is a large number of RDIs.

Errors in FCS response is causing delays in Collectors registration.

Target executable for Library Load events cannot be queried.

The Central Manager is slow to respond following playbook actions of device isolation due to a redundant full configuration.

Threat hunting export logs show inconsistent results.

High CPU on the Central Manager server due to deadlock with handling IOT devices responses.

Central Manager UI crashes when trying to load events with a long reclassification history.

OOTB connectors actions do not work with shared cores that serve as Jump Box.

SQL error displayed on Events page.

Exceptions are loaded very slowly on UI.

Internal DB failure when deleting applications.

Collector registration fails when it is allocated with the same ID of a deleted Collector.

Central Manager is inaccessible when running full configuration in an environment with lots of exceptions.

IoT license seat calculation is wrong.

IoT changes in settings such as auto-grouping cannot be saved.

Slow free-text search on the Events page.

Setting a vendor as allowed on a Communication Control Policy does not propagate to application and version. Hence the application is still blocked.

MITRE tag links do not work for part of the rules.

Expired Collectors are not properly calculated so no proper message is displayed on the Licensing page, and the corresponding system events are not being sent.

Failure starting manager when LDAP configuration has spaces due to missing escaping.

Low disk space alerts since Aggregator holds references to deleted configurations.

NPE during the processing of FCS response is causing delays in Collectors registration.

Managed devices with multiple mac addresses are wrongly displayed as unmanaged devices.

Repeating system events on a migrated Collector that failed to register in the destination environment.

Collectors failed to register with the Central Manager.

Events are triggered even when there is Exception that is using IP Set.

Aggregator malfunction due to load of Events.

Communication Control tab is slow.

Cannot set Exception on Listen events due to missing IP.

Email notifications arrive with delay.

Playbook failed to trigger when “Move to High Security Group” is selected.

Error when creating communication control policy rule with many vendors.

Central Manager general slowness.

Collectors displayed as disconnected on Central Manager although they are running.

IOT devices are not discovered across multiple subnets .

Events advanced search window opens up very slowly.

Manager fails to start due to incorrect LDAP/SAML settings .

Failed deleting a security event in an environment with many events.

LDAP configuration cannot be saved when done with Local Admin permissions.

LDAP configuration cannot be saved when done with Local Admin permissions.

Pivoting from Forensics to Threat Hunting using PID yields empty results.

Cannot run a file scan if there are more than 20K Collectors in the specified Collector group .

Installations of on-premises Threat Hunting repository is not supported.

IOT allow option to ignore external IP when looking for managed devices.

Network discovery wrongly marks devices with existing Collectors as unmanaged devices and makes duplications of IOT devices.

IOT scan cannot be configured to be performed from a Windows server.

Deleting Collectors and tenants can take a very long time.

Search for Collectors last seen on Inventory works well only for part of the Collector Groups.

Export Collectors from Inventory is not working when done on search results.

Request Collectors installers group dropdown is empty when there are more than 100 groups in the environment.