Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Resolved Issues

 

The following are the resolved issues addressed in the JSA 7.3.3:

  • AQL QUERIES CONTAINING ASSET FUNCTIONS CAN FAIL WHEN RUN AGAINST LARGE ASSET MODELS.

  • ADVANCED SEARCH (AQL) FAILS WHEN USING THE LABELS OF A CUSTOM EVENT PROPERTY FIELDS IN A GROUP BY.

  • AQL OUTPUT IS INCORRECT WHEN USING SOURCE ASSET NAME FILTER BASED ON PAYLOAD.

  • JSA VULNERABILITY MANAGER: API DOES NOT FACTOR RISK SCORE FOR RETURNED RESULTS.

  • BULK EDITING/ADDING/DELETING A LARGE NUMBER OF LOG SOURCES CAN GENERATE A JVM EXCEPTION IN JSA LOGGING.

  • DOCKER IPTABLES CAN GROW UNEXPECTEDLY IN SIZE WHEN APPS ARE INSTALLED/MIGRATED/REMOVED CAUSING DEPLOYS TO FAIL.

  • PERFORMING A RESTORE AND SELECTING ‘CUSTOM RULE CONFIGURATION’ ONLY DOES NOT INCLUDE REFERENCE DATA DEPENDENCIES.

  • RESTORING A CONFIGURATION BACKUP DOES NOT RESTORE CUSTOM_FUNCTION TABLES.

  • JSA RISK MANAGER: '[REPORTING THREAD - SIMEVENT/SIMARC BUNDLE1]...PROFILER DROPPED XXXX EVENTS' MESSAGES IN JSA LOGGING.

  • REPLICATION FOR ARIEL_PROPERTY_LEEF_EXPRESSION AND ARIEL_PROPERTY_CEP_EXPRESSION NOT WORKING AS EXPECTED.

  • JSA DEPLOY FUNCTIONS CAN TIMEOUT WHEN THE CERTIFICATE VALIDATOR FAILS DUE TO EMPTY CERTIFICATES BEING PRESENT.

  • DEPLOY FULL CONFIGURATION DOES NOT COMPLETE (TIME OUT) WHEN THE FILE HOSTCONTEXT.NODOWNLOAD IS PRESENT.

  • 'UNABLE TO DEPLOY CHANGES, COULD NOT RETRIEVE UNDEPLOYED CHANGE LIST -- THE REQUEST TIMED OUT.

  • JSA LOG MANAGER DOMAIN MANAGEMENT ‘ADD’ BUTTON DOES NOT WORK AS EXPECTED.

  • EVENTS CAN SOMETIMES BE DROPPED WHEN AN EVENT COLLECTOR IS USED FOR MULTIPLE TENANTS.

  • EVENT COLLECTOR IS NOT AWARE OF NETWORK NAME/RANGE AS THE TABLE IS NOT REPLICATED TO THE EVENT COLLECTOR(S).

  • FLOW PROCESSOR CAN SOMETIMES PARSE NETFLOW/JFLOW INCORRECTLY.

  • FLOW SOURCE COLUMN AND FLOW INTERFACE COLUMN CAN DISPLAY 'HOST_NAME" INSTEAD OF THE EXPECTED HOSTNAME.

  • NO FLOW SOURCE ALIAS ARE DISPLAYED IN THE JSA USER INTERFACE.

  • EVENT/FLOW FORWARDING USING ENCRYPTED OFFSITE SOURCE AND TARGET CAN NOT BE ACCOMPLISHED SUCCESSFULLY.

  • GEOGRAPHIC LOCATION IS USING IPV4 ADDRESS WHEN CONFIGURED IN RULES INSTEAD OF THE IPV6 ADDRESS.

  • GEOGRAPHIC RULE TESTS USING ‘AND NOT WHEN THE SOURCE IS LOCATED IN OTHER’ ARE NOT WORKING AS EXPECTED.

  • 'EXCEPTION NOT HANDLED. UNDEFINED BEHAVIOR' MESSAGE IN LOGGING ON JSA HIGH AVAILABILITY APPLIANCES.

  • JSA VULNERABILITY MANAGER LICENSE WARNING BANNER CAN DISPLAY WHEN IT SHOULD NOT.

  • USING THE 'UPDATE' BUTTON ON A LOG ACTIVITY SEARCH PAGE THE DAY OF A DST (TIME) CHANGE MOVES THE START/END TIME ONE HOUR.

  • 'NO JESSIONID PASSED WITH COOKIE' MESSAGES IN JSA LOGS.

  • TOMCAT OUT OF MEMORY CAN OCCUR WHEN ASSIGNING LOG SOURCES TO GROUPS IN SYSTEMS WITH VERY LARGE NUMBER OF LOG SOURCES.

  • LOGROTATE CONFIGURATION NEEDS TO BE UPDATED TO BETTER HANDLE /VAR/LOG/CRON.LOG.

  • EXCEPTIONED VULNERABILITIES REAPPEAR IN MANAGE VULNERABILITIES TAB AFTER RESCANNING.

  • ATTEMPTING TO RE-ADD A MANAGED HOST (MH) THAT ORIGINALLY FAILED TO ADD DUE TO TIMEOUT CAN LEAVE THE MH IN A STUCK STATE.

  • USERS ASSIGNED TO A DOMAIN DO NOT HAVE ACCESS TO OFFENSES WHERE THE TARGET IS FROM THE NETWORK "OTHER".

  • SOURCE IP OR DESTINATION IP FILTER IS NOT AN AVAILABLE TEST OPTION FOR 'COMMON' RULES.

  • SOME SPECIFIC ARIEL CUSTOM EVENT PROPERTIES INDEXING CAN CAUSE ARIEL INDEXING AND RULE EVALUATION DEGRADATION.

  • INCORRECT RX AND TX RING BUFFER SETTINGS CAN CAUSE PERFORMANCE ISSUES ON BOND0 OR BOND1 MANAGEMENT INTERFACES.

  • HEALTH METRIC DATA CAN BE MISSING FROM EVENT COLLECTORS DUE TO MISSING DATABASE TABLE FIELDS WITHIN REPLICATION.

  • INACTIVE REPORT CAN CAUSE A 'NULLPOINTEREXCEPTION' IN JSA LOGGING AND JSA OPERATIONS APP FAILS TO DISPLAY EPS RATE.

  • VULNERABILITY SCAN RESULT CSV FILE CAN INCORRECTLY DISPLAY IP ADDRESSES ACROSS MULTIPLE COLUMNS.

  • REFERENCE SET DATA CAN BE MISSING FROM EVENT COLLECTORS DUE TO MISSING DATABASE TABLE FIELDS WITHIN REPLICATION.

  • REPORTS WITH ONLY ONE OUTPUT COLUMN FAIL TO GENERATE IN XLS FORMAT.

  • JSA VULNERABILITY MANAGER: REPORTRUNNER OUT OF MEMORY CAN OCCUR WHEN RUNNING THE DEFAULT SCAN SUMMARY REPORT.

  • FAILED XLS TABLE REPORT WITH “MERGED REGION A1 MUST CONTAIN 2 OR MORE CELLS” MESSAGES IN JSA LOGGING.

  • REPORT DOES NOT CHART THE TOP 5 DESTINATION PORTS FOR TIME VS COUNT.

  • SHORT REPORTS CONFIGURED WITH LINE OR BAR CHARTS CAN FAIL TO GENERATE WITH AN SQL EXCEPTION WRITTEN TO JSA LOGGING.

  • REPORT Y-AXIS VALUE PLOTTED CAN BE PULLED FROM DIFFERENT COLUMN THAN WHAT WAS CONFIGURED FOR THE REPORT.

  • ROUTING RULES FOR ASSET HOSTNAME FILTERING ON SPECIFIC EVENT COLLECTOR APPLIANCES DOES NOT WORK AS EXPECTED.

  • DEVICE (+TYPE +GROUP) STOPPED SENDING EVENTS RULE TEST IS NO LONGER FIRING THE PROPER 'DEVICE STOPPED SENDING EVENTS' EVENT.

  • JSA USER CAN ACCESS CUSTOM RULE INFORMATION WHEN NOT GIVEN ACCESS TO ‘VIEW CUSTOM RULES’ AND ‘MAINTAIN CUSTOM RULES’.

  • JSA RULES PAGE CAN TAKE LONGER THAN EXPECTED TO LOAD.

  • JSA VULNERABILITY MANAGER: SCAN EXCLUSION PAGE CAN SOMETIMES HANG FOR AN EXTENDED PERIOD OF TIME WHEN ADDING MULTIPLE, LARGE IP RANGES.

  • SCAN PROFILES WHICH USE PUBLIC KEY AUTHENTICATION DO NOT WORK CORRECTLY AFTER UPGRADING TO JSA VULNERABILITY MANAGER (QVM) 7.3.2.

  • 'AN ERROR OCCURRED EXECUTING THE QVM SCAN. PLEASE TRY AGAIN LATER' WHEN RUNNING ON DEMAND SCAN.

  • PATCH SCANNING RETURNS SUGGESTION FOR AN AIX PATCH THAT DOES NOT EXIST.

  • IDENTITY EXCLUSION RULES ARE NOT LOADED WHEN THE FILTER CONTAINS A REFERENCE DATA RELATED SEARCH.

  • MANAGED HOSTS CONFIGURED USING IPV6 CANNOT PROPERLY TIME SYNC TO THE JSA CONSOLE.

  • SYSTEM NOTIFICATION 'UNABLE TO DETERMINE ASSOCIATED LOG SOURCE' CREATED FOR SOME INFORMATIONAL VULNERABILITY EVENTS.

  • ‘VIEW TOPOLOGY’ WHEN SELECTED FROM ASSET DETAILS DIALOG NEVER COMPLETES.

  • POST_INSTALL.SH SCRIPT THAT RUNS DURING THE PATCH PROCESS CAN CAUSE MULTIPLE LOGROTATE FILES TO BE CREATED.

  • JSA INSTALLATION HANGS WHEN USING COMPRESSED IPV6 ADDRESS.

  • UNABLE TO CONFIGURE BONDED MANAGEMENT INTERFACE USING QCHANGE AFTER MOVING FROM A 8028 TO 3128 APPLIANCE TYPE.

  • REQUIRED APPLIANCE REBOOT DURING JSA PATCHING CAN SOMETIMES CAUSE DATA LOSS, A SOFT CLEAN SIM, OR FILE CORRUPTION.

  • THE JSA PATCH PRETEST FAILS WHEN A BACKUP IS IN 'MISSING' STATE IN THE DATABASE.

  • JSA USER INTERFACE LOGIN MESSAGE LINE FORMATTING IS NOT WORKING AS EXPECTED.

  • JSA USER INTERFACE CAN BECOME INACCESSIBLE DUE TO AN OUT OF MEMORY OCCURING WHEN USING THE ASSET API.

  • UNABLE TO CREATE USERNAMES CONTAINING WHITESPACE CHARACTERS AND AN INCORRECT WARNING MESSAGE IS DISPLAYED WHEN ATTEMPTED.

  • VULNERABILITY HISTORY LIST DATE ORDERING IS INCORRECT.