Hunting USB Devices with Azure Sentinel – Part 2

March 23, 2020 Craig Fretwell

In Part 1 of my previous blog post, I demonstrated how to enable USB Logging to Collect the Data from a USB Device that has been inserted into a demo machine.

I will now run through the same process, but using a malicious USB device which, when plugged in, executes a PowerShell script to download a file onto my machine.

  • Let’s first check if any current suspicious PowerShell scripts have recently been found. Checking this can be done in the “Logs” section of Sentinel.
  • Paste the query below in, hopefully nothing should display …yet.
    SecurityAlert
    | where ProviderName == "Detection"
    | where DisplayName == "Suspicious Powershell Activity Detected"
    | order by TimeGenerated desc
    1
  • Now let’s plug in my device and we can see what happens.
  • If we run our previous query in Part 1, we should see our USB Device pop up.
1
2
3
Event
| where EventID in (2003, 2004, 2006, 2010, 2100, 2101, 2105, 2106)
| order by TimeGenerated desc

2

  • So my device was registered in LA at 09:12:12:00
  • Now let’s re-run our Security query to check for PowerShell activity.
1
2
3
4
SecurityAlert
| where ProviderName == "Detection"
| where DisplayName == "Suspicious Powershell Activity Detected"
| order by TimeGenerated desc 

So you can see below that Sentinel has detected suspicious activity after the USB insertion.

3

If we drill down further, you can see there was some malicious code executed.

4

On further investigation, you can see that a payload was injected as soon as the USB was plugged in. The payload ran a malicious PowerShell script which, after further investigation, found that it downloaded a file and copied this file to my computer.

The one-liner is actually launching Command Prompt, which then opens PowerShell to bypass UAC and download a file to the C:\temp drive.

5

If we have a look at the extended properties, it gives us a more clear visual representation.

6

Now let’s take a look at the file it’s downloaded.

7

8

How crazy is that!

A USB got plugged in at 09:12, launched a malicious CMD which spawned a PowerShell session which downloaded a file to my machine all within a few seconds.

Going forward, I need to be notified by email as soon as this happens, so let’s create a basic Playbook (Logic App) which will email me as soon as this alert is triggered and because I love automation, this part was really cool.

  • Hop over to Sentinel and click “Playbooks” then Add playbook, fill in the required information and click Create
  • Once your playbook is created we need to select “Blank Logic App”
  • Search “Sentinel” within the connections and triggers bar.

9

At the time of writing this there is only 1 Trigger for Sentinel.

10

  • Make your connection to Sentinel.

11

  • Next click “+ New Step” and search for YOUR email action, for me, I’ll be using Outlook.com
  • Fill in the Body, Subject and To section with which ever information you’d like to be emailed once an alert is triggered.

I’ve done some basic formatting inside the body of the email, so my email alert makes sense and is laid out nicely.

12

  • Click Save, we can now attach our playbook to the security query. For us to be notified of this, we need to create a Scheduled Analytic Query Rule.
  • Click “Analytics” and “Create – Scheduled query Rule”

13

  • Click “next” to create the Rule Logic and paste in the above query.

14

Here I’ve defined that I want to be alerted on any detections that contain “Suspicious PowerShell Activity Detected”. You can set your own frequency depending on your requirements. As with Log Analytics, the lowest frequency is 5 minutes.

  • Run through the rest of the setup and Save.

Now I’m going to repeat the same steps as before. I’m going to plug my USB back into my demo machine which contains a malicious script to download a file onto my machine, and after 2-3 minutes I got an email.

15

Now I know this isn’t down to the second, but you have to admit that from when I plugged in the USB, the data from my computer went to Log Analytics, which created the Incident, which triggered the playbook…all within a few minutes. I am now free to respond to this through the portal, contact the user or do whatever remediation needs to be done.

Now the great thing about that playbook we made is that we can assign it to multiple analytic rules, so you can make as many playbooks as you want, incorporating different methods and assign whichever ones you wish to that alert. If you have a team of Security Analysts proactively hunting for threats, then they should be able to pick this up very quickly. Using Sentinels built-in queries are , but you may want to create your own. Collecting all your logs is great, but that’s not providing any prevention. Collection isn’t Detection.

Previous Article
What’s New in Azure: Insight From the Experts
What’s New in Azure: Insight From the Experts

We already know that running a business with the power of Azure helps to provide scalability, flexibility a...

next Asset
NS:GO Data Estate Modernization 2020
NS:GO Data Estate Modernization 2020

New Signature’s Data Estate Modernization framework is designed to help you transform your existing data pl...