--- title: "Importing a script into an existing script" slug: "importing-a-script-into-an-existing-script" tags: ["EDR with Forensics (EDRF)", "Endpoint Security"] updated: 2026-08-26T19:31:16Z published: 2026-08-26T19:31:16Z canonical: "docs.trellix.com/importing-a-script-into-an-existing-script" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Importing a script into an existing script **To import a script into an existing data acquisition script:** 1. Select **Data Acquisition Scripts** from the **Configure** section in the main menu of the Endpoint Security (HX) Web UI. 2. Select the script into which you want to import another script on the left side of the Data Acquisition Scripts page. Details about the script appear on the right side of the page, including separate sections for each operating system supported by the script. 3. At least two **Actions** menus appear for user-defined scripts. One menu appears in the heading area and one appears for each operating system that the script supports. (The supplied Standard Investigative Details, Comprehensive Investigative Details, and Process Details scripts do not have an **Actions** menu in the heading area.) As appropriate, select **Import Windows version**, **Import macOS version**, or **Import Linux version**, in the **Actions** menu in the heading area. Make sure you select the menu option matching the operating system of the script you want to import. A browser window appears. 4. Locate and the script you want to import. 5. Select the script you want to import and click **Open** to import the script. If the Endpoint Security (HX) has problems interpreting the script or does not recognize an audit in the script, a message appears. ![HX_ScriptImportError.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-23a73708-1a1e-77ad-b6ec-e07b8a80a218.png?sv=2026-02-06&spr=https&st=2026-11-19T21%3A46%3A12Z&se=2026-11-19T22%3A46%3A12Z&sr=c&sp=r&sig=ZBiegLc6aMj1%2B3OgOhcsDETnz1ZNIePlv6OWCR1kVnM%3D) Select **Download the list of import issues** to download a text file containing a list of what was not imported. - If you have selected the wrong operating system of the script you are importing, the audits that cannot be imported are removed from the script and reported in the error text file. - Some audits in a script cannot be imported. When this happens, the audits that cannot be imported are removed from the script and reported in the error text file. See [Audits that cannot be imported](/v1/docs/audits-that-cannot-be-imported) . If the import goes well, the Data Acquisition page adjusts so only the script section associated with the imported script appears. You can identify the operating system by the icon displayed to the left of the script name: Windows (![IconWinHost.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-26b5a9ba-7467-57f0-68ee-2137a7d3e705.png?sv=2026-02-06&spr=https&st=2026-11-19T21%3A46%3A12Z&se=2026-11-19T22%3A46%3A12Z&sr=c&sp=r&sig=ZBiegLc6aMj1%2B3OgOhcsDETnz1ZNIePlv6OWCR1kVnM%3D)), OS X (![IconOSXHost.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-21791862-73d1-a85f-4a19-74dd680f7870.png?sv=2026-02-06&spr=https&st=2026-11-19T21%3A46%3A12Z&se=2026-11-19T22%3A46%3A12Z&sr=c&sp=r&sig=ZBiegLc6aMj1%2B3OgOhcsDETnz1ZNIePlv6OWCR1kVnM%3D)), or Linux (![linux.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dae4f255-9c27-002c-7754-81de107994f2.png?sv=2026-02-06&spr=https&st=2026-11-19T21%3A46%3A12Z&se=2026-11-19T22%3A46%3A12Z&sr=c&sp=r&sig=ZBiegLc6aMj1%2B3OgOhcsDETnz1ZNIePlv6OWCR1kVnM%3D)). 6. Click **Save** to save the script in Endpoint Security (HX). You can create a script with unresolved import issues.