Manual AV Magic

This post is aimed at people who are looking to detect anti-virus in a none standard way or are looking to detect Microsoft Defender for Endpoint using Automate.

Firstly, this is not as simple as just importing a virus definition for Automate. Because Defender for Endpoint is essentially an extension for Windows Defender, there doesn’t appear to be a single file that exists that definitively says “This agent has Defender for Endpoint on it”.

Step 1

The first step is to generate something locally (a file) that we can then detect using standard Automate AV Definitions, based on conditions we can script for. With Defender for Endpoint I know that two things are true when it is installed.

  1. The service called “sense” AKA “Windows Defender Advanced Threat Protection Service” is enabled and started; on machines with standard Windows Defender deployed this service is disabled
  2. A registry key exists in HKLM:\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status called OnboardingState, set to 1, that exists on machines with Defender for Endpoint on.

Based on this we can schedule a script to run (say daily) on all Automate machines that does the following:

This script creates a file called DefenderForEndpointPlaceholder.txt in a folder if the machine is Defender for Endpoint. If it isn’t detected, it deletes the file. We can then create a standard virus definition based on the creation of that file. You would need to put this in an Automate Script and schedule it to run (say daily) against all the endpoint you want to detect this on.

Step 2

If you do exactly that, then you can simply run this SQL insert command to add the final step in, which is an Automate AV detection template.

If you’re hosted, save that string as a .SQL file and import it in System > General > Import > SQL File

If you’d prefer to add the Virus Scan definition yourself, go to Dashboard > Config > Configurations > Virus Scan

The values, for easy copy/paste:

Remember – to properly detect the AV as a test, you need to run an Update Config THEN a Resend System Info. Bear in mind the thick client likes to lag and tell you AV is not installed unless you perform some voodoo magic and do a Reload System Cache. I personally just check in Automate Web as a simple F5 on the agent in the browser will tell you immediately.

Troubleshooting AV Detection

Confirm the configs.gz file under LTShare\Transfer folder has a timestamp newer than your last change. Use the Resend Config command  to teach the agent about the current definitions. Use the Resend System Inventory command to perform AV detection and report the results. AV Product definitions that are detected on the agent are reported back, but only the lowest virusscanner.vscanid (Scanner ID, value in computers.virusscanner) is reported as the agent’s AV product. The Status\Antivirus Status Dataview can display the VirusScanner ID #. For an excellent article on how AV detection works in depth see Darren White’s post at https://forums.mspgeek.org/topic/4956-antivirus-tile-priority-manually-change/?tab=comments#comment-29012