Producent oprogramowania Fortinet udostępnił najnowszą aktualizację dla produktu FortiAnalyzer o numerze wersji 7.0.5. W tej wersji rozwiązano problem z błędnym wyświetlaniem prawidłowych adresów IP wraz z wersją oprogramowania urządzeń FortiGate. Ponadto, aktualizacja naprawiła problem dotyczący komunikacji do FortiClient EMS. Po więcej ciekawych informacji zapraszamy do dalszej części artykułu.
Rozwiązane problemy:
Device Manager
Bug ID | Description |
---|---|
798197 | Under the Device Manager, FortiAnalyzer does not show the color of the logging devices properly (red or green). |
811627 | FortiWeb FlexVM is not supported by the FortiAnalyzer. |
816072 | In Device Manager, model device configured with a pre-shared key is not automatically authorized. |
819664 | Under Device Manager, Average Log Rate is displayed zero for FortiGates HA Cluster. |
827276 | FortiAnalyzer does not let all VDOMs to be added to the Device Manager if the FortiGates have more than 10 VDOMs. |
835653 | The FortiGate’s IP address and firmware version are not updated when FortiGates are added manually to a non-root ADOM. |
837310 | FortiAnalyzer does not show the correct IP addresses and firmware versions for its registered FortiGates. |
Event Management
Bug ID | Description |
---|---|
825422 | FortiAnalyzer Event Handler does not trigger any alerts when „Log Field” has been set to „Virtual Domain (vd)”. |
Fabric View
Bug ID | Description |
---|---|
824417 | Failed to save the „FortiClient EMS Cloud” configuration under the Fabric Connector as it kept changing to the regular „FortiClient EMS” setting. |
FortiSOC
Bug ID | Description |
---|---|
701751 | FortiGate connectors disappearing from FortiSOC connectors list. |
757650 | Wrong device name (devname) is filled in event email notification. |
784316 | FortiSOC Connectors do not display the status of all the cluster’s members. |
814419 | When creating/configuring a playbook from scratch for an incident the task status failed because of a missing category. |
821135 | EMS connector status is inconsistent. |
833991 | FortiOS connector does not display health status of the Security Fabric members. |
FortiView
Bug ID | Description |
---|---|
754733 | „No entry found” is displayed when checking the „Top Cloud Applications” logs under the FortiView. |
754781 | FortiView widgets log out even if the auto-refresh feature is being used. |
760228 | FortiView displays higher bandwidth value than Report. |
818065 | FortiView Top Applications view does not show any data. |
818077 | Top application axis labels are not displayed correctly in Monitor section. |
822462 | Secure SD-WAN Monitor devices are not sorted alphabetically like other widgets. |
822471 | SD-WAN Performance Status widget under the Secure Monitor displays gray intervals even if there is data available. |
Log View
Bug ID | Description |
---|---|
682584 | FortiClient logging for Chromebook stops intermittently and can be only resumed by restarting FortiAnalyzer. |
797985 | After downloading the IPS logs, the „cve field” is missing. |
816490 | In Log Browse, for HA devices, only primary device’s log files are displayed. |
820560 | When log filters have been applied, Log View does not return all the matching logs; only displays one page of matching logs. |
836777 | When admin profile is set as „Read-Only”, Add Filter under the LogView/FortiView displays no fields. |
843730 | Fabric log host_name and host_osname fields are displayed with incorrect values. |
817761
828139 |
Downloading the traffic logs with custom time in text format displays error 500. |
Others
Bug ID | Description |
---|---|
719298 | FortiAnalyzer failed to provide API Response to the FortiPortal’s API Requests. |
779943 | High memory usage has been observed when creating dataset or running reports on FortiAnalyzer. |
792963 | Switching between ADOMs and going to the Device Manager shows a blank page. |
804934 | Type mismatch error is displayed for the column „dstuuid”. |
812730 | There is an issue on HA member synchronization on the Azure platform. |
817639 | FortiAnalyzer archive logs caused unexpected increase in the disk quota usage. |
818118 | Logs between HA members are not synched. |
829869 | When FortiAnalyzer is working on Collector Mode, system storage size increases over time; hence, FortiAnalyzer might stop receiving new logs. |
Reports
Bug ID | Description |
---|---|
764194 | Playbooks run_report fails with „missing device(s)” if „Playbook Starter” as devices filter is selected. |
768843 | FortiAnalyzer does not support importing outbreak alert reports to ADOM type FortiGate. |
783172 | Reports may only show 64 devices report details after upgrade. |
788801 | „Throughput utilization billing report” does not display the complete data for the „yesterday” time-period. |
816975 | Not able to upload the report to server by output profile. |
824260 | Failed to create reports using API request in FortiAnalyzer. |
832037 | „Create Chart” window does not display all the parameters. |
835422 | FortiAnalyzer does not display any data on its report when group filter and LDAP query is being used. |
837395 | „Show Top” & „Drilldown Top” preview features under the „Edit Chart” do not display the chart based on the selected values. |
System Settings
Bug ID | Description |
---|---|
669478 | Several dev-type mismatches have been observed between CLI and GUI under log-forwarding configuration. |
734407 | HA status does not display the DB inserting issue on the secondary member. |
745468 | Enabling the SNMP event „raid-changed” in CLI does not enable it on the GUI. |
752111 | Traffic, Security and Event logs section under the LogView tab are missing for Primary HA. |
759601 | FortiAnalyzer using Azure AD SAML SSO may show 'invalid_logout_response_error’ after logout. |
813243 | FortiAnalyzer log-forwarding not able to forward FortiManager events with Log-ID filter to syslog |
815644 | In FortiAnalyzer cannot configure log forwarding exclusions for FortiClient. |
839783 | When Interface type is in Aggregate mode, the „Administrative Access” services are not displayed correctly based on how they have been configured. |
842943 | After upgrading FortiAnalyzer, „fortinet-ca2” is missing under the CA Certificates; this prevents devices from establishing connections to FortiAnalyzer. |
Notatki producenta: FortiAnanlyzer 7.0.5
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie