All Release Notes Reporter for Cisco Firepower 1.0.0.13 (2022-09-13)

• You can now adjust the username display format in Settings | Directory / LDAP | User Settings.
  By default, for new installs, authenticated users are displayed as “displayName (samAccountName)”. E.g. “Jane Doe (j.doe)”, to assist in identifying different users with the same name. More advanced customizations using other AD attributes can be made by carefully editing the UserAttrDisplayName element in Fastvue Reporter’s Settings.xml file when the Fastvue Reporter service is stopped. Please reach out to support@fastvue.co for assistance.
• Search term extraction logic and has been updated to better support a range of websites, including TikTok, Pinterest, Yandex, Tumblr, Swiggle & Internet Archive.
• Fixed issues with the keyword highlighting feature that may occur when multiple keywords or excludes exist in a phrase.
• The data retention size threshold now ignores the current day to prevent the index from being destroyed and recreated repeatedly, but this may mean that the size threshold may be ignored if the current day exceeds the limit. Also added a daily clean up task to remove temporary files more regularly.
• LDAP directory import implementations have been updated to better handle timeouts and ldap exceptions/errors.
• Added a user interface to manage Elasticsearch indexes in Settings | Diagnostic | Database | Index Management. This includes options to open, close, reindex, merge segments, and delete indexes.
• Added a user interface to change Elasticsearch’s Index Store Mode from mmapfs (default) to niofs. This is available in Settings | Diagnostic | Database | Memory Settings. When using mmapfs you’ll see increased memory usage but faster report generation. With niofs you’ll see reduced memory usage but slower report generation. The only time you should consider changing to niofs is when your Fastvue server is constrained on memory, but you have very fast SSD harddrives, and you’re willing to wait longer for reports to generate. For more information about these Elasticsearch Index Store Modes, see https://www.elastic.co/guide/en/elasticsearch/reference/5.6/index-modules-store.html
• If reports on large date ranges are failing with a timeout error, you can now configure this timeout by carefully editing the DatabaseElasticRequestTimeout element in Fastvue Reporter’s Settings.xml file when the Fastvue Reporter service is stopped. The value is specified in seconds, and defaults to 300 (5 minutes). If you’re experiencing timeout errors when running reports, try increasing this value to 1200 (20 minutes). This changes how long Fastvue Reporter is willing to wait for a response from the Elasticsearch database when running queries.

Download Latest Update