Producent oprogramowania udostępnił najnowszą aktualizację dla FortiManger o numerze wersji 6.4.10. Dzięki nowszej wersji oprogramowania został naprawiony problem z zawieszającym się procesem ,,svc sys”, również skorygowano proces aktualizacji urządzeń działających w klastrze HA, gdyż przy próbie aktualizacji urządzenia wpadały w pętle i stale się restartowały. Ponadto, poprawiono konfigurowanie polityk, gdzie problem dotyczył błędnego przypisywania do niewłaściwej sekcji bądź miejsca. Po więcej ciekawych informacji zapraszamy do dalszej części artykułu.
Aktualnie wspierane modele:
| FortiManager | FMG-200F, FMG-200G, FMG-300E, FMG-300F, FMG-400E, FMG-400G, FMG-1000F, FMG-2000E,
FMG-3000F, FMG-3000G, FMG-3700F, FMG-3700G, FMG-3900E, and FMG-4000E. |
| FortiManager VM | FMG-VM64, FMG-VM64-Ali, FMG-VM64-AWS, FMG-VM64-AWSOnDemand, FMG-VM64-Azure, FMG-VM64-GCP, FMG-VM64-HV (including Hyper-V 2016, 2019), FMG-VM64-KVM, FMG-VM64-OPC, FMG-VM64-XEN (for both Citrix and Open Source Xen). |
Rozwiązane problemy:
Device Manager
| Bug ID | Description |
|---|---|
| 812687 | Unable to add FortiGate WiFi-80F-2R to FortiManager when Trusted Platform Module (TPM) is enabled. |
Global ADOM
| Bug ID | Description |
|---|---|
| 835439 | Global Policy assignment is not completed successfully due to some missing objects on Global ADOM. |
Others
| Bug ID | Description |
|---|---|
| 742819 | Promote to global feature should not be possible since GLOBAL ADOM are not accessible in FortiManager Cloud. |
| 750242 | FortiManager’s DB in HA clusters are not properly synced together. |
| 796506 | Upgrading HA cluster via FortiManager puts members into a restart loop. |
| 850377 | In Workflow Mode, when new session is created, the Policies disappear. |
Policy and Objects
| Bug ID | Description |
|---|---|
| 698838 | „Download Conflict File” does not display all of the firewall objects conflicts when importing policy packages from FortiGate to FortiManager. |
| 762392 | The rating lookups does not return the correct category for the URL when it ends with „/” character. |
| 767592 | FortiManager shows „Validation Failed” and „No installation Targets on package” when an unmodified policy package is pushing to the FortiGates. |
| 808900 | Incorrect error message is displayed when re-installing the same policy to FortiGate immediately after the first installation. |
| 831273 | FortiManager does not allow deleting the entries for „server-info” under the log „npu-server”. |
| 834806 | Installation fails due to extra back slashes when installing the custom IPS signatures to the FortiGates. |
| 835079 | Detail of the „Firewall Security Policy” when running the Policy Package Diff does not display data for all fields. |
| 836103 | FortiManager pushes old internet-service-names „Facebook” instead of „Meta”. |
| 841966 | When Inserting „Above” or „Below” to add policy, the policy is added to the wrong section/place. |
| 846634 | GUI does not allow to edit the custom Application and Filter Overrides. |
| 849470 | When creating a new firewall policy via API Request, the „global-label” option is skipped. |
Services
| Bug ID | Description |
|---|---|
| 846198 | FortiManager’s „svc sys” daemon is crashing repeatedly. |
System Settings
| Bug ID | Description |
|---|---|
| 823898 | FortiManager does not use all of the configured „ssl-cipher-suites” under its „system global” settings. |
| 841931 | When FortiManager works in Workspace Mode, users are able to disable „Per-Device Mapping” without locking the ADOMs. |
Notatki producenta: FortiManager 6.4.10
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie
