Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues

The issues resolved in the JSA 7.5.0 Update Package 16 are listed below:

  • Log Source Management incorrectly reports DSM updates as available when the latest version is already installed.

  • JSA: XML, generic list, NVP and calculated expression Tables Not Replicated from Console to Event Collector.

  • Inconsistent offense-event association causes inaccurate event counts on the offense summary page.

  • JSA: Legacy patch mode skips or ignores manual input if the patch.conf file exists.

  • Forwarded Events will prefix the syslog header even if the RFC5424 syslog header is present which routes them to the incorrect log source on the destination system.

  • Configuration and Data Backups can fail after upgrading to JSA 7.5.0 Update Package 15 Interim Fix 01.

  • JSA-30521: Backup and Restore | POST API | Backup API to take config backup fails with 500 Internal server error.

  • Report PDF generation fails with `fo:static-content is not a valid child of fo:table-body` when report data spans multiple page sequences.

  • Offense Summary charts display counts from all domains instead of filtering by user's security profile domain.

  • Report generation fails when payload contains special characters.

  • While deleting/modifying a Custom Event Property the Dependency check sometimes fails displaying the message "Error occurred while searching for dependents.".

  • Dependency Check Inconsistent When Disabling a CEP.

  • Event Export link in EMail points to the IP Address and not the FQDN of the JSA Console sometimes leading to broken links.

  • JSA: jsch jar removed from ecs-ec-ingress packaging in JSA 7.5.0 Update Package 14 Interim Fix 02.

  • TCPSyslog: Blank Payload Events Visible When Empty Syslog Messages Are Received via UDP.

  • XML root element disappears from DSM Editor Workspace when using XML Expression with path "/", preventing accurate field extraction setup.

  • Unable to update existing event regex properties using the API when the properties were originally created using an API token.

  • Support for 0.0.0.0 and 255.255.255.255 IP addresses were removed following IPv6-related core changes, causing incorrect source IP handling in log activity.

  • After upgrade to JSA 7.5.0 Update Package 12, reports are queued and no report is executed with exception java.lang.NoClassDefFoundError: javax.xml.ws.Service.

  • DSM Editor crashes and becomes unstable when opened for Custom Log Source types due to bad regex parsing.

  • When a rule is configured with an offense action or response and the offense is indexed on a custom property, but the triggering event has a null value for that custom property, the rule is incorrectly tagged as a partial match.

  • Inconsistent offense-event association causes inaccurate event counts on the offense summary page.

  • JSA: CIDR Reference Sets used in rules and filters are not functioning correctly.

  • Reference Map of Maps filter does not match or exclude events in rules.

  • Issue where a monitor closes inactive protocol connections while the connection is being attempted can lead to event ingestion stopping.

  • Rules page is taking too long to load rules list and search bar.

  • Changes in System Settings can be made using the mouse scroll wheel.

  • A syslog header created during offline forwarding will have the value of the source IP instead of the value of the log source identifier.

  • AQL properties do not parse and report 'N/A' in Log Activity.

  • Parsing disruption due to StackOverflowError from regular expression matching.

  • Order by column reset after navigating to page to of result set.

  • The removal dependency check does not look for "when the event matches this AQL filter query" when it is used by a custom rule.

  • Unable to edit searches or add filters due to invalid characters in autodetected properties.

  • Dependency checker can incorrectly delete one or more custom properties when dependency exists.

  • Hitting a max memory limit for imq service causing searches and deploy issues.