Update – 30. Oktober 2023: We received feedback from our partners that the issue probably occurred again today. Fortinet confirmed the issue, here is their response: Few cases have been reported to us with this issue during the weekend, this seems to be issue with Fortiguard anycast when Daylight Saving…
Last Friday the first patch for FortiOS 7.4 has been released. As always with a brand new minor or major FortiOS version a lot of issues have been resolved and a lot of new features have been introduced. No Security Fabric root for FG60E/F anymore Interestingly, however, we found an…
During Accelerate 2023, Fortinet has introduced the new Fortinet NSE Certification Program which will come into effect on October 1st 2023. Let’s summarize what will change and what is important to know:
Most of you have already read about the latest release of Fortinet’s new PSIRT advisories. There are 15 new vulnerabilities for FortiOS and other products with severity level from low up to critical. We strongly recommend that you checkt the PSIRT advisories and update your Fortinet products to one of…
In the last two weeks we have received many support requests because of non-functioning SSL connections from our Fortinet, Palo Alto Networks and Watchguard customers. Incoming SSL connections on port tcp/443 suddenly stop working. These can be SSLVPNs, Global Protect connections, port forwardings (VIPs, Destination NAT) for internal web servers…
Today Fortinet has published a new critical vulnerability in their FortiGate products. A successful attack allows arbitrary code or commands to be executed. The problem exist in the SSLVPN module – and you might be vulnerable if you are using SSLVPN and not running the latest patch release of the…
Hi all, another vulnerability – log4j – is keeping us all on our toes.In this blog article you will find information about log4j from our vendors.
After Fortigate upgrade v6.4 > v7.0.1 (or later) the S2S-dialup VPNs did not work anymore. Tunnel negotiation is successful and phase 1 and 2 get up. Traffic from spoke is routed into the tunnel, but is seems that the traffic is not received by the hub.
Some of you may have noticed that a Fortigate – configured to use the FortiGuard DNS Servers – is not resolving some DNS names anymore. Consequences can be that FQDN address objects can not be resolved or a configured mail server can not be used anymore.
For some reasons Fortigates are are not able to load the FortiGuard DDNS server list. Therefore you are not able to configure DynDNS on your Fortigate anymore. In the WebUI you will see following error message under Network > DNS > FortiGuard DDNS and you are not able to list…
Sind Sie interessiert, den BOLL Blog als RSS Feed zu abonnieren?