New and updated

To improve security and allow advanced troubleshooting with the AUTOMATE engine, the controller installer now generates a unique, encrypted engine key.
To automatically merge cases in watch folder workflows, the Magnet AUTOMATE REST API includes the following new method: Start a Merge Workflow Run and Assign to a Case. This method starts a new workflow run that merges existing runs and associates them with an existing case. In each method call, you can specify multiple run IDs and the workflow to merge those runs.
From an AXIOM Process element in a workflow, you can now specify parsing and carving options for the artifacts you selected. Previously, you could only specify parsing and carving options from the AXIOM Process CLI.
The Magnet AUTOMATE REST API documentation is now available from the Support Portal. Previously, the Magnet AUTOMATE REST API documentation was only available from a Magnet AUTOMATE installation.
Note: To access all Magnet AUTOMATE product documentation, you must sign in to the Support Portal.
Custom case variables defined at case creation are now available from merge workflows. This ensures that you can build output paths using the custom case variables and include the case information in workflow run summaries, aligning with your organization's policies and procedures.
When using the new -h, --FinalExportPath option with the AXIOM Exporter CLI, the exporter workflow log now includes the final export path for the export summary file.
Note: If the upgrade to Magnet AUTOMATE 3.12 fails due to a missing or incorrectly formatted export template, any associated workflows are automatically turned off and the errors are logged.

Bug fixes

When copying images to a local node before starting a workflow, image file names containing periods were split after the first period, resulting in unexpected files being copied to the local node. (AU-351)
Security - CVE-2022-31129 and CVE-2022-24785: Removed an unused vulnerable moment-2.29.1.tgz library. (AU-95)
When an application did not exist on a node, the status was reported as "canceled" in the run summary instead of "failed". (AU-246)
For some distributed workflows, cases completed successfully; however, the related copy operations failed, causing the cases to remain in progress on the dashboard. (AU-445)
When data validation was turned on for UFD and UFDX files in localized workflows, the validation failed when copying the data to the final destination. (AU-492)
When setting up a watch folder, the Evidence number variable drop-down list was cut off, preventing you from viewing all items in the list. (AU-432)

Known issues

In an image processing workflow, AXIOM Process cannot read an iOS image with a keychain encrypted by BitLocker. To successfully read and process this type of image, copy the keychain to an external drive not encrypted with BitLocker. Additionally, if the AUTOMATE agent node's workspace is encrypted with BitLocker, workflows that have been configured to "turn on local image mode" will not be able to read these images. -AXP-10310
During data validation, if the source destination contains an image with copies of the same image in subfolders, the data validation fails. In this scenario, the expected behavior is that Magnet AUTOMATE doesn't recursively catalog identical files. -AUTO-3407
When copying files during data validation, the associated node is in use; however, the Nodes column for cases in progress appears empty. The expected behavior is that the Nodes column should display the active node. -AUTO-3406
When data validation begins, the workflow run log records a "Creating hash catalog" status. If files fail to copy after creating file hashes, there is no status in the workflow run log to indicate when copying started. The expected behavior is that there should be a "Copying" status after "Creating hash catalog" to indicate the sequence of events and when they occurred. -AUTO-3408

Magnet AXIOM and Magnet AXIOM Cyber updates

Updated agent installers to include the latest version of workflow applications: AXIOM Process, AXIOM Exporter, AXIOM Post-Processing, and Magnet ACQUIRE.
Updated the AXIOM Exporter CLI to include the new -h, --FinalExportPath option, which specifies the final export path where the export summary file is copied to. In an exporter workflow, this is a required parameter that must be specified with the --Output option, ensuring that AXIOM Examine can locate the export summary file for review. At the completion of the exporter workflow, the output path and dashboard are updated with the final export path.
For more information about Magnet AXIOM 7.0 updates, see the Magnet AXIOM 7.0 Release Notes.
For more information about Magnet AXIOM Cyber 7.0 updates, see the Magnet AXIOM Cyber 7.0 Release Notes.