Act on jQuery scan results with the Upgrade Readiness App
After you scan your Splunk platform instance with the Upgrade Readiness App, you can review and act on the results to remove dependencies on lower versions of jQuery from your deployment.
Review and act on the scan results for all your public apps. Public apps are apps that are available on Splunkbase.
The Upgrade Readiness App scan results include Splunk-supported apps and third-party apps supported by partners and developers. App owners are responsible for updating their apps and releasing new versions after removing jQuery vulnerabilities.
If you've extended an app or customized anything locally, review the results for any custom file paths that you've added to that app and take action on those to prepare for the upgrade. Otherwise, you can wait for the app owner to make updates.
For third-party apps, you can contact the developer directly using their contact details on Splunkbase to learn more about their upgrade plans. If the developer does not plan to update the app, you can make the updates yourself using the guidance in the private scan checks.
If you have a version of a public app that is failing, but a compatible version is available on Splunkbase, then the scan results direct you to download that version from Splunkbase to pass the check.
The Public App status fails and displays a warning icon for any public app that does not have a version available in the splunkbase.csv list. This list is shipped with the app and updates at 7 minutes past every eight hour in a sync to SplunkbaseIn the event that a connection to Splunkbase fails, the most recent or the shipped CSV report is used in respective order as a failsafe.
To identify what is causing your public app to fail, you can export the results of the scan to download a JSON scan report.
Review and act on the scan results for all your private apps. Private apps are apps that are private to your organization and are not available on Splunkbase.
Resolve blocking issues in your private apps and your customized Splunkbase apps, if any. Check all other file paths flagged by the app and determine what actions to take to make them upgrade-ready.
If one or more checks in an app is marked SKIPPED, this means that the Upgrade Readiness App wasn't able to complete the check due to the way the app is packaged. You can repackage the app using the Splunk Packaging Toolkit and run the scan again, or check for the upgrade compatibility issues manually. For more information, see Package apps for Splunk Cloud Platform or Splunk Enterprise using the Splunk Packaging Toolkit on the Splunk Developer Portal.
Apps that have no jQuery vulnerabilities are marked as PASSED. After the app is marked PASSED, test the app thoroughly to determine whether you need to take any further action.
Public and private apps
Review and act on the scan results with methods that apply to both public and private apps.
Dismiss file paths
The Upgrade Readiness App lets you dismiss individual file paths from the scan results. Dismiss file paths after you verify that they have no jQuery vulnerabilities to narrow down the list to files that still require attention.
When you dismiss a file path, you'll be able to see such files in a separate table, and they won't be accounted as a failure in subsequent scans.
If you've previously dismissed a file, but it is included in a scan despite being marked as an exception, optionally use the following command to remove the file directly from the dismiss lookup:
curl -k -u admin:changeme -X DELETE https://localhost:8089/servicesNS/nobody/python_upgrade_readiness_app/storage/collections/data/jra_remote_dismiss_file
The Upgrade Readiness App lets you dismiss both public and private apps from the scan results. Dismiss apps after you verify that they have no jQuery vulnerabilities to narrow down the list to apps that still require attention.
When you dismiss an app, that app is marked as an exception and it won't be accounted as a failure in the subsequent scans. You'll still be able to execute scans on that app and view results.
If you've previously dismissed an app, but it is included in a scan despite being marked as an exception, optionally use the following command to remove the app directly from the dismiss lookup:
curl -k -u admin:changeme -X DELETE https://localhost:8089/servicesNS/nobody/python_upgrade_readiness_app/storage/collections/data/jra_remote_dismiss_app
Reinstating dismissed file
Take one of the following actions if you accidentally dismiss an app or file path and want to reinstate it in future scans:
- If you're using Splunk Enterprise, delete the Upgrade Readiness App from your instance and then reinstall it. This method is only available in Splunk Enterprise, not in Splunk Cloud Platform.
- Run the following command in the Search & Reporting app to recover all the file paths you have ever dismissed:
| outputlookup jra_remote_dismiss_file
- Run the following command in the Search & Reporting app to recover all the apps you have ever dismissed:
| outputlookup jra_remote_dismiss_app
Act on Python scan results with the Upgrade Readiness App
Act on Splunk Platform Compatibility scan results with the Upgrade Readiness App
This documentation applies to the following versions of Splunk Cloud Platform™: 9.0.2209 (latest FedRAMP release), 8.2.2201, 8.2.2202, 8.2.2203, 9.0.2205, 9.0.2208
Feedback submitted, thanks!