Fortinet publikuje nową wersję oprogramowania dla produktu FortiAnalyzer! W nowej wersji – 6.0.8 naprawiono problem z poprawnym pobieraniem logów po wystąpieniu problemów z procesami systemowymi. Nowa wersja eliminuje błędy związane z wyświetlaniem skompromitowanych końcówek, czy wyświetlaniem danych w zakładce FortiView!
Rozwiązane problemy:
Event Management
| Bug ID | Description |
|---|---|
| 563514 | Event handler does not work properly for FortiSandbox. |
FortiView
| Bug ID | Description |
|---|---|
| 562834 | On FortiView > Top Sources, FortiAnalyzer displays incorrect data when trying to filter logs with Source and User. |
| 574836 | FortiAnalyzer may not be able to show the Compromised Hosts. |
| 574998 | FortiAnalyzer may not be able to show new logs under FortiView. |
| 581158 | Sorting by Threat Score in descending order should display entries with most Threat Score first. |
Log View
| Bug ID | Description |
|---|---|
| 573281 | Unregistered syslog device appears with FortiMail’s IP after added FortiMail device. |
Others
| Bug ID | Description |
|---|---|
| 601383 | FortiAnalyzer may become unresponsive when source IPs change often for all endpoints due to DHCP. |
| 544516 | FortiAnalyzer with Hyper-V live migration blocks access to GUI. |
| 588074 | FortiAnalyzer may stop receiving logs and event logs, and continuously display oftpd re-initialization. |
| 590368 | FortiAnalyzer may stop receiving logs after oftpd crashed. |
| 596252 | The clustered daemon may consume high CPU resource. |
Reports
| Bug ID | Description |
|---|---|
| 552414 | Read-write permissions are required to view and download reports through API call. |
| 589496 | FortiAnalyzer may generate a different result when running a report on the same time period either with a custom time period or a specific time period from the dropdown list. |
System Settings
| Bug ID | Description |
|---|---|
| 565200 | FortiAnalyzer may show incorrect Available Disk space status under storage information. |
| 571412 | Logging topology is misleading when collector mode in FortiAnalyzer is deployed. |
| 590109 | Some time zone are not formatted correctly when forwarding as syslog. |
| 600639 | FortiAnalyzer may not be able to move a VDOM with a long name from the Root ADOM to another ADOM. |
Znane problemy do rozwiązania:
Device Manager
| Bug ID | Description |
|---|---|
| 596832 | FortiGate Cluster is removed from log forwarding on failover when FortiAnalyzer is managed by a FortiManager. |
Log View
| Bug ID | Description |
|---|---|
| 550523 | Downloading logs from Log View randomly fails. |
| 579871 | Restoration of logs does not show correct timestamps under log browse after a NTP out of sync event. |
| 591841 | There may be a delay for FortiAnalyzer to show Historical Logs. |
| 597192 | Downloading logs may take longer than log search. |
Others
| Bug ID | Description |
|---|---|
| 587489 | Analytic data may be removed due to high disk usage. |
| 592593 | FortiAnalyzer may update ADOM disk allocation or create ADOM without any checks when request is made via JSON API. |
Reports
| Bug ID | Description |
|---|---|
| 547496 | FortiAnalyzer generates a report for selected device with outputs for all devices. |
| 553495 | FortiAnalyzer may prompt Web Server 404 Error when trying to download Report with 100,000 lines. |
| 557388 | There are discrepancies in Bandwidth and Applications Report for predefined data sets on the same report time period. |
| 558084 | FortiAnalyzer should not generate logs stating „Can not find user:admin when running report:1000060025”. |
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie
