Twin Cities Security User Group

 View Only

Metrics using data from SEPM 

Aug 20, 2009 11:50 AM

Do you provide reports to management on the current threat level for your organization? Or are you simply interested in figuring out the ‘trouble’ areas of your organization (from an endpoint protection stance)?   If so, continue reading this article is for you!
 
This article is going to provide you with the following:
 
Hard data on where and who your risky users are
Data that a good management team can sink their teeth into
Show your management team your knowledge regarding your endpoint protection stance
Allow you to track your security statistics across your entire SEPM infrastructure
Help you find gaps in your protection of endpoints
Find weak areas of your security awareness training program.
 
Sound good? I sure hope so. I have used this information to put myself directly in front of our senior leadership team as the expert (in our organization) on our stance to internet based threats, malware protection controls, and all around good guy…. Well that last part might be in my head, but I hope they see it that way. 
 
Things you will need (and I’ll assume you have some familiarity with)
Access to your SEPM Console as an administrator
Ability to see the Monitor/Logs in SEPM (without restrictions)
Excel (or similar spreadsheet application)
 
Let’s get started.
 
Exporting the necessary logs
With your SEPM console open click on the Monitors item in the left window pane.
Click on the Logs tab in the main window.
Choose the Log Type Risk
Choose the Time Range: Specify the date/time for your metric program
Click the Advanced Settings option
Click Save Filter
Name the Filter: Monthly Risk Report Metrics
Click OK after the window pops up stating the filter was saved.
Now that the saved filter is “Monthly Risk Re….” click View Log
Once your log opens, it should look similar to below.
 
imagebrowser image
 
Now click the Export link.

imagebrowser image
A typical Microsoft windows box opens to save the file. Normally I will save the file in the format 0709_Risk_Report.txt for historical purposes.  (Although I used an since our deployment of SEP to have some extra large numbers for show)
 
imagebrowser image
 
Copy the file to your local workstation (unless it’s already there of course).
 
 
Importing logs into excel
 
Open excel
Click Data, Import External Data, Import External Data
Navigate to the location of the text file exported from SEPM
Click Open
Choose Delimited, then Next
Select Comma
Click Finish
Your view should now look similar to the below (minus the blanked sections)
 
imagebrowser image
 
 Manipulating the Data
 
Results in this section may vary depending upon your SEPM configuration. I did not test for every type of scenario. This is a single site with multiple groups, and no AD integration.
 
First thing we need to do is to Open the data in a PivotTable. 
Click Data, PivotTable and PivotChart Report
Here’s where the rubber meets the road. I would suggest playing with the pivot table to get an idea on how well it can help you break down the data. 
 
On the sample data I am using I have a total of 8,298 infections during the past month. Show that number alone to management and it could get ugly. Why isn’t the antivirus software stopping viruses, how could over 8,000 infections be detected, that would be one per machine? We need to replace our Antivirus product posthaste. However, when we begin digging into the data we’ll see it really is not as alarming.
 
Your blank pivot table should look similar to the below image. 

imagebrowser image

Note the headings. This is what I will refer to when dropping items from our Field list. If you are familiar with Pivot tables you can probably skip this section
 
  • Drop Page Fields Here
  • Drop Row Fields Here
  • Drop Column Fields Here
  • Drop Data Items Here
 
For management I typically pull the following information (broken down into each of the respective AD domains that our users log into)
 
  • Number of Infected Computers
    • Enterprise
    • Remote Staff
    • Asia
    • Contractors
    • Administrators
    • System
  • Number of Infected Users
    • Enterprise
    • Remote Staff
    • Asia
    • Contractors
    • Administrators
    • System
  • Number of Infected Files
    • Enterprise
    • Remote Staff
    • Asia
    • Contractors
    • Administrators
    • System
 
There are other views which I pull from for my own reporting/analysis but more on those for another article (or update to this article).
 
The primary fields we will work with from the Field List are:
 
Computer name -Drop Column Fields Here
Occurrences - Drop Data Items Here
Username – Drop Row Fields Here
Client Group - Drop Page Fields Here
 
The PivotTable should now resemble the image below. It starts to get difficult showing images now because I need to block out so much data from our sample set. Hopefully my explanations will suffice.
 
Now under my organization’s usernames each domain begins with a unique character making it easy for me to massage the data. Here’s the (made up) key that I have for my information.
 
Username begins with
Domain user belongs to
E
Enterprise
RS
Remote Staff
A
Asia
M
Contractors (on-shore)
V
Contractors (off-shore)
Z
Domain Administrators
 
Now I click on the drop down for the Username option. Uncheck Show All. Select the usernames that begin with E. Now we have all the Enterprise domain users (and their associated computers which reported an infection). Use Excel to count the number of computers and usernames. You now have an accurate count of the impact to one of the domains.   In my sample data there were 32 computers and 32 users infected during the month (we have a one-to-one relationship with user to computer).
 
imagebrowser image
 
Now rinse and repeat for each of the users and we get an accurate account of the actual number of users infected with malware. I use this data to target stronger endpoint protection policies, lucky receipts of updated security awareness training material, and to demonstrate to management ‘who’ practices insecure activities on company resources. Specifically one of our major areas of infection was our Remote Staff. This domain normally had 3:1 infections when compared to our Enterprise staff. What we found by looking at the infected file location was these Remote staff users abused policies and used work laptops for personal web surfing. We implemented a remote filtering agent that controls access to specific categories of websites. Since the implementation of that the actual number of infections for our Remote Staff has dropped to a 1:1 ratio with our Enterprise users.
 
There is a great deal of information stored in the SEPM databases. I am working on a couple of downloads that will automate more of the other metric information I use however I still need to perform my normal work duties. J Play with the data exported from SEPM Logs. 
 
Another hint on a metric I use. Clear your pivot table. Put the following into the Pivot table
 
Risk Name in the Drop Row Fields Here
Occurrences in the Drop Page Fields Here
 
imagebrowser image
 
This is a quick and dirty way to get a report on the malware infecting your systems on a monthly basis. I normally save this report for comparing with previous months. You can also take and group the malware into items like:

 
Adware -- begins with Adware.
Heuristics Detected – begins with Bloodhound
Downloaders – begins with downloader
InfoStealers – begins with infostealer
Packed – begins with packed
Suspicious – begins with suspicious
Tracking Cookies
Trojans – begins with trojans
Virus – begins with anything that I missed previously.
 

Statistics
0 Favorited
12 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Oct 09, 2013 02:33 AM

supab article!! vote upyes..

Apr 06, 2011 01:31 PM

Nice article

Feb 04, 2011 07:29 AM

Hello,

Amazing... Great Explaination...

Perfect..very helpful...

A Must read for every Security administrator dealing with Reports and Threats.

 

Dec 23, 2010 03:31 PM

Hi Andy.

Could you go into more details on what metrics you use for §3 and §3.1

  • How do you determine what is active on the network?
  • Do you consider only workstations with SEP installed as protected or any other AV as well?
  • Do use time or signature revisions for out of date reports?
  • Do you consider last contact time or AV signatures out of date?
  • What about Network/Proactive Threat Protection definitions? Is that included in any report?

Thanks.

Sep 08, 2009 02:48 PM

A little later than I planned but moving took more of my time this weekend than planned.  Here is part three to my metrics article.  I just submitted so it should be published (approval by moderators) within the next couple of hours/days.

https://www-secure.symantec.com/connect/articles/metrics-using-data-sepm-part-three

Sep 07, 2009 07:45 AM

Helpful Article.

Aug 29, 2009 04:20 AM

awesome, is the only word that I can think of right now :)

Aug 29, 2009 12:49 AM

Part 2 of the Metrics article has been published... specifically addressing Andy's question on mining the data for "where" the threats came from.

https://www-secure.symantec.com/connect/articles/metrics-using-data-sepm-part2

I am planning on releasing Part 3 later this weekend (hopefully).

Aug 29, 2009 12:33 AM

@Andy. 

I am glad to see how you are breaking down the metrics.  Gives me some ideas on improving my own metrics. 

As for the correlation... I couldn't agree more!  I have found one way to incorporate that into my my reports but it takes a couple of steps.  I am thinking about putting together a 'part 2' on the metrics article and will include the details there.

Cheers!

Jeff

Aug 26, 2009 05:52 AM

Good Article.

Infact I have been doing the simliar for the past 1 year.

I reports on the following metrics to the management:

1. No of Computers detecting Viruses - Breakdown by Region
2. No of Viruses detected - Breakdown by Region
3. No of Computers with Anti-Virus agents (Active on the network)
3.1 No of Computers with out-dated Virus Protection 

Its ashamed that SEP does not have the correlation capabilitiy to determine whether the source of virus, based on the location of the virus file. e.g Did it comes from the Internet, Shared Drive or Email or USB/CD-Rom? It will be so nice to have this metric.


Aug 21, 2009 11:02 AM

Thank you for putting this up!  Looks like a pretty easy way to mine tasty morsels of virus info.

Aug 21, 2009 04:47 AM

 This is basically what I have been doing but it is nice to have this article as reference.

Thanks!

Aug 21, 2009 12:25 AM

Yes Very good article.

Aug 20, 2009 02:27 PM

I think many of you will appreciate this article from Jeff.  Let us know what you think!

Eric

Related Entries and Links

No Related Resource entered.