FortiSASE Proactive Software Maintenance - FortiSASE release 25.3.c

Scheduled for Oct 7, 16:00 UTC  -  Oct 8, 00:00 UTC

Scheduled

Anticipated Impact: Potential for short interruption of customer instances and configuration portal during the window.
The Operations team will be installing a rolling software update. There is potential for short connectivity impact (approximately ~1-2 minutes) for each customer instance and the configuration portal while these components are updated. No other impact on service delivery is expected.

Features included in the 25.3.c release include

For Feature release:
Added support for using a custom domain and a certificate for the custom domain that can be used to access a ZTNA private application.
Added a built-in custom PAC file editor for creating and editing PAC files hosted on FortiSASE.
For FortiSASE instances with Proxy (formerly SWG) enabled, added a best practice recommendation to migrate to secure explicit proxy.
Added support for additional Web Filter configuration settings including the ability to prioritize URL filter entries, logging search keywords, and displaying the FortiGuard web filter category and subcategory in a tooltip when hovering over a domain.
Added support for configuring application control filter overrides based on multiple filters including application category, behavior, popularity, protocol, risk, technology, and vendor. Also, added support for configuring actions for custom application signatures.
Administrator logins, configuration audit logs, and user audit logs have been introduced in the System > Administration page.
The UI version has been removed from the FortiSASE portal URL, ensuring a consistent path for ease of access.
The recommendation to use SOCaaS log forwarding is presented in the Operations > Logs > Settings page and through additional portal notifications. Enabling SOCaaS log forwarding is included as a best practice recommendation.
Added support for a new endpoint vulnerability report based on logs collected from FortiClient endpoints.
Added support for a new Secure Private Access (SPA) report displaying the health of each connected SPA hub, the traffic through popular hubs, and the status of SD-WAN performance SLAs.
Added support for a new Cloud Security Usage Report to identify the total number of users in the reporting period and per PoP, the number of sessions, and total traffic.
Added support for Public Cloud security PoPs: Chicago - Illinois - USA, Delhi - India, and Perth - Australia.
Support FortiClient 7.2.12 as the recommended version for FortiSASE desktop users.


For Mature release:
The UI version has been removed from the FortiSASE portal URL, ensuring a consistent path for ease of access.
Added support for Delhi, India as a Public Cloud security PoP.
Support FortiClient 7.2.12 as the recommended version for FortiSASE desktop users.


For further information on what's new: https://docs.fortinet.com/document/fortisase/latest/release-notes/661728/whats-new
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #390058.
Posted Oct 03, 2025 - 19:10 UTC
This scheduled maintenance affects: Fortinet Cloud Locations (Dubai, UAE (DXB-F1), Frankfurt, Germany (FRA-F1), Hong Kong (HKG-F1), Paris, France (PAR-F1), Valbonne, France (NCE-F1), Bangalore, India (BLR-F1), Frankfurt, Germany (FRA-F2), Pune, India (PNQ-F1), Paris, France (PAR-F2), Istanbul, Turkey (IST-F1), Johannesburg, South Africa (JNB-F1), Dubai, UAE (DXB-F2), Frankfurt, Germany (FRA-F3), Paris,France(PAR-F3), Madrid, Spain (MAD-F1), Paris,France (PAR-F4), Frankfurt, Germany (FRA-F4)) and Public Cloud Locations (Johannesburg, South Africa (JNB-G2), Milan, Italy (MIL-G1), Tel Aviv, Israel (TLV-G1), Hamina, Finland (HEL-G2), Amsterdam, Netherlands (AMS-G2), Tel Aviv, Israel (TLV-G2), Madrid, Spain (MAD-G2), Melbourne, Australia (MEL-G2), Doha, Qatar (DOH-G2), Jakarta, Indonesia (JKT-G2), Milan, Italy (MIL-G2), Mumbai, India (BOM-G2), Dammam, Saudi Arabia (DMM-G2), Taipei, Taiwan (TPE-G2), Hong Kong, China (HKG-G2)).