Release Notes

Installing the JSA 7.5.0 Update Package 12 Interim Fix 03 Software Update

JSA 7.5.0 Update Package 12 Interim Fix 03 resolves reported issues from users and administrators from previous JSA versions. This cumulative software update fixes known software issues in your JSA deployment. JSA software updates are installed by using an SFS file. The software update can update all appliances attached to the JSA Console.

The 7.5.0.20250707122114.sfs file can upgrade the following JSA version to JSA 7.5.0 Update Package 12 Interim Fix 03:

• JSA 7.5.0 Update Package 12 SFS

This document does not cover all the installation messages and requirements, such as changes to appliance memory requirements or browser requirements for JSA. For more information, see the Juniper Secure Analytics Upgrading JSA to 7.5.0.

Ensure that you take the following precautions:

• Back up your data before you begin any software upgrade. For more information about backup and recovery, see the Juniper Secure Analytics Administration Guide.
• To avoid access errors in your log file, close all open JSA webUI sessions.
• All managed hosts in the deployment must be on the same version as the console before you upgrade.
• Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed.

To install the JSA 7.5.0 Update Package 12 Interim Fix 03 software update:

1. Download the 7.5.0.20250707122114.sfs from the Juniper Customer Support website.
2. Using SSH, log into your system as the root user.
3. To verify you have enough space (10 GB) in /store/tmp for the JSA Console, type the following command:
   df -h /tmp /storetmp /store/transient | tee diskchecks.txt
4. Best directory option: /storetmp. It is available on all appliance types at all versions. In JSA 7.5.0 versions, /store/tmp is a symlink to the /storetmp partition.
5. To create the /media/updates directory, type the following command:
   mkdir -p /media/updates
6. Using SCP, copy the files to the JSA Console to the /storetmp directory or a location with 10 GB of disk space.
7. Change to the directory where you copied the patch file. For example, cd /storetmp
8. Unzip the file in the /storetmp directory using the bunzip utility:
   bunzip2 7.5.0.20250707122114.sfs.bz2
9. To mount the patch file to the /media/updates directory, type the following command:
   mount -o loop -t squashfs /storetmp/7.5.0.20250707122114.sfs /media/updates
10. To run the patch installer, type the following command:
    /media/updates/installer
11. From the patch installer menu, you can upgrade your JSA products by using Legacy Patching (Sequential) or Parallel Patching. For more information, see Upgrading JSA by using Parallel Patching.
12. During installation, users will be prompted with the following questions. You can confirm the action and continue patching. This patch introduces a kernel RPM update. Please note that if you continue with the patch and the kernel is upgraded:
    • This system is restarted automatically after patch installation is complete.
    • On all managed hosts patched from the Console, a restart occurs automatically after patch installation is complete.
    Do you wish to continue? (Y/N):
13. Ensure that all apps on your system are updated before you update QRadar. Out-of-date apps might not work after you install this update.
14. Do you want to continue, or abort the patch?
    1. Yes, my apps are up-to-date and I want to continue.
    2. No, abort the patch so I can update my apps.
15. An update for the event collection service is available.

    Currently Running Version: 2021.6.8.20240302192142

    New Available Version: 2021.6.11.20250122185136

    Applying the update requires the event collection service to restart, which could result in a gap in data collection. You can continue to use the version that you are currently running, and update to the new version later. For more information about manually updating the event collection service, see the IBM Security QRadar Administration Guide.

    Note: The option that you choose is applied to all managed hosts that are patched from this QRadar console.

    Choices:

    1. Update and restart the event collection service now.
    2. Continue using the current version of the event collection service for now. Update the event collection service during the next restart.
    3. Abort patch
16. After the patch installation is complete, reboot the system.

Installation Wrap-up

1. After the patch completes and you have exited the installer, type the following command:
   umount /media/updates
2. Clear your browser cache before logging in to the Console.
3. Delete the SFS file from all appliances.

A summary of the software update installation advises you of any managed host that were not updated. If the software update fails to update a managed host, you can copy the software update to the host and run the installation locally. After all hosts are updated, administrators can send an email to their team to inform them that they will need to clear their browser cache before logging in to the JSA.

Clearing the Cache

After you install the patch, you must clear your Java cache and your web browser cache before you log into the JSA appliance.

Before you begin

Ensure that you have only one instance of your browser open. If you have multiple versions of your browser open, the cache might fail to clear.

Ensure that the Java Runtime Environment is installed on the desktop system that you use to view the user interface. You can download Java version 1.7 from the Java website: http://java.com/.

About this task

If you use the Microsoft Windows 7 operating system, the Java icon is typically located under the Programs pane.

To clear the cache:

1. Clear your Java cache:
   1. On your desktop, select Start > Control Panel.
   2. Double-click the Java icon.
   3. In the Temporary Internet Files pane, click View.
   4. On the Java Cache Viewer window, select all Deployment Editor entries.
   5. Click the Delete icon.
   6. Click Close.
   7. Click OK.
2. Open your web browser.
3. Clear the cache of your web browser. If you use the Mozilla Firefox web browser, you must clear the cache in the Microsoft Internet Explorer and Mozilla Firefox web browsers.
4. Log in to JSA.

Known Issues and Limitations

None.

Resolved Issues

• JSA: CEP (Custom property) cache issues when a system has over 1000 properties.
• Any firewall rules set through the Custom UI will be overridden by the rules defined in the console.default file.
• Reference set "does not exist in any/all of" filters return incorrect search results.
• Header text is not visible in Offenses->Rules table for Dark theme.
• Backup failing after upgrade to UP12.