--- title: "Best practice: Automating DAT file testing" slug: "best-practice-automating-dat-file-testing" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-08-27T19:32:20Z published: 2026-09-07T17:47:17Z canonical: "docs.trellix.com/best-practice-automating-dat-file-testing" --- > ## 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. # Best practice: Automating DAT file testing Use the built-in functionality of ePO - On-prem to automatically validate DAT file compatibility and content files that are downloaded from the Trellix public site. Trellix Advanced Research Center rigorously tests the content, such as DAT and engine files, before they are released on the public update servers. Because every organization is unique, you can perform your own compatibility validation to ensure the compatibility of DATs and content in your unique environment. The compatibility validation processes vary by organization. The process in this section is meant to automate much of the compatibility validation process and reduce the need for administrator intervention. > [!TIP] > Tip > > **Best practice:** To confirm that only compatible DAT files are distributed in your environment, you might chose move the content manually from the **Evaluation** branch into the **Current** branch of the repository. 1. A server task pulls DAT updates from the Trellix public site to the Evaluation branch of the Main Repository. 2. A Trellix Agent policy applies the DAT files from the Evaluation repository branch restricted to a group of systems in a Test group. 3. A Trellix Agent update client task installs the DAT on the Test group systems. 4. An on-demand scan task runs frequently on the Test group. 5. Depending on the on-demand scan output, one of these scenarios occurs: 1. If the DAT is not compatible with the test group, an **Automatic Response** email is sent to the appropriate administrators. The email tells the administrators to stop distribution of the DAT files from the **Current** repository. 2. Otherwise, after a specified time, a server task copies the files from the **Evaluation** branch to the **Current** branch of the repository. Then those files are automatically sent to the rest of the managed systems. ### DAT file validation overview **Automatic DAT file testing steps**![Automatic DAT file testing steps](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-332f1dc7-fb20-6bb9-37f4-21674d41d8d1.png?sv=2026-02-06&spr=https&st=2026-11-19T22%3A56%3A13Z&se=2026-11-19T23%3A56%3A13Z&sr=c&sp=r&sig=hr6A1GuJvG77KoXXDBeezDCxj%2FtGoh9Fa9csaS9qGiY%3D)