How to use Application and Device Control (ADC) to limit the spread of a threat.
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.
- In SEP 11.0, Application and Device Control functions only on 32-bit Operating Systems. ADC is not possible on 64-bit computers. In 12.1 both 32-bit and 64-bit Operating Systems are supported.
- 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
Microsoft has a freely available utility called the File Checksum Integrity Verifier.
The utility is discussed in great detail in Microsoft's KB 841290.
SlavaSoft has a utility called HashCalc that is freely available for download on the Internet at http://www.slavasoft.com/hashcalc/.
1. Download and install the HashCalc software.
2. Run the HashCalc software from the All Programs menu.
3. In the drop down menus at the top select File for Data Format.
4. In the Data field, click the "..." button.
5. Navigate to the executable file that is suspicious and click Open.
6. Make sure the check box for MD5 is checked.
7. Click the Calculate button at the bottom.
The Endpoint Protection client comes with a Sygate 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.
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.
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.
1. Log in to the SEPM.
2. Click on Policies.
3. Click on Application and Device Control.
4. Under Tasks, click on Add an Application and Device Control Policy.
5. On the top left click on Application Control.
6. Click on the Add... button.
7. Click on the Add... button on the bottom left under Rules.
8. Select Add Condition.
9. Select Launch Process Attempts.
10. Click on the Add... button on the right next to "Apply to the following processes:".
11. Click on the Options>> button at the lower right.
12. Select the Radio button for "Match the file fingerprint".
13. Copy the MD5 hash into the field for the fingerprint.
14. Check "Only match processes with the following arguments" and add an * in the box and select "Match exactly"
15. Click OK.
16. Click OK.
17. Click OK.
18. Click Yes to assign the policy.
19. Check the boxes for any group that the policy should be applied to.
20. Click OK.
An article created in Symantec's Connect Forums illustrates how to Block Software By Fingerprint.
Microsoft KB 841290