New and updated

Magnet AUTOMATE Enterprise now supports AXIOM Cloud, allowing you to create workflows that acquire cloud evidence from a supported cloud platform, which you can then process with AXIOM Process. This functionality is available from the user interface and CLI. Previously, you could only create workflows with images that had already been acquired using AXIOM Cloud with a Magnet AXIOM Cyber license.
Note: Currently, AXIOM Cloud supports the Microsoft 365 and Microsoft Teams cloud platforms, allowing you to acquire one cloud evidence source (OneDrive, Outlook, SharePoint, Chats, or Channels) per workflow. For more information, refer to the Magnet AUTOMATE User Guide.
To more easily report on your cases, run summaries are automatically included as .txt files in the AUTOMATE Run Logs folder of each workflow run. For example, \\Automate\Cases\0001\AUTOMATE Run Logs\13_39_53-run-summary-1.txt. Previously, only the run log was automatically included in the AUTOMATE run logs folder.
When configuring an AXIOM Process element in a workflow, "Select platform" is now the default, prompting you to choose an appropriate platform for the evidence source. Previously, "Windows" was the default platform.
For added flexibility when customizing workflows, this release adds the following new workflow variables: ${IMAGE_FILENAME} and ${FINAL_OUTPUT_PATH}. For example, you could use the ${IMAGE_FILENAME} variable to dynamically copy image files for backup purposes. You could also use the ${FINAL_OUTPUT_PATH} variable to manage final case output to align with your organization's procedures.
When configuring a GrayKey hardware imager workflow, you can now choose "Use detected platform" as the Platform in an AXIOM Process element. With this change, the platform is now saved to the evidence metadata and passed to the workflow run as a ${PLATFORM} variable.
Improved efficiency and accuracy of UFD and UFDX image size calculation during case creation.
When you log in to Magnet AUTOMATE, the Cases page now displays by default, ensuring that you immediately see the status of your cases.
Updated the Jenkins libraries from 2.375.2 to 2.401.3.
The AUTOMATE User Guide and AUTOMATE Feature and Technical Overview Guide are now available in dark mode! Use dark mode to reduce eye strain when reading the documentation. To view dark mode, click Theme in either of the guides.
Note: To access all Magnet AUTOMATE product documentation, you must sign in to the Support Portal.
This release introduces the Magnet AUTOMATE Quick Start Guide, available from the Support Portal. This guide is intended for new users and provides basic steps for setting up Magnet AUTOMATE (installing and configuring the controller and a single node on the same computer), creating a simple workflow and case, and monitoring the status of the case.

Bug fixes

When creating a case for a GrayKey hardware imager workflow, selecting the evidence source did not automatically select the associated image, incorrectly allowing you to create the case, resulting in a failed workflow run. (AU-373)
When upgrading from AUTOMATE 3.12 to a later version, draft workflows containing the AXIOM Exporter application with no configured export format type caused the migration to fail. (AU-868)

Known issues

When setting up a GrayKey hardware imager, the Hostname field does not accept a valid hostname, preventing you from clicking Connect. As a workaround, enter a valid IP address instead. -AU-908
When cloning a workflow, any information you initially add or change in the Create workflow step is not saved (name, keyword list, password list, etc.). As a workaround, after you initially save a cloned workflow, edit the workflow and save your information again. -AU-733
Long lines in log files may fail to wrap correctly, causing them to overlap with other lines. To resolve the issue, refresh the log you are viewing. -AU-699
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 run log records a "Creating hash catalog" status. If files fail to copy after creating file hashes, there is no status in the 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 Cloud, AXIOM Process, AXIOM Exporter, AXIOM Post-Processing, and Magnet ACQUIRE.
For more information about Magnet AXIOM 7.5 updates, see the Magnet AXIOM 7.5 Release Notes.
For more information about Magnet AXIOM Cyber 7.5 updates, see the Magnet AXIOM Cyber 7.5 Release Notes.