How to use Application and Device Control (ADC) to limit the spread of a threat.
Symptoms There is a threat in the environment that is not being mitigated by the Antivirus functionality on the Symantec Endpoint Protection client.
The Application and Device Control feature is installed on the clients and functioning normally. A suspicious file has been identified as a threat.
There are some threats that mutate and change the files that they use to launch infections. This behavior can change the fingerprint of the file. These steps may not be completely effective against all threats.
The first step is to identify the MD5 hash of the threat. There are several ways to find this information.
Generating a fingerprint
The Endpoint Protection client comes with a utility called Checksum.exe. This utility will generate a file with MD5 hash value for a specified file.
Open a command prompt window.
Start > Run >type: cmd > hit Enter or OK.
Navigate to the directory that contains the file checksum.exe. By default, this file is located in the following location: C:\Program Files\Symantec\Symantec Endpoint Protection.
by default: cd C:\Program Files\Symantec\Symantec Endpoint Protection
Type the following command: checksum.exe outputfile inputfile
where 'outputfile' is the name of the text file that contains the checksum for specified file. The output file is a text file (i.e. outputfile.txt).
where 'inputfile' is the exact path to the file you want to generate the hash value from.
The following is an example of the syntax you use: checksum.exe C:\checksum.txt "C:\Program Files\sample.exe"
In this example the command creates a file that is called checksum.txt in the root C: folder. It would contain the checksum of the specified file sample.exe.
Microsoft has a freely available utility called the File Checksum Integrity Verifier. The utility is discussed in great detail in Microsoft's KB 841290.
Run the HashCalc software from the All Programs menu.
In the drop down menus at the top select File for Data Format.
In the Data field, click the "..." button.
Navigate to the executable file that is suspicious and click Open.
Make sure the check box for MD5 is checked.
Click the Calculate button at the bottom.
Symantec has created a utility called EsugMD5.exe, which can be provided to customers upon request.
You may submit a file to www.threatexpert.com and the generated report will contain the hash value. This report will be emailed to your chosen email address and made available on the site.
Some of the tools used to generate MD5 hashes are 32-bit applications and due to Windows file system redirection on 64-bit Operating Systems, some unexpected behavior will occur.
If an application (like notepad.exe) is present in C:\Windows\SysWOW64 and C:\Windows\System32 folders, both the files have different hash values and it is recommended to add both hash values to the policy.
Some MD5 Hash tools may provide the hash of the file from C:\Windows\SysWOW64\ though the user requests hash for the file from C:\Windows\System32\ folder.
Symantec’s Checksum.exe tool generates/provides hash value for the exact file path requested.
Hash of C:\Windows\SysWOW64\notepad.exe will be provided if requested for C:\Windows\SysWOW64\notepad.exe Hash of C:\Windows\System32\notepad.exe will be provided if requested for C:\Windows\System32\notepad.exe
We would recommend to use Symantec’s checksum tool for generating the hash values.
Configuring the Policy
Once the MD5 hash is known, the Application and Device Control policy can be configured to prevent that specific file from launching on the clients and beginning an active infection. The following steps demonstrate how to create a new Application and Device Control policy to block the specific threat and assign it to clients.
Log in to the SEPM.
Click on Policies.
Click on Application and Device Control.
Under Tasks, click on Add an Application and Device Control Policy.
On the top left click on Application Control.
Click on the Add... button.
Under Apply this rule to the following processes, click on the Add... button
Under Process name to match field, enter * (wildcard)
Click on the Add... button on the bottom left under Rules.
Select Add Condition.
Select Launch Process Attempts.
Click on the Add... button on the right next to "Apply to the following processes:".
Click on the Options>> button at the lower right.
Select the Radio button for "Match the file fingerprint".
Copy the MD5 hash into the field for the fingerprint.
Check "Only match processes with the following arguments" and add an * in the box and select "Match exactly"
Click Yes to assign the policy.
Check the boxes for any group that the policy should be applied to.