Some security researchers have demonstrated three high risk vulnerabilities for exchange server systems. Microsoft has published information about the vulnerability today and even has a patch for the problem already in place.
Even though we, as Boll Engineering AG, are not associated in any way with the affected product, a lot of our customer reported, that they have vulnerable systems in place and may be affected by this bug. We have been asked if IPS signatures and WAF patches are already implemented. Therefore we decided to post this blog to raise the awareness of this vulnerability once more, even after the broad press has already published a lot of releases regarding this matter.
Even though we, as Boll Engineering AG, are not associated in any way with the affected product, a lot of our customer reported, that they have vulnerable systems in place and may be affected by this bug. We have been asked if IPS signatures and WAF patches are already implemented. Therefore we decided to post this blog to raise the awareness of this vulnerability once more, even after the broad press has already published a lot of releases regarding this matter.
Below you can find the related articles or microsites to the matter from our different vendors we distribute.
Please note, that some of the solutions had a signature in place already, when the broad exploitation of the vulnerability started. Therefore not only the information IF a signature is available, it is also important from WHEN this signature has been applied on your system.
During the lifecycle of firewalls, they are often replaced with a newer model, but you would like to keep the configuration. In this case, there are several possibilities, which we present in this blog post:
Öfters sehen wir Fragen oder Probleme zur korrekten Subnettierung von Netzen. Mit dem folgenden Raster kann man schnell und einfach die richtige Anzahl Host oder die Subnetzmaske herausfinden.
Die erste Adresse des Subnetz nennt man Netzadresse. Diese kann nicht für Hosts verwendet werden (Bsp. 192.168.10.0 bei einem Subnetz von 255.255.255.0 oder /24)
Ebenso die letzte Adresse des Subnetz. Diese ist die Broadcast Adresse und steht Clients nicht zur Verfügung (Bsp. 192.168.10.255 bei einem Subnetz von 255.255.255.0 oder /24)
Die verbleibenden IP Adressen können von Hosts genutzt werden (Anzahl Hosts in der Tabelle, also 256-2= 254 bei einem Subnetz von 255.255.255.0 oder /24)
Bekommt man nun zum Beispiel die Angabe, dass ein Provider Subnetz 6 nutzbare IP Adressen hat, entspricht dies in der Tabelle einer Subnetzmaske von 255.255.255.248 oder /29. Die nutzbaren IP Adressen sind dann zum Beispiel 8.65.34.25 bis 8.65.34.30. Die .24 ist die Netzadresse, die .31 die Broadcast Adresse. Meistens ist es dann so, dass der Router selber die .25 bekommt, die Firewall die .26. Die weiteren nutzbaren Adressen sind dann .27 bis .30.
With the possibility to include external lists from third parties via the feature «External Dynamic List EDL», this opens up many possibilities to restrict your own security policies even better and to prevent access to the TOR network.
In the following tutorial I will show you how to configure the list of TOR exit nodes, which can be found at https://check.torproject.org/torbulkexitlist as a list of IP addresses.
1. Create External Dynamic IP List
First, create a new EDL. Objects > External Dynamic Lists > Add
The list of TOR Exit Nodes and further information can be found here:
As type you should choose the «IP List» selection. This assumes a list with one IP per line. If you look at the provided IP list, this is the case:
2. Download the CA Certificate from the website as .pem format.
Since the list is provided via HTTPS and therefore signed with a certificate, the Palo Alto Firewall must trust the CA certificate which signed the server certificate. This is solved via the import of the CA certificate into the firewall.
Please use your browser capabilities to display and download the CA certificate.
3. Add the CA certificate to firewall’s the certificate list
After you have downloaded the CA certificate, you can upload it to the firewall’s certificate store.
4. Create a certificate profile and add the Tor_CA certificate
Now that the certificate has been uploaded to the firewall’s certificate store, it can be used in a certificate profile.
5. Add certificate profile in EDL list
Now the certificate profile with the CA certificate can be used in the configuration of the EDL list.
Also note the update frequency of the list, if the list contains new values. The new entries are added automatically with the update, and a Commit is not necessary.
6. Add EDL in Security Policy
Now everything is prepared and the EDL list can be inserted in the security policy as source or destination address object.
It makes sense to use a security policy with the action Block at the beginning of your security policies.
Policies > Security > Add
7. Commit changes
Save the changes so that they become active.
8. Verify if EDL list contains entries
After the initial synchronization of the list, you can check its content as follows.
Objects > External Dynamic Lists > Edit Tor Exit nodes > List Entries and Exceptions Check if list contains entries:
The Swiss National Cyber Security Centre has a new form to report attacks on infrastructures of Swiss companies. Furthermore, the website has been revised and now has some more information to offer than before.
Das Nationale Zentrum für Cybersicherheit der Schweiz hat ein neues Formular um Angriffe auf Infrastrukturen von schweizer Firmen zu melden. Ausserdem wurde die Webseite überarbeitet und hat nun einige Informationen mehr zu bieten als bisher.
Spoiler Alert! – Since the release of macOS 11.0 aka Big Sur, your FortiClient VPN might not be working as expected anymore if you have already upgraded.
There’s a chance you might not have noticed it, in the case that you’re using SSL VPN only in your environment. But as soon as you also have IPsec tunnels you’d like to use, you might find yourself with a successfully established tunnel, but no traffic is reaching your remote end.
The System Engineers of BOLL Engineering have been supporting Fortigate devices for 18 years. This year, FortiOS v6.4 was released and we have again gathered all the troubleshooting commands that we use regularly in our new CheatSheet.
Hopefully this CheatSheet will help you as well.
You will find the most important commands on the first page. The second page contains troubleshooting commands for problems with firewall policies and security profiles, followed by the third page with commands for network problems. The last page covers system and hardware commands and general information.
Updated to v1.1 (addition and correction for FortiToken, 11.12.2020)
Since a while, the most recent macOS versions the system do report the use of «legacy system extensions» which is often triggered by modules or plugins of low-level software like VPN Clients, AV software etc.
