Best practice: Automating DAT file testing Use the built-in functionality of McAfee ePO to automatically validate DAT file compatibility and content files that are downloaded from the McAfee public site. McAfee Labs 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: 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. A server task pulls DAT updates from the McAfee public site to the Evaluation branch of the Master Repository. A McAfee Agent policy applies the DAT files from the Evaluation repository branch restricted to a group of systems in a Test group. A McAfee Agent update client task installs the DAT on the Test group systems. An on-demand scan task runs frequently on the Test group. Depending on the on-demand scan output, one of these scenarios occurs: 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. 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 Pull and copy DAT updates from McAfee To create an automated DAT file testing process requires configuring tasks to pull the DATs from McAfee and copy them to the Current branch of the repository. Best practice: Create a test group of systems To safely test DAT and content files, create a test group of systems used to run the files in your Evaluation repository. Best practice: Configure an agent policy for the test group Create a McAfee Agent policy with an update task that automatically copies DAT and content files to the systems in your test group. Best practice: Configure an on-demand scan of the test group Create an on-demand scan task that starts after you update the DAT files to your test group, to scan for any problems that occur in your test group. Best practice: Schedule an on-demand scan of the test group Schedule your on-demand scan task to run five minutes after each McAfee Agent policy update from the Evaluation repository to the test group. Best practice: Configure an Automatic Response for malware detection If malware is found by the on-demand scan in the test group, you want to block the files from being copied automatically to the Current repository. Set up an automatic notification to the administrator.