Custom Assessment and Remediation Release 2.9.2
August 19, 2026
Import Assets from a CSV File to Run Scripts and Schedule at Scale
You can now upload a CSV file containing asset names to quickly select up to 5,000 assets when testing, running, or scheduling a script. This feature eliminates the need for manual asset selection, making it easier to target large sets of assets at once.
Key Capabilities
- Supports only CSV files up to 2 MB.
- Supports up to 5,000 assets per import.
- Automatically validates imported assets before execution.
- Allows downloading a report of assets that failed validation.
- Supports both immediate and scheduled script execution workflows.
To use this feature, go to the Scripts tab, select a script, and choose Test Script, Run Now, or Schedule Script from the Quick Actions menu. On the Select Assets page, click Import Assets from File and then click Browse to upload your CSV file.
CSV file must be in the comma-delimited format.
For the Software Packages, navigate to Scripts > Software Packages, select the package, and click Test Package or Run Now from the Quick Actions menu. On the Select Assets page, you can view the Import Assets option. Click Browse to upload the CSV file from your destination.

After the CSV file is uploaded, the system validates each asset name in the file. You can download an invalid asset CSV listing assets that failed validation. Each entry includes the asset name and a validation message explaining why the asset was excluded. The script runs only on the assets that pass validation. For more details, refer to Execute Script and Execute Package.
The CSV file must contain only unique asset names. Any duplicate asset names found in the CSV file are marked as invalid with the reason Duplicate asset. Ensure each asset name is displayed only once in the file before uploading.
Limitations
- Asset names must exist in the database to pass the validation.
- Failed asset download information is available for a limited duration after validation.
Target the Right Assets for Script Execution Using a QQL Query
You can now use the Automated Asset Selection option to search and filter assets for script execution using a QQL query. This enhancement helps you quickly target the required assets while reducing manual selection effort.
To access this feature, go to the Scripts tab, select the script, and click Run Now from the Quick Actions menu. On the Select Assets page, you can view the Automated Assets Selection option. Enter a valid QQL query in a Search field. You can preview the results to view the assets that match the query.
Example: operatingSystem.name:windows

After you enter the QQL query, you can proceed with the script execution.
For more details, refer to Execute Script and Execute Package.
Edit Technologies for Approved Control ID Remediation Scripts
You can now edit the Technologies list for approved Control ID Remediation scripts created directly in CAR or imported from the Library. This enhancement lets you update the technologies associated with an approved script without creating a duplicate script.
To edit the Technologies list, go to the Scripts tab and apply the Policy Audit Fix filter. Select an approved Control ID Remediation script, and click Edit from the Quick Actions menu. On the Script Details page, under Control Details, you can update the Technologies field as required and save your changes.
The Control CID Number field is not editable after the script is approved.
For more information, refer to Control ID Remediation Script.
Enhanced Readability and Visual Clarity
With this release, we have introduced an improved user experience across all CAR pages. You can see updates across fonts, colors, typography, and buttons, making the interface more intuitive and easier to use.
These updates create a more consistent visual experience across the application and support improved readability and navigation. The update also provides a more consistent user interface, improves text readability, and helps users identify important information more easily.
Key benefits
- Cleaner, more consistent screens
- Easier-to-read and understandable text
- Consistent text style for status and source names across the application
- Uniform text colors in tables, filters, page numbers, and tabs

