FortiSASE Proactive Software Maintenance - FortiSASE release 25.1.a
Completed
The scheduled maintenance has been completed.
Posted Feb 12, 2025 - 17:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Feb 12, 2025 - 11: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.
For further information describing the monthly maintenance schedule and impact for FortiSASE, please see:
https://docs.fortinet.com/document/fortisase/latest/administration-guide/190872/appendix-e-monthly-maintenance
Features included in the 25.1.a release include:
Supported FortiClient version has been updated to 7.2.8. Customers will not be automatically upgraded but a portal notification will be displayed recommending this upgrade.
Change of IPsec client VPN configuration.
Important: For IPSec enabled tenants with on-premise FGTs defined in Geofencing priority and custom fail-over connections:
Please note IPSec DH group 15 will now be enforced instead of DH group 5.
Option added to block access to local subnet when connected to SASE (IPSec-enabled tenants only).
Automatic vulnerability patching on endpoints.
Support for Firewall Schedules & Services Groups.
Configuration of Personal VPNs on FortiClient.
Firewall Policies will now have a Comments field for improved policy management.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #324656.
Posted Feb 07, 2025 - 23:45 UTC
This scheduled maintenance affected: Fortinet Cloud Locations (Dallas, TX, US (DFW-F1), Komagome, Japan (TYO-F1), San Jose, CA, US (SJC-F1), Singapore (SIN-F1), Sydney, Australia (SYD-F1), Tokyo, Japan (TYO-F2), Vancouver, Canada (YVR-F2), San Jose, CA, US (SJC-F2), Singapore(SIN-F2), Dallas, TX, US (DFW-F2), San Jose, CA, US (SJC-F3)) and Public Cloud Locations (Santiago, Chile (SCL-G2), Seoul, South Korea (SEL-G2), Portland, OR, US (PDX-G2), Sao Paulo, Brazil (SAO-G2), Las Vegas, NV, US (LAS-G2), Osaka, Japan (OSA-G2)).